Last Updated: May 2026
The WhatsApp Business Notifications API lets you send transactional messages, alerts, and updates to users on WhatsApp programmatically. It is Meta's interface for businesses to deliver templated notifications at scale, including order confirmations, OTPs, shipping updates, appointment reminders, and account alerts.
With over 3 billion users globally (per Meta's 2025 platform reporting), WhatsApp is the most widely used messaging platform in the world. For products serving users in India, Brazil, Southeast Asia, the Middle East, and parts of Europe, WhatsApp is often the primary communication channel. Even in markets where SMS dominates (like the US), WhatsApp adoption is growing fast enough that ignoring it means leaving a high-engagement channel on the table.
But integrating WhatsApp for notifications is not like adding another email provider. You are working within Meta's rules: pre-approved templates, per-conversation pricing, quality ratings that throttle sending, and a 24-hour messaging window. This guide covers the full integration path, from Cloud API vs BSP selection, to template economics, production architecture, quality management, and how WhatsApp fits within a broader notification stack.
What Is the WhatsApp Business Notifications API?
The WhatsApp Business API is Meta's programmatic interface for medium and large businesses to send and receive messages at scale. It is distinct from the WhatsApp Business App (small business manual messaging) and the consumer app.
Key facts about the API as of 2026:
- Cloud API is the only path. Meta deprecated the on-premise API on October 23, 2025. All new integrations go through Cloud API, hosted on Meta's infrastructure.
- Template-based outbound messaging. Every business-initiated message must use a pre-approved template. Free-form messaging is only allowed within a 24-hour window after the user messages you first.
- Conversation-based pricing. You pay per conversation (24-hour window), not per message. Pricing varies by category and recipient country.
- Throughput: Cloud API throughput scales by messaging tier. Published BSP guides cite up to 500 messages per second once a number reaches the higher tiers.
- Rich media support: Unlike SMS, WhatsApp supports images, videos, documents, buttons, list messages, and interactive elements.
WhatsApp Cloud API vs BSP: Which Integration Path to Choose
You have two ways to connect to the WhatsApp Business API: integrate directly with Meta's Cloud API, or go through a Business Solution Provider (BSP) like Twilio, Gupshup, or 360dialog. This is the first decision you need to make.
The practical recommendation: if WhatsApp is your only messaging channel and you have engineering capacity, go direct. If WhatsApp is one channel among many (email, SMS, push), a BSP or a notification infrastructure platform that abstracts the BSP is more efficient. Integrating and maintaining the Cloud API directly, alongside separate integrations for email, SMS, and push, creates a maintenance burden that compounds with each channel.
Message Template Categories and What They Cost
Meta classifies every outbound template into one of four categories. The category determines pricing, delivery priority, and what rules apply. Meta also enforces strict template content guidelines. Promotional copy, coupons, discounts, and cold outreach are explicitly disallowed in template bodies, regardless of category.
US marketing restrictions
Meta has restricted marketing template delivery to US phone numbers, and the policy has shifted multiple times. Check Meta's current developer documentation before launching US promotional flows. Utility and authentication templates are not affected. For US-targeted promotional messaging, default to email, SMS, or push.
Pricing by country
Conversation rates vary significantly by country. Authentication rates in some emerging markets cost a fraction of authentication in Western Europe or North America. Marketing rates also vary widely by region (where marketing is available). Check Meta's rate card for your target markets before budgeting.
How conversations work
A conversation opens when you send a template and lasts 24 hours. All messages within that window (including follow-ups) are covered by one conversation charge. Service conversations (user-initiated) are free. If the user messages you first (e.g., via a Click-to-WhatsApp ad), a free 72-hour window opens.
How to Send WhatsApp Notifications in Production
Here is the end-to-end flow for sending WhatsApp notifications in a production system.
Step 1: Register and verify your business
Whether you go direct or through a BSP, you need a verified Meta Business account. Submit business documentation (registration number, address, website) through Meta's verification process. Verification takes anywhere from a few hours to several weeks.
Step 2: Set up a WhatsApp Business phone number
You need a dedicated number that is not registered on the WhatsApp consumer app. BSPs may provide one or help you port an existing number. For Cloud API direct, register through Meta Business Manager.
Step 3: Create and submit message templates
Each template requires a name, language, category (utility/authentication/marketing), and body text with variables in double curly braces (e.g., "Your order {{1}} has shipped"). Optional components include headers (text, image, document, video), footers, and buttons (quick reply or CTA). Submit through Meta Business Manager, the Cloud API, or your BSP's dashboard.
Step 4: Build the sending pipeline
- Event occurs in your system (order placed, payment processed, OTP requested).
- Backend triggers a notification with event type, recipient phone number (E.164 format), and template variables.
- Template is selected and populated with dynamic variables.
- API call to Cloud API or BSP sends the message.
- Webhook receives delivery status (sent, delivered, read, failed) for tracking and fallback logic.
Step 5: Handle delivery failures
Common failure reasons: user not on WhatsApp, phone offline, template rejected, rate limit hit, quality rating restriction. Each requires a different response. For transactional notifications like OTPs, configure automatic fallback to SMS within 30-60 seconds. For non-urgent messages, queue for retry.
WhatsApp Quality Rating: How to Avoid Getting Blocked
This is the section most WhatsApp API guides skip, and it is the one that causes the most production headaches. Meta assigns a quality rating to your WhatsApp Business phone number based on how users respond to your messages. If your rating drops low enough, Meta restricts your messaging tier or blocks you entirely.
How Meta calculates quality rating
Meta scores your number based on three signals: block rate (most heavily weighted), report rate (users marking you as spam), and read rate (low reads suggest irrelevance). Your rating shows in Meta Business Manager as Green (high), Yellow (medium), or Red (low).
What causes rating drops
- Sending to users who did not opt in: The most common cause. Imported phone lists lead to mass blocks.
- Irrelevant marketing messages: Promotional content to users who expected only transactional updates.
- Too-frequent messaging: Even opted-in users block you if you message too often.
- Category mismatch: Submitting marketing content as utility to get cheaper rates. Meta reclassifies it and penalizes you.
- Bad timing: Messages at 3 AM get blocked at higher rates than messages during business hours.
How to maintain a high quality rating
- Explicit opt-in: Collect WhatsApp opt-in separately from SMS consent. Be clear about message types.
- Respect user preferences: A notification preference center that lets users control WhatsApp categories per notification type is essential.
- Monitor block rates per template: Track which templates trigger blocks and revise or retire them.
- Start slow: Launch new templates with small batches. Monitor quality signals before scaling.
- Respect time zones: Send during the recipient's local business hours.
Recovering from a low rating
If your rating drops to Yellow or Red: pause all non-critical messaging, identify which templates caused blocks (per-template analytics in Business Manager), remove or rework them, resume at lower volume with best-performing templates, and wait for recovery over the rolling window (days, not hours). A Red rating can reduce your messaging tier or block business-initiated messages entirely. Recovery from a restriction takes weeks. Prevention is far cheaper.
WhatsApp as Part of a Multi-Channel Notification Stack
Most WhatsApp API guides treat WhatsApp as a standalone channel. In production, it is one channel within a broader notification infrastructure. The real question is not "how do I send a WhatsApp message?" but "how does WhatsApp fit into my delivery strategy alongside email, SMS, push, and in-app?"
Why WhatsApp alone is not enough
- Not everyone has WhatsApp: WhatsApp penetration in the US is far lower than in markets like India or Brazil. Your delivery strategy has to handle both.
- WhatsApp can fail: Network issues, rate limits, quality restrictions, or offline devices all cause delivery failure.
- Different messages suit different channels: OTPs work best on SMS (auto-fill support). Invoices work best on email (permanent record). Real-time alerts work best on push. WhatsApp is high engagement with rich media, but not always the right fit.
- User preferences vary: Some users want WhatsApp for everything. Others find it intrusive. Your system needs to respect individual channel preferences.
Fallback routing: WhatsApp to SMS
The most common multi-channel pattern: attempt WhatsApp first, wait 30-60 seconds for a delivery webhook, fall back to SMS if delivery fails, then email if SMS also fails. This is especially important for OTPs. WhatsApp OTP templates are cheaper than SMS in most markets, making WhatsApp-first the cost-optimal strategy. But the fallback must be automatic and fast. A user waiting 2 minutes for an OTP because your system is slow to detect failure will abandon the flow.
Smart channel routing
Beyond simple fallbacks, smart routing chooses the best channel per user per message type. Users with WhatsApp opt-in and high engagement get WhatsApp as primary. Users with opt-in but low engagement get WhatsApp with a shorter SMS fallback timeout. Users without opt-in skip WhatsApp entirely. Users who have opted out of WhatsApp for a specific category route to the next preferred channel. For high-frequency events, notification batching and digest logic can group multiple updates into a single WhatsApp message rather than sending one per event.
This routing logic belongs in a workflow engine, not your application code. Hardcoding channel selection means every routing change requires a deployment. A workflow engine lets you adjust rules without touching code.
WhatsApp open rates in context
You will see claims that WhatsApp has "98% open rates." The widely cited figure lacks a primary source. WhatsApp does not expose "opens" the same way email does. "Read receipts" require the user to have read receipts enabled, and many users turn them off. Independent measurement of opt-in marketing broadcasts puts read rates closer to the 60-70% range. That is still significantly higher than email's roughly 20% benchmark and comparable to push notifications, but it is not the near-universal 98% that marketing materials claim.
How SuprSend Integrates with WhatsApp
SuprSend connects to WhatsApp through BSP providers (Twilio, Gupshup, 360dialog) or directly via Meta's Cloud API. See the WhatsApp setup guide for the full integration path. Rather than replacing your BSP, we sit as a routing and orchestration layer on top of it. Here is what that means in practice.
Single API, every channel
One API call triggers notifications across WhatsApp, email, SMS, push, and in-app. Your backend sends one event payload. The workflow engine routes it to the right channels based on user preferences and workflow configuration.
WhatsApp template management
Create and manage WhatsApp templates in the SuprSend dashboard. Templates sync with your BSP and map to notification categories alongside email, SMS, and push templates for the same event.
Fallback routing built in
Configure WhatsApp as the primary channel with automatic SMS fallback if delivery fails. The workflow engine monitors delivery status and triggers fallback after a configurable timeout. No custom code required.
Per-tenant configuration
For multi-tenant products: different tenants can use different BSPs or WhatsApp Business numbers. Tenant A uses Twilio, Tenant B uses Gupshup, all managed in one workspace.
User preference management
Users opt in or out of WhatsApp per notification category through a preference center. The workflow engine respects these preferences without conditional logic in your code.
Delivery observability
Every WhatsApp notification is tracked end-to-end: sent, delivered, read, failed, with the specific failure reason. Logs show whether a message was delivered via WhatsApp or fell back to SMS, and why.
FAQ
What is the difference between WhatsApp Business App and WhatsApp Business API?
The Business App is a free mobile app for small businesses to chat manually. The Business API enables automated, template-based messaging at scale through programmatic integrations. You need the API for any production notification system.
How much does it cost to send WhatsApp notifications?
Pricing is conversation-based, not per-message. A conversation lasts 24 hours and is priced by category and recipient country. Authentication is cheapest, marketing most expensive. BSPs add a markup on top of Meta's rates.
Can I send WhatsApp marketing messages to US users?
Meta restricts marketing template delivery to US phone numbers, and the policy has shifted multiple times. Check Meta's current developer documentation before launching US promotional flows. Utility and authentication templates are not affected. Default to email, SMS, or push for US promotional content.
Do I need user opt-in to send WhatsApp business notifications?
Yes. Meta requires explicit opt-in for business-initiated messages. Collect it through your app, website, or WhatsApp conversation. Sending without opt-in causes high block rates and damages your quality rating.
What happens if my WhatsApp quality rating drops to Red?
Meta restricts your messaging tier, reducing how many unique users you can contact per day. In severe cases, your number gets blocked from business-initiated messages entirely. Recovery takes days to weeks of reduced-volume, high-quality sending.
How do I handle users who are not on WhatsApp?
Build fallback routing. Attempt WhatsApp first, fall back to SMS for time-sensitive messages or email for non-urgent ones if the number is not on WhatsApp. A workflow engine handles this automatically.
Can I send WhatsApp notifications without a BSP?
Yes. Integrate directly with Meta's Cloud API (you only pay Meta's per-conversation fees). The tradeoff: you handle setup, webhooks, and error handling yourself. BSPs simplify onboarding but add fees.
How fast are WhatsApp notifications delivered?
Cloud API throughput scales by messaging tier, with published BSP guides citing up to 500 messages per second once a number reaches the higher tiers. Delivery to online users happens within seconds. Offline users receive messages when their device reconnects. For OTPs, configure a 30-60 second timeout before SMS fallback.
TL;DR
- The WhatsApp Business Notifications API lets you send templated messages (order updates, OTPs, reminders) to users on WhatsApp programmatically. Use the Cloud API for direct integration or a BSP (Twilio, Gupshup, 360dialog) for faster setup.
- Every business-initiated message requires a pre-approved template. Templates are categorized as utility, authentication, marketing, or service, and each category has different pricing and rules.
- Marketing template delivery to US numbers is restricted by Meta. Check current policy before launching US promotional flows. Utility and authentication templates remain available globally.
- Quality rating determines your messaging capacity. High block/report rates from users drop your rating, which reduces your sending tier. Explicit opt-in, relevant content, and preference management are the best defenses.
- WhatsApp should not be your only delivery channel. Build fallback routing (WhatsApp to SMS to email) for critical messages, and use smart channel selection based on user preferences and engagement data.
- A notification workflow engine removes the need to hardcode channel routing. Configure WhatsApp alongside email, SMS, push, and in-app in one system, with automatic fallbacks and per-user preferences.
