Revoke a sandbox session
Hard-deletes the session. The user loses the ability to send to that phone via the sandbox until they re-activate it. Existing conversations and messages already exchanged with that phone are untouched — revocation only blocks FUTURE sends.
Sessions belonging to other users cannot be revoked; the response is the same 400 as "session not found" so existence isn't leaked.
API key authentication - use your Zernio API key as a Bearer token
In: header
Path Parameters
The session id returned by POST /v1/whatsapp/sandbox/sessions.
Response Body
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.whatsappsandbox.deleteWhatsAppSandboxSession({ path: { sessionId: 'session_abc123', },});console.log(data);{
"success": true
}{
"error": "Unauthorized"
}Start a sandbox activation for a phone POST
Creates (or refreshes) a pending sandbox session for the given phone and immediately fires the verified sandbox template from the shared sandbox number to that phone. The session activates when the phone owner replies to that WhatsApp message — the reply itself is proof of ownership. One phone per user: if the caller already has a non-expired session for a DIFFERENT phone, the request is rejected with `invalid_field_value` (the message names the existing phone so it can be revoked first). Re-creating a session for the SAME phone is idempotent and refreshes the verification template. If Meta rejects the template send (not a WhatsApp number, paused WABA, token issue), the pending row is rolled back and the Meta error message is returned in `error` so the caller knows why.
Get reviews GET
Returns reviews for a GBP account including ratings, comments, and owner replies. Use nextPageToken for pagination.