Summary
Wati provides Application Programming Interfaces (APIs) that let you connect Wati with your existing systems, automate messaging, manage contacts, run campaigns, and access other Wati features programmatically.
This guide provides an overview of the available Wati APIs, including their endpoints, supported API versions, and links to additional developer resources.
Important: v3 is recommended for all new integrations. Legacy v1 and v2 endpoints remain available where supported.
Instructions
1. Understand Wati API Versions and Endpoints
Wati API endpoints use different URL formats depending on the API version.
Base URL: https://live-mt-server.wati.io
API version | URL path format | Tenant ID required in path? |
v3 |
| No |
v1 |
| Yes |
v2 |
| Yes |
For v1 and v2 endpoints, replace {tenantId} with your Wati tenant ID. For v3 endpoints, the tenant ID is not included in the URL path.
Use v3 for new integrations wherever the required operation is supported. Use legacy endpoints when the required operation is not available in v3.
2. Create an API Token
You need an API token to authenticate requests to Wati API endpoints.
To create an API token:
Log in to your Wati account.
Go to Connector > API.
Select Create API Token.
Create a token with the appropriate permissions for the API operations you want to perform.
For v3 endpoints, select the required token scope:
Token scope | Used for |
| Contact operations |
| Conversation operations |
| Sending message templates |
Make sure your token has the required scope for the endpoint you want to use.
3. Explore Available Wati APIs
The following sections group Wati APIs by functionality. Each table lists the available operations and their documented endpoint paths.
3.1 Channels API
Use the Channels API to retrieve information about your connected WhatsApp numbers.
Operation | Method | v3 endpoint | v1 endpoint |
List connected WhatsApp numbers | GET |
|
|
3.2 Messaging API
Use the Messaging API to send messages, retrieve conversation message history, and manage conversations.
Operation | Method | v3 endpoint | v1 endpoint |
Get message history for a contact | GET |
|
|
Send a session text message | — | v3 available |
|
Send a session file | — | v3 available |
|
Send a session file via URL | — | v3 available |
|
Send a template message | — | v3 available |
|
Send template messages in bulk | — | v3 available |
|
Send template messages using a CSV file | POST | — |
|
Send an interactive button message | — | v3 available |
|
Send an interactive list message | — | v3 available |
|
Send an interactive call-to-action (CTA) URL message | POST | — |
|
Update conversation status | PUT |
|
|
Assign an operator to a conversation | PUT |
|
|
Important notes:
The Get Message History API retrieves the conversation history for a specific contact. It does not retrieve all messages received by your WhatsApp number.
A successful HTTP
200response from a message-sending API means the request was accepted. It does not confirm that the message was delivered to the recipient.Use the
sentMessageDELIVERED_v2webhook event to track message delivery. ThetemplateMessageFailedevent reports message-sending failures.
3.3 Contacts API
Use the Contacts API to create, retrieve, update, delete, and organize contacts in Wati.
Operation | Method | v3 endpoint | v1 endpoint |
List contacts | GET |
|
|
Add a contact | POST |
|
|
Update contact attributes | PUT |
|
|
Update multiple contacts | POST | — |
|
Get contact details | GET |
| — |
Get the total contact count | GET |
| — |
Delete a contact | — | v3 available | — |
Assign contacts to teams | PUT |
| — |
Plan requirement: Updating multiple contacts through the v1 endpoint requires a Business plan.
3.4 Message Templates API
Use the Message Templates API to retrieve, create, and delete WhatsApp message templates.
Operation | Method | v3 endpoint | v1 endpoint |
List message templates | GET |
|
|
Get a template by ID | GET |
| — |
Create a template | POST | — |
|
Delete a template | DELETE | — |
|
3.5 Campaigns API
Use the Campaigns API to retrieve campaign information, estimate campaign costs, and manage scheduled broadcasts.
Operation | Method | v3 endpoint | v1 endpoint |
List campaigns | GET |
| — |
Get campaign details | GET |
| — |
Get campaign recipients | GET |
| — |
Get campaign overview | GET |
| — |
Estimate campaign cost | POST |
| — |
Schedule a campaign | POST | — |
|
Delete a scheduled campaign | DELETE | — |
|
3.6 Tags API
Use the Tags API to organize conversations by adding or removing tags.
Operation | v3 availability |
Add a tag to a conversation | Available |
Remove a tag from a conversation | Available |
Refer to the Wati API documentation for the relevant endpoint paths and request details.
3.7 Typing Indicator API
Use the Typing Indicator API to display a typing indicator to a contact during an active messaging session.
Operation | v3 availability |
Send a typing indicator | Available |
Refer to the Wati API documentation for endpoint details.
3.8 Calls API
Use the Calls API to retrieve call logs, recordings, transcripts, and summaries.
Operation | Method | v3 endpoint |
Get call logs | GET |
|
Get a call recording | GET |
|
Get a call transcript | GET |
|
Get a call summary | GET |
|
Retrieve multiple recordings, transcripts, or summaries | — | v3 available |
Refer to the Wati API documentation for the request details for batch operations.
3.9 Chatbots API
Use the Chatbots API to retrieve available chatbots and start chatbot flows.
Operation | Method | v3 endpoint | v1 endpoint |
List chatbots | GET |
|
|
Start a chatbot | POST |
|
|
Plan requirement: The Chatbots API requires a Pro or Business plan.
3.10 Segments API
Use the Segments API to retrieve contact segments, evaluate segment filters, and create custom segments.
Operation | Method | v3 endpoint | v1 endpoint |
List segments | GET |
| — |
Get a segment | GET |
| — |
Evaluate segment filters | — | v3 available | — |
Create a custom segment | POST | — |
|
Plan requirement: Creating a custom segment through the v1 endpoint requires a Pro or Business plan.
3.11 Webhook Management API
Webhooks allow Wati to send event notifications to a URL you configure. You can use the Webhook Management API to manage webhook subscriptions programmatically.
Operation | Method | v3 endpoint | v2 endpoint |
List webhook subscriptions | GET |
| — |
Get a webhook subscription | GET |
| — |
Update a webhook subscription | PUT |
| — |
Delete a webhook subscription | DELETE |
| — |
List available webhook event types | — | v3 available | — |
Create a webhook subscription | POST | — |
|
For instructions on configuring and handling webhook events, see the Wati Webhooks Documentation.
3.12 Instagram API
Use the Instagram API to retrieve Instagram posts and comments and reply to comments.
Operation | Method | v3 endpoint |
List Instagram posts | GET |
|
Get an Instagram post | GET |
|
List comments on a post | GET |
|
Get the unread comment count | GET |
|
Reply to a comment | POST |
|
Send a private reply to a comment | POST |
|
3.13 Account Credits API
Use the Account Credits API to check the credit balance of your Wati account.
Operation | Method | v3 endpoint |
Get account credits | GET |
|
3.14 Media and Token Management APIs
Use the Media APIs to retrieve media files and the token management API to block an API token.
Operation | Method | v3 endpoint | v1 endpoint |
Get media by file name | GET | — |
|
Get media by message ID | GET |
| — |
Block a token | POST | — |
|
Important: The v1 rotateToken endpoint blocks the specified token. It does not generate a replacement token. To create a new API token, go to Connector > API > Create API Token in your Wati account.
3.15 Model Context Protocol (MCP) Server
Wati provides a Model Context Protocol (MCP) server that allows AI tools and agents to connect directly to Wati capabilities.
For setup instructions, see the Wati developer documentation.
4. Additional Resources
Use the following resources to explore API endpoints, configure webhooks, and test API requests.
Wati API documentation — Explore API endpoints and request details.
Wati Webhooks Documentation — Learn how to configure webhooks and handle event notifications.
Wati Postman collection — Find a collection for testing Wati API requests using Postman.
5. Important API Notes
Keep the following points in mind when integrating with Wati:
Choose the right API version: Use v3 for new integrations wherever the required operation is supported. Legacy v1 and v2 endpoints remain available where documented.
Use the correct URL format: v3 endpoints do not include the tenant ID in the path. The documented v1 and v2 endpoints include
/{tenantId}/.Use the correct token scope: Create an API token with the permissions required for your v3 operations.
Check message delivery separately: A successful HTTP
200response from a message-sending endpoint does not confirm delivery. Use the relevant webhook event to track delivery or failure.Understand token rotation: The v1
rotateTokenendpoint blocks a token rather than creating a new one.
For endpoint-specific parameters, request formats, responses, and examples, refer to the Wati API documentation.
