API documentation
Current endpoints, auth families, health checks, sends, webhooks, inbox reads, status codes, and boundaries.
Open docsHelp center
Implement EZWhatsApp without guessing the product boundary.
This help center is scoped to the current Platform: linked-device WhatsApp lines, shared inbox operations, line-scoped API tokens, webhooks, and agency delivery templates.
Reference corpus
API examples
Copy-ready cURL and JavaScript examples for health, text, media, webhook setup, and inbox reads.
Open examplesAgency templates
Implementation templates for order updates, appointment reminders, lead handoff, CRM sync, campaign replies, and support escalation.
Open templatesWebhooks
Configure line webhooks, handle EZWhatsApp delivery headers, map inbound messages to conversations, and retry safely.
Open webhook guideAPI tester
Build safe requests, generate cURL, and optionally test from the browser when the API environment allows it.
Open testerIntegrations
Patterns for CRM, e-commerce, forms, calendars, Google Sheets, Make, Zapier, n8n, and custom backends.
Open integrationsMost common implementation questions
Which token do I use?
Use ezw_line_... line tokens for Channel API v1. Use workspace ID tokens only for logged-in workspace/admin/operator routes.
Can I send campaigns through the direct send API?
Do not hide campaign blasts inside generic direct-send loops. Campaigns have their own customer-admin workflow and execution boundary.
Can I upload files with Channel API v1?
No. Channel API media sends are URL-only. Workspace sends currently support one uploaded image through multipart form data.
Can I treat webhook payloads as ownership truth?
No. Webhooks are integration events. Workspace assignment, ownership, and durable conversation state remain inside Platform source-of-truth APIs.