开云体育

Hi All, one question on volume data received from IBKR. I know that requesting data for STK, on past days with reqHistoricalData, for example the ohlcv with 1 min bar, for past days the volume is

Hi Bredan: I'm also having issues with IB Gateway crashes. Is it possible to restart it without manual intervention? Regards, Jesús

Ohhhhhhh. That makes sense. Alright, I'll have to do some coding. I'll check back in here if I get stuck. Thank you :).

You would have only one TestApp(). But you would remember the value of app_underlying.nextId() used for the subscription of each contract since future data callbacks will contain that requestId. That

Hello! I am not a programmer by trade. I started messing around with the TWS API as a side project to learn a little bit of coding. I have figured out how to get historical data, get a full option

Good point. It shouldn't trigger something about Shorting. Try setting OpenClose to "C". Are you doing this in TraderWorkstation or through the API?

I will try to lower LMT price. This is for the STP LMT to work. Original issue I'm having are orders that get an error message about not being able to short the stock. I never ask to short a stock. I

Copilot is suggesting it'll work after hours as long as you set outsideRTH to true but some exchanges restrict these. It might also work if you just lower the STP LMT price if it's the order type that

That's actually what I was analyzing just now. But isn't an STP order only good within normal trading hours? My app works outside normal hours, I think that's why I had used STP LMT.

Hi Patrick. I think the order isn't filling because the STP LMT order's LMT price is too high.? The LMT price normally will have to be lower than your STP price for this order to be triggered. Can

thank you for trying. I wanted to use the IB contract lookup tool and was surprised to see it had nothing in it. Have an excellent weekend. cp

3 STP orders should have hit here this morning:

All four contract details come up just fine for me. I simply use INDEX as the security type, the respective name as the symbol, and leave the resp undefined. Don't "overspecify" the contract for the

using the IB contract lookup tool I can enter PCUSEQTR, COR1M ,COR3M ,COR70D and they all are contracts BUT there is no information pertaining to Type,Symbol,Exchange,Currency. I can also add them

That's a good point, I will look into this. Normally the way it's set every OCA group should sell. Thats' the goal anyway...

Did the OCA group in question fail to perform as expected though? I.e. none of the orders executed when price targets were reached, and/or some OCA orders were not dropped following another's

Thanks Orion. The Order seems correct. I found one such case (AREB) which should have closed at 9:26:15 or a few seconds later. The MKT order (highlighted) was submitted at 9:23:15, should have become

In Classic TWS, if you do a mouse right-click over an API order placed by your application, then follow Modify -> Order Ticket and finally review all fields and tabs in the Order Ticket dialog do you

Does anyone have this issue? This is the case for orders submitted through the API, manually through TWS, or entered manually on the website. The paper trading API also has all kinds of weird

Changing the price so all orders have different prices doesn't change anything. Here is an example of this morning where 3 OCA groups on 3 have the same issue. Bought 3 stocks, trying to sell 1 stock