IBKR WebAPI | Trading Web API

Websocket market data requests using the SMD topic will terminate after 10 minutes. To continue retrieving data for the instrument, a new smd request for the instrument/fields must be delivered.

important

IBKR APIs | IBKR WebAPI | Web API Reference

In addition to Crypto and Forex, Stocks now support cashQty to submit a cash value to indicate shares to purchase.

new

IBKR APIs | IBKR WebAPI | Web API Reference

The WebAPI now supports model management through a series of new /fa endpoints.

new

IBKR APIs | IBKR WebAPI | Web API Reference

The description of the various Order Status Values have been updated to precisely mirror those of other Interactive Brokers platforms.

update

IBKR APIs | IBKR WebAPI | Web API Reference

New market data fields have been added for identifying the Stock Type and Option Right of the requesting instrument.

new

IBKR APIs | IBKR WebAPI | Web API Reference

OAuth 2.0 clients must establish websockets by setting the sessionToken query parameter to the bearer token.

new

IBKR APIs | IBKR WebAPI | Web API Reference

Morningstar Ratings are no longer supported for trading via API.

warning

IBKR APIs | IBKR WebAPI | Web API Reference

The /unsubscribe and /unsubscribeall endpoints are now documented for insights into managing market data subscriptions for the API backend.

new

IBKR APIs | IBKR WebAPI | Web API Reference

The /md/regsnapshot endpoint is no longer supported for users to query a regulatory snapshot via API.

warning

IBKR APIs | IBKR WebAPI | Web API Reference

Advisors may now submit in-line allocation orders in place of modifying an allocation group in /iserver/account/allocation/group then placing orders through the jsonPayload field in an order body.

new

IBKR APIs | IBKR WebAPI | Web API Reference

The source parameter has been added for the /iserver/marketdata/history endpoint, allowing users to declare the type of historical data to retrieve through the endpoint.

new

IBKR APIs | IBKR WebAPI | Web API Reference

Fundamental Data tags, including Dividend Amount, Dividend Yield %, Ex-Date, P/E, Market Capitalization, EPS, and Beta are deprecated and no longer available via API.

warning

IBKR WebAPI | Web API Reference

The /iserver/marketdata/snapshot conids parameter is now limited to 100 conids per query with 50 maximum fields at any given time.

update

IBKR WebAPI | Trading Web API

The /hmds/history endpoint has been removed from the documentation as it is now considered deprecated. Users interested in retrieving historical data from the WebAPI should instead use the /iserver/marketdata/history endpoint.

update

IBKR WebAPI | Trading Web API

The sor websocket topic now includes the “filters” argument, which can take any one order status to filter orders by.

new

IBKR APIs | IBKR WebAPI | Web API Reference

Beginning May 1st, all requests to Place an Order, Cancel an Order, or Modify an Order for US Futures Orders must include the manualIndicator field.

The Manual Indicator field is used to determine if an order was manual entered or done through an automated tool.

This field is required in order to remain in compliance with CME Group Rule 536-B.

important

Account Management API

New ‘types’ added for /enumerations endpoint.

  • COMPLEX_ASSET_TRANSFER: Query most up to date values for brokerName. Used if submitting a ComplexAssetTransfer (Basic FOP)
  • questionnaires: Query questions associated with EDD (Enhanced Due Diligence) or AVT (Additional Verification) tasks assigned to an account.
  • quiz-questions: Obtain list of questions associated with IBKR knowledge assessment.
  • security-questions: Obtain list of questions supported for IBKR security questions.
new

Account Management API

Extend accountManagementRequests to support assignment of fee template and account closure requests.

new

IBKR API Changelog

Unique changelog pages have been created for each major section of the IBKR Campus API Documentation.

new

IBKR WebAPI | Trading Web API

Fully revamped the OAuth 1.0a documentation section to further clarify involved RFC values as well as provide additional samples of how OAuth 1.0a can be implemented.

The new OAuth 1.0a documentation structure provides direct procedural documentation for easy of implementation with exact information for each endpoint.

update