开云体育

@Francois: There is no error message. Everything is returned as it should just that both change in initial margin and change in maintenance margin are returned as zero. I tested it now all week and

To get the current day's volume, a simple snapshot request via reqMktData( reqId, contract, "", true) is sufficient, and you'll receive the volume as one of the returned data fields. If you also want

Hello. What is the best way to get volume and open interest for an option contract? Regards

Yes, you'll only see the "End" called when your initial download is complete.? Subsequent updates don't have an end per se, so it's up to you to manage how you trigger off the values changing over

This is on a paper trading account, and WHATIF orders always worked fine.

Despair, I just tried now (07:29 AM UTC) markets closed, and it works fine, either for single leg or combo whatif orders. See attached screenshot, one is for single legs, one is for combo. I use

Hello guys, my client needs the following functionality for their platform: * Create a model portfolio through the API (not so important since they could create them through TWS which they can *

@Francois G: One more question. Do the whatif orders work for you also when the market is closed (like on weekends)? I'm asking because I ran the program on the weekend and yesterday before the market

The only differences to my code that I can spot directly is that I use MKT orders. Also I don't explicitly set the transmit flag (I think it is true by default). Further I already experimented with

oups! Vrai means True (in french)

The code I use, with dummy parameters: IContractOrd is IBApi.Contract ... IOrderLabo is IBApi.Order stOrderState is

Hmm Ok thanks, then there must be a bug in my code. I will debug it again :-)

Hi, I use WHATIF orders via API everyday and it always worked fine. One leg or multi-leg combos, everything OK. Try to build the same order on TWS, and see the margin impact. You should get exactly

error? the EtradeOnly is for electronic quotes? all electronic... hahah I don't have the history to say why it was raising a fatal error.? I looked back and will say that first ocurrance was on

It looks like one of the recent TWS versions must have removed support "Excluded Quotes" and must have started to send the warnings when orders set one r both fields to true. As you can see below,

This raises a very good next question. Do you guys lock in versions of TWS API, TWS, ect ect to avoid these problems in the future? Or is this just going to be the dance moving forward when they

You have to agree to license and get invited to be able to see that Github project. Browse to beta API. - Bruce

Thanks everyone! Strange richard, the link isnt working. I'm going to try patching the order.py and see what happens.

I don't think this is a bug. There was an update to the API repository called 'Desupport of ETradeOnly, FirmQuoteOnly and NbboPriceCap attribs. (#1032)' about a week ago. If you have access to

I saw the same in C++ as well. Forgot why they were popping up. I use the LATEST ibkr library. - Bruce