Resume Mailboxes
Admin+: resume the named mailboxes (`mailbox_ids`) or every mailbox of a sending domain (`domain`), whoever paused them (an admin or the deliverability guard); the guard's window restarts now.
API key access
admin scope with an API key (ro_pat_...). A signed-in session uses the caller's role./api/v1/deliverability/fleet/resumeAccess token from /api/v1/auth/login, or an API key (ro_pat_..., RO-176) from /api/v1/workspaces/current/api-keys: the key implies its workspace and needs the route's scope. MCP connectors (/api/v1/mcp only) may use an OAuth access token (ro_oat_..., RO-284).
In: header
Header Parameters
Id of the workspace to act on (must be a member).
1 <= items <= 500Response Body
curl -X POST "http://localhost:8000/api/v1/deliverability/fleet/resume" \ -H "X-Workspace-Id: string" \ -H "Content-Type: application/json" \ -d '{}'{
"changed": 0,
"mailbox_ids": [
"497f6eca-6276-4993-bfeb-53cbbbba6f08"
]
}{
"detail": [
{
"loc": [
"string"
],
"msg": "string",
"type": "string",
"input": null,
"ctx": {}
}
]
}Resume Mailbox
Resume sending from a mailbox the deliverability guard paused (admins). The guard pauses a mailbox whose hard-bounce or spam-complaint rate spikes over a rolling window (`paused_at` / `pause_reason`); the sequence runner, one-off sends and reply drafts all refuse a paused mailbox. Resuming clears the pause and restarts the guard's window, so the bounces that caused it don't pause the mailbox again. Idempotent: a mailbox that isn't paused is returned unchanged.
Send Mailbox Email
Send a one-off email from a connected mailbox to a lead (manual follow-ups and replies). Enforced in code, exactly like the sequence runner's sends: the lead's email must not be on the suppression list and `can_contact(email, purpose)` must allow it (409 `Sending is not allowed: <reasons>`), the mailbox must be connected, not paused by the deliverability guard and under its daily cap (409). A marketing send held back by the contact-pressure rules (a manual touch: exempt while the lead is in a conversation with us) or a resource rate limit is a 409 with `code` `contact_deferred`, the `reasons` and `next_allowed_at`. A `marketing` email (the default) gets one-click `List-Unsubscribe` headers (RFC 8058) and the CAN-SPAM footer with the workspace's postal address (409 `missing_postal_address` without one). The send is logged and appended to the lead's timeline (`email_sent`, by the caller). `reply_to_message_id` threads the email under a provider message (e.g. the lead's reply).