AsyncAPI channel · Pusher · Pusher Channels WebSocket Protocol

channel/event

Generic channel event delivered by the server to subscribers. Carries the application-defined `event` name, the `channel` it was triggered on, a JSON-encoded `data` payload, and, when the publish was made via a signed-in user, an optional `user_id`. Encrypted channels deliver the same envelope, but `data` contains `ciphertext` and `nonce` fields produced by libsodium secretbox.

Open source AsyncAPI → All Pusher channels Pusher provider profile
Provider: Pusher AsyncAPI: v2.6.0 Spec: Pusher Channels WebSocket Protocol Operations: 1 Messages: 2

Channel address

channel/event

Operations

onChannelEvent
Receive an application channel event

Messages

ChannelEvent
Server-delivered application event on a public, private, presence, or cache channel.
Content-Type: application/json
EncryptedChannelEvent
Server-delivered event on a `private-encrypted-*` channel; payload is libsodium secretbox-encrypted.
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.

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.