Start an outbound call
Places an outbound call: the assistant must be active and needs an outbound-capable phone number (assigned to it, or passed via phone_number_id). Returns the created call immediately (status queued) — poll GET /calls/{id} or use the assistant’s webhook for the result and provider-neutral failure guidance. Destinations that are not allowed return 403 destination_forbidden. Required scope: calls:write (keys without scope restrictions have full access).
Authorizations
API key (fam_..., created under Settings → API Keys) or an OAuth 2.0 access token (fam_at_...). REST operations also require API Access for the credential's workspace. Keys can be restricted to scopes such as assistants:read, calls:write, campaigns:write, automations:read, dashboards:read, dashboards:write, leads:write, segments:write, loop:read, loop:write, phone_numbers:write, sip_trunks:write, knowledge:write, voices:read, billing:read, settings:write, platform:read, platform:write; a *:write scope implies the matching *:read. Automation and dashboard endpoints also accept the legacy calls:* scope. Keys without scope restrictions have full access within the workspace's available capabilities.
Body
Assistant that runs the call. Must be active.
Destination in E.164 format, e.g. +4930123456.
Arbitrary key/value context injected into the conversation (e.g. the callee's name).
Optional explicit caller ID (one of your phone numbers). Defaults to the number assigned to the assistant.
Response
The created call (status queued).