---
title: "Delete a file"
method: DELETE
path: "/v1/mailboxes/{mailbox_id}/files/{file_id}"
tags: ["Files"]
---

# Delete a file

`DELETE /v1/mailboxes/{mailbox_id}/files/{file_id}`

## Request

- Base URL: `https://api.revdoku.com`
- URL: `https://api.revdoku.com/v1/mailboxes/{mailbox_id}/files/{file_id}`
- Auth: HTTP bearer

Requires mailbox-admin permission. Files under _email/ return EMAIL_PATH_READ_ONLY; delete the email instead.

## Path parameters

- `mailbox_id` string, required
- `file_id` string, required

## Query parameters

- `account_id` string
- `reason` string, nullable: Optional purpose for this action. AI agents should explain intentional reads and changes when known; omit when unknown. Do not include secrets, file contents, or transcripts.

## Response `200`

Deleted

- object
  - `success` true, required
  - `data` DeleteResult, required
    - `deleted` true, required
    - `id` string, required: ID of the deleted resource. A webhook delete returns the mailbox ID.

## Other responses

- `default`: Request failed. See error.code. Any 429 or 503 response with Retry-After (for example 503 EMAIL_LABELING_PENDING or 503 EMAIL_INDEX_BUILDING): wait that many seconds, then try the read again. 429 EMAIL_SEND_RATE_LIMITED has no Retry-After. Never retry EMAIL_LOOP_DETECTED.

---

[API](https://skmtc.dev/revdoku/apis/revdoku-api.md) · [All operations](https://skmtc.dev/revdoku/apis/revdoku-api/llms.txt) · [OpenAPI document](https://skmtc.dev/revdoku/apis/revdoku-api/revisions/3ff4e2540a8b?raw)