开云体育

Using which receiving endpoint ? Can you post a code snippet ? I can see differences in date format, but date is always sent Preemptive answers

I contacted IB support. This is what they had to say: //// Dear Mr. xxx, Thank you for contacting Interactive Brokers. Unfortunately the data for older EUREX contracts is no longer available, and

Hi All, I seems to be working again. Thanks for the replies. So i knew the problem wasn't in my code. Thanks for pushing the tickets to IB. Arnoud

When i requested for historical data using "yyyymmdd hh:mm:ss xxx", I got different versions of date time results. If the data is from today, the date is not shown. If the data is from a previous day,

I run it through TWS beta 10.19.0a I mean to say I set eTradeOnly = false since I'm using the C++ interface

That should do it for Python (right?). Other languages would probably have to set it to "false" or move to A?I 9.85 or above. Just out of curiosity, do you run a V10 TWS/IBGW and is that standalone

I didn't change anything between yesterday and today. I'm running 9.81 Mac/UNIX Stable release. I solved the problem by setting the field eTradeOnly = NULL.

Well, something must have changed if you suddenly get this error. Did your TWS Version change recently? Maybe from a V9 to a V10 level? The eTradeOnly field has been retired a long time ago. Just

I just got the following message while trying to place orders via the API from macOS "Code: 10268, Msg: The 'EtradeOnly' order attribute is not supported." I don't route orders to ETrade so I have no

I don't think that there is anything unclear about the "-": * The preferred format going forward is "yyyymmddd hh:mm:ss TZ" (e.g. a space separates date and time) with an explicit time zone identifier

Yes, I made minor changes in the past without issue and figured I could get away with the same treatment this time.? But as this is my first major update consider the lesson learned - and - healthy

We just had a topic on this less than two weeks ago, Orionn. I merged your new topic into the existing one to avoid further fragmentation. Ongoing discussions should take place in the original "

Well, moving from TWS API V9 to V10 is a major step with several syntax and semantic changes due to new functionality. Among them the introduction of the Decimal type, the deprecation of time strings

Jürgen, So I sent my progam with 10.18 (and Decimal) into the market today applying the conversion *decimalToDouble()* anywhere I had callback doubles in my 9.81 code to abject failure!? Orders

They haven’t just deleted the data, the contracts are no longer there at all as far as I can see. Nice one IB… Sent: 06 September 2022 20:29 To: [email protected] Subject: [TWS API] Historical

In July, IB sent out the following message to Eurex traders: 'Please note that Interactive Brokers is merging products currently listed on exchange names DTB and SOFFEX into a single exchange named

Thanks, Seems mandatory as of this morning, From experiment on syntax: "%Y%m%d %H:%M:%S UTC" Worked fine (do NOT use "GMT" which is a Time zone, not a Time standard) It seems documented that a dash

Just a heads-up that, starting with TWS 10.18, the following errors/warnings started to trigger when requesting historical data: 2174 : Warning: You submitted request with date-time attributes without

Ah, this makes sense now - I saw the decimalToDouble() method but didn't put two and two together. Thanks! T.

No worries. You will still be able to short positions with TWS API 10.18 (or any of the version 10 APIs for that matter). Version 10 TWS APIs introduce a Decimal data type for various size fields so