AsyncAPI channel · WellnessLiving · WellnessLiving Real-Time Notifications (WebSocket)

wl/websocket/channel

A generic WellnessLiving real-time channel. The concrete channel is selected at subscribe-time by `cid_channel` (the channel-controller CID) plus `a_key` (the key fields that scope the channel, e.g. business/report, business/user/visit, or a messenger channel key). Known CIDs observed in the official OpenAPI schema include 735 (report generation progress), 1921 (visit status), and 1583 (messenger

Open source AsyncAPI → All WellnessLiving channels WellnessLiving provider profile
Provider: WellnessLiving AsyncAPI: v2.6.0 Spec: WellnessLiving Real-Time Notifications (WebSocket) Operations: 2 Messages: 2

Channel address

wl/websocket/channel

Operations

publish
receiveBroadcastMessage
Server pushes queued/live messages for the subscribed channel to the client.
subscribeToChannel
Client authorizes onto a channel immediately after opening the WebSocket connection.

Messages

ChannelBroadcastMessage
A queued or live event delivered to a subscribed channel.
Content-Type: application/json
SubscribeRequest
Authorizes and subscribes the current WebSocket connection to a channel.
Content-Type: application/x-www-form-urlencoded

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 Agent Skill and MCP server surfaces of the same providers.