AsyncAPI channel · Mastodon · Mastodon Streaming and Web Push API

`webpush/{endpoint}`

Name: webpush/{endpoint}
Creator: Mastodon

Outbound Web Push delivery from Mastodon to the push service URL that the client previously registered via `POST /api/v1/push/subscription`. Mastodon POSTs an `aes128gcm` encrypted body containing a notification payload, signed with the instance's VAPID key pair (RFC 8292). Decryption requires the `p256dh` and `auth` keys the client supplied at subscription time (RFC 8291). After decryption the p

Open source AsyncAPI → All Mastodon channels Mastodon provider profile

Provider: Mastodon AsyncAPI: v2.6.0 Spec: Mastodon Streaming and Web Push API Operations: 1 Messages: 1

Channel address

webpush/{endpoint}

Parameters

endpoint — Opaque path component of the push service endpoint URL the client registered. Treated as an opaque identifier by Mastodon.

Operations

publish

deliverWebPush

Encrypted Web Push notification delivered to the registered endpoint.

Messages

WebPushNotification

Outbound RFC 8030 push message body (encrypted with aes128gcm per RFC 8291). The plaintext, after decryption with the subscription's `p256dh`/`auth` keys, is a JSON object describing the notification.

Content-Type: application/octet-stream

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 Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.