WhatsApp Business API Setup Guide

April 9, 2026

18 min read

Nikita Jerschow

WhatsApp Business API Setup Guide — Complete Developer Walkthrough (2026)

The WhatsApp Business API lets companies send and receive messages programmatically at scale through the WhatsApp network. This guide walks through every step of setting up the Cloud API via Meta's developer platform, covers message templates, pricing changes in 2025-2026, and explains why US-focused businesses should seriously evaluate iMessage and RCS as higher-engagement alternatives before committing to WhatsApp infrastructure.

What is the WhatsApp Business API?

WhatsApp offers three distinct products for businesses, and understanding the differences is critical before you commit engineering resources to an integration.

WhatsApp Messenger is the consumer app used by over 2 billion people worldwide. It is designed for personal conversations and explicitly prohibits commercial use in its terms of service. You cannot use it to send business messages at scale.

WhatsApp Business App is a free mobile application built for small businesses. It supports a business profile (address, description, hours), quick replies, labels for organizing chats, and a product catalog. However, it is limited to a single device (with up to four linked devices), requires manual operation, and has no API access. It works well for a local shop handling a dozen conversations a day, but it does not scale.

WhatsApp Business API (now called the WhatsApp Business Platform) is the programmatic interface for medium and large businesses. It allows you to send and receive messages via HTTP requests, integrate with CRMs and support desks, automate conversations with chatbots, and handle thousands of concurrent threads. There is no user interface included — you build your own or use a third-party dashboard.

Until October 2025, the API came in two flavors:

On-Premises API — you hosted the WhatsApp docker containers on your own infrastructure. Meta officially sunset this in October 2025. All On-Premises deployments were required to migrate to Cloud API.
Cloud API — Meta hosts the infrastructure. You make REST API calls to graph.facebook.com. This is now the only supported option and the one covered in this guide.

The Cloud API is free to access (no license fee), but you pay per message sent based on the conversation category. More on pricing later.

The Business Solution Provider (BSP) model

Historically, WhatsApp required businesses to go through a Business Solution Provider (BSP) — companies like Twilio, MessageBird, Vonage, Infobip, and Gupshup that had direct partnerships with WhatsApp. BSPs provided the API access, managed the phone number registration, and offered their own dashboards and SDKs on top of the raw API.

Since Meta launched the Cloud API, direct integration is available to any business with a Meta Business Account. You no longer need a BSP. However, many companies still choose BSPs for the additional tooling they provide: multi-agent routing, analytics dashboards, no-code template builders, and compliance features. BSPs also charge a markup per message — typically $0.002-$0.005 on top of Meta's base rate — so the tradeoff is convenience versus cost.

If you are a developer building a direct integration, the Cloud API is the straightforward path. If your team wants a managed solution without writing webhook handlers and template management code, a BSP may make sense.

One thing to keep in mind: the WhatsApp Business API is fundamentally a global messaging platform. Its architecture reflects markets where WhatsApp is the dominant communication channel — India, Brazil, Indonesia, Germany, Nigeria, Mexico. The template approval system, 24-hour customer service window, and conversation-based pricing all make sense in markets where 90%+ of the population uses WhatsApp daily. Whether these design choices work well for your US-focused business is a question this guide will help you answer.

WhatsApp Business API setup — step by step

Setting up the WhatsApp Cloud API involves eight steps. The process typically takes 1-3 business days, assuming your business verification goes through without manual review.

Step 1: Create a Meta Business Account and verify your business

Go to business.facebook.com and create a Meta Business Account if you do not already have one. You will need:

Your legal business name (must match official registration documents)
Business address and phone number
A business website URL
Tax ID or business registration number

After creating the account, submit business verification. Meta will ask you to upload documents such as a business license, utility bill, or tax certificate. Verification typically takes 2-5 business days, but can take longer if Meta requests additional documentation. You cannot send messages to customers until verification is approved.

Step 2: Set up a Meta Developer account

Navigate to developers.facebook.com and register as a Meta developer using the same account linked to your Meta Business Account. Accept the developer terms of service and complete any identity verification prompts. This is straightforward and usually completes in minutes.

Step 3: Create a WhatsApp Business app in the Meta Developer dashboard

