Run history actions on any channel
Cross-channel superset of POST /calls/actions. Re-evaluate the post-conversation analysis (summary, sentiment, success verdict and extracted fields), start an enhanced re-transcription from a call recording, resend the end-of-conversation webhook, reopen a completed WhatsApp conversation with AI auto-replies, or add/remove the contact phone from the suppression (blacklist) list.
Set kind to select the record type:
call— phone calls, live chat, avatar sessions and WhatsApp voice (idsare call IDs)messaging— WhatsApp, Telegram, Slack, Messenger, Teams, Discord, Google Chat and X conversations (idsare conversation IDs)email— email threads (idsare the thread’s root message ID, which is whatGET /historyreturns as the rowid)
retranscribe is only valid for kind: call, requires exactly one ID, and returns the rounded recording minutes plus the credit quote. resend_webhook always rebuilds the payload from the record as it is stored right now, so a resend after a reanalyze delivers the updated analysis. resume_ai is only valid for kind: messaging and only while a completed WhatsApp conversation’s 24-hour customer service window is still open. It starts a fresh internal inactivity timer without extending the Meta window. blacklist_add and blacklist_remove are phone-based and therefore only valid for kind: call.
Other actions process up to 50 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
reanalyze, retranscribe, resend_webhook, resume_ai, blacklist_add, blacklist_remove Which History record type the ids address.
call, messaging, email 1 - 50 elementsResponse
Per-record results.