Skip to main content
POST
Run history actions on any channel

Authorizations

Authorization
string
header
required

API key (fam_..., created under Settings → API Keys) or an OAuth 2.0 access token (fam_at_...). 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.

Body

application/json
action
enum<string>
required
Available options:
reanalyze,
retranscribe,
resend_webhook,
resume_ai,
blacklist_add,
blacklist_remove
kind
enum<string>
required

Which History record type the ids address.

Available options:
call,
messaging,
email
ids
string<uuid>[]
required
Required array length: 1 - 50 elements

Response

Per-record results.

data
object
required