In the Meta Developer dashboard, click "Create App." Select Business as the app type. Give your app a name (e.g., "MyCompany WhatsApp") and associate it with your verified Meta Business Account.

Once the app is created, navigate to the app dashboard and click "Set Up" under the WhatsApp product card. This adds the WhatsApp API to your app and provisions a test phone number with limited free messages for development.

Step 4: Add a phone number

In the WhatsApp section of your app, go to "Phone Numbers" and click "Add Phone Number." This number will be your business sending number — the number customers see when you message them.

Critical requirement: the phone number you add must not be currently registered on any WhatsApp account (consumer or business app). If it is, you must first delete the WhatsApp account associated with that number. You can use a landline, a mobile number, or a toll-free number. Meta will verify ownership via SMS or voice call in the next step.

Step 5: Verify the phone number via SMS/voice OTP

Meta sends a 6-digit verification code to your phone number via SMS or voice call (your choice). Enter the code in the developer dashboard. Once verified, the number is registered as a WhatsApp Business API number and can no longer be used with the WhatsApp consumer or Business app.

Step 6: Generate a permanent access token

The temporary token Meta provides in the developer dashboard expires after 24 hours. For production use, you need a permanent token:

Go to your Meta Business Account > Business Settings > System Users
Create a System User (Admin role recommended)
Assign the System User to your WhatsApp Business app
Grant the whatsapp_business_messaging and whatsapp_business_management permissions
Click "Generate Token" — this token does not expire unless revoked

Store this token securely. It provides full API access to send messages, manage templates, and configure webhooks.

Step 7: Configure webhooks for inbound messages

To receive messages from customers, you need a webhook endpoint. Meta sends POST requests to your URL when messages arrive, when messages are delivered/read, and when message status changes.

Your webhook must handle two things: the initial verification challenge (GET request) and incoming event notifications (POST requests). Here is a minimal Node.js/Express implementation:

const express = require('express');
const app = express();
app.use(express.json());

const VERIFY_TOKEN = process.env.WHATSAPP_VERIFY_TOKEN;
const ACCESS_TOKEN = process.env.WHATSAPP_ACCESS_TOKEN;

// Webhook verification (Meta sends a GET request to verify your endpoint)
app.get('/webhook', (req, res) => {
  const mode = req.query['hub.mode'];
  const token = req.query['hub.verify_token'];
  const challenge = req.query['hub.challenge'];

  if (mode === 'subscribe' && token === VERIFY_TOKEN) {
    console.log('Webhook verified');
    return res.status(200).send(challenge);
  }
  return res.sendStatus(403);
});

// Incoming messages and status updates
app.post('/webhook', (req, res) => {
  const body = req.body;

  if (body.object === 'whatsapp_business_account') {
    body.entry?.forEach(entry => {
      entry.changes?.forEach(change => {
        if (change.field === 'messages') {
          const messages = change.value.messages;
          messages?.forEach(msg => {
            console.log(`From: ${msg.from}, Type: ${msg.type}`);
            if (msg.type === 'text') {
              console.log(`Text: ${msg.text.body}`);
            }
          });

          const statuses = change.value.statuses;
          statuses?.forEach(status => {
            console.log(`Message ${status.id}: ${status.status}`);
            // status.status: 'sent', 'delivered', 'read', 'failed'
          });
        }
      });
    });
  }

  res.sendStatus(200);
});

app.listen(3000, () => console.log('Webhook server running on port 3000'));

In the Meta Developer dashboard, go to your WhatsApp app > Configuration > Webhook. Enter your public HTTPS URL (e.g., https://yourdomain.com/webhook) and the verify token you chose. Subscribe to the messages field. Meta will send a GET request with the challenge — your server must respond correctly to complete setup.

Step 8: Apply for Official Business Account (green checkmark) status

The green checkmark badge next to your business name in WhatsApp increases trust and may improve message deliverability. To apply:

Go to WhatsApp Manager in Meta Business Suite
Navigate to Account Tools > Phone Numbers
Select your number and click "Submit Request" under Official Business Account

Requirements include a verified Meta Business Account, a notable brand presence (press coverage, significant following), and consistent messaging quality. Approval is not guaranteed and typically takes 1-4 weeks. Many legitimate businesses operate without the green checkmark.

Sending your first template message

Once setup is complete, you can send a template message via the Cloud API. Here is a curl example using the hello_world default template:

curl -X POST "https://graph.facebook.com/v19.0/YOUR_PHONE_NUMBER_ID/messages" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "messaging_product": "whatsapp",
    "to": "14155551234",
    "type": "template",
    "template": {
      "name": "hello_world",
      "language": {
        "code": "en_US"
      }
    }
  }'

