|
Re: bunch of reqMktData requests for options
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 |
|
Re: reqMarketData live data lagging
Nick
While IB does sometimes mess up, these types of things are almost always due to an issue with the client app.
toggle quoted message
Show quoted text
The first step is to enable the API log and look to at the data TWS actually sends. If this is indeed a problem on IB's end I'd expect the group would have exploded with activity. On 3/8/2022 2:38 PM, movais996@... wrote:
After a certain period, this gap grows to even a 10 or more minutes lag between the price received by API and the price shown on terminal! Has anyone experienced it? |
|
reqMarketData live data lagging
Hi there, relatively new to tws api. |
|
Re: bunch of reqMktData requests for options
开云体育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:
|
|
Re: 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:Did a downgrade to 9.73 (where did you get it from?) solved the issue? |
|
Re: bunch of reqMktData requests for options
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 |
|
Re: Software version upgrade, recommendations?
Hi, ? Thanks and regards |
|
Re: TWS API returns "Error: 0 200 No security definition has been found for the request" in reqMktData() for INDEX
开云体育You can't use SMART for indexes. The exchange for the ES index is GLOBEX. ? From: [email protected] <[email protected]> On Behalf Of Tareq Naushad
Sent: 08 March 2022 10:57 To: [email protected] Subject: [TWS API] TWS API returns "Error: 0 200 No security definition has been found for the request" in reqMktData() for INDEX ? Hi, |
|
TWS API returns "Error: 0 200 No security definition has been found for the request" in reqMktData() for INDEX
Hi,
I am trying to pull real-time data for some INDEX in a Python based project, I write the following code to pull the data:?? ``` contract = Contract() contract.symbol = "ES" contract.secType = "IND" contract.exchange = "SMART" contract.currency = "USD" reqMarketDataType(1) reqMktData(2, contract, "", False, False, []) ``` But it always returns?"Error:? 0? ?200? ?No security definition has been found for the request". Does anyone know what's wrong with my code? - Thanks Tareq |
|
Futures Ratio Bag
When amending my code to a non-standard combo (such as simultaneously Buying 2 futures contracts).....I receive an error message not authorized to trade?
Code that works: vix1_contract = Contract()
vix1_contract.symbol = "VIX"
vix1_contract.secType = "FUT"
vix1_contract.exchange = "CFE"
vix1_contract.currency = "USD"
vix1_contract.lastTradeDateOrContractMonth = "20220315"
vix1_contract.primaryExchange = "CFE"
?
ib.qualifyContracts(vix1_contract)
?
vix2_contract = Contract()
vix2_contract.symbol = "VIX"
vix2_contract.secType = "FUT"
vix2_contract.exchange = "CFE"
vix2_contract.currency = "USD"
vix2_contract.lastTradeDateOrContractMonth = "20220420"
vix2_contract.primaryExchange = "CFE"
?
ib.qualifyContracts(vix2_contract)
?
contract = Contract()
contract.symbol = vix1_contract.symbol
contract.secType = "BAG"
contract.currency = 'USD'
contract.exchange = 'CFE'
?
leg1 = ComboLeg()
leg1.conId = vix1_contract.conId
leg1.ratio = 1
leg1.action = "SELL"
leg1.exchange = 'CFE'
print(vix1_contract)
print(vix2_contract)
leg2 = ComboLeg()
leg2.conId = vix2_contract.conId? ? ? ?#DBK MAR 15 2019 C
leg2.ratio = 1
leg2.action = "BUY"
leg2.exchange = 'CFE'
?
contract.comboLegs = []
contract.comboLegs.append(leg1)
contract.comboLegs.append(leg2)
?
limit_price = -1.7 Code (amended) that doesn't work: ........ leg1 = ComboLeg()
leg1.conId = vix1_contract.conId
leg1.ratio = 1
leg1.action = "BUY"? ? ?#changed from SELL
leg1.exchange = 'CFE'
print(vix1_contract)
print(vix2_contract)
leg2 = ComboLeg()
leg2.conId = vix2_contract.conId? ? ? ?#DBK MAR 15 2019 C
leg2.ratio = 1
leg2.action = "BUY"
leg2.exchange = 'CFE'
?
contract.comboLegs = []
contract.comboLegs.append(leg1)
contract.comboLegs.append(leg2)
?
limit_price = 65.05
------------------------------------------------ Error Message: " Rejected by the system.? No trading permissions for the product." |
|
Undocumented updateAccountValue() keys
These keys I seem to be missing from the docs ():
NLVAndMarginInReview Guarantee Guarantee-C Guarantee-S PhysicalCertificateValue PhysicalCertificateValue-C PhysicalCertificateValue-S TotalDebitCardPendingCharges TotalDebitCardPendingCharges-C TotalDebitCardPendingCharges-S Could they be added? Cheers, .mm |
|
Re: historical market data pacing violations are back?!
I may have reported too soon. Suddenly, on Friday afternoon in the last hour of trading before the futures markets closed, I got multiple pacing violations messages on various futures contracts. Even though I was only requesting historical data sequentially, one contract at a time.
|
|
Re: next valid id on initial connection
It depends on your definition of good. The solution uses sleep for synchronization, so I would not call it a good solution. It does not address the mismatch between synchronous and asynchronous processing and only addresses one of the many API callback scenarios. On the other hand, it will probably work reliably since the loop blocks your client until the nextValidId callback has taken place (as long as the sleep does not interfere with proper API background message processing). 闯ü谤驳别苍 |
Tareq Naushad
Moritz M?ller