Opt Out
Suppress the lead (phone + every channel per policy) and stop their sequences. Idempotent; accepted even after the call completed.
API key access
/api/v1/calls/{call_id}/opt-outPer-call token issued when the call was created (job metadata api_token).
In: header
Path Parameters
uuidHeader Parameters
Workspace of the call (must match the token).
uuid""length <= 2000items <= 4Response Body
curl -X POST "http://localhost:8000/api/v1/calls/497f6eca-6276-4993-bfeb-53cbbbba6f08/opt-out" \ -H "X-Workspace-Id: string" \ -H "Content-Type: application/json" \ -d '{ "lead_id": "9bddab70-98e6-43a9-8f32-c9788b9de0c0" }'{
"detail": [
{
"loc": [
"string"
],
"msg": "string",
"type": "string",
"input": null,
"ctx": {}
}
]
}Knowledge Search
Approved snippets from the workspace knowledge base. Never fails the call: when search can't run (free-tier quota used up, embeddings not configured, provider error) it returns no snippets and a ``reason``, and the agent promises a follow-up instead of guessing.
Request Handoff
Flag the call for a human follow-up: the first request puts a task note for a human on the lead's timeline (RO-134). RO-064: with ``live_transfer: true`` and a live-transfer target the workspace allows now (Settings -> Live transfer: enabled, within its hours, on an outbound call dialled through LiveKit SIP, not a test call, no opt-out), the answer carries ``transfer`` (the team line and its ring timeout) and the task note waits for ``/transfer-result`` instead.