Replace YOUR_PHONE_NUMBER_ID with the phone number ID from your dashboard (not the phone number itself — it is a numeric ID visible in WhatsApp Manager under Phone Numbers) and YOUR_ACCESS_TOKEN with your permanent System User token.

A successful response returns a JSON object with a messages array containing the id of the sent message. You can use this ID to correlate delivery receipts from your webhook. If the message fails, the response includes an error object with a code and human-readable description — common errors include invalid phone number format (must be country code + number without the leading +), expired access token, and unapproved template name.

Rate limits: The Cloud API enforces rate limits based on your messaging tier. New accounts start at Tier 1 (1,000 unique customers per 24 hours). As you send messages without quality issues, Meta automatically upgrades you to Tier 2 (10,000), Tier 3 (100,000), and Tier 4 (unlimited). Each tier upgrade requires a minimum of 48 hours at the current tier with a green quality rating. These limits apply to the number of unique recipients, not the total number of messages — you can send multiple messages to the same customer without hitting the tier cap.

WhatsApp message types and templates

WhatsApp Business API messages fall into four categories, each with different rules, approval requirements, and pricing.

1. Marketing messages

Promotional content: product launches, discount offers, re-engagement campaigns, newsletters. These require pre-approved templates and have the highest per-message cost. Important: Meta paused marketing message templates for US phone numbers in April 2025. As of April 2026, this restriction remains in effect. US businesses cannot send marketing messages via WhatsApp.

2. Utility messages

Transactional notifications directly related to a prior transaction or request: order confirmations, shipping updates, appointment reminders, payment receipts, account alerts. These require pre-approved templates but are less restricted than marketing messages and cost less per message.

3. Authentication messages

One-time passwords (OTPs) and verification codes. These use a special Meta-provided template format with a built-in OTP button. Authentication messages have the lowest per-message cost and are subject to specific rate limits to prevent abuse.

4. Service messages (free-form within 24-hour window)

When a customer messages your business first (or replies to a message), a 24-hour customer service window opens. Within this window, you can send free-form text messages without using a pre-approved template. This is designed for conversational customer support. Once the 24-hour window closes, you must use a template to re-initiate conversation.

Template approval process

Templates are submitted through WhatsApp Manager or the Management API. Each template includes:

Name — a unique identifier (e.g., order_confirmation_v2)
Category — Marketing, Utility, or Authentication
Language — templates must be submitted per language
Body text — the message content with variable placeholders using {{1}}, {{2}} syntax
Header (optional) — text, image, video, or document
Footer (optional) — short text line
Buttons (optional) — call-to-action or quick-reply buttons

Meta reviews templates within minutes to 24 hours. Common rejection reasons include vague content, misleading language, missing opt-out instructions for marketing, and templates that could be used for spam. Rejected templates can be edited and resubmitted.

Quality rating system

Meta assigns each template a quality rating based on user feedback:

Green — high quality, no issues. Full sending capability.
Yellow — medium quality. Some users have blocked or reported your messages. You receive a warning.
Red — low quality. Your sending limits may be reduced, and the template may be automatically paused. If quality does not improve, the template can be permanently disabled.

Quality ratings are calculated from signals including block rates, report rates, and reply rates. Sending irrelevant or too-frequent messages degrades your quality score. Once a template is paused for low quality, you must create a new template rather than reusing the paused one.

This quality management system is one of the more operationally demanding aspects of the WhatsApp API. Unlike SMS or iMessage where your messages simply deliver (or get carrier-filtered in the case of SMS), WhatsApp requires ongoing monitoring of each template's quality score. A single marketing campaign that triggers too many blocks can cascade — dropping your quality from Green to Red, reducing your sending limits, and potentially pausing your most important templates. For teams accustomed to email-style batch sends, this feedback loop requires a meaningful shift in how you think about message frequency and relevance.

