AiSensy
Connect AiSensy to send WhatsApp campaigns and messages, manage contacts and templates, and track campaign analytics.
You paste the project's API key from AiSensy's Manage screen. Pro-plan projects also hand you a Project ID and an App Password, which unlock the Project API tools.
App review before this connector works
Meta - not AiSensy - must approve the WhatsApp Business Account behind the key: the display name is reviewed, each message template is reviewed, and Facebook Business Manager verification is needed for full access.
- Typical wait
- AiSensy states "the majority of reviews are completed instantly (within 10 minutes) - only the Display Name can take max. 3-4 hours to get approved." Message templates typically clear in minutes to 24 hours, and Meta Business verification (needed to lift messaging limits) commonly takes 1-5 business days.
- Cost
- AiSensy's own approval steps are free: it runs a Free Forever plan that includes WhatsApp Business API access and the API key. Paid tiers on aisensy.com/pricing are listed in rupees - about Rs 2,500/month for the chatbot builder tier and Rs 3,500/month for the AI agent tier, cheaper on annual billing. Meta bills separately per conversation.
- Blocked until approved
- Sending anything. The API key is visible immediately, but the campaign endpoint (POST https://backend.aisensy.com/campaign/t1/api/v2) requires a live API campaign built on an approved template attached to a verified WABA - until the display name and template pass Meta review, calls fail or messages are never delivered.
- Works meanwhile
- Create the AiSensy account, connect a dedicated phone number not already on WhatsApp, copy the API key from Manage > API Key, draft templates, and wire up the integration code.
Where to apply: In the AiSensy dashboard, run the WhatsApp Business API application flow (embedded Meta signup) - it asks for your Facebook Business Manager, a display name, and a dedicated number. Templates are submitted under the Template Message section; Business verification is done in Meta Business Suite > Business Settings > Security Centre.
- The phone number must not be registered to any existing WhatsApp or WhatsApp Business app account - migrating requires deleting it there first.
- Display names that do not match the business or website get rejected; Meta expects the name to reflect a real, verifiable brand.
- Restricted categories (alcohol, illegal goods, unsafe supplements and the rest of WhatsApp's Commerce Policy) are refused outright.
- Marketing templates are rejected for promotional wording, missing variable samples, or placeholder text left in the body.
- Without Business verification the number stays on the low messaging tier (1,000 unique customers/day), which reads like an API failure at scale.
- Setup time
- 6 min
- Auth
- API credentials
- API base URL
- https://backend.aisensy.com
- Rate limits
- Not documented publicly. Throughput is governed by your WhatsApp Business API messaging tier and plan, for example 40 messages per second on higher AiSensy plans.
Before you begin
- An AiSensy project with a verified WhatsApp Business API number (a live, approved WABA)
- At least one approved WhatsApp template message. API campaigns can only send approved templates
- A live API campaign, because the Send Campaign tool sends by campaign name
- A Pro plan if you want the Project API tools, plus a request to AiSensy support for the Project ID and App Password. Basic plans expose only the API key
- Direct API and Partner API access are granted by AiSensy on request. Skip those fields unless AiSensy has enabled them for you
Get your credentials
Sign in and switch to the right project
Go to app.aisensy.com and sign in. Use the project switcher above the sidebar to select the project holding the WhatsApp number you want PopMCP to use.
Dashboard
Northwind Retail / +91 98765 ***21
| WhatsApp number | Quality | Messaging tier | Status |
|---|---|---|---|
| +91 98765 ***21Northwind Retail | High | 10,000 / 24h | Connected |
Check the project name in the switcher before copying anything.
Launch a live API campaign
Open Campaigns, click Launch and choose API Campaign. Pick your approved template, set the campaign live, and copy its name exactly.
Campaigns
API campaigns are the only campaigns the send endpoint can trigger.
| Campaign | Template | Type | Status |
|---|---|---|---|
| order_updatesCreated Mar 4, 2026 | order_shipped_v2 | API | Live |
| cart_recoveryCreated Feb 18, 2026 | cart_reminder_v1 | API | Paused |
PopMCP references the campaign name verbatim.
Copy the credentials from Manage
Click Manage in the sidebar, then API Keys. Copy the API Key. On a Pro plan also copy the Project ID and App Password that AiSensy support issued for the project.
API Keys
Credentials for the Northwind Retail project.
- API Key
- eyJhbG****Xq7T
Basic plans show only the API Key. Pro plans add the Project ID and App Password, which AiSensy support issues on request.
Paste the values into PopMCP
Put the key in API key. Fill App Password and Project ID only if your project showed them, and leave Business ID, Direct API token, Partner API key and Partner ID empty.
Connect in PopMCP
Open your workspace, choose AiSensy in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| API keysecret | Dashboard → open your project → Manage → API Key → Generate/Copy. Powers the Send Campaign tool (the key is sent in the request body, no header). Stored encrypted; used server-side only.Encrypted with AES-256-GCM on save and never shown again. |
| App Password (optional)secret | Unlocks the Project API (messaging, contacts, templates, campaigns, webhooks, catalog, media). Sent as the X-AiSensy-Project-API-Pwd header. Set it on the project's API/Manage screen.Encrypted with AES-256-GCM on save and never shown again. |
| Project ID (optional)text | Required alongside the App Password for every Project API tool; it scopes the calls to your project. Find it in the dashboard URL or project settings. |
| Business ID (optional)text | Only needed for the Get Business Profile project tool. |
| Direct API token (optional, advanced)secret | Enables the Direct API (WhatsApp Cloud-API-style messaging, flows, media, WABA, phone numbers, payments). Provide username:password:projectId; we base64-encode it and mint the bearer JWT automatically. Requires Direct API access from AiSensy.Encrypted with AES-256-GCM on save and never shown again. |
| Partner API key (optional, advanced)secret | Enables the Partner/white-label API (manage client projects, billing, plans, WABA onboarding). Sent as the X-AiSensy-Partner-API-Key header. For AiSensy partners only.Encrypted with AES-256-GCM on save and never shown again. |
| Partner ID (optional, advanced)text | Required alongside the Partner API key for every Partner API tool. |
PopMCP verifies the credential against AiSensy immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
PopMCP shows AiSensy as Connected, and a test send through your live API campaign delivers a WhatsApp message to the destination number you supply.
Troubleshooting
Campaign not found or invalid campaign
Why: The campaign name does not match, or the API campaign was never set live.
Fix: Open Campaigns and copy the name exactly as listed, confirming its status is Live.
Sends fail after working fine
Why: Someone regenerated the project's API key, which invalidates the previous one.
Fix: Copy the new key from Manage, API Keys, and reconnect PopMCP.
No Project ID or App Password on the API Keys screen
Why: The project is on the Basic plan, which exposes only the campaign API key, or the Pro credentials have not been issued yet.
Fix: Move the project to Pro, then ask AiSensy support over Live Chat to issue the Project ID and App Password.
Project API tools return unauthorized
Why: App Password or Project ID missing, mismatched, or belonging to a different project.
Fix: Re-copy both from the same project's API Keys screen. They must be supplied as a pair.
Template rejected on send
Why: The template is not approved by Meta, or the variable count does not match the template body.
Fix: Check the template's status under Templates and pass exactly as many parameters as the body defines.