Update Inbox Auto Send Settings
Admins: turn "Auto-send confident answers" on or off (RO-388, off by default). Turning it on is for a person in the app only (403 `human_only` from Zero, MCP or an API key). Changes are audited (`inbox.auto_send_answers_changed`). Answers still go out only while the Inbox agent is at Auto with Email approval "none", and through every RO-368 rule.
API key access
admin scope with an API key (ro_pat_...). A signed-in session uses the caller's role./api/v1/inbox/auto-sends/settingsAccess 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).
"Auto-send confident answers". Turning it on: an admin in the app only.
Response Body
curl -X PUT "http://localhost:8000/api/v1/inbox/auto-sends/settings" \ -H "X-Workspace-Id: string" \ -H "Content-Type: application/json" \ -d '{ "auto_send_answers": true }'{
"enabled": true,
"at_auto": true,
"auto_send_answers": true,
"can_manage": true,
"min_confidence": 0.1,
"daily_cap": 0,
"categories": [
"string"
],
"sent_today": 0,
"items": [
{
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"lead_id": "9bddab70-98e6-43a9-8f32-c9788b9de0c0",
"lead_name": "string",
"draft_id": "d998e5e8-954a-4a68-bb9e-7305e87278c0",
"category": "string",
"confidence": 0,
"outcome": "string",
"reasons": [
"string"
],
"sent_message_id": "10e758d6-1ff1-42da-b026-45795a3d5469",
"created_at": "2019-08-24T14:15:22Z"
}
]
}{
"detail": [
{
"loc": [
"string"
],
"msg": "string",
"type": "string",
"input": null,
"ctx": {}
}
]
}Send Reply Draft
Send an approved draft to the lead, threaded under their reply. 409 if the draft isn't approved, the lead may not be contacted (suppressed, opted out, no consent basis), the mailbox isn't connected or hit its daily cap; 502 on a provider error. A resource rate limit (RO-228: the core's per-mailbox/domain/workspace/provider token buckets) answers 409 `contact_deferred` with the `reasons` and `next_allowed_at`. Unsubscribe (RO-104): every send carries one-click `List-Unsubscribe` headers. A reply in the lead's own thread has no footer; a call recap (or a reply sent from another mailbox, i.e. a new thread) gets the CAN-SPAM footer with the postal address (409 `missing_postal_address` without one).
Cancel Research Batch
Stop the batch: pending items are skipped (an item being researched still finishes). 409 once it ended.