Initial Login Domain request authenticating the session.
Content-Type:
ItemRequest
Request to open or reissue a streaming or snapshot item.
Content-Type:
Close
Client-initiated close of a stream by its ID.
Content-Type:
Pong
Liveness pong sent by the client in response to a Ping.
Content-Type:
Post
Off-stream or on-stream post used for contribution and inserts.
Content-Type:
GenericMsgOut
Domain-defined message sent by the client.
Content-Type:
LoginRefresh
Server response to a Login request indicating session state.
Content-Type:
Refresh
Full image of an item, sent on initial open or when re-syncing.
Content-Type:
Update
Incremental update to a streaming item.
Content-Type:
Status
Stream or data state change for an item (including stream close).
Content-Type:
Ping
Liveness ping sent by the server.
Content-Type:
GenericMsgIn
Domain-defined message exchanged outside the request/refresh model.
Content-Type:
Ack
Acknowledgement of a Post message, including any NAK code.
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.