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

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

Operations

publish
sendPing
Send a heartbeat ping
onPing
Receive a heartbeat ping

Messages

PusherPing
Heartbeat ping (sent either direction).
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.