---
title: "Disconnect Mailbox"
method: DELETE
path: "/api/v1/mailboxes/{mailbox_id}"
tags: ["mailboxes"]
---

# Disconnect Mailbox

`DELETE /api/v1/mailboxes/{mailbox_id}`

## Request

- Base URL: `https://api.nudgelink.co` (the document declares no server; this is the origin it was published from)
- URL: `https://api.nudgelink.co/api/v1/mailboxes/{mailbox_id}`
- Auth: HTTP bearer

Works without a plan: a downgraded client can still remove a mailbox.
It stops sending at once, even if Unipile is unreachable.

Release review 2026-10-13 (DB-1 / DB-2 / DB-6 / EMAIL-6): the row is kept
(``disconnected``) instead of deleted, so every email already sent from it
keeps its ``mailbox_id`` and replies/bounces to it still match — and a
reconnect of the same address reuses the row. If Unipile's delete fails
the row stays ``disconnecting`` with its account id, and
``tasks/mailboxes.retry_disconnects`` retries until Unipile lets go.

## Path parameters

- `mailbox_id` string, uuid, required

## Response `204`

Successful Response

## Other responses

- `422`: Validation Error

---

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