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

Provider: Pusher AsyncAPI: v2.6.0 Spec: Pusher Channels WebSocket Protocol Operations: 1 Messages: 1

Channel address

pusher/connection_established

Operations

onConnectionEstablished
Receive connection-established acknowledgement

Messages

PusherConnectionEstablished
Server-sent connection acknowledgement.
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.