AsyncAPI channel · Infoway Real-time Market Data API · Infoway WebSocket Streaming API

/ws

One duplex WebSocket session. Every client frame carries an integer protocol `code` and a client generated `trace` id; every server frame echoes the `trace` on acknowledgements. A heartbeat (code 10010) must be sent at least once per minute or the server treats the connection as inactive and closes it.

Open source AsyncAPI → All Infoway Real-time Market Data API channels Infoway Real-time Market Data API provider profile
Provider: Infoway Real-time Market Data API AsyncAPI: v3.0.0 Spec: Infoway WebSocket Streaming API Operations: 10 Messages: 14

Channel address

/ws

Operations

send
sendSubscribeTrade
receive
receiveTrade
send
sendSubscribeDepth
receive
receiveDepth
send
sendSubscribeCandles
receive
receiveCandles
send
sendHeartbeat
send
sendUnsubscribeTrade
send
sendUnsubscribeDepth
send
sendUnsubscribeCandles

Messages

subscribeTrade
Subscribe trades
Content-Type:
subscribeTradeAck
Content-Type:
tradePush
Trade push
Content-Type:
unsubscribeTrade
Content-Type:
subscribeDepth
Content-Type:
subscribeDepthAck
Content-Type:
depthPush
Order-book depth push
Content-Type:
unsubscribeDepth
Content-Type:
subscribeCandles
Subscribe K-line
Content-Type:
subscribeCandlesAck
Content-Type:
candlePush
K-line push
Content-Type:
unsubscribeCandles
Content-Type:
unsubscribeAck
Unsubscribe acknowledgement (all types)
Content-Type:
heartbeat
Heartbeat
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 Agent Skill and MCP server surfaces of the same providers.