8 August 2026

Connection lifecycle events + GET /account slot quota

New feature.

Two webhook events were added for partners who run our connections inside their own product: connection.disconnected (a number stopped working and its owner must pair again) and connection.connected (it recovered). Both fire once per real transition, on qr connections, and the QR is deliberately NOT in the payload — it is a scan-to-login credential, so fetch it from your authenticated GET /connections/{id}.

GET /account (scope whatsapp.read) answers "can I onboard another number right now?" before you take the order: { slots: { total, used, available, nextExpiry }, connections: { total, connected, needsReconnect } }.

A slot is capacity, not a phone number — it attaches when a number actually pairs and returns to your pool with whatever time is left on it when the connection is deleted, so a paid slot moves from a departing customer to a new one without paying twice. You map our connection id to your own customer record; we mint the id, you map it.

Subscriptions created before 10 August 2026 must re-consent to receive the connection.* events.

Also from this date, the connection provider field speaks the public vocabulary: qr and cloud_api. See Connection types.