Search "WhatsApp API pricing India" and you get a wall of provider pages, each explaining a different price. Here is the whole model in plain words — what Meta charges, what providers add, and where businesses quietly overpay.
The three layers of what you pay
Layer 1 — Meta's per-message charge. Since Meta moved from conversation-based to per-message pricing, every template message you send is billed by category:
| Category | Used for | India ballpark* |
|---|---|---|
| Marketing | Offers, festival pushes, win-back | Under ₹1 per message — the costliest category |
| Utility | Order updates, payment reminders, receipts | A small fraction of marketing (paise-level) |
| Authentication | OTPs, login codes | Similar paise-level range |
| Service replies | Answering a customer within 24h | Free |
*Mid-2026 ballpark. Meta revises rates periodically — treat these as orientation and confirm against Meta's current rate card before budgeting.
Layer 2 — your provider's markup. Most businesses access the API through a BSP or SaaS platform. Some pass Meta's rates through and charge a clean platform fee; others add a paisa-markup per message that looks tiny and compounds at volume. Ask the direct question: "Meta rate pass-through hai ya markup?"
Layer 3 — the platform/automation fee. The dashboard, templates, campaign tools, automation. This is where value differs wildly — and where task-metered tools quietly bill your retries and failures on top.
Where businesses actually overpay
- Marketing category used for transactional messages. An order update sent as a marketing template can cost several times the utility rate. Categorise correctly — at thousands of messages a month this is real money.
- Ignoring the free window. If the customer messaged you in the last 24 hours, your reply is free. Well-built automation tracks the window per contact and only uses paid templates when it must.
- Dirty lists. Sending marketing pushes to people who opted out doesn't just waste money — it invites blocks, which damage your number's standing. Opt-outs must auto-enforce.
- Paying for failures. If your automation platform meters "tasks", the send that failed and retried thrice still consumed your quota. (Our stance in Yantra's pricing: a failed run is never billed.)
A realistic monthly picture
Take a D2C brand doing 1,000 orders/month: ~3 utility messages per order (confirm, dispatch, delivered) is 3,000 paise-level messages — chai-budget territory. Add a monthly marketing push to 5,000 opted-in customers at under a rupee each, and the whole WhatsApp line item still sits comfortably under what one missed enquiry costs. The expensive part was never Meta's rates — it's the hours a human spends sending these by hand, which is the part worth automating.
Automation that respects your message budget
Window-aware sends, auto opt-outs, and failed runs never billed. Start free — 1,000 runs.
Start free