Update sending settings
Change one Gmail mailbox's daily send cap or switch its sending on or off.
https://api.rankparse.com/v1/outreach/sendingFreeAPI keyChanges the settings of one mailbox: the default unless you pass mailbox_id. Each mailbox has its own cap and switch, shared by every campaign that sends from it. Stopping (a lower cap, or turning sending off) always applies at once. Raising the cap or turning sending on is held for a person's approval when an agent asks in an account where the approval inbox is enforced.
Body parameters
mailbox_idstringA mailbox_id from Get sending settings. Omit it for the default mailbox. A value that is not a non-empty string returns 400 invalid_mailbox_id; an id outside your workspace returns 404 mailbox_not_found.
max_sends_per_dayinteger1 to 100. Otherwise 400 invalid_send_cap. A plan cap, when one applies, still limits what is actually sent.
auto_send_enabledbooleanfalse stops all sending from the mailbox, true resumes it. Not a boolean returns 400 invalid_auto_send.
agent_autosendbooleanOnly false is accepted: it turns off Let Claude send without review for the mailbox. Only a person can turn it on, in RankParse; true returns 403 human_only_setting.
Send at least one of max_sends_per_day and auto_send_enabled (or agent_autosend: false), otherwise 400 nothing_to_update. Every field is validated before anything is written, so a 400 means nothing changed. Other keys are ignored.
Response
A change that applies directly returns 200:
okbooleantrue.
An agent call (MCP, or the header X-RankParse-Client: mcp) that raises the cap or turns sending on, in an account where the approval inbox is enforced, returns 202 and changes nothing yet except any stopping part of the same request:
statusstringawaiting_approval, or approved when the same change was already approved and is running.
proposal_idstringThe outreach_sending_change proposal. See Proposals.
review_urlstringWhere the user approves it. Show it to them.
appliedobjectPresent when the request mixed a stop and an increase: the fields that took effect now (for example { "auto_send_enabled": false } or a lower max_sends_per_day). The message then starts with "Applied now:".
messagestringPlain-text guidance to relay to the user.
A new increase for the same mailbox replaces a pending one (the old proposal becomes superseded). A sending-change proposal expires after 3 days.
Errors
| HTTP | Code | When |
|---|---|---|
| 400 | invalid_json | The body is not valid JSON. |
| 400 | invalid_mailbox_id | mailbox_id is not a non-empty string. |
| 400 | invalid_send_cap | max_sends_per_day is not an integer from 1 to 100. |
| 400 | invalid_auto_send | auto_send_enabled is not a boolean. |
| 400 | nothing_to_update | No field to change. |
| 400 | gmail_not_connected | There is no mailbox to change, or (agent increase) Google stopped accepting it and it needs reconnecting. |
| 403 | capability_missing | Your role cannot manage outreach. |
| 403 | human_only_setting | agent_autosend was not false. |
| 403 | action_disabled_by_policy | Agent increase: the owner turned this action Off. |
| 404 | mailbox_not_found | mailbox_id is not a mailbox of your workspace. |
| 409 | change_in_progress | Agent increase: a different sending change for this mailbox is already approved and running. The increase was not applied; any stopping part was. Try again after it completes. |
| 429 | too_many_pending_proposals, daily_proposal_limit_reached | Agent increase: the proposal limits. |
Plus the shared errors.
Related
MCP tool: outreach_configure_sending (accepts max_sends_per_day, auto_send_enabled, mailbox_id). Confirm with the user before changing these: they control real email volume.