Template best practices:

Include clear opt-out instructions ("Reply STOP to unsubscribe") in all marketing templates
Personalize templates with the recipient's name and relevant context — generic blast messages get blocked more often
Limit frequency to 2-4 messages per contact per month for marketing; transactional messages have more tolerance
Monitor quality ratings daily during new campaign launches and pause sending immediately if you see a Yellow warning
Create templates in multiple languages if you serve a multilingual audience — sending English templates to Spanish-speaking users increases block rates

WhatsApp Business API pricing (2026)

WhatsApp's pricing model changed significantly in July 2025 when Meta shifted from per-conversation pricing to per-message pricing. Under the old model, you paid for a 24-hour conversation window regardless of how many messages were exchanged. Under the current model, each business-initiated message incurs a charge.

Current per-message rates (US numbers)

Category	Cost per message (USD)	Status
Marketing	~$0.025	Paused for US numbers since April 2025
Utility	~$0.015	Active
Authentication	~$0.0135	Active
Service (within 24h window)	Free	Active

Rates vary by country. Messages to India cost approximately $0.0042 (utility) — significantly cheaper than US rates. Messages to Brazil cost approximately $0.0080 (utility). Meta publishes a full rate card on the WhatsApp Business pricing page.

Additional cost considerations:

BSP markup: If you use a Business Solution Provider, expect an additional $0.002-$0.005 per message on top of Meta's rate.
Phone number hosting: The Cloud API does not charge for hosting your number. Some BSPs charge a monthly fee ($10-$100/month) for number management.
No volume discounts: Unlike most messaging APIs, WhatsApp does not offer tiered pricing for high-volume senders as of 2026.

How this compares to Sendblue

Sendblue's pricing is based on a monthly subscription with included message credits, starting at $29/month for the Starter plan. iMessage, RCS, and SMS are all sent through the same endpoint with no template approval overhead. There are no per-category pricing tiers, no 24-hour window restrictions, and no risk of template pauses degrading your sending capability. For US-focused businesses, the total cost of ownership is typically lower with Sendblue when you factor in the engineering time saved on template management, webhook complexity, and the Meta business verification process.

WhatsApp API limitations for US businesses

WhatsApp is the dominant messaging platform globally, but its position in the US market is materially different from markets like India, Brazil, or Europe. Before investing engineering resources in a WhatsApp integration for a US audience, consider these limitations:

Low US penetration

Approximately 32% of US smartphone users have WhatsApp installed, compared to 95%+ in India, 93% in Brazil, and 85%+ across most of Western Europe. In the US, the native Messages app (iMessage for iPhone, Google Messages for Android) is the default — most Americans do not check WhatsApp regularly for business communications. By contrast, 57% of US smartphone users are on iPhone with iMessage enabled.

Marketing message pause

Meta paused all marketing message templates for US phone numbers in April 2025. Over a year later, there is no announced timeline for resumption. This means you cannot use WhatsApp for promotional outreach, re-engagement campaigns, product announcements, or sales messaging to US customers. Only utility (transactional) and authentication (OTP) messages are permitted.

24-hour customer service window

Outside of the 24-hour window after a customer's last message, you can only send pre-approved template messages. You cannot send a free-form follow-up to a customer who messaged you yesterday. This creates friction in sales workflows where conversations naturally span multiple days. iMessage and SMS have no such restriction — you can message any opted-in contact at any time.

Template approval delays

While most templates are reviewed within minutes, complex templates or templates from newly verified accounts can take 24+ hours. If a template is rejected, the edit-and-resubmit cycle adds more delay. During a product launch or time-sensitive campaign, this review process can be a bottleneck. Sendblue requires no message approvals — you send whatever content you need immediately.

No blue bubble engagement advantage

iMessage messages appear as blue bubbles on iPhone — a visual signal that recipients recognize and trust. Blue bubble messages have no spam filtering, appear in the native Messages app without requiring a separate download, and consistently achieve 30-45% response rates in business use cases. WhatsApp messages in the US achieve approximately 4% response rates — comparable to email and significantly below iMessage.

