WhatsApp and SMS
WhatsApp Cloud API vs Z-API vs Twilio
WhatsApp Cloud API, Z-API, Twilio side by side: price, free tier, who each one fits and when to skip it.
| Item | |||
|---|---|---|---|
| What it does | Meta's own API for sending and receiving WhatsApp messages from your app, hosted by Meta and billed per delivered message. | Brazilian REST API that connects a regular WhatsApp number to your app for a flat monthly fee, outside Meta's official API. | Developer API for SMS, WhatsApp, voice and email, with SDKs in every major language. |
| Best for | A SaaS that sends login codes and billing reminders on WhatsApp and wants the lowest official rate with no middleman fee. | An early MVP that needs to send free-form WhatsApp messages today, with no template approval and no per-message cost. | A SaaS selling in several countries that wants SMS and official WhatsApp behind one API and one bill. |
| Skip it if | You need to launch this week: every outbound template has to be approved by Meta and the business needs a verified Meta Business account. | WhatsApp is core to your product: it isn't Meta's official API, so the number can get banned and you lose the channel overnight. | Almost all your volume is WhatsApp: Twilio adds $0.005 to every message, sent or received, on top of Meta's rate. |
| Setup | Needs a developer. A first test message in an afternoon; plan 1 to 2 weeks for business verification and approved templates before real customers. | Needs a developer. Same day: no business verification or template approval; the first message goes out in minutes. | Needs a developer. First test message in an hour; plan 1 to 2 weeks for Meta approval on WhatsApp and up to 10 weeks if you want a US short code. |
| Price | Per delivered message to US numbers: $0.0034 for utility, authentication and service, $0.025 for marketing. | R$99.99/month per instance (number); R$89.99 each from 10 instances. | WhatsApp: Meta's rate + $0.005 per message sent or received. SMS to the US: $0.0083 per segment plus carrier fees. |
| What it costs in practice | SaaS with 500 US customers: 4 billing reminders each is 2,000 utility messages × $0.0034 = $6.80. Plus 1,500 support replies: 1,000 free, 500 × $0.0034 = $1.70. About $8.50/month, estimated. | One number for reminders and support: R$99.99/month whatever the volume, or R$1,079.89 paid yearly. A SaaS where 10 customers each connect a number pays 10 × R$89.99 = R$899.90/month, estimated. | SaaS sending 2,000 WhatsApp reminders and getting 500 replies: 2,500 × $0.005 = $12.50 to Twilio, plus Meta's rate on the 2,000 sent. Add 300 SMS codes × $0.0599 ≈ $18. About $30/month plus Meta, estimated. |
| Free plan | No monthly fee; 1,000 free service messages per number each month, then you pay per message. | 2-day free trial with no credit card; then a monthly fee per number. | Free trial with no credit card; after that you pay per message. |
| Price per message | $0.0034 (utility) to $0.025 (marketing), US | No per-message fee; R$99.99/month per number | Meta + $0.005 (WhatsApp); $0.0083 US SMS |
| Official WhatsApp API | Yes, it's Meta's own | No, unofficial alternative | Yes, official Meta partner |
| Channels | WhatsApp only | WhatsApp only | SMS, WhatsApp, voice, email |
| Open source | No: no | No: no | No: no |
| Before you build |
|
|
|
| Price checked | Checked on Oct 28, 2026 · official pricing | Checked on Oct 28, 2026 · official pricing | Checked on Oct 28, 2026 · official pricing |
Prices are read from each official pricing page on the date shown and can change. Always confirm before signing up.
Faundr
Picked your tools? Build it with AI, safely.
Faundr keeps your project’s memory, blocks what can’t be undone and tells you if it’s safe to launch, inside Claude Code and Codex.