AsyncAPI channel · Interactive Brokers · Interactive Brokers Client Portal API WebSocket

smd+{conId}

Streaming, top-of-book (level 1) market data for a single contract. Subscribe message is `smd+conId+{"fields":[...]}` where `conId` is the IBKR contract identifier and `fields` is an array of market data field identifiers (see `/iserver/marketdata/snapshot` for the field reference). Contracts use SMART routing by default; specify `conId@EXCHANGE` to route a specific exchange. Unsubscribe with `umd

Provider: Interactive Brokers AsyncAPI: v2.6.0 Spec: Interactive Brokers Client Portal API WebSocket Operations: 2 Messages: 2

Channel address

smd+{conId}

Parameters

Operations

publish
subscribeMarketData
Subscribe to streaming market data
onMarketData
Receive streaming market data ticks

Messages

SubscribeMarketData
Subscribe to streaming market data for a contract.
Content-Type: text/plain
MarketDataTick
Streaming top-of-book tick for the subscribed contract.
Content-Type:

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.