AsyncAPI channel · Mastodon
· Mastodon Streaming and Web Push API
/api/v1/streaming
Multiplexed WebSocket entry point. After connecting, the client
either passed `?stream=` (and any required `tag`/`list`) on
the upgrade request, or sends one or more JSON `subscribe` control
frames to attach to streams. The server emits framed JSON messages
identifying which stream produced each event.
Provider:MastodonAsyncAPI: v2.6.0Spec: Mastodon Streaming and Web Push APIOperations: 2Messages: 4
Channel address
/api/v1/streaming
Operations
publish
sendControlMessage
Client -> server control message (subscribe / unsubscribe).
subscribe
receiveStreamFrame
Server -> client stream event frame.
Messages
SubscribeControl
Client asks the server to start delivering events for a stream.
Content-Type: application/json
UnsubscribeControl
Client asks the server to stop delivering events for a stream.
Content-Type: application/json
WsStreamFrame
Wrapped event delivered over the multiplexed WebSocket.
Content-Type: application/json
WsErrorFrame
Server-side error reported over the WebSocket.
Content-Type: application/json
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.
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.