Operator read endpoints for listing contacts, synced WhatsApp templates, campaigns, and journey definitions. Use compatibility endpoints to upsert contacts from external systems.
The contacts API provides operator read access to the contact store, synced WhatsApp templates, campaigns, and journey definitions. These are internal endpoints intended for the operator application — they expose paginated lists you can use for search, dashboards, and configuration views. To create or update contacts from an external CRM or automation platform, use the compatibility endpoints instead.
All /internal/* endpoints are intended for the operator application and should be placed behind an authenticated session in production. Workspace scoping is enforced at the data layer.
List WhatsApp message templates synced from the Meta Graph API. Templates are synced from your connected WhatsApp Business Account and reflect the approved templates available for sending.
Templates are synced from the Meta Graph API via a sync job, not fetched in real time. If you’ve recently submitted or approved a template and don’t see it here, trigger a template sync from the operator application.
The read endpoints above are for the operator application. If you need to create or update contacts programmatically from a CRM, marketing platform, or other external system, use the compatibility endpoints:
POST /compat/contact — upsert with a Charles-compatible request body
PUT /api/v1beta/contact/ — same behavior with a legacy response shape
See Compatibility for full request schemas and response examples.