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

smh+{conId}

Streaming historical market data bars for a single contract. Subscribe with `smh+conId+{...}` where the JSON arguments may include `exchange`, `period` (e.g. `1d`, `2h`, `30min`), `bar` (bar size e.g. `5min`, `1h`, `1d`), `outsideRTH` (boolean), `source` (`midpoint|trades|bid_ask|bid| ask`), and `format` (e.g. `%o/%c/%h/%l/%v`). A maximum of 5 concurrent historical data subscriptions is permitted.

Open source AsyncAPI → All Interactive Brokers channels Interactive Brokers provider profile
Provider: Interactive Brokers AsyncAPI: v2.6.0 Spec: Interactive Brokers Client Portal API WebSocket Operations: 2 Messages: 2

Channel address

smh+{conId}

Parameters

Operations

publish
subscribeHistorical
Subscribe to streaming historical bars
onHistorical
Receive historical bar data

Messages

SubscribeHistorical
smh+conId+{params}
Content-Type: text/plain
HistoricalBars
Historical bar response
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.