开云体育

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

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

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

You probably might want to reread at least the Order Management ( https://interactivebrokers.github.io/tws-api/order_management.html ) section of the TWS API Reference Guide (

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:

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

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 EWrapper::mktDepthExchanges (

I don't see any reason to handle that from that place. From an individual account generally you find access to data package in the web page once you login account->Settings->MarketData

Thanks for the help everyone, unfortunately when I tried it the changes didn't work, but the problem seems to have resolved itself mysteriously... the only major change I've done is upgrade my EC2

Good evening all (and Happy holidays!) I recently upgraded to IB Gateway 10.19 there's a message that says 'Click here to subscribe to API-specific market data packages', however when I click on it

Thank you Dave, very useful reply.

A reqId and an orderId are two quite different beasts and behave differently. reqIds are sent once to the API, and only ever once. They are used for 'requests' for data rather than for orders - i.e.

Hi Tom, Thanks for that reply... I am making an assumption from your reply that this is the first of a list of changes that is likely to affect other currencies as well... would that be correct?....

Lol, you're so lazy apparently that it's not enough someone tell you so... but you actually need to have each and every detail of just how lazy you're being spelt out. Glad you got the answer you were

OUTSTANDING thank you so much Jürgen. The error callbacks you have encountered over time is something that will save me a lot of time.? The data started flowing again this morning of it's own

The approach you describe sounds reasonable and seems to have worked for you for a while. But there are a few details that come to mind that make the process more robust and tolerant of changes by

Either am I, guess that was my point. I would post my C++ solution which works very well for my purposes but that would be inappropriate. Not to mention, at the very core, it's basically just like the

Hi, IB support mentioned they changed the variable type of AUD.USD to decimal. This is the first of a long list of changes among currency pairs. This change is permanent, so I would not expect any

Hi, I have met some troubles with the latest change in AUD.USD spot on IB. I would need to retrieve an older version of TWS to make it compatible with my third party api version. Would anyone know if

I'm not expecting anything as I can't see any other way to handle it. It's just a basic awaitio loop with tagging. Been around since the late 80's nothing particularly innovative about it. I'm just