IB API Order ID question
- Thread starter bidask
- Start date
Don't assign your own orderId's. Use the nextValidId callback function tell you what it is.
Yes, manually entered orders (into TWS) have order IDs too.
Yes, manually entered orders (into TWS) have order IDs too.
is there a way to stay comfortable out of range of the orderIDs generated by manual orders?
for example, if manual orderIDs start from 1 and i know that i won't have 100 manual orders, I'll start the API orderIDs at 500 and start incrementing up from there.
the problem with nextvalid id is that it doesn't generate ids fast enough. it seems like if i request the id right before the order, the order will get sent before it retrieved the id from nextvalidid.
reqIds(1) // then the id is saved into a variable
placeOrder(...) //this order gets sent before the new id comes in
but if i just increment the orderID by 1 right before sending the order, it works fine.
orderID++;
placeOrder(...)
for example, if manual orderIDs start from 1 and i know that i won't have 100 manual orders, I'll start the API orderIDs at 500 and start incrementing up from there.
the problem with nextvalid id is that it doesn't generate ids fast enough. it seems like if i request the id right before the order, the order will get sent before it retrieved the id from nextvalidid.
reqIds(1) // then the id is saved into a variable
placeOrder(...) //this order gets sent before the new id comes in
but if i just increment the orderID by 1 right before sending the order, it works fine.
orderID++;
placeOrder(...)
I use the Java API and I have always used:
(int)(System.currentTimeMillis()%Integer.MAX_VALUE)
as the start value and the incremented by one from there..
I have been using the API before they added the nextID callback, and havent bothered to change my code to use that method.
Seems to work fine for me..
(int)(System.currentTimeMillis()%Integer.MAX_VALUE)
as the start value and the incremented by one from there..
I have been using the API before they added the nextID callback, and havent bothered to change my code to use that method.
Seems to work fine for me..
When you first connect through the API, nextValidId is called, so you remember that number and use it on the next transaction. Each time you want a new ID, just increment it.
I never enter manual transactions when using my custom app so I don't know what happens to the ID numbers then.
I never enter manual transactions when using my custom app so I don't know what happens to the ID numbers then.
IB's User's Guide says this
id - The next available order ID received from TWS upon connection. Increment all successive orders by one based on this ID.
It seems like IB wants you to just increment by1 too. I'm just worried about it conflicting with manual orders. Wish they can address this.
id - The next available order ID received from TWS upon connection. Increment all successive orders by one based on this ID.
It seems like IB wants you to just increment by1 too. I'm just worried about it conflicting with manual orders. Wish they can address this.
