# Pause, resume and warmup

> pause sets the mailbox's status to paused and resume sets it back to active; both return { "ok": true }. resume also clears a campaign-sending pause. If the…

Source: https://warmerly.com/docs/accounts/pause-resume-and-warmup

```text
POST /accounts/{id}/pause
POST /accounts/{id}/resume
POST /accounts/{id}/warmup/toggle
POST /accounts/{id}/send-test
POST /accounts/{id}/oauth/reconnect
```

`pause` sets the mailbox's `status` to `paused` and `resume` sets it back to `active`; both return `{ "ok": true }`. `resume` also clears a campaign-sending pause. If the mailbox is flagged as needing a reconnect, `resume` first tests the stored login and answers `409` with code `reconnect_required` when it fails. Resuming a `dead` or `flagged` mailbox can return `402 plan_capacity` when the workspace is at its mailbox limit.

`warmup/toggle` takes `{ "enabled": true | false }` (required) and is the supported way to start or stop warmup for one mailbox; it returns `{ "account": { … } }`. Enabling it for the first time also stamps the warmup start date the ramp is measured from.

The free mailbox every new account is given (`managedBy: "warmerly_sandbox"`) keeps warming for as long as you have it: `pause`, and `warmup/toggle` with `{ "enabled": false }`, answer `409` with code `sandbox_warmup_locked` for it. Delete it (`DELETE /accounts/{id}`) if you no longer want it.

`send-test` takes `{ "to": "you@example.com" }` (a valid email) and sends one real message through this mailbox, with a fixed subject and body, the fastest way to prove SMTP works end to end. It returns `{ "ok": true }`. A failed send returns `500` with `{ "error": { "message": ... } }` where `message` is `smtp_auth_failed`, `smtp_timeout`, `smtp_connection_failed` or `send_failed` (this response has no `error.code`).

`oauth/reconnect` is for mailboxes connected with Google or Microsoft sign-in. It returns `{ "auth_url": "..." }`, a consent URL to open in a browser; completing it reconnects the mailbox (for example a Microsoft 365 mailbox that authenticates but fails to send, see [Troubleshooting](https://warmerly.com/docs/troubleshooting)). It returns `400` for a mailbox that was not connected with OAuth.

## More from Accounts

- [Blocklist status](https://warmerly.com/docs/accounts/blocklist-status): Whether the account's sending domain appears on public DNS blocklists. GET returns the last 10 checks; POST…
- [Activity and warmup history](https://warmerly.com/docs/accounts/activity-and-warmup-history): stats is today-and-7-day counters for one mailbox. "Today" is the UTC day:
- [OAuth-connected accounts](https://warmerly.com/docs/accounts/oauth-connected-accounts): Outlook.com and Microsoft 365 accounts can also be connected via OAuth instead of raw SMTP/IMAP credentials.…