Engagement comparison

Metric	WhatsApp (US)	iMessage (US)
US penetration	~32%	~57% (iPhone users)
Open rate	~98% (for users who have the app)	~98%
Response rate	~4%	30-45%
Spam filtering	User reports affect quality score	None
Marketing allowed (US)	Paused since April 2025	Yes, no restrictions
Template approvals	Required for all outbound	Not required
Time window restrictions	24-hour service window	None

WhatsApp vs iMessage vs SMS vs RCS for US business messaging

Choosing the right messaging channel depends on your audience geography, use case, and technical requirements. Here is a comprehensive comparison for US-focused businesses:

Feature	WhatsApp	iMessage	SMS	RCS
US reach	~32% of smartphone users	~57% (iPhone users)	~100% (all phones)	~90%+ (Android + iOS 18)
Response rate (US)	~4%	30-45%	~6%	~10-15%
Read receipts	Yes	Yes	No	Yes
Typing indicators	Yes	Yes	No	Yes
Rich media	Yes	Yes	MMS (compressed)	Yes
Branded sender	Business profile	No	No (10DLC required)	Yes (verified)
Registration required	Meta Business verification + phone number	None (via Sendblue)	10DLC/A2P registration	RBM verification
Template approvals	Yes (all outbound)	No	No	Yes (for RBM)
Cost per message	$0.0135-$0.025	Included in plan	$0.007-$0.02	Included in plan
Carrier/spam filtering	Quality score system	None	Heavy A2P filtering	Moderate
24h window restriction	Yes	No	No	No
Setup time	3-7 days	Minutes	1-3 days (10DLC)	1-2 weeks (RBM)
Marketing in US	Paused	Unrestricted	Allowed (with consent)	Allowed

For US-market businesses, the data makes a clear case: iMessage should be the primary channel for iPhone users (57% of the US market), with SMS and RCS providing fallback coverage for Android users. This combination — which Sendblue handles from a single API endpoint — reaches 100% of US phone numbers with the highest possible engagement on each device type.

WhatsApp becomes the right choice when your audience is primarily international, particularly in markets where WhatsApp penetration exceeds 90%. A company selling to customers in India, Brazil, or Western Europe should absolutely integrate WhatsApp. But routing US customers through WhatsApp when iMessage is available leaves significant engagement on the table.

Consider the end-user experience: when a US iPhone user receives an iMessage from your business, it appears in their native Messages app as a blue bubble — the same format they use with friends and family. It feels personal and immediate. When that same user receives a WhatsApp message, they have to open a separate app they may check infrequently (if they have it installed at all), navigate to an unfamiliar business conversation, and engage in an app they do not associate with commercial interactions in the US context. The engagement gap is not surprising when you consider this difference in native integration.

When WhatsApp Business API makes sense

Despite its limitations for US audiences, the WhatsApp Business API is the right tool for several specific use cases. Here is an objective assessment of when to invest in a WhatsApp integration:

International audience with high WhatsApp penetration

If your customers are in India (95%+ WhatsApp penetration), Brazil (93%), Indonesia (87%), Germany (85%), or most of Latin America, Africa, and Southeast Asia, WhatsApp is likely the highest-engagement channel available. In these markets, WhatsApp is the default messaging app — the equivalent of what iMessage is in the US. Customer support via WhatsApp in these regions gets open rates above 95% and response rates of 25-40%, rivaling iMessage performance in the US.

Inbound customer support

The 24-hour service window is designed for reactive support. When a customer messages your business with a question, the free-form reply capability within the window makes WhatsApp an effective support channel. The rich media support (send PDFs, images, location pins) makes it especially useful for troubleshooting and order-related inquiries. If your support volume is primarily inbound and you have international customers who prefer WhatsApp, this is a strong use case.

Transactional notifications

Utility messages — shipping confirmations, appointment reminders, payment receipts, flight status updates — work well on WhatsApp even in the US. These are messages the recipient explicitly expects, so open rates are high and quality scores stay green. If you are already sending transactional SMS and want richer formatting (images, buttons, structured layouts), WhatsApp utility templates provide that upgrade for the subset of your users who have WhatsApp.

