WhatsApp Business API (Meta Cloud API)

Meta's Cloud-hosted WhatsApp Business API for sending template messages, free-form messages, media, and interactive messages to WhatsApp users from verified business phone numbers.

Evaluated Mar 07, 2026 (0d ago) vcurrent
Homepage ↗ Communication whatsapp meta messaging sms-alternative customer-notifications cloud-api business-messaging webhooks
⚙ Agent Friendliness
50
/ 100
Can an agent use this?
🔒 Security
78
/ 100
Is it safe for agents?
⚡ Reliability
71
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
--
Documentation
75
Error Messages
65
Auth Simplicity
65
Rate Limits
62

🔒 Security

TLS Enforcement
100
Auth Strength
80
Scope Granularity
58
Dep. Hygiene
75
Secret Handling
78

TLS enforced. System User tokens provide service-account-style auth without requiring user OAuth flows. Webhook payloads should be verified using the X-Hub-Signature-256 header (HMAC-SHA256 with app secret). WhatsApp end-to-end encryption protects message content in transit on the WhatsApp network; Meta's servers process metadata. No per-number scope isolation — one system user token can manage all phone numbers in the Business Account.

⚡ Reliability

Uptime/SLA
78
Version Stability
72
Breaking Changes
65
Error Recovery
68
AF Security Reliability

Best When

A business needs to send high-trust transactional notifications or handle customer support in markets where WhatsApp is the dominant messaging platform (Brazil, India, Europe).

Avoid When

Your use case involves unsolicited outreach, your users haven't opted in, or you need a conversational agent that maintains context across sessions longer than 24 hours.

Use Cases

  • Sending transactional notification messages (order confirmations, shipping updates, appointment reminders)
  • Running customer support chatbots that respond to inbound WhatsApp messages
  • Sending OTP/verification codes to WhatsApp as an SMS alternative
  • Broadcasting approved template messages to opted-in customer lists
  • Building conversational commerce flows for product inquiries and order placement

Not For

  • Unsolicited marketing messages — WhatsApp actively polices spam and bans phone numbers
  • Bulk cold outreach — requires prior opt-in and template pre-approval; violations ban the number
  • Multi-step conversational agents that need to maintain long dialog state — session windows are 24-hour
  • Any non-business use — personal WhatsApp accounts cannot use the Cloud API
  • Real-time low-latency applications — message delivery via WhatsApp adds variability

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
No
SDK
Yes
Webhooks
Yes

Authentication

Methods: bearer_token system_user_token
OAuth: No Scopes: No

System User Access Tokens via Meta Business Manager are the standard for server-to-server agent use. Tokens are long-lived but must be rotated manually or via API. No OAuth 2.0 user delegation needed for sending — the business owns the phone number. Token management requires Meta Business Manager access, which itself requires business verification. App Secret is needed for webhook signature validation.

Pricing

Model: usage
Free tier: Yes
Requires CC: Yes

Pricing is per conversation (24-hour window), not per message. A customer service session can include many messages within one billable conversation. Marketing conversations are the most expensive. Pricing varies dramatically by country — US rates differ from India or Brazil. Free tier of 1,000 conversations/month is meaningful for small deployments.

Agent Metadata

Pagination
cursor
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • 24-hour customer service window: after a user's last inbound message, you can only send free-form messages for 24 hours; after that, only approved templates are allowed
  • Template messages must be pre-approved by Meta before use — approval takes 1-3 days and templates can be rejected without clear explanation
  • Phone number quality rating affects throughput — sending too many messages that get blocked or reported degrades your rating and reduces your per-second limit
  • WhatsApp phone numbers are one-time use for cloud API — cannot migrate a number used in the on-premises BSP solution to Cloud API without downtime
  • Webhook delivery is not guaranteed at-least-once with strong ordering; agents must handle out-of-order and duplicate webhook events
  • Business verification in Meta Business Manager can take days to weeks and may require uploading business documents
  • Opt-in is the user's responsibility — businesses must collect and document user consent; WhatsApp audits this and can ban numbers for violations
  • Media messages require uploading media first to get a media ID, then sending the ID — direct URL sending is not supported for all media types

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for WhatsApp Business API (Meta Cloud API).

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-07.

6267
Packages Evaluated
26150
Need Evaluation
173
Need Re-evaluation
Community Powered