Replies

List Inbox Auto Sends

The Inbox agent's automatic answers (RO-368, RO-388): whether they are on (Auto, only with Email approval "none", plus the admin's opt-in; without it Auto only filters spam and junk), its rules (confidence, categories, daily cap), today's count, and the audit trail of every answer it sent or skipped, with the reasons.

API key access

Needs the replies:read scope with an API key (ro_pat_...). A signed-in session uses the caller's role.
GET/api/v1/inbox/auto-sends
AuthorizationBearer <token>

Access 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

X-Workspace-Id?string | null

Id of the workspace to act on (must be a member).

Response Body

curl -X GET "http://localhost:8000/api/v1/inbox/auto-sends" \  -H "X-Workspace-Id: string"
{
  "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"
    }
  ]
}