Interactive Brokers enhances TWS API
.Net client library targets .Net Standard 2.0 in the latest version of the API.
Online trading major Interactive Brokers keeps adding new capabilities to its API, which enables the clients of the brokerage to build their own trading applications, obtain market and chart data and view IBKR account details.
The .Net client library in the latest version of the TWS API (which requires TWS version 979 or higher) targets .Net Standard 2.0.
Also, more complete “family codes” information has been added (changes server-side).
The developers have also added setConnectionOptions() to the Python API. Now you can add the “+PACEAPI” connection option in Python, as you can with other API technologies.
Minor fixes to python and C++ client libraries have been made.
In the preceding release, the company has added support for a default value for use with the price management algo attribute.
In addition, the function reqCompletedOrders() allows all completed orders, whether filled or cancelled, to be returned.
One of the earlier releases of TWS API started providing a DDE Socket Bridge API. This feature adds the same functionality included in Interactive Brokers’ socket-based APIs to the DDE API, so DDE users now have access to many features not previously available, including daily open price, multiple account data subscriptions and more. In addition, it is backwards-compatible with earlier DDE syntax and worksheets.
Beginning in API v975, a new DDE API is offered which connects to TWS via a DDE socket bridge that uses the open source Java – DDE interoperability library JDDE. The newer API has some advantages over the legacy DDE API, such as compatibility with either 32 or 64 bit TWS.