> ## Documentation Index
> Fetch the complete documentation index at: https://docs.inboxapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# message.deleted

> Occurs when a message is deleted

<ResponseExample>
  ```json Example payload theme={null}
  {
    "id": "ck9v2m5nj0xp4wq7ybftrae8",
    "seq": 104,
    "teamId": "hzcai5t59nn9vsck3rbuepyg",
    "type": "message.deleted",
    "timestamp": "2025-01-15T16:00:00.000Z",
    "version": "1.0",
    "data": {
      "messageId": "p8rvk2m5j0xn4wq7ybftcael",
      "threadId": "l44e15irdq4db30i77cgphhx"
    }
  }
  ```
</ResponseExample>

## When it fires

* A message is deleted through the Inbox UI
* A message is deleted via the [Delete message](/api-reference/messages/delete-message) API endpoint
* A message is deleted on the platform and the deletion is synced to Inbox

## Payload

<ResponseField name="messageId" type="string" required>
  The ID of the deleted message.
</ResponseField>

<ResponseField name="threadId" type="string" required>
  The ID of the thread the message belonged to.
</ResponseField>

<Tip>
  Inbox stores full message history, including deleted messages. You can still retrieve the original content using the [Get message history](/api-reference/messages/get-message-history) endpoint after receiving this event — no need to store message content preemptively.
</Tip>