AsyncAPI channel · Pusher · 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.

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

Channel address

pusher/pong

Operations

publish
sendPong
Send a heartbeat pong reply
onPong
Receive a heartbeat pong reply

Messages

PusherPong
Heartbeat pong reply.
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.