Create / update / submit / sync / send / delete WhatsApp templates
Body.action: create | update | submit | sync | send | delete. Sync follows all provider pages and imports templates that do not yet exist locally. Required scope: assistants:write. Plan flag whatsapp_channel required.
Authorizations
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
create, update, submit, sync, send, delete Template body. Variables must use positive contiguous numbering: {{1}}, {{2}}, {{3}}.
Official library preset name. When supplied with action=create, the preset is created directly for the sender.
Button index to HTTPS URL or E.164 phone number. Required for official library templates with URL or phone-number buttons.
UTILITY, MARKETING, AUTHENTICATION Maps component positions (1, 2, header.1) to system, lead, assistant, or custom variable keys.
Meta template components. Call-permission templates use a BODY plus a CALL_PERMISSION_REQUEST component.
Response
Action result.