---
title: "Permanently delete a conversation"
method: DELETE
path: "/conversation/{conversation_id}/force-delete"
tags: ["Conversations"]
---

# Permanently delete a conversation

`DELETE /conversation/{conversation_id}/force-delete`

## Request

- Base URL: `https://api.thrivedesk.com/v1`
- URL: `https://api.thrivedesk.com/v1/conversation/{conversation_id}/force-delete`
- Auth: HTTP bearer

Irreversible. The conversation must already be in the trash, so soft-delete it with `DELETE /v1/conversation/{conversation_id}` first; calling this on a live conversation returns 404.

Everything hanging off the conversation goes with it: thread events, messages, attachments and the files behind them in object storage, tag links, and custom field values. There is no restore afterwards.

Trashed conversations are also purged automatically once they pass the organization's trash lifetime (30 days by default).

Personal access token only. The API supports a second, partner-issued token class that is not part of the public surface. This endpoint does not accept that class.

## Path parameters

- `conversation_id` string, required

## Response `200`

Success.

- object
  - `message` string

## Other responses

- `401`: Missing or invalid bearer token.
- `403`: Token is valid but does not include a required scope, or the user does not have access to the resource.
- `404`: Resource not found.
- `422`: Request body failed validation.
- `429`: Rate limit exceeded. The `Retry-After` header indicates how long to wait before retrying. See [Pagination and rate limits](/get-started/pagination) for the full rate-limit policy.
- `500`: Unexpected server error.

---

[API](https://skmtc.dev/thrivedesk/apis/thrivedesk-public-api.md) - [All operations](https://skmtc.dev/thrivedesk/apis/thrivedesk-public-api/llms.txt) - [OpenAPI document](https://skmtc.dev/thrivedesk/apis/thrivedesk-public-api/revisions/dce9c632a018?raw)