Run call history actions
Re-evaluate post-call analysis, start an enhanced re-transcription from one call recording, resend call.completed webhooks, or add/remove the contact phone from the suppression (blacklist) list. retranscribe requires exactly one call ID and returns the rounded recording minutes and credit quote. Other actions process up to 50 call IDs per request. Required scope: calls:write. Blacklist actions also need suppression:write or campaigns:write (unrestricted keys 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
Response
Per-call results.