---
title: "Delete an inbox"
method: DELETE
path: "/v1/inboxes/{inbox_id}"
tags: ["inboxes"]
---

# Delete an inbox

`DELETE /v1/inboxes/{inbox_id}`

## Request

- Base URL: `https://cherami.to`
- URL: `https://cherami.to/v1/inboxes/{inbox_id}`
- Auth: HTTP bearer

Deletes the inbox with all its received and sent mail, drafts, attachments and conversations. Deletion is final: nothing goes to Trash, and the address is retired for everyone, so no inbox can use it again and mail sent to it does not arrive. Confirm the exact inbox with your human first; the API asks for no other confirmation.

The slot is freed at once. A repeated request returns `202` or `404`.

[Deletion guide](https://cherami.to/docs/guides/deletion)

## Path parameters

- `inbox_id` string, required

## Response `202`

Accepted.

- Deleted
  - `id` string, required: Cherami resource ID.
  - `status` 'deletion_pending', required
  - `message` string, required

## Other responses

- `401`: `unauthorized`: Send a valid API key as `Authorization: Bearer <key>`. If the key stopped working, get a new one through [recovery](https://cherami.to/docs/guides/recovery).
- `403`: `operation_not_allowed`: Sending, or deletion and restore, is turned off for this account; the message says which. Contact hello@cherami.to.
- `404`: `not_found`: The resource does not exist or does not belong to this account. A reply or forward source must also be in the sending inbox.
- `500`: `internal_error`: The operation failed. Retry a read; after a write the change may have happened, so recover as [retry by operation](https://cherami.to/docs/api/errors#retry-by-operation) describes.

---

[API](https://skmtc.dev/cherami/apis/cherami-http-api.md) · [All operations](https://skmtc.dev/cherami/apis/cherami-http-api/llms.txt) · [OpenAPI document](https://skmtc.dev/cherami/apis/cherami-http-api/revisions/7bd993d538af?raw)