---
title: "Revoke a sandbox session"
method: DELETE
path: "/v1/whatsapp/sandbox/sessions/{sessionId}"
tags: ["WhatsApp Sandbox"]
---

# Revoke a sandbox session

`DELETE /v1/whatsapp/sandbox/sessions/{sessionId}`

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.

## Path parameters

- `sessionId` string, required

## Response `200`

Session revoked

- object
  - `success` boolean

## Other responses

- `400` — Invalid or unknown session id
- `401` — Missing or invalid API key. `code` is `missing_credentials` when no Authorization header was sent and `invalid_credentials` when the key is unknown, revoked or expired.
- `403` — Inbox addon required

## Changes

- **2026-10-06** `f8c8f34fb41a` — 1 warning
  - added the new `account` enum value to the `details/budgetScope` response property for the response status `401`
- **2026-10-02** `d556591af3f6` — 7 info
  - added the optional property `code` to the response with the `401` status
  - added the optional property `details` to the response with the `401` status
  - added the optional property `docUrl` to the response with the `401` status
  - added the optional property `param` to the response with the `401` status
  - …3 more

[Change history](https://skmtc.dev/zernio/apis/zernio-api/changes/v1/whatsapp/sandbox/sessions/:sessionId/delete.md)

---

[API](https://skmtc.dev/zernio/apis/zernio-api.md) · [All operations](https://skmtc.dev/zernio/apis/zernio-api/llms.txt) · [OpenAPI document](https://skmtc.dev/zernio/apis/zernio-api/revisions/664b218652be?raw)