Account and device status
Webhook on whapi channels and session status
Channel Statuses in Whapi.Cloud
Whapi.Cloud API channels can have different statuses during their lifecycle. Here’s what each status means:
✅ AUTH (Authorized): Your channel is fully connected and operational. You can send and receive messages.
📷 QR (Waiting for QR code scan): The channel is waiting for the QR code to be scanned or pairing to be completed. Make sure to scan the code promptly — if it expires, refresh the page or restart pairing.
⏳ INIT (Initialization): Temporary state of channel initialization on the server. If the channel remains in INIT for more than 40–50 seconds, something likely went wrong. Please contact support.
😴 LAUNCH (Connecting / Inactive): The channel is attempting to establish a technical connection to the WhatsApp account. This usually takes a few seconds. If it lasts longer, it may indicate a connection issue (e.g., number is blocked or session failed). If the status doesn’t change, contact support.
⛔️ STOP (Stopped): The channel is deactivated. Possible reasons: -End of trial or subscription; -Manual deactivation; -Billing or technical issue; Check your subscription status or contact support for assistance.
⚠️ SYNC_ERROR (Synchronization issue): There is a sync failure between your WhatsApp account and the API. You can still send messages, but GET requests (e.g., to fetch chats or messages) will not work. To resolve this, log out the channel and reconnect it. Read more: Channel status “SYNC_ERROR”
Webhook to change channel status
The health object contains information about the uptime of the channel and the status of the channel. Sent on event "channels.post"
The QR code object contains the QR code image and the status of the QR code. The QR code is only valid for a limited time. Sent on event "channels.patch"
Why Does My Channel Change Status During the Day?
It’s normal for WhatsApp Web–based channels to briefly reconnect throughout the day. During this process, you may receive a sequence of webhook events such as:
INIT → LAUNCH → AUTH
This typically lasts 2–3 seconds and may occur once or several times a day, depending on device conditions and connection stability.
While the API continues to work normally, requests made during this short window may return 401 "need channel authorization" errors.
To handle this smoothly:
Use webhooks to track channel status changes;
Pause message sending while the channel is not in
AUTH;Add retry logic for API calls that fail with 401;
Connecting an account to the channel
You can also use a webhook to track the connection/disconnection of an account to a channel. To do this, use the users.post and users.delete settings.
Disconnect account from channel
Last updated
Was this helpful?