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

tic

Ping the session to keep `/iserver` and `/ccp` endpoints alive. Sent as `tic` (no arguments). IBKR advises pinging at least once per minute. A periodic call to the REST `/tickle` endpoint is still required for session maintenance.

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: 1 Messages: 1

Channel address

tic

Operations

publish
pingSession
Ping the session

Messages

PingSession
tic
Content-Type: text/plain

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.