Interactive Brokers advises API users to upgrade to Version 36 or higher
Electronic trading major Interactive Brokers has issued a notice to API users, advising them to upgrade to Version 36 or higher.
Ongoing updates to the API require clients that are using a version below 36 to upgrade to avoid unsupported attributes.
One example is the Outside RTH feature. The paradigm that once included two attributes – rthOnly and triggerOutsideRth – is obsolete and may cause issues. This feature is now supported via a single OutsideRTH attribute and requires an API version of 36 or higher.
Interactive Brokers regularly updates its API. The latest version of the TWS platform featured enhancements for Time Zone Entry for BasketTrader File Import and TWS API.
In the last release the broker modified the time zone functionality so that all product-related actions in TWS, including orders and algos with start/end time, will now use the time zone of the instrument’s exchange instead of the user’s time zone.
Now users who import a BasketTrader .csv file and/or use the TWS API can send the date/time in several different formats:
Using the Login time zone: This must be an exact match to the Time Zone declaration in the login box (the part following the (UTC-5:00) portion) with any spaces being replaced with an underscore. For example:
- America/Nome
- America/New_York
- Using the exchange time zone, for example AAPL 20220614 15:00:00 US/Eastern
- Using the UTC format, for example format 20220614-15:00:00
- No time zone: If no time zone is entered, the value will default to the Login time zone.
The time zone value will be show in the exchange TZ fields.