开云体育

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

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

I'm upgrading my c++ API to 10.18 and I realized that with the new Decimal type, positions are represented as *unsigned long long* , where they were double before (9.81).? This would mean that short

Hi Loic, does not work on my side :-( on Aug, 30th support wrote: My suggestion: the more support tickets IB gets the higher the pressure for them to solve the issue (hopefully) -> open support

@Jürgen Reinold thanks so much for your help!

I find the following solution for myself. I hope that might help someone else. I separated the closing positions action in a dedicated "app". In this case the reqPositions() runs only once if

Re client.start(), I found this in the API docs ( https://interactivebrokers.github.io/tws-api/connection.html ) :

Hi Steve This code is simple and robust, works like a charm, GREAT, just what I was looking for. The only code I added was: def connect_to_TWS ( self ): TWS_PORT = 7497 ....... # added at

Hello, Could someone please advise how the daylight saving shift can be accounted to avoid running scripts outside of FOREX's open market hours? Will UTC help instead of GMT? Thank you.

...or in python: def is_demo(account_number: str) -> bool: return account_number.startswith('D')

No, NextValidId occurs once when you connect to the API. It tells you the first unused order ID for the current ClientID. For each new order, you have to then increment the order id in some fashion so

So it looks like what happened is the orderId got reused for some reason. ExecDetails shows orderId 14100 happening yesterday at 08:36 and today at 08:35. Is it my responsibility to ensure the orderId

You might want to re-read the TWS API Guide sections on Executions and Commissions, ( https://interactivebrokers.github.io/tws-api/executions_commissions.html ) IBApi.EWrapper.execDetails, (

Hey All, I'm curious if anyone else has experienced problems with the Execution details (execDetails) being returned from the TWS API. I'm using the C# version. Intermittently I've been getting

It seems we talked about two different columns. I was referring to IV rank/IV percentile for individual options on the chain -- the menu option for this column also disappeared in the meanwhile.

Anyone...?

I tried to upgrade to 10.17 as the server has stopped handling my requests due to the age of my current API (what the people at IB told me). They suggested moving to 10.17 which has some new

HI i tried a buy order followed by a sell order for TSLA/SPX options. THe buy order goes through in about few seconds - the order gets fulfilled and the program also gets a call back ( with

thanks alot . worked :)