AsyncAPI channel · Mastodon
· Mastodon Streaming and Web Push API
/api/v1/streaming/user
Home timeline plus notifications for the authenticated user. Requires the `read:statuses` and `read:notifications` scopes.
Channel address
/api/v1/streaming/user
Operations
subscribe
streamUser
SSE stream of home timeline and notification events.
Messages
update
A new status (post) has appeared in the subscribed timeline.
Content-Type:
application/jsondelete
A status was deleted; payload is the deleted status ID as a string.
Content-Type:
text/plainnotification
A notification (mention, follow, favourite, etc.) was created.
Content-Type:
application/jsonstatus.update
A previously-seen status has been edited.
Content-Type:
application/jsonconversation
A direct-message conversation has a new or updated last status.
Content-Type:
application/jsonfilters_changed
Notification that the user's keyword filters were modified; no payload.
Content-Type:
application/jsonannouncement
An administrator published a server-wide announcement.
Content-Type:
application/jsonannouncement.reaction
A user reacted with an emoji to a server announcement.
Content-Type:
application/jsonannouncement.delete
A server announcement was removed; payload is its ID as a string.
Content-Type:
text/plainnotifications_merged
Server signals that previously delivered notifications have been
grouped/merged. Clients that ignore grouping can ignore this.
Content-Type:
application/jsonAbout 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 Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.