开云体育

Thank you Dave, very useful reply.

Yes very useful indeed
Just a grain of salt about request ID: Some request (just a few) does use a request ID but do not send it in the call back.
like ? that deliver back mktDepthExchanges(const std::vector<DepthMktDataDescription> &depthMktDataDescriptions)? without reqID.

In never saw this as an issue because these kinds of requests are far less critical, they are either:
- part of what should be called only once on init. (and are serviced back very quickly)
- are far less critical, the only one I take some care about is reqAccountUpdates (if you use it, this is not so critical as it's serviced rather quickly)
- does return OrderId (or Order.orderId) which is enough to collate results (but still do not deliver the reqId that trigger the call);

You are correct that there are a few responses that return no reqId and I agree with your assessment that those really don't need to be called several times in parallel.

But the corresponding requests do not require reqId either. Here the request call signatures for the response example you gave:

Where I am now confused is how to modify an existing order using permID and not orderID.

I have been modifying orders within a running instance of TWS using an Order() object, eg to change a stoploss:

stopLoss = Order()
stopLoss.orderId = 99
stopLoss.action = "SELL"
stopLoss.orderType = "STP"
stopLoss.auxPrice = 100.01
stopLoss.tif = "GTC"
stopLoss.totalQuantity = 1
stopLoss.parentId = 98                  # Parent ID
stopLoss.transmit = True
stopLoss.eTradeOnly = ""
stopLoss.firmQuoteOnly = ""
self.placeOrder(99, IBContract, stoploss)

Where does permID get put in here?

And once TWS is closed, all of this information becomes redundant (eg- "parentId" because this is the stop loss in an OCA Buy order) - so how do I modify an order now? (I use python).

Thanks.

• Client 0
• Master Client - configured in the API section of TWS/IBGW global configuration.
  NOTE: Master Client can be set to "0" to make the client with id 0 a "super client" that has the "powers" of both the "Master Client" and "Client 0"
• The API configuration "Use negative numbers to bind automatic orders" and the tooltip

Clients can request the ability to control existing or future open orders that were placed by the same clientId, all other clientIds, or even via the TWS GIU. This is done by "binding" those orders (that you you currently see with an orderId of 0) to an orderId the client can use.

We find it most convenient to enable the "Use negative numbers ..." option since that nicely separates ids for orders placed by the client from "bind" orders that the client did not create but may wish to control.

Order binding works even after TWS or your client restarts. You will receive openOrder callbacks with (negative) orderIds other than 0 after your client makes one or more of the open orders requests mentioned above.

闯ü谤驳别苍

If nobody gives you exact answer, my suggestion is to learn and try.
Most likely everyone has methods of their own for placing /managing orders? and may not be exactly as you asked for it.
So your relatively on your own to master that.
And it is not a waist of time to try and experiments.

The API is pretty powerful. The price you pay is that you should do your own gradual experiments.

?

Suggestion for learning it:

#1 Become familiar with OrderID

Read carefully this one (twice)

Read it also with other language like Java or C++ aside of Python (your language). because this may help you getting a better understanding of how crude examples are :

In C++? exemple:

m_pClient->placeOrder(m_orderId++, ContractSamples::USStock(), OrderSamples::LimitOrder("SELL", stringToDecimal("1"), 50));

I read IB intent for training , using the “++” in m_orderId++ as a way to say “be sure to never reuse same ID for next order, so here we force a new one, that can be as simple as +1 of previous”

?

also C++: m_pClient->cancelOrder(m_orderId-1, "");

Same thing with “-1” to be understood as meaning: ?“here we cancel last order, could be any other, but please be sure to use a freshly brewed orderId for next 辫濒补肠别翱谤诲别谤(…).”

Java: IB exemple use a “cancelID” which I don’t know about but seems to me more an implementation method, I don't see what else it could be aside of the Orderid you use for the 辫濒补肠别翱谤诲别谤(…).

?

#2 Become familiar with the Order object
This object is a major one and is returned once you 辫濒补肠别翱谤诲别谤(…)? when call back fires up.
This bring to you the order.permId and order.orderRef

?

Oups !
Looks like Jurgen Reinold did answered you while I was writing also an answer.
Sorry Jurgen

Hi, thank you for your replies, but I am still confused on what to do next with my code after reading all the posts. I dont understand what to do.

How do I send a new placeOrder() to amend an existing order using permID?

You cannot just with permId. You will always need an orderId.

I repeat my recommendation that you study and specifically .

闯ü谤驳别苍

I think I understand now. Thanks for your reply. I didnt know that orders need to be bound first and then mapped: