interactive broker and api

the mule

Junior member
Messages
38
Likes
0
hi guys
someone know if we loose time when we take an order with an API like ninjatrader or buttontrader ...
maybe it's better to use TWS (uggly but not so bad to use) and more fast?:?:
 
hi guys
someone know if we loose time when we take an order with an API like ninjatrader or buttontrader ...
maybe it's better to use TWS (uggly but not so bad to use) and more fast?:?:

so thanks everybody for your interest:mad:
 
By lose time do you mean add a delay ? The API code simply makes a TCP/IP connection to the TWS java code (usually to port 7496 on the local host), so the only delay is that for sending TCP/IP messages from/to the same machine and that for the TWS java code decoding those messages. Probably a very small fraction of a millisecond at most unless the machine is heavily loaded.
 
By lose time do you mean add a delay ? The API code simply makes a TCP/IP connection to the TWS java code (usually to port 7496 on the local host), so the only delay is that for sending TCP/IP messages from/to the same machine and that for the TWS java code decoding those messages. Probably a very small fraction of a millisecond at most unless the machine is heavily loaded.

hello gc1,
thanks for your answer:)
if i understand i will not get delay that will include slippage if i use button trader as an api with interactive brokers TWS(ideal pro)
because even if we can work with ideal pro, it's easyer to prepare strategie order on button trader (and to make adaptation if we need)
do you think that this set up is possible:
have ib+button trader to take order(graph by tick)+another software for graph like esignal?
i talk about a third one because the graph of tws are uggly.
 
execute you strategies and orders via your app in some native language via ihe API/IB and use another package for charting. We use C++. The latency is quite l ow with C++ and IB API.
 
Last edited:
Top