AsyncAPI channel · Pusher · Pusher Channels WebSocket Protocol

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 included). The server forwards the event to other subscribers but does not echo it back to the sender. Rate limited; exceeding the limit yields a `pusher:error` with code 4301.

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

channel/client_event

Operations

publish
sendClientEvent
Trigger a client event on an authorized channel

Messages

ClientEvent
Client-published event on a private or presence channel. Event name must start with `client-`.
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.