AsyncAPI channel · Pusher · 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 channels the data payload contains the current `presence` member list.

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

pusher_internal/subscription_succeeded

Operations

onSubscriptionSucceeded
Receive subscription confirmation

Messages

PusherInternalSubscriptionSucceeded
Server-sent confirmation of subscription.
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.