---
title: "Delete a conversation"
description: "Delete a conversation for good, as the inbox's Delete does. `DELETE /api/v1/email/threads/{id}`"
url: https://www.unitpost.com/docs/email/delete-email-threads-id
section: "Email API reference"
updated: 2026-10-13
---
# Delete a conversation

`DELETE /api/v1/email/threads/{id}`

Delete a conversation for good, as the inbox's Delete does. Its received messages are erased (they still count toward usage, and never come back); replies and forwards sent from it stay on your sent emails. It can't be undone. Also requires `emails:read`. Requires the `emails:send` capability.

## Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `id` | path | string | yes | — |

## Response fields (200)

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `object` | enum | yes | One of: `email_thread`. |
| `id` | string | yes | — |
| `deleted` | enum | yes | One of: `true`. |
| `deleted_messages` | integer | yes | Received messages erased. |

## Responses

| Status | Description |
| --- | --- |
| 200 | Deleted. |
| 401 | Missing or invalid API key. |
| 403 | Insufficient scope (`emails:read` and `emails:send`). |
| 404 | Conversation not found. |

## Example request

```bash
curl -X DELETE 'https://www.unitpost.com/api/v1/email/threads/thr_123' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'User-Agent: my-app/1.0'
```

## Example response (200)

```json
{
  "object": "email_thread",
  "id": "id_123",
  "deleted": true,
  "deleted_messages": 0
}
```

## Links

- HTML reference (with Node.js, Python, Ruby, PHP, Laravel, Go, Java, Rust, .NET and CLI examples): https://www.unitpost.com/docs/email/delete-email-threads-id
- OpenAPI 3.1 (full schemas): https://www.unitpost.com/api/v1/openapi.json