AsyncAPI channel · Pusher · Pusher Channels WebSocket Protocol

pusher/signin

User authentication. Client sends `pusher:signin` with a server-signed `auth` token and a `user_data` JSON string containing at least an `id` field (and optionally `user_info` and a `watchlist` of up to 100 user IDs). Used to associate the connection with an authenticated user for user authentication, watchlists, and end-to-end features.

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/signin

Operations

publish
sendSignin
Authenticate the current connection as a user

Messages

PusherSignin
Client-sent user sign-in.
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.