---
title: "Delete a conversation"
method: DELETE
path: "/v1/threads/{thread_id}"
tags: ["threads"]
---

# Delete a conversation

`DELETE /v1/threads/{thread_id}`

## Request

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

Moves every message currently in the conversation, with attachments, to the inbox's [Trash](https://cherami.to/docs/api/trash/list-trash). Trash lists them one by one: [restore](https://cherami.to/docs/api/trash) each within seven days to bring the conversation back; after that they are permanently deleted.

The counts say how many messages moved. A repeated request returns `202` or `404`.

## Path parameters

- `thread_id` string, required

## Response `202`

Accepted.

- DeletedThread
  - `id` string, required: Cherami resource ID.
  - `inbox_id` string, required: Cherami resource ID.
  - `message_count` integer, required
  - `received_count` integer, required
  - `sent_count` integer, required
  - `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)