Pusher

Channels

• channel/client_event
  Client-triggered event. The `event` name must start with `client-`, and the `channel` must be a private (`private-*`) or presence (`presence-*`) channel (encrypted/cache variants of these prefixes inc
  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
  Pusher Channels WebSocket Protocol
• pusher/connection_established
  Sent by the server immediately after a successful WebSocket handshake to hand the client its `socket_id` and the server-recommended `activity_timeout` (seconds of idle before the client should ping).
  Pusher Channels WebSocket Protocol
• pusher/error
  Sent by the server on any protocol error. The data payload contains a human-readable `message` and a numeric `code` from the documented 4000-4399 ranges (non-recoverable, reconnect-with-delay, reconne
  Pusher Channels WebSocket Protocol
• pusher/ping
  Heartbeat. The server sends `pusher:ping` if no activity is seen within the activity timeout; the client may also send `pusher:ping` to the server. The recipient must reply with `pusher:pong`.
  Pusher Channels WebSocket Protocol
• pusher/pong
  Reply to a `pusher:ping`. Sent in both directions. If the server does not receive a `pusher:pong` within the pong timeout (recommended 30s), it closes the connection with error code 4201.
  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
  Pusher Channels WebSocket Protocol
• pusher/signin_success
  Acknowledgement of a successful `pusher:signin`. The data echoes back the signed `user_data` and `auth` payload.
  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 `c
  Pusher Channels WebSocket Protocol
• pusher/subscription_error
  Server-sent failure for a subscription request, typically due to an invalid auth signature on a private, presence, encrypted, or cache channel.
  Pusher Channels WebSocket Protocol
• pusher/unsubscribe
  Client requests removal of a previous subscription. No server response is sent.
  Pusher Channels WebSocket Protocol
• pusher_internal/member_added
  Server informs subscribers of a presence channel that a new member has joined. Data contains the new member's `user_id` and optional `user_info`.
  Pusher Channels WebSocket Protocol
• pusher_internal/member_removed
  Server informs subscribers of a presence channel that a member has left. Data contains the departing member's `user_id`.
  Pusher Channels WebSocket Protocol
• pusher_internal/subscription_succeeded
  Server confirms a subscription. For public, private, encrypted, and cache channels the data payload is an empty object (cache channels may additionally replay the last cached event). For presence chan
  Pusher Channels WebSocket Protocol