Blog/Technical
Technical12 min readPublished 2026-02-08

WhatsApp Business API: Everything You Need to Know

The WhatsApp Business API is more complex than most guides suggest. This covers BSP selection, template message approval, conversation pricing, 24-hour windows, and the cases where the API genuinely makes sense for your business.

BulkSMSRates Team

Engineering · BulkSMSRates

WhatsApp Business API: Separating Hype from Reality


The WhatsApp Business API gets a lot of attention. 2.7 billion users, high engagement rates, rich media support — the pitch writes itself.


The reality is more nuanced. The API is genuinely powerful for specific use cases, but it's more complex and constrained than most articles suggest. Before you invest time and money into WhatsApp Business integration, you need to understand how it actually works.


The Three Tiers of WhatsApp Business


Meta has created three different products for businesses:


WhatsApp Business App — free mobile app for small businesses, handles conversations manually, limited to one device (recently expanded to multi-device), no automation, no API. Fine for a sole trader managing a handful of customer conversations.


WhatsApp Business Platform (Cloud API) — Meta's direct cloud-hosted API. Launched in 2022, simpler to set up than the legacy on-premise solution, still requires a Meta developer account and approval process.


WhatsApp Business Platform (On-Premises) — self-hosted solution for very large enterprises. Being phased out in favour of Cloud API.


For 99% of businesses reading this: you want the Cloud API, accessed through a Business Solution Provider (BSP).


The BSP Ecosystem (And Why It Matters)


You can't just sign up directly with Meta and start sending. You need to go through a Business Solution Provider — a company that has a direct partnership with Meta and provides the API infrastructure, compliance, and support.


Major BSPs include: Twilio, MessageBird (Bird), Vonage, Sinch, Infobip, Clickatell, and many smaller regional providers.


