Channel address
/
Operations
publish
publish /
subscribe
subscribe /
Messages
ErrorMessage
Error notification.
Content-Type:
SetupMessage
Allows setting up connection.
Content-Type:
AuthMessage
Allows the client to authorize.
Content-Type:
KeepaliveMessage
Allows the connection to stay alive.
Content-Type:
FeedChannelRequestMessage
Allows the client to request the feed channel.
Content-Type:
DomChannelRequestMessage
Allows the client to request the dom channel.
Content-Type:
ChannelCancelMessage
Allows the client to cancel channel requests.
Content-Type:
FeedSetupMessage
Allows the client to configure the `FEED` service.
Content-Type:
FeedSubscriptionMessage
Allows the client to manage their subscriptions in the `FEED` service.
Content-Type:
DomSetupMessage
Allows the client to configure the `DOM` service.
Content-Type:
AuthStateMessage
Notification of authorization state.
Content-Type:
ChannelOpenedMessage
Notification of the opened channel.
Content-Type:
ChannelClosedMessage
Notification of the closed channel.
Content-Type:
FeedConfigMessage
Notification of the `FEED` service configuration.
Content-Type:
FeedDataMessage
Contains the data of subscribed market events.
Content-Type:
DomConfigMessage
Notification of the `DOM` service configuration.
Content-Type:
DomSnapshotMessage
Contains the snapshot of request depth of market.
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.
Work with this as data
Every channel here is available over the APIs.io API and to AI agents over MCP.