Authentication and OTPs

WhatsApp authentication messages are a viable alternative to SMS-based OTP for users who have WhatsApp installed. The delivery is more reliable than SMS in some international markets where SMS infrastructure is less dependable. The built-in OTP button with auto-fill reduces friction compared to asking users to copy a code from an SMS.

Businesses already in the Meta ecosystem

If you are already running Facebook/Instagram ads and using Meta's Conversions API, WhatsApp integrates natively with click-to-WhatsApp ads. Users can tap an ad and land directly in a WhatsApp conversation with your business — no landing page, no form fill, no app download. This ad-to-conversation flow has strong performance in markets where WhatsApp is dominant.

Multi-channel strategy

For global businesses, the optimal approach is often multi-channel: WhatsApp for international customers, iMessage (via Sendblue) for US iPhone users, and SMS/RCS as universal fallback. The channels are not mutually exclusive — they serve different segments of your audience. The key is choosing the right primary channel for each geographic segment rather than forcing a single platform across all markets.

A practical way to think about it: route by geography. If the recipient's phone number starts with +1 (US/Canada), send via Sendblue (iMessage → RCS → SMS). If the number starts with +91 (India), +55 (Brazil), +49 (Germany), or other high-WhatsApp-penetration country codes, send via WhatsApp. This geographic routing gives you the highest possible engagement for each segment without asking any individual customer to use a platform they do not prefer.

Using Sendblue instead — iMessage + RCS + SMS from one API

For US-focused businesses, Sendblue provides a fundamentally different approach to business messaging. Instead of managing template approvals, 24-hour windows, and quality scores across a platform that 68% of your US audience does not use, Sendblue lets you reach every US phone number from a single API endpoint with automatic protocol routing.

How it works

You make one API call. Sendblue determines the best protocol for each recipient:

iMessage — if the recipient has an iPhone with iMessage enabled (57% of US users). Blue bubble delivery, 30-45% response rates, no spam filtering, read receipts.
RCS — if the recipient is on Android with RCS support (most modern Android devices). Rich media, read receipts, typing indicators, branded sender profile.
SMS — universal fallback for any phone number. 100% reach.

No template approvals. No 24-hour windows. No quality score system. No Meta business verification. You sign up, get API keys, and start sending.

Send a message with curl

curl -X POST https://api.sendblue.co/api/send-message \
  -H "Content-Type: application/json" \
  -H "sb-api-key-id: YOUR_API_KEY_ID" \
  -H "sb-api-secret-key: YOUR_API_SECRET_KEY" \
  -d '{
    "number": "+14155551234",
    "content": "Hey! Your order #4821 has shipped. Track it here: https://track.example.com/4821",
    "media_url": "https://yourserver.com/orders/4821/receipt.png"
  }'

That is the entire integration for sending. The same endpoint handles iMessage, RCS, and SMS — Sendblue selects the protocol automatically.

Send a message with Node.js

import fetch from 'node-fetch';

async function sendMessage(toNumber, text, mediaUrl) {
  const payload = {
    number: toNumber,
    content: text,
  };

  if (mediaUrl) {
    payload.media_url = mediaUrl;
  }

  const response = await fetch('https://api.sendblue.co/api/send-message', {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      'sb-api-key-id': process.env.SENDBLUE_API_KEY_ID,
      'sb-api-secret-key': process.env.SENDBLUE_API_SECRET_KEY,
    },
    body: JSON.stringify(payload),
  });

  const data = await response.json();
  console.log('Status:', data.status, '| Handle:', data.messageHandle);
  return data;
}

// Send to any US number — Sendblue picks the best protocol
await sendMessage('+14155551234', 'Your appointment is confirmed for tomorrow at 2pm.');

// With image attachment
await sendMessage(
  '+14155551234',
  'Here is your invoice:',
  'https://yourserver.com/invoices/INV-2026-0412.pdf'
);

Key differences from WhatsApp API

