开云体育

Hi all, The TWS API docs say that 2 years of expired futures contracts is available for historical data. Is that true for tick data? I am wondering if I could actually get multiple years, even 2, of

The adjusted "stop" is when the trailing algorithm is activated. It is thus not a property of the trailing algorithm per se, strictly speaking. Once activated at this "stop" ("trigger" might be a

Thank you very much for your help. I changed the Start Date/Time from "US/Eastern" to "US/Central" in my function call. It works OK now. Thanks a lot!

If you specify a timezone in a historical data request, it has to be either the timezone defined in the contract details, or your local timezone. For INDU, the timezone is US/Central, not

I used the function ibClient.ClientSocket.reqHistoricalTicks(reqId, contract, "20230911 11:01:00 US/Eastern", "", 50, "Trades", 0, false, null) to obtain the historical Time & Sales data of INDU (the

Hi, I am trying to subscribe to market data using reqMktData for SPX option chain. When I subscribe to just one option contract, TWS is showing the subscription count as 2 (Alt+Ctrl+=). Any idea why

I got another reply from IBKR a couple of hours ago. They just repeated that the issue is with the developers, and stated there is no current timeline for resolution. I responded pointing out that

Aha! That certainly looks like a plausible explanation. Thanks, Jürgen! (And Franco!)

A closer look at historical TWS API source code revealed that TWS API version 161 was actually introduced more than two years ago (but less than three) n tws-api-9.85.2 and not 9.72 as I had

I suspect it is not since the GoLang API implements TWS API version 161 and we are at 178 now. Version 161 was introduced three years ago around TWS API 972. Traditionally connecting clients that use

Check if your golang implementation is compatible with the last stable version of TWS or IBGateway.

Connection: {"level":"info","ts": 1694722816.2040021,"caller":" [email protected] f1841ded5152/client.go:107"," msg":"Connect to client","host":"[hostname]. com","port":4002,"clientID":

Logs would be the best initial indication of where to start.

Hello, While I very much appreciate that you don't support golang, I wonder if you can point me in a helpful direction, because I'm unable to find any useful docs at all. I'm rather lost, so I'm

One more confirmation, my setup is one PC running 24/7, with 2 TWS windows at all time, client(s) connecting via socket either to live (API trading) or paper (for code development and testing).? This

Hello, I have been using a bracket order for stop-loss and profit-takers which has been working fine (C++). Now I want to attach a 'Trailing Stop'? when a specific price is reached. My confusion lies

Sounds like the typical HelpLess Desk answer they gave you, Richard. That is disappointing since the problem seems impact more than just API clients. We have one remote system that constantly runs a

I got a useless interim response from IBKR to my support ticket, but they say they’ve passed it to the developers, who are looking into it. I’ll keep you informed… Sent: Thursday,

Same here. I hope it's a bug - not a new feature. 14:32:11:010 <- 20-1612-540729664-DAX-FUT-20230915-0--25-EUREX--EUR-FDAX SEP 23-FDAX-0-20230911 00:00:00 MET-1 day-1 W-1-TRADES-1-0-- 14:32:11:195 ->

I have the same problem. 1 account in 1 computer TWS Live + TWS Paper, from 2 days the Paper account is receiving no market data. I have version 10.25.1 on Linux 64-bit on the AWS virtual