WhatsApp API Pricing 2026: Twilio vs Meta Per Message
Choosing a WhatsApp API provider is one of the most impactful decisions for your messaging infrastructure. The pricing models vary wildly, from per-message fees to flat monthly rates, from free tiers to enterprise minimums. This guide breaks down the real costs across the major providers so you can make an informed decision.
Pricing Models Explained
WhatsApp API providers generally use one of three pricing models:
- Per-message pricing: You pay for each message sent or received (Twilio, Meta Cloud API via BSPs)
- Per-template pricing: since July 1, 2025, Meta charges per delivered template message, passed through by BSPs
- Flat-rate pricing: Fixed monthly cost regardless of message volume (WSAPI, WAHA)
Provider Comparison
WSAPI
| Plan | Price | Messages | Meta Verification |
|---|---|---|---|
| Free trial | $0 for 14 days | Unlimited | Not required |
| Single | $5/mo | Unlimited | Not required |
| 5-pack | $4.75/mo per instance | Unlimited | Not required |
| 20-pack | $4.60/mo per instance | Unlimited | Not required |
WSAPI uses a flat-rate model with no per-message fees. You pay per WhatsApp instance (phone number), not per message, so the send-a-text-message endpoint costs the same on your first message and your millionth. This makes costs completely predictable.
Twilio
| Component | Cost |
|---|---|
| Twilio fee | $0.005 per message, inbound or outbound |
| Meta fee, utility templates | $0.0034 per message in the US, free inside the 24-hour service window |
| Meta fee, authentication templates | $0.0034 per message in the US, charged even inside the window |
| Free-form replies | No Meta fee, but only allowed inside the 24-hour service window |
| WhatsApp Business API access | Free, requires Meta Business verification |
Meta Cloud API (Direct)
| Component | Cost |
|---|---|
| Pricing model | Per delivered template message, since July 1, 2025 |
| Free-form replies inside the 24-hour window | Free |
| Utility templates inside the window | Free |
| Utility and authentication templates outside the window | $0.0034 per message in the US, varies by country |
| Hosting and infrastructure | You manage it, or use a BSP |
360dialog
| Component | Cost |
|---|---|
| Platform fee | From ~€49/mo per number |
| Meta per-message template fees | Passed through at cost |
| Setup | Requires Meta Business verification |
WAHA (Self-Hosted Open Source)
| Component | Cost |
|---|---|
| Software license | Free and open source, no paid tier needed since version 2026.6.1 |
| Server hosting | $5 to $50 per month (VPS) |
| Messages | Unlimited |
| Support | Community, with an optional paid community tier |
Cost Scenarios
These scenarios assume US recipients. Twilio and Meta now charge per message, so the real cost depends on your mix: free-form replies inside the 24-hour service window cost nothing on Meta's side, while templates sent outside it do. The range below goes from "all free-form replies" to "all utility templates".
| Volume | WSAPI | Twilio | Meta Cloud API (direct) |
|---|---|---|---|
| 100 messages/day (~3,000/month) | $5 | $15 to $25 | $0 to $10 |
| 1,000 messages/day (~30,000/month) | $5 | $150 to $252 | $0 to $102 |
| 10,000 messages/day (~300,000/month) | $5 | $1,500 to $2,520 | $0 to $1,020 |
Meta direct has no Twilio fee, but you run the infrastructure yourself or pay a BSP on top. WAHA stays at the cost of your server at every volume.
Hidden Costs to Watch For
- Meta Business verification: Required for Twilio, 360dialog, and Meta Cloud API. Can take days to weeks and may be rejected.
- Message template approval: Meta requires pre-approved templates for business-initiated messages. Approval is not guaranteed.
- Templates outside the 24-hour window: once a customer has not written to you for 24 hours, you can only reach them with pre-approved templates, and Meta charges for each one.
- Number porting: Moving your phone number between providers can cause downtime and may not be supported.
- Support tiers: Many providers charge extra for priority support. WSAPI includes email and ticket support on all paid plans.
Quick API Comparison
Here's what sending a simple text message looks like across providers:
curl -X POST https://api.wsapi.chat/messages/text \
-H "x-api-key: your-api-key" \
-H "x-instance-id: your-instance-id" \
-H "Content-Type: application/json" \
-d '{"to": "1234567890", "text": "Hello!"}'Decision Framework
Choose based on your priorities:
- Lowest cost at any volume → WSAPI (flat $5/mo, unlimited messages)
- Enterprise compliance requirements → Meta Cloud API or Twilio (official BSP channel)
- Maximum control, no vendor lock-in → WSAPI self-hosted or WAHA
- Existing Twilio infrastructure → Twilio (if you're already paying for their platform)
- Fastest time to first message → WSAPI (QR code scan, no verification needed)
Next Steps
- See WSAPI pricing details including volume discounts
- Self-hosted vs Cloud: deep dive into deployment models
- Send your first WhatsApp message with Python once you have picked a provider
- How WSAPI compares with Meta Cloud API if the official route is what you are weighing
- Get started in 5 minutes with the WSAPI quickstart guide