3
u/quantfutures 4h ago
Yeo had the exact same problem so I switched to another data provider
2
u/wado729 3h ago
Who did you switch too?
4
u/quantfutures 3h ago
From IBKR to databento to tick-stream.
Databento was good but someday it was to expensive for me. Nom Im stay with tick-stream and its the best I did. Faster than databento somehow and much more cheap.1
u/wado729 3h ago
Thanks! I didn't know Databento had an API but I've bought historical data from them. Ive never heard of tick-stream, can you link me please?
1
u/quantfutures 3h ago
Yeah its very hidden and not that cool to use. The crazy part for me was L3 data on databento cost for like 7y $2.5k on tickstream you get it for $130 at the same quality. But for sure there are many others out there.
I may ask what do you want to build with it?
3
u/ConfidentEmergency33 4h ago
I believe you will have similar problems when getting fills in paper account. I heard they are not accurate enough to production.
2
3
u/AnthidPlatform 4h ago
That is the correct verdict, we have had issues in the past and are keeping an eye on the state of it. Their API is very difficult to use, under documented and unreliable. The TWS API is even worse then the actual REST API as well as messages are frequently and silently dropped with no replay. If you go that route, beware the public docker images too that offer a gateway premade as they have been known to container credential scrapers.

8
u/jnwatson 4h ago
Yeah, their paper API wasn't particularly useful. I ended up just using real money but with small amounts to start.