Delete a connection
Permanently removes the connection and its adapter session. This cannot be undone — the user will need to create a new connection and go through QR pairing again.
Permanently removes the connection and its adapter session. This cannot be undone — the user will need to create a new connection and go through QR pairing again.
The default way to authenticate. Create a key at https://developers.wasync.app/keys and send it as Authorization: Bearer wsk_live_….
The key is shown once at creation and stored only as a hash — lose it and you revoke it and create another. Each key carries its own scopes (whatsapp.read, whatsapp.send, whatsapp.events, whatsapp.manage) and an optional IP allowlist.
Errors: an unknown or revoked key returns 401 invalid_key; a key whose IP allowlist does not cover the calling address returns 403 ip_not_allowed (a distinct code on purpose — the key is fine, the address is not). Both carry a WWW-Authenticate: Bearer challenge. Scopes and the connection list are resolved live on every request, so revoking a key or narrowing it takes effect on the next call.
In: header
Path Parameters
Connection id (from POST /connections or GET /connections).
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X DELETE "https://example.com/connections/string"{ "ok": true}Get connection status GET
Returns the current status and metadata of a single connection. Poll every 3–5 s during QR pairing — `status` becomes `"connected"` once the user scans the code. The `qr` field carries a NEW pairing code on each poll — re-render it every time. WhatsApp rotates the code roughly every 20 s, so a QR displayed for longer than that will not scan.
Restart a connection session POST
Restarts the WhatsApp adapter session without deleting the connection record. After a restart, poll `GET /connections/{id}` and re-render the QR code if `status` returns to `"connecting"`.