开云体育

You get what you ask for based upon the useRTH parameter in your request. Jürgen

Thanks! That is close to what I'm looking for. However it seems that only the trading hours are returned but not liquid hours (market). For example, this is a sample of the returned data, whereas I'm

You should take a look at our archive. There are many detailed discussions about this topic, but here the highlights: * There is no standard which trades are included * When you request data, are you

Take a look at whatToShow "SCHEDULE" for IBApi.EClient.reqHistoricalData ( https://interactivebrokers.github.io/tws-api/classIBApi_1_1EClient.html#aad87a15294377608e59aec1d87420594 ). You will receive

Hi, I'm wondering why I'd be getting very different trade volume data from IB via TWS when compared to other data providers? Here's a sample for 1 day trade bar 'volume' data for QQQ, the first data

I have historical trading data from past years (received with reqHistoricalData) for a specific contract. I need to know the trading hours / liquid hours for this contract for each day in this

It will take a while to convert over to this new API design.?? I think its a mistake to be doing this to a mature product that essentially has no new or important trading method additions pending

My problem is TWS is showing CDT after logon, even though it's configured to EDT in the "more options" screen available at logon.? I have another Window's 11 computer that doesn't have this

Hi Jürgen, Many thanks. So, it appears we have some time but perhaps not to get third party frameworks up to date. Pranav

Yes, Pranav. All TWS API clients that want to communicate with the capabilities of API 10.35.01 (server version 201) and higher will have to be able to send and receive protobuf formatted messages.

TWS switched mostly to canonical tz-database designations some time ago. America/New_York is in EDT, together with a few other US and non-US canonical regions from Canada and the Caribbean, so a any

Hi Richard, I see from the documentation that python is supported by protocol buffers. Does this mean that third party APIs like ib_async are impacted by this change? Pranav

No, the ActiveX API is a wrapper around the C-Sharp API, and this change is internal to the C-Sharp API so it won’t look any different to the ActiveX code. Richard Sent: 03 April 2025

What about the API implementations for Excel & vba? Are those affected? Thank you (<noreply.section+dev@...>) escribió:

On this topic, I also enquired with IB about some mechanism to opt-in/opt-out protobuf, possibly via a connection option or a TWS configuration setting, but they said no. So, even though your client

Ross You’re absolutely right! I was too lenient in my earlier post, because after a cursory glance a couple of weeks back I had mistakenly thought that the EClient.useProtoBuf() function was

I see in 10.35 in the C++, there is no option to ignore this ProtoBuf.? 10.35 is version 201 (MIN_SERVER_VER_PROTOBUF), and its all coded into the source.? It does not seem there is way to avoid

I’m in the central time zone but I have my computers on EDT. When I run TWS on my new computer it displays CDT, not EDT. When I run it on any of my other computers it uses EDT. My new computer is

When use of Protocol Buffers was first suggested back in 2015, I posted some comments on IBKR's GitHub repository that were fairly critical of the idea. If you have access to the API repository, you

Would anyone like to comment on the introduction of Google Protocol Buffers in the Latest Java TWS API version 10.35 ? -- https://www.tradingsoftwarelab.com