AsyncAPI channel · Pusher · Pusher Channels WebSocket Protocol

pusher/subscribe

Client requests a subscription to a channel. For private, presence, encrypted, and cache channels the `auth` field carries the server-issued HMAC signature; presence channels additionally require a `channel_data` JSON string containing the `user_id` and optional `user_info`.

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

Channel address

pusher/subscribe

Operations

publish
sendSubscribe
Subscribe to a channel

Messages

PusherSubscribe
Client-sent channel subscription request.
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.