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
Server pushes queued/live messages for the subscribed channel to the client.
subscribe
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.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.