MessagingPermanent System User access tokenPricing verified 2026-10-06
WhatsApp Cloud API
Two-way WhatsApp in every lead's timeline: templates, media, documents, payment links, broadcasts, campaigns, order updates and workflow automation.
AProvider definition
- Provider
- WhatsApp Cloud API
- What it does
- WhatsApp CRM: two-way chat in every lead's timeline, templates, media, documents, campaigns and workflow automation. Meta's conversation/template fees are billed by Meta separately.
- Why we need it
- Two-way WhatsApp in every lead's timeline: templates, media, documents, payment links, broadcasts, campaigns, order updates and workflow automation.
- Used in
- WhatsApp · CRM · Commerce order updates · Workflows · AI Calling follow-ups
BAccount requirements
- Account type
- Meta Business Portfolio with a WhatsApp Business Account (WABA)
- Prerequisites
- A phone number not registered on the WhatsApp app (or migrated)
- Meta app with the WhatsApp product
- Verification
- Business Verification raises messaging limits and is needed for an Official Business Account.
CConnection method
- Authentication
- Permanent System User access token
- Where to enter it
- Your workspace: App → Integrations → Providers & API keysWorkspace owner or admin. Keys added here are used only by your workspace (AI keys here don't use plan credits).
Setup steps
- 1developers.facebook.com → your app → Add product → WhatsApp → set up the WABA and add your phone number.
- 2Business Settings → System users → create a system user, assign the app and WABA, generate a permanent token with whatsapp_business_messaging and whatsapp_business_management.
- 3WhatsApp → Configuration: set the webhook callback URL below and the verify token; subscribe to the messages field.
- 4Copy the Phone number ID and WABA ID; add a payment method in WhatsApp Manager.
- 5Enter the values in the application and send a test message.
DPermissions & API scopes
No OAuth scopes — access is controlled by the key or token itself. Restrict keys to the APIs listed in the setup steps where the provider allows it.
- whatsapp_business_messaging
- Send and receive messages.
- whatsapp_business_management
- Sync message templates and phone number details.
This list is generated from the scopes the application's code requests.
EFree vs paid
- Free account / free API access
- Messages users send you are free; replies within the 24-hour service window were free until 30 Sep 2026.
- Card or billing account required?
- Yes — a payment method in WhatsApp Manager for template messages.
- Paid plan / costs
- Per delivered message by category (marketing, utility, authentication) and recipient country. From 1 Oct 2026 service replies are also charged after 1,000 free service messages per number per month.
- Quota and usage limits
- Messaging tier limits (unique users per 24 h) rise with quality and verification.
- Production restrictions
- Outside the 24-hour window only approved templates can be sent.
Checked against official/current sources on 2026-10-06. Provider pricing changes often — re-check before publishing.
FSetup screenshots
Capture each step with real values masked. Save images as public/docs/integrations/whatsapp/1.png … 10.png and they appear here automatically.
- Screenshot to add1. Account login / creationThe provider's sign-in or sign-up page.
- Screenshot to add2. Developer consoleThe developer console or dashboard home.
- Not applicable3. Project / app creationCreating the app or project used for this integration.
- Not applicable4. API enablementThe API or product enabled for the project.
- Not applicable5. OAuth configurationConsent screen / OAuth settings with the redirect URIs.
- Screenshot to add6. API key / credentials creationCreating the key, secret or token (mask the value).
- Not applicable7. Permissions / scopesThe scopes or permissions requested or approved.
- Screenshot to add8. Billing / quota settingsBilling, credits or quota page.
- Screenshot to add9. Application connectionThe provider card in our application with fields filled (secrets masked).
- Screenshot to add10. Successful connectionThe green Test result or the connected account listed.
GApplication configuration
Never include real API keys, client secrets, access tokens or passwords in screenshots, tickets or documentation. Values below are field names and examples only.
| Field | Required | Example / default | Notes |
|---|---|---|---|
| Phone number ID | Yes | — | |
| WhatsApp Business Account ID | Optional | — | Needed to sync your approved message templates. |
| Permanent access token | Yes | •••••••• | Stored encrypted; shown masked after saving. |
| Webhook verify token | Yes | — | |
| App secret (signature check) | Optional | •••••••• | Stored encrypted; shown masked after saving. |
Paste these into the provider's console
- Webhook callback URL
https://api.socialmati.com/api/webhooks/whatsapp
HTesting
- 1Click Test on the WhatsApp card.
- 2Send yourself a template from WhatsApp → Templates, reply from your phone and check the reply appears in the inbox.
ITroubleshooting
| Problem | What to do |
|---|---|
| 131047 re-engagement message | More than 24 hours since the customer's last message — send an approved template. |
| Webhook verification failed | The verify token in the app must match the one in WhatsApp → Configuration. |
| Token expired | Use a System User permanent token, not a temporary user token. |
| Invalid credentials | The key or token is wrong, revoked or from another project. Create a new one and paste it again, then click Test. |
| Missing permissions | The key's project or role doesn't include this API. Grant access or create the key in the right project. |
| API not enabled | Enable the API/product for the project or app in the provider console and wait a few minutes. |
| Quota exceeded | Wait for the quota window to reset (see section E) or request a higher quota / add credits. |
| Account not eligible | Check the account requirements in section B (e.g. business/professional account, verified property, registered organisation). |
| Billing required | Add a payment method or prepaid credits on the provider account (see section E). |
JDisconnect & security
- Revoke access at the provider
- Delete or regenerate the system user token in Business Settings; remove the app from the WABA.
- Disconnect in the application
- App → Integrations → Providers & API keys → open the card → Remove / Disconnect. Connected accounts can be disconnected per brand.
- Rotate credentials
- Create the new key or secret first, paste it into the same card and Test, then delete the old one at the provider — no downtime.
- How credentials are stored
- Encrypted at rest with AES-256-GCM using the server's ENCRYPTION_KEY, shown masked after saving, never returned to the browser, and used only from the API server.
- What data the application can access
- Messages, media and delivery receipts for the connected number.

