Start integrating with the WATI API for messaging, contacts, automation, and workspace operations.
WATI APIs connect messaging, contacts and automation to your applications and AI agents. Start with Getting started, Authentication, or the MCP guide.
For AI clients, use the canonical Markdown URLs listed in llms.txt to read the current documentation release, or connect to the documentation MCP at https://docs.wati.io/mcp. Both follow the default release. To execute WATI operations, use the separate product MCP.
Use V3 first
Use V3 for supported business operations and adopt its request, response, pagination and batch behavior. API Documentation V3 is the main reference. Compatibility endpoints and old recipes remain reachable by their existing links; they are omitted from primary navigation. This documentation change does not retire any API.
Use Legacy exceptions only for the capabilities below. A different identifier, payload or batch format alone is not a missing capability.
| Capability still requiring a legacy operation | Reference |
|---|---|
| Create/delete a WhatsApp template | Create, delete by name, delete a language |
| Create a webhook subscription; manage it with V3 afterward | V2 create |
| Cancel a scheduled campaign or configure its original automatic retry policy | Cancel, retry policy |
| Schedule a campaign with legacy reaction reply actions (ordinary scheduling uses V3) | Reaction scheduling |
| Send a CTA URL or ask the recipient to share contact information | CTA, request contact information |
| Quote an earlier message or supply a local message ID, then look it up | Text, local-ID lookup |
| Send a voice message | Upload, URL |
| Retrieve message history with server-side time filters | Time-filtered history |
| Use DirectSend delivery mode | Single, batch |
| Persist or delete saved segments | Create, update, delete, batch delete |
| Read members or schedule a campaign from a saved segment ID | Members, schedule |
| Discover WhatsApp business accounts/numbers, including the default number, or read a number profile | Business accounts, numbers, profile |
| WhatsApp order/payment messages and payment status | Order details, order template, status, status template, checkout template, read order, payment status |
V3 covers ordinary text/media, buttons/lists/products, template reads/sends/scheduling, contacts, chatbot operations, team/operator/status updates, and segment reads/evaluation. A legacy exception does not make every legacy send the recommended choice. Account, channel, session and permission requirements still apply to each operation.
Base URL and versions
Use the API host and credential provided for the intended workspace and region, for example https://live-mt-server.wati.io.
- V3:
{host}/api/ext/v3/...— no tenant ID in the URL. - Retained V1/V2:
{host}/{tenantId}/api/v1/...or{host}/{tenantId}/api/v2/....
tenantId is a workspace ID, not a phone number. API route version does not select the authentication mechanism.
2.6 identifies this documentation release and the OpenAPI artifact's info.version. It is independent of the API route version (for example V3). Versioned links refer to this release; the site's default selector determines the default documentation release.