API Support Forum
OEC API > Market Data > Empty bars on historical end request
Author Topic: Empty bars on historical end request
(3 messages, Page 1 of 1)
Moderators: VPfau
CWhite140
Posts: 9
Joined: Feb 28, 2013


Posted: Feb 06, 2014 @ 11:44 AM             Msg. 1 of 3
What is the purpose of this "empty request"? Is this because a single historical request can trigger multiple calls/event fires?

Are there any flags within the subscription type itself that tells us the historical request is complete -- say for subscriptions where we want to know when the history is complete and we are receiving real-time data?


Curtis White
Edited by CWhite140 on Feb 6, 2014 at 11:44:45
VictorV
Posts: 746
Joined: May 08, 2007


Posted: Feb 06, 2014 @ 11:49 AM             Msg. 2 of 3
Empty response is a sign of the end of historical data and the next response will be a real-time one.

Victor Vins
Lead Software Developer
CWhite140
Posts: 9
Joined: Feb 28, 2013


Posted: Feb 06, 2014 @ 12:10 PM             Msg. 3 of 3
Thanks. Yes, that's what I assumed but I thought there might be some other flag so that I didn't have to maintain the state of requests in my program.

Curtis White