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.
WhatsApp Flows
Collect leads, bookings and feedback with multi-screen forms that open in WhatsApp. Build them in Wati with no code today. The Flows API is coming soon.
Part of the WhatsApp developer API.
Last updated
| Capability | How you use it | Status |
|---|---|---|
| Build a Flow in a drag-and-drop builder, from a template or from scratch | Wati app: Automation > WhatsApp Flows | Live |
| Send a Flow during a chatbot conversation | Chatbot builder: WhatsApp Flow node | Live |
| Send a Flow to a list of contacts | Attach it to a template, then send a campaign | Live |
| Save every answer to the contact | Custom attributes, created automatically | Live |
| Send a Flow template from your own code | Template send API, like any approved template | Live |
| Create and manage Flows by API | Flows API | Coming soon |
WhatsApp Flows are available on Pro and Business plans: Pro includes up to 2 Flows and Business up to 10. There are no Flows endpoints in the Wati API yet. Talk to us about your use case.
Lead forms, bookings and surveys that customers fill in without leaving WhatsApp.
WhatsApp Flows are forms that open inside a WhatsApp chat. A customer taps a button, moves through one or more screens of fields, dropdowns and date pickers, and sends the answers back without leaving the conversation.
Go to Automation > WhatsApp Flows. Start from the Lead Generation or Feedback Form template, or from scratch, then publish.
Add a WhatsApp Flow node to a chatbot, or attach the Flow to a template and send it in a campaign.
Each answer is saved to the contact as a custom attribute, so your team inbox and your next chatbot step can use it.
Ask for name, company and what the lead needs in one form. Your sales team sees the answers on the contact in the team inbox.
Lead Generation templateLet customers choose a service and a date for an appointment, a class or a callback, in a few taps.
Date pickerSend a short survey after a delivery or a support chat, and keep each score on the contact.
Feedback Form templatePick 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.
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
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.
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}/tagsList 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.
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.
Step-by-step setup is in the help center. How to create and use WhatsApp Flows
WhatsApp Flows are forms that open inside a WhatsApp chat. A customer taps a button in a message, fills in one or more screens and submits, without leaving the chat. Businesses use them for lead forms, bookings, appointments, surveys and feedback.
Go to Automation > WhatsApp Flows. Pick the Lead Generation or Feedback Form template, or start from scratch, and edit it in the drag-and-drop builder. You can add screens, dropdowns and a date picker.
Save it as a draft or publish it. A published Flow can't be edited, so keep it as a draft until it is ready.
Two ways. In a chatbot, add a WhatsApp Flow node and pick a published Flow. To reach a list of contacts, attach the Flow to a template, get the template approved and send it in a campaign.
Each answer is saved to the contact as a custom attribute, and you can see it in the team inbox.
Not yet. The Flows API is coming soon, and there are no Flows endpoints in the Wati API today. Share your use case with our team.
Until then, build Flows in the Wati app. If a Flow is attached to an approved template, you can send that template from your code like any other approved template.
WhatsApp Flows are available on Pro and Business plans: Pro includes up to 2 Flows and Business up to 10. Meta also asks for a verified Business Portfolio, a messaging limit of at least 2,000 and a high quality rating.
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.
Core messaging, template and contact endpoints are on every plan. Team assignment, chat status, chatbots and custom segments need Pro or Business. The docs list endpoint availability by plan.
Flows work in Wati today, with no code. The Flows API is coming soon. Share your use case with our team.