AsyncAPI channel · PartyKit · PartyKit Realtime Protocol

/parties/{party}/{room}

A PartyKit room channel. The `party` segment identifies which Party class to route to (defaults to `main`), and the `room` segment is the room id. The PartyKit runtime guarantees that every connection using the same `room` id is routed to the same Durable Object instance, so a room represents a single, isolated, stateful server. Clients open a WebSocket against this path; the server invokes `onCon

Provider: PartyKit AsyncAPI: v2.6.0 Spec: PartyKit Realtime Protocol Operations: 2 Messages: 3

Channel address

/parties/{party}/{room}

Parameters

Operations

publish
clientSendMessage
Client sends a message to the party.
serverPushMessage
Server pushes a message to the client.

Messages

ClientMessage
An inbound message from a connected client.
Content-Type: application/json
ServerMessage
A targeted message sent by the party to one connection.
Content-Type: application/json
BroadcastMessage
A message fanned out by the party to all connected clients via `Room.broadcast()`. The party may pass an optional list of connection ids to exclude from delivery.
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.