Wawp’s Session Lifecycle

Wawp’s session API makes sessions reliable, secure, and easy to automate — a clear win for users, integrators, and operations teams.

Instances API is the operational backbone for provisioning and managing WhatsApp sessions at scale.

Screenshot 2025-09-10 at 21-51-51 Connect - Wawp.png

Before you can 📤 Send or 📥 Receive messages you must:

Create a session (and optionally Start it) from https://wawp.net/account/connect.

Authenticate it by scanning a QR code or entering a pair-code in WhatsApp.

By exposing deterministic lifecycle endpoints (create, start, stop, restart, delete, logout, info, and data) Wawp transforms what’s normally a manual, fragile process into an automated, auditable workflow.

Developers benefit from consistent validation and error shapes, which reduces integration friction and support load: when a request fails, the response explains what failed and why in a machine-friendly format.

Micro-caching of safe GETs reduces latency for dashboards and status checks while request-scoped caches cut DB hits during bulk operations.

Operators get better telemetry and a clean lifecycle for recovery and maintenance — scheduled restarts, controlled shutdowns, and clean deletions help with incident response and capacity reclaiming.

Documenting these operations on https://docs.wawp.net with practical examples, common error cases, and recommended polling/backoff strategies will speed adoption and cut developer support.

🔄 `session.status` values

Status	Meaning & next step
STOPPED	Session is not running. Call Start to launch it.
STARTING	Engine is booting. Wait for the next status update.
SCAN_QR_CODE	WhatsApp needs a fresh login. • Fetch the latest QR each time you get this status (it changes frequently). • Display the QR (or pairing code) to the operator/user.
WORKING	Session is authenticated and ready to send/receive messages.
FAILED	Something went wrong (e.g., lost auth, device unlinked). • First try Restart. • If that fails, Logout and Start again to obtain a new QR.

🌐 Example `session.status` webhook payload

{
  "instance_id": "123456789",
  "status": "SCAN_QR_CODE",
  "qr": "data:image/png;base64,iVBORw0KGgoAAA...",
  "ts": 1722170400
}

Handle each new SCAN_QR_CODE event by replacing any previously shown QR/pair-code with the updated one.

#

🔄 session.status values#

🌐 Example session.status webhook payload#

🔄 `session.status` values

🌐 Example `session.status` webhook payload