Personal messages, sent at scale.
Pick an approved template and pass up to 10,000 recipients. Each person gets their own variables, and each result comes back by number.
One request sends an approved template to up to 10,000 people, each with their own details. Schedule it, estimate the cost first, then read results per recipient.
Prefer no code? Send a WhatsApp broadcast from Wati.
Each person gets their own name, order or date. Each result comes back by number.
Pick an approved template and pass up to 10,000 recipients. Each person gets their own variables, and each result comes back by number.
Inside the 24-hour window, send text, images, files, reply buttons and list pickers, with a typing indicator while you work.
Your store, booking or billing system sends an approved template when something changes. Customers tap a button or reply.
The message webhook brings each new message to your server. Reply with the send endpoints, or start a Wati chatbot on Pro and Business.
Webhooks push new messages, read receipts, clicks and failures to your URL. No polling.
Replies land in the Wati team inbox. Assign an operator, set status and add tags by API, so the right person picks it up.
Create and update contacts with custom attributes, then preview a segment before you message it.
List comments on your posts, reply in public or send a private reply. Instagram DMs work too: reply to active conversations by REST or through the Wati MCP server.
Link your WhatsApp number through Meta's Embedded Signup inside Wati.
Create an API token in Wati and give it only the scopes you need. Keep it on your server.
Send an approved template with one request. Then add a webhook to follow delivery.
Here is what goes into one request, and where each part shows up in the message.
The customer's WhatsApp number, with country code.
phone_number14155552671The name of a template that Meta has approved in your account.
template_nameorder_updateThe values for the blanks in the template, one per person.
custom_paramsname = Mayaorder_id = 10482Your API token, sent with every request. Keep it on your server.
Authorization: Bearer <token>A 200 means Wati accepted the message, with a broadcast_id. Delivered and read arrive later by webhook.
200broadcast_idThe message text and order_update are examples. Your approved template sets the wording.
The comment you are answering. You get its ID when you list a post's comments.
comment_idin the URL pathYour Instagram account connected to Wati.
channelThe person who wrote the comment, taken from the same comment.
userIduserNamePlain text up to 1,000 characters, or a template with buttons.
type = texttexttype = templateA 200 with ok set to true means the private reply went through. Use the same Authorization header as every other call.
ok: trueresult: successPOST /api/ext/v3/comments/{comment_id}/privateReply. The comment and reply text are examples. See the request in the docs
curl -X POST "https://live-mt-server.wati.io/api/ext/v3/messageTemplates/send" \
-H "Authorization: Bearer $WATI_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"template_name": "order_update",
"broadcast_name": "order_update_api",
"recipients": [
{
"phone_number": "14155552671",
"custom_params": [
{ "name": "name", "value": "Maya" },
{ "name": "order_id", "value": "10482" }
]
}
]
}' {
"success": true,
"broadcast_id": "broadcast_123456",
"recipients": [
{
"local_message_id": "local-msg-123",
"phone_number": "14155552671",
"errors": []
}
]
} https://mcp.wati.io/mcphttps://eu-mcp.wati.io/mcp{
"mcpServers": {
"wati": {
"url": "https://mcp.wati.io/mcp"
}
}
} claude mcp add --transport http wati https://mcp.wati.io/mcp Sign in with OAuth when your client asks. No API key goes in the config. For EU workspaces, use the EU URL. MCP docs
Connect through Meta's Embedded Signup. The WhatsApp Business Account is registered to your business.
Approval, quality and category changes arrive as webhooks, so you know before a send fails.
Up to 144 retries, every 10 minutes. If your endpoint keeps failing, Wati emails you.
Go too fast and you get 429 with a Retry-After header. Accepted messages wait in a queue.
A shared team inbox for the conversations your code should not answer alone.
v3 supports scoped tokens, so each integration gets only the access it needs.
Schedule a template send for later with one call. Wati sends it on time.
Estimate what a broadcast will cost before anything is sent.
| Field | Required | Notes |
|---|---|---|
template_name | Yes | An approved template in your account. List them with GET /messageTemplates. |
broadcast_name | Yes | Your own label for this send |
recipients | Yes | 1 to 10,000 people, each with a phone_number |
custom_params | Per recipient | Name and value pairs for the template's variables |
local_message_id | No | Your own ID, returned in the per-recipient results |
channel | No | The sending number, by name or number. Default channel if left out. |
From the v3 send endpoint schema. The response has success, a broadcast_id and per-recipient errors.
Start conversations with approved templates, now or scheduled.
Docs →GET/messageTemplatesPOST/messageTemplates/sendPOST/messageTemplates/scheduleRead campaign results and per-recipient status, and estimate cost first.
Docs →GET/broadcastsGET/broadcasts/{broadcast_id}/recipientsPOST/broadcasts/estimate-costReply with text, media or buttons inside the 24-hour window.
Docs →POST/conversations/messages/textPOST/conversations/messages/fileViaUrlPOST/conversations/messages/interactivePOST/conversations/typingIndicatorList your Wati chatbots and start one for a contact.
Docs →GET/chatbotsPOST/chatbots/startManage subscriptions and list the event types you can receive.
Docs →GET/webhooksGET/webhooks/event-typesPUT/webhooks/{id}Sync contacts and attributes from your CRM, then target segments.
Docs →POST/contactsPUT/contactsPOST/segments/evaluateAssign an operator, change status, add or remove tags.
Docs →PUT/conversations/{target}/operatorPUT/conversations/{target}/statusPOST/conversations/{target_conv}/tagsRead call logs, recordings, transcripts and summaries. Read-only.
Docs →GET/callsGET/calls/{call_id}/transcriptGET/calls/{call_id}/summaryList posts and comments, reply in public or in private, check permissions.
Docs →GET/posts/{post_id}/commentsPOST/comments/{comment_id}/repliesPOST/comments/{comment_id}/privateReplyGET/channels/{channel}/permissionsPaths are relative to https://live-mt-server.wati.io/api/ext/v3. Creating a webhook uses the legacy path POST /{tenantId}/api/v2/webhookEndpoints.
For AI agents, the Wati MCP server covers the same WhatsApp actions, and can reply to Instagram DMs and Messenger chats with text.
WhatsApp events only: there are no Instagram webhook events yet. BSUID versions of several events are also available. Webhook docs
Calls to send templates, depending on your plan (Growth, Pro or Business).
One template, up to 10,000 people, each with their own variables.
Text, media and buttons need an open customer service window. Outside it, send a template.
Wati tells you how long to wait. Accepted messages are processed in a queue.
| Endpoint | Growth | Pro | Business |
|---|---|---|---|
/addContact, /getContacts | 10 / 10 s | 10 / 10 s | 10 / 10 s |
/getMessages | 10 / 10 s | 10 / 10 s | 10 / 10 s |
/sendTemplateMessage | 30 / 10 s | 60 / 10 s | 100 / 10 s |
/sendTemplateMessages | 30 / 10 s | 60 / 10 s | 100 / 10 s |
Limits as published on Errors & Rate Limits, listed by endpoint name. The v1 bulk call takes up to 1,000 contacts. Core messaging, template and contact endpoints are on every plan. Team assignment, chat status, chatbots and custom segments need Pro or Business. Updating attributes for many contacts at once needs Business. Endpoint availability by plan. For higher limits, talk to Wati about your use case.
Up to 10,000 recipients per v3 send call. You send one approved template, and each recipient can have their own variables, like a name or order number. Template sends are limited to 30, 60 or 100 calls per 10 seconds, depending on your plan. Your number's Meta messaging limit and template quality still apply, so warm up a new number before large sends.
Yes. POST /messageTemplates/schedule sends at a time you choose, and POST /broadcasts/estimate-cost estimates the cost before anything is sent.
Call GET /broadcasts for your campaigns and GET /broadcasts/{broadcast_id}/recipients for per-recipient status. For real-time updates, subscribe to webhooks such as sentMessageDELIVERED_v2, sentMessageREAD_v2 and templateMessageFailed.
Give each recipient a local_message_id, such as your order ID. Wati returns it in the per-recipient results of the send call, next to any errors for that number.
Yes. Pass channel with the sending number's name or number. Leave it out to send from your default channel.
Less than you used to. AI app builders can write the API calls from plain-English instructions, and the examples on this page show each call.
You still need a WhatsApp number connected to Wati, an API token, and a template that Meta has approved before you can start a conversation. If an AI tool writes the code, check that your token stays on the server.
Contact and message-history calls are limited to 10 requests per 10 seconds on every plan. Template sends are limited to 30, 60 or 100 requests per 10 seconds on Growth, Pro and Business. When you hit a limit you get HTTP 429 with a Retry-After header. For higher limits, contact Wati.
On WhatsApp, free-form text, media and interactive messages need an open 24-hour customer service window. Outside that window, start the conversation with a template that Meta has approved.
The Business app is for manual chats on a phone, with up to 5 linked devices and broadcast lists capped at 256 contacts. The API connects WhatsApp to your own systems. You can send approved templates at volume, automate replies, receive webhooks and share one number across a team inbox.
Get access, connect your WhatsApp number in Wati and make your first call.