BSPs add:

  • API wrapper and SDKs
  • Sending infrastructure (so you don't manage servers)
  • Compliance and number registration support
  • Dashboard and analytics
  • Their own markup on top of Meta's conversation fees

The BSP markup matters. Meta charges a conversation fee. The BSP charges an additional fee on top. Some BSPs charge per message on top of that. The total cost to you can be 1.5–3x Meta's base rate depending on the BSP.


Shop around on BSP pricing before committing. And read the terms carefully — some have minimum monthly commitments.


How Message Templates Work


This is the part that trips up most teams coming from SMS.


In WhatsApp Business, you cannot just send arbitrary text to a user. For any business-initiated conversation, you must use a pre-approved message template.


Templates must be:

  • Submitted to Meta for review before use
  • Approved (review typically takes 2–72 hours, but can take longer)
  • Used without modification beyond specified variable slots
  • Categorised as utility, authentication, or marketing

A template looks like this:


Hello {{1}}, your order {{2}} has shipped and will arrive by {{3}}.
Track here: {{4}}

The {{1}}, {{2}}, etc. are variable placeholders that you fill in when sending. Everything else is fixed.


Template categories:

  • Authentication: OTPs, verification codes. Lower conversation cost.
  • Utility: Transactional notifications — order updates, appointment confirmations, shipping alerts. Moderate cost.
  • Marketing: Promotional messages, offers, re-engagement. Higher cost.

Template approval is not guaranteed. Meta reviews templates against their content policy. Templates can be rejected for:

  • Content that violates their policies (obvious)
  • Vague or unclear variables
  • Template that could be "repurposed" for marketing when categorised as utility
  • Certain industries (financial products, gambling, healthcare products need extra care)

Rejected templates can be revised and resubmitted, but this takes time. If you're planning a campaign and need a new template, build in 3–5 days buffer.


The 24-Hour Conversation Window


Here's the mechanic that catches everyone off guard.


Once a user messages your business, you have a 24-hour window to reply with any message — free-form text, no template required. This is the "service window."


Once that 24-hour window expires, you can only contact the user again using a pre-approved template. You cannot send a free-form message outside the window.


What this means practically:

  • Customer service conversations that are ongoing feel natural — you can reply freely within 24 hours
  • Re-engaging a customer you haven't heard from in weeks requires a template
  • If a customer replies to your template message and the conversation starts, you now have 24 hours of free-form messaging

For customer support teams, the 24-hour window is genuinely convenient. For marketing teams trying to re-engage lapsed customers, it's a constraint.


Conversation-Based Pricing


Unlike SMS (charged per segment), WhatsApp charges per "conversation" — a 24-hour messaging window. One conversation fee covers unlimited messages within that window.


Pricing as of Q1 2026 (UK numbers, approximate):


CategoryMeta base rateTypical BSP total
Marketing$0.0600$0.08–0.10
Utility$0.0280$0.04–0.06
Authentication$0.0190$0.03–0.04
Service (user-initiated)$0.0250$0.03–0.05

Rates vary by country — India and Indonesia have much lower rates. Brazil and Germany are higher.


Compare these to SMS: BulkSMSRates UK SMS is £0.0300/message. A WhatsApp marketing conversation at $0.09 total is roughly £0.072 — about 2.2x the SMS cost for one interaction.


If the conversation has 4+ exchanges, WhatsApp becomes cheaper per message. For single-touch marketing (send an offer, recipient clicks), SMS is cheaper.


What You Need to Set Up


Getting WhatsApp Business API working requires:


1. Meta Business Account: Verify your business with Meta. Requires business documentation and takes 1–3 days.


2. WhatsApp Business Account (WABA): Created as part of the Meta setup. Your WABA contains your phone numbers.


3. Phone number verification: The number you send from must be verified. You can use an existing business number (if not already on WhatsApp) or get a new one. Numbers cannot simultaneously be active on WhatsApp personal app.


4. BSP registration: Sign up with your chosen BSP, connect your WABA, configure webhooks for incoming messages.


5. Template creation: Design your message templates, submit for approval, wait for approval.


6. Opt-in collection: You cannot message users without opt-in. Set up a way to collect WhatsApp opt-in consent (separate from SMS opt-in if you're running both channels).


Realistically: plan 2–4 weeks from decision to first message sent, if everything goes smoothly.


Practical Use Cases Where WhatsApp Wins


Order tracking and shipping notifications: Rich media (tracking link with map, package images), two-way conversation if the customer has questions. Much better experience than SMS for complex multi-step delivery flows.


Appointment management: Send confirmation, allow the customer to confirm/cancel by replying, send reminder. Two-way WhatsApp is significantly better UX than SMS for this.


Customer support escalation: After resolving a ticket, follow up on WhatsApp for satisfaction rating. Feels natural because it's the same interface customers use with friends.


High-value customer nurturing: For B2B or high-AOV B2C, personalised WhatsApp messages from a real account executive carry more weight than broadcast SMS. But this is the WhatsApp Business App territory, not the API.


Post-purchase experience: Order confirmation → shipping notification → delivery confirmation → "how was your order?" This 4-step sequence in a WhatsApp conversation is genuinely better than 4 separate SMS.


Where SMS Still Makes More Sense


  • Single-touch promotional sends (a flash sale with one link)
  • Reaching older demographics or users without WhatsApp
  • International campaigns where WhatsApp penetration is lower
  • When you need to send immediately without template approval
  • When cost per contact matters more than rich media capability
  • SMS fallback when WhatsApp delivery fails

The Bottom Line


WhatsApp Business API is genuinely powerful for businesses with conversational use cases — support, two-way scheduling, post-purchase sequences. For these, it's worth the setup complexity.


For one-way promotional broadcasting, the template restrictions, approval delays, and higher per-conversation cost make SMS more practical. Many businesses use both: WhatsApp for service conversations, SMS for promotional sends.


If you're evaluating both channels, the SMS vs WhatsApp comparison post goes deeper on the trade-offs.

#WhatsApp Business API#BSP#template messages#Meta#WhatsApp pricing

More Articles

Ready to send bulk SMS?

Start from £0.0300/segment. No monthly fees. Free test credits. Setup in minutes.

Create Free Account →