QR session lifecycle
Page updated: 2026-04-03
Summary
The QR session is the live link between WAPing and the WhatsApp client on your phone. API behavior and inbox behavior depend on this session being healthy.
Canonical reference: Hostnames, path prefixes, JSON field names, and changelog are maintained on docs.waping.app. Examples below are illustrative — align your integration with the live OpenAPI/reference there.
Connection model: WAPing links WhatsApp through a QR session (similar in concept to WhatsApp Web). This is not Meta’s WhatsApp Business Cloud API product, and you do not complete Meta BSP / Cloud API onboarding inside WAPing for this path.
Purpose
Explain how linkage behaves over time so operators and engineers can design alerts, pauses, and recovery — without assuming Meta Cloud API semantics.
Best for
- Teams that monitor device status and pause sends when disconnected.
- Products where an operator can re-scan QR when WhatsApp logs out.
Not for
- Fully unattended phones with no recovery path—disconnects block sends until re-linked.
- Requirements that mandate Meta-hosted Cloud API template-only outbound—different product path.
Session states (conceptual)
| Term | Definition |
|---|---|
| Unlinked | No active session; operator must scan QR to pair a device record. |
| Linked / connected | Session healthy; outbound API and inbox behave normally for that deviceId. |
| Degraded | Intermittent connectivity; expect retries, delayed delivery, or delayed webhooks. |
| Disconnected | Session unusable until re-established (often re-scan QR or follow in-app recovery). |
Workflow
1) Pair
Operator scans QR → device record appears with status transitions. Until connected, do not send production traffic through API.
2) Monitor
Use dashboard + optional webhooks (session events) to detect disconnects early.
3) Recover
On disconnect, pause automation that sends messages, surface operator alerts, and re-scan QR when prompted.
What triggers disconnect
- WhatsApp logged out on the phone, reinstall, or security prompts.
- Long idle periods or policy changes from WhatsApp.
- Phone offline or OS restrictions on background activity.
Errors
API calls that require a live session may return SESSION_DISCONNECTED (or equivalent) — see Errors.
Published device limits per plan
Each deviceId maps to one linked session; multi-device workspaces route traffic per device. Counts below are from published pricing.
| Plan | WhatsApp devices (linked) | Outbound messages / month | REST API & webhooks |
|---|---|---|---|
| Free | 1 | 500 | Not included |
| Starter | 1 | 3,000 | Included |
| Growth | 5 | 30,000 | Included |
| Pro | 15 | 300,000 | Included |
| Enterprise | 50 | 1,000,000 | Included |
Source: /pricing plan cards (2026-04-03).
Caveats
- If procurement requires Meta’s official Cloud API with BSP onboarding and hosted template governance, WAPing’s QR model may not match — compare requirements explicitly.
- Do not equate “verified Meta Business” flows with WAPing QR linkage — different product path.
Related documentation
Citation note: This page is a marketing-site overview. Authoritative request/response schemas and rate values live on docs.waping.app and in your workspace dashboard. Numeric plan quotas match /pricing (reviewed 2026-04-03). Guide text updated 2026-04-03.