Keyboard Shortcuts
Likes
Search
bunch of reqMktData requests for options
Hello, Could someone conduct the following test on this workstation and tell me if he receives the delayed market data (delayed bid price / delayed ask prices) for all the instruments. ? ? ? ? m_pClient->reqMarketDataType(4); // send delayed-frozen (4) market data type m_pClient->reqMktData(2100, ContractSamples::USOptionContract("20220121", "C", 400), "", false, false, TagValueListSPtr()); m_pClient->reqMktData(2101, ContractSamples::USOptionContract("20220121", "C", 450), "", false, false, TagValueListSPtr()); m_pClient->reqMktData(2102, ContractSamples::USOptionContract("20220121", "C", 500), "", false, false, TagValueListSPtr()); m_pClient->reqMktData(2103, ContractSamples::USOptionContract("20220121", "C", 550), "", false, false, TagValueListSPtr()); m_pClient->reqMktData(2104, ContractSamples::USOptionContract("20220121", "C", 570), "", false, false, TagValueListSPtr()); m_pClient->reqMktData(2105, ContractSamples::USOptionContract("20220121", "C", 600), "", false, false, TagValueListSPtr()); m_pClient->reqMktData(2106, ContractSamples::USOptionContract("20220121", "C", 620), "", false, false, TagValueListSPtr()); m_pClient->reqMktData(2107, ContractSamples::USOptionContract("20220121", "C", 650), "", false, false, TagValueListSPtr()); m_pClient->reqMktData(2108, ContractSamples::USOptionContract("20220121", "C", 670), "", false, false, TagValueListSPtr()); m_pClient->reqMktData(2109, ContractSamples::USOptionContract("20220121", "C", 680), "", false, false, TagValueListSPtr()); m_pClient->reqMktData(2110, ContractSamples::USOptionContract("20220121", "C", 690), "", false, false, TagValueListSPtr()); m_pClient->reqMktData(2111, ContractSamples::USOptionContract("20220121", "C", 700), "", false, false, TagValueListSPtr()); m_pClient->reqMktData(2112, ContractSamples::USOptionContract("20220121", "C", 710), "", false, false, TagValueListSPtr()); m_pClient->reqMktData(2113, ContractSamples::USOptionContract("20220121", "C", 720), "", false, false, TagValueListSPtr()); m_pClient->reqMktData(2114, ContractSamples::USOptionContract("20220121", "C", 730), "", false, false, TagValueListSPtr()); m_pClient->reqMktData(2115, ContractSamples::USOptionContract("20220121", "C", 740), "", false, false, TagValueListSPtr()); m_pClient->reqMktData(2116, ContractSamples::USOptionContract("20220121", "C", 750), "", false, false, TagValueListSPtr()); m_pClient->reqMktData(2117, ContractSamples::USOptionContract("20220121", "C", 760), "", false, false, TagValueListSPtr()); m_pClient->reqMktData(2118, ContractSamples::USOptionContract("20220121", "C", 770), "", false, false, TagValueListSPtr()); m_pClient->reqMktData(2119, ContractSamples::USOptionContract("20220121", "C", 780), "", false, false, TagValueListSPtr()); m_pClient->reqMktData(2120, ContractSamples::USOptionContract("20220121", "C", 790), "", false, false, TagValueListSPtr());
Contract ContractSamples::USOptionContract(const std::string& maturityAsString, const std::string& callorput, double strike){ Contract contract; contract.symbol = "TSLA"; contract.secType = "OPT"; contract.exchange = "SMART"; contract.currency = "USD"; contract.lastTradeDateOrContractMonth = maturityAsString; // = "20220121"; contract.strike = strike; contract.right = callorput; // "C"; contract.multiplier = "100"; return contract; ? } |
Another strange thing, If I open TWS Option chain for these TESLA options first.
And i do the API requests in a second stage, I receive delayed bid/ask prices through the API running TWS > 9.76 So I suspect this behavior is related to IB pacing algorithm (at it has been introduced after TWS 9.73 which works fine. Few months ago, IB support recognize there was a bug about it. Regards, |
Hi there,
I also have the exact same problem. Interestingly, after I tried to fetch the data via API from TWS and didn't get the prices though (I always got the message that the "requested market data is not subscribed"), the TWS seems to "lock" this strike/expiry date combination of this symbol. If I load the option chain in TWS, the combinations for which I didn't receive the data have blank lines and a link to the market data manager. This can only be fixed with a restart of the TWS. Did someone found a solution for solving this problem? Did a downgrade to 9.73 (where did you get it from?) solved the issue? Thanks a lot! Andreas |
You should try and get your client working on a "stable" 981.3 or a "latest" TWS version of at least 10.12.2, Andreas. The same applies to IBGW. I am not aware of any links where you can download older versions. And even if you'd get you hands on a 973, IBKR will refuse login attempts. The security issue that was found in December 2021 in the log4j library utilized by TWS was fixed in 981.3 and 10.12.2. Vulnerable TWS versions (such as 973) will be refused. 闯ü谤驳别苍 On Tue, Mar 8, 2022 at 11:46 AM, <hansblafoo@...> wrote:Did a downgrade to 9.73 (where did you get it from?) solved the issue? |
开云体育Just an update on this. ? I still have a 973 Windows installer (now more than three years old), and I ran that earlier today and was surprised to find that it still works. It now gives a message after login that it will be disabled on 31 March 2022. So presumably IBKR were pressured into easing the timescale for mothballing these dodgy versions. ? I absolutely agree with 闯ü谤驳别苍 that running old versions like this, even if they appear to work, is not a good idea. If by running it you convince yourself that something that worked with 973 no longer works with 981+, I'm not sure that really helps: especially if there is only a couple of weeks that you can use 973. ? If this problem with delayed options data is really causing a problem, then gather evidence and submit it to IBKR: there's nothing anyone on this group can do about it. ? Or put your hand in your pocket and subscribe to the options market data… ? ? From: [email protected] <[email protected]> On Behalf Of 闯ü谤驳别苍 Reinold via groups.io
Sent: 08 March 2022 19:01 To: [email protected] Subject: Re: [TWS API] bunch of reqMktData requests for options ? You should try and get your client working on a "stable" 981.3 or a "latest" TWS version of at least 10.12.2, Andreas. The same applies to IBGW. I am not aware of any links where you can download older versions. And even if you'd get you hands on a 973, IBKR will refuse login attempts. The security issue that was found in December 2021 in the log4j library utilized by TWS was fixed in 981.3 and 10.12.2. Vulnerable TWS versions (such as 973) will be refused. 闯ü谤驳别苍 On Tue, Mar 8, 2022 at 11:46 AM, <hansblafoo@...> wrote:
|
Hi together,
thanks for your responses! :-) I'm running the latest TWS API version and the most recent TWS version. As described, this TWS version seems to be flawed since I cannot reliably request delayed (!) market data. I would love to use this version, really, but it drives me crazy. Later, I discovered the files section of this group and under API old versions, you can find a 972.1x TWS which I've downloaded and installed. It was built on 20th February 2020 (so roundabout two years old) and I can easily log in. There is only the message, that I should update. I then started my client without changing anything (!), I didn't even change to another TWS API version. Now, it runs absolutely fine - no problems anymore, delayed market data runs in very fast and without any issue. I guess, that this should be enough of a proof that newer TWS versions seem to be buggy regarding this type. @Richard: To be honest, my plan is to subscribe realtime data later. As for now, I want to use the delayed data because I'm still developing my application (thus I don't need realtime data for now) and ironically, I also want to check how stable and realible the TWS API is before I'm going to invest any money on that. ;-) Do you know a channel or an IB mail address I can report this issue to? I only found the contact form which allows to enter 200 characters or something like that, which is not enough to describe this problem. Best regards Andreas |
开云体育Andreas ? Login to Account Management and you can submit a trouble ticket there. It's easy enough to find the mechanism once you've logged in. ? The cost of the US Equity and Options Add-On Streaming Bundle is $4.50 per month and the US Futures Value PLUS Bundle (which you also need) is $5.00 per month. ? So for a monthly sum of $9.50 you could have saved yourself a lot of hassle, not to mention the amount of time I and others have spent on this topic today. Besides which I would never expect delayed data to give me any realistic indication of how the live feeds perform: they're probably pretty good, but there's no reason to expect them to be – they're free after all! ? Go figure…? ? ? ? ? From: [email protected] <[email protected]> On Behalf Of hansblafoo via groups.io
Sent: 08 March 2022 20:23 To: [email protected] Subject: Re: [TWS API] bunch of reqMktData requests for options ? Hi together, |
Hi Richard,
I created a ticket. Let's see whether they will fix it. From a retrospective view, you're right and I could have saved me a lot of hassle. But to be fair, I couldn't be sure before whether this bug resides inside the TWS or anywhere else. Therefore, I didn't know whether this issue could be resolved by using realtime data. Additionally, I considered these actions as part of a test of the TWS API and thus, I wouldn't invest money into something that doesn't work properly. As for the time you and 闯ü谤驳别苍 have spent for supporting me, this is the biggest downside but to drag this into a positive light, you might have learned something new regarding the TWS. ;-) By the way, for my use case, delayed data should be fine so far. Regards Andreas |
Sorry for my late reply, But I've opened several tickets about it.
The IB development is investigating it.? Hope they will patch it soon. I opened my first tickets about this issue more than 2 years ago. We still use TWS 9.73 as it was the last release before the 'regression/bug' was introduced in their code. |
Do you also get the message that they will stop the support for older versions after 31st March 2022? I'm still unsure what this actually means. It could be that starting from this day, this client will not work anymore. It could also mean that they would just don't process any tickets regarding this version anymore.
So hopefully, they will fix it asap. |
Hi all, |