---
title: "Delete conversation"
method: DELETE
path: "/v1/inbox/conversations/{conversationId}"
tags: ["Messages"]
---

# Delete conversation

`DELETE /v1/inbox/conversations/{conversationId}`

## Request

- Base URL: `https://zernio.com/api`
- URL: `https://zernio.com/api/v1/inbox/conversations/{conversationId}`
- Auth: HTTP bearer

Permanently deletes Zernio's stored copy of one conversation and every message in it, in one transaction, and unlinks the contact channel that pointed at it. Nothing is deleted on the platform (the thread stays in WhatsApp, Messenger or Instagram), and the contact record is kept: call DELETE /v1/contacts/{contactId} to erase the person's name and number as well. A platform re-sync can import the thread again: WhatsApp coexistence numbers receive their messaging history from Meta repeatedly, and a Facebook or Instagram account whose DM history walk has not finished imports it on that walk. Inbound media copies Zernio stored are removed on a best-effort basis.

## Path parameters

- `conversationId` string, required

## Query parameters

- `accountId` string, required

## Response `200`

Conversation deleted

- object
  - `success` boolean
  - `data` object
    - `id` string
    - `accountId` string
    - `platform` string
    - `deletedMessages` integer

## Other responses

- `400`: Invalid request
- `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
- `404`: Account or conversation not found

## Changes

- **2026-10-15** `e99596c766c9`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/zernio/apis/zernio-api/changes/v1/inbox/conversations/:conversationId/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/4e74db179e73?raw)