Capability	WhatsApp Cloud API	Sendblue API
Setup time	3-7 days (business verification)	Minutes (sandbox available instantly)
Template approvals	Required for all outbound	Not required
24-hour window	Yes (service messages only)	No restriction
US marketing messages	Paused since April 2025	Unrestricted
US response rates	~4%	30-45% (iMessage)
US reach	~32%	100% (iMessage + RCS + SMS)
Protocol routing	WhatsApp only	Automatic (iMessage → RCS → SMS)
Webhook format	Meta Graph API format	Simple JSON with status + messageHandle
Quality score risk	Templates can be paused	No quality score system

Sendblue also includes a free sandbox with no credit card required, so you can test the integration before committing. The sandbox includes real iMessage and SMS delivery to your own phone number for validation.

Frequently asked questions

Is WhatsApp Business API free?

The API itself is free to access — there is no license fee or setup charge for the Cloud API. However, you pay per message sent. Utility messages cost approximately $0.015 per message in the US, authentication messages cost approximately $0.0135, and service conversations (replies within the 24-hour window after a customer messages you) are free. Marketing messages to US numbers have been paused since April 2025. If you use a Business Solution Provider (BSP), they charge an additional per-message markup on top of Meta's rates.

Can I send bulk marketing messages on WhatsApp in the US?

No. Meta paused marketing message templates for US phone numbers in April 2025, and this restriction remains in effect as of April 2026 with no announced timeline for resumption. You can still send utility messages (order updates, shipping notifications, appointment reminders) and authentication messages (OTPs) to US numbers. For bulk marketing to US audiences, iMessage via Sendblue is the highest-engagement alternative — no template approvals, no restrictions, and 30-45% response rates.

Do I need a BSP for WhatsApp API?

No. Since Meta launched the Cloud API, any business with a verified Meta Business Account can integrate directly without a BSP. The Cloud API is free to access, and you interact with Meta's servers via standard REST API calls. BSPs like Twilio, MessageBird, and Vonage add value through managed dashboards, multi-agent routing, analytics, and simplified template management — but they also add per-message costs ($0.002-$0.005 markup). Choose direct integration if you have engineering resources to build webhook handlers and template management; choose a BSP if you want a turnkey solution.

WhatsApp Business API vs WhatsApp Business app — what's the difference?

The WhatsApp Business app is a free mobile application for small businesses to manually manage conversations on a single phone (with up to four linked companion devices). It includes a business profile, quick replies, and labels. The WhatsApp Business API (Cloud API) is a programmatic HTTP interface for sending and receiving messages at scale — it has no user interface and is designed for integration with CRMs, chatbots, and automation workflows. The API supports thousands of concurrent conversations, requires Meta Business verification, and charges per message. The Business app is free with no per-message fees.

Can I use both WhatsApp and iMessage for business messaging?

Yes, and for global businesses, a multi-channel approach is often optimal. Use iMessage (via Sendblue) as your primary channel for US customers — 57% of US smartphone users are on iPhone, and iMessage delivers 30-45% response rates with no spam filtering. Use WhatsApp for international customers in markets where WhatsApp penetration exceeds 90% (India, Brazil, Europe, Southeast Asia). Sendblue handles iMessage, RCS, and SMS from one API endpoint, while WhatsApp requires a separate Cloud API integration through Meta.

What's the best messaging API for US businesses?

For US-focused businesses, Sendblue consistently outperforms WhatsApp on every engagement metric. iMessage reaches 57% of US phone users natively, achieves 30-45% response rates (vs WhatsApp's ~4% in the US), requires no template approvals, has no 24-hour messaging window, and faces zero carrier spam filtering. With Sendblue's automatic protocol routing, non-iPhone users receive RCS or SMS — covering 100% of US phone numbers from a single API endpoint. WhatsApp's strength is international markets, not the US.

Related guides

iMessage vs RCS vs SMS vs WhatsApp — Complete Comparison (2026) — Side-by-side analysis of all four messaging protocols
RCS Business Messaging Setup Guide — Launch verified RCS campaigns with branded sender profiles
Apple Messages for Business vs iMessage API — Which Apple messaging channel do you need?
RCS API Complete Guide — Build rich messaging experiences with automatic protocol routing
Sendblue API Reference — Full endpoint documentation

WhatsApp API

Business Messaging

iMessage API

API Guide

Reach every US phone number — iMessage, RCS, and SMS

Free sandbox, no credit card required. No template approvals needed.

Get API Access