WATI
Connect WATI to manage WhatsApp contacts and conversations, send and schedule templates, and run broadcasts and chatbots.
You end up pasting a Wati Bearer API token, and optionally the API endpoint URL that carries your numeric tenant id.
- Setup time
- 4 min
- Auth
- API credentials
- API base URL
- https://live-mt-server.wati.io/{tenantId}/api/v1
- Rate limits
- About 10 requests per 10 seconds for contact and message reads on every plan. Template and bulk-template sends allow 30, 60 or 100 requests per 10 seconds on Growth, Pro and Business respectively.
Before you begin
- A Wati account on the Growth, Pro or Business plan, since API access is not available on the trial-only tiers
- Admin access to the Wati dashboard so you can create tokens
- Some endpoints are plan-gated. /assignTeam, /updateChatStatus, /chatbots and /createCustomSegment need Pro, and /updateContactAttributesForMultiContacts needs Business
Get your credentials
Open Connector → API in the Wati dashboard
Sign in at live.wati.io and open Connector → API. Existing tokens are listed on the API Tokens page.
API Tokens
Tokens that authenticate calls to the Wati API on behalf of this workspace.
| Name | Scopes | Expires | Status |
|---|---|---|---|
| ZapierCreated Mar 4, 2026 | contacts:read | Sep 1, 2026 | Active |
| Old CRM syncCreated Jan 12, 2025 | contacts:read, contacts:write | Jan 12, 2026 | Expired |
Tokens are listed by name only. The value itself is never shown again after creation.
Generate a token with the scopes you need
Click Generate new token and name it PopMCP. Tick contacts:read, contacts:write and messagetemplate:read, plus the send scopes if PopMCP should send templates and run broadcasts.
Generate new token
Name the token, pick its scopes, and set an optional expiry.
Wati recommends rotating tokens every 6 months.
Copy the token into PopMCP
Copy the token from the dialog and paste it into PopMCP's Access token field. Copy it before closing the dialog, because Wati shows the value once.
API Tokens
PopMCP sends the value as Authorization: Bearer <token>. Paste the token without the word Bearer.
Copy your API endpoint URL (optional)
Click API Docs in the navigation menu and copy the API Endpoint URL. Paste it into PopMCP's API endpoint URL field.
API Docs
The endpoint and bearer token required to authenticate and make API calls.
- API Endpoint URL
- https://live-mt-server.wati.io/123456/
- Access Token
- Bearer eyJhbG****Zk3Q
- Tenant id
- 123456
The /123456/ segment is your tenant id and differs per Wati workspace.
Connect in PopMCP
Open your workspace, choose WATI in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| Access tokensecret | WATI dashboard → top nav API Docs (it shows your Bearer token), or the newer Connector → API → Create API Token (give it a name, pick scopes, and copy it; it's shown only once). Stored encrypted.Encrypted with AES-256-GCM on save and never shown again. |
| API endpoint URL (optional)text | Shown right next to the token on the WATI API Docs page. It contains your numeric tenant id (the /123456/ part). Only needed for the legacy v1/v2 operations (template authoring, WABA/phone management, webhooks); modern v3 operations work from the token alone. |
PopMCP verifies the credential against WATI immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
PopMCP shows the WATI connector as Connected and can list your WhatsApp contacts. A successful call returns HTTP 200, which means Wati accepted the message rather than delivered it, since delivery arrives by webhook.
Troubleshooting
401 Unauthorized
Why: Wati documents 401 as "No valid API key provided." Usually a truncated paste, or a token that has expired or been rotated.
Fix: Generate a fresh token under Connector → API and paste the whole value, without the word Bearer.
403 Forbidden
Why: Wati documents 403 as "The API key doesn't have permissions to perform the request."
Fix: Re-create the token with the missing scope ticked, or upgrade the plan if the endpoint is Pro or Business only.
The token was lost before it was copied
Why: Wati displays a token value once, at creation.
Fix: Generate a replacement token under Connector → API, or call POST /api/v1/rotateToken, then delete the old token.
404 Not Found on legacy v1 calls
Why: The API endpoint URL is missing or carries the wrong tenant id segment.
Fix: Copy the API Endpoint URL exactly as shown on the API Docs screen, including the /123456/ tenant segment.
429 Too Many Requests
Why: Wati rate-limits per 10-second window and per plan.
Fix: Slow the calls down, since contact and message reads are capped at 10 requests per 10 seconds on every plan. Wati invites customers to "reach out to us about your use case" for higher limits.
Reference
Twilio
Connect Twilio to send SMS/MMS/WhatsApp, place and control voice calls, search and buy phone numbers, run Verify (OTP), Lookups, Messaging Services, Conversations, Content templates, and Studio. All of Twilio from one connection.
WhatChimp
Connect WhatChimp to send WhatsApp messages and templates, manage subscribers and labels, and run chatbot flows.