AsyncAPI channel · Aeternity
· Aeternity Middleware WebSocket API
/
The control channel — the same socket carries Subscribe, Unsubscribe and Ping commands and their replies.
Channel address
/
Operations
send
subscribe
Subscribe to a channel. The reply is a single-element list containing only the newly subscribed channel.
send
unsubscribe
Unsubscribe from a channel. The reply is a single-element list containing only the removed channel.
send
ping
Liveness and subscription-count check; takes no payload field. The Pong reply always carries `count` (the true total) and a fixed-size sample of up to MAX_PING_LIMIT (default 1000) subscriptions, with
Messages
SubscriptionCommand
Subscribe / Unsubscribe / Ping
Content-Type:
SubscriptionReply
Since v1.105.0 the reply is lean — a single-element list naming only the channel just added or removed. WS_SUBS_FULL_LIST_REPLY restores the pre-1.105 full-list behaviour and is slated for removal.
Content-Type:
PongReply
Pong
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.