AsyncAPI channel · Papercups · Papercups Realtime Chat (WebSocket / Phoenix Channels)

conversation:{conversation_id}

Per-conversation channel. After `phx_join`, clients send new messages with the `shout` event and read receipts with `messages:seen`, and receive the same events broadcast from other participants (agent or customer).

Open source AsyncAPI → All Papercups channels Papercups provider profile
Provider: Papercups AsyncAPI: v2.6.0 Spec: Papercups Realtime Chat (WebSocket / Phoenix Channels) Operations: 2 Messages: 4

Channel address

conversation:{conversation_id}

Parameters

Operations

publish
sendShout
Send a message (and read receipts) into the conversation.
receiveConversationEvents
Receive broadcast messages and acknowledgements.

Messages

shout
A new chat message broadcast to a conversation channel.
Content-Type: application/json
messages:seen
Marks agent messages in the conversation as seen.
Content-Type: application/json
phx_join
Phoenix channel join request.
Content-Type: application/json
phx_reply
Phoenix acknowledgement reply (status ok/error).
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.