WhatsApp API : Basics

What Is the WhatsApp Business API?

TL;DR: The WhatsApp Business API (officially the "WhatsApp Business Platform") lets medium and large businesses send and receive WhatsApp messages programmatically — through a CRM, helpdesk, or dashboard — instead of a phone app. Unlike the free WhatsApp Business App, it has no built-in interface, supports multiple agents and automation, and is billed per message rather than per download. As of 2025, it runs exclusively on Meta's Cloud API; the older On-Premises API has been retired.

WhatsApp Business App vs. WhatsApp Business API

Most businesses start with the free WhatsApp Business App and outgrow it. Here's the real difference:

If you're regularly missing messages because more than one person needs to reply, or you want to trigger messages automatically from an order or booking system, that's the point to move to the API. See how Chakra's shared inbox handles this.

How the WhatsApp Business API actually works

There's no app to download. Instead, the flow looks like this:

1. You (or your provider) create a Meta app and connect a WhatsApp Business Account (WABA) through Meta's App Dashboard.
2. You verify your business on Meta Business Manager and register a phone number — this number can no longer also run the consumer WhatsApp Business App unless you use WhatsApp Coexistence.
3. You send messages through Meta's Cloud API, either by writing direct API calls or, far more commonly, through a Business Solution Provider (BSP) dashboard like Chakra that handles the technical layer for you.
4. Two message types govern what you can send: if a customer messages you first, you get a 24-hour window to reply with anything. If you want to message first, it must be a pre-approved message template.

For the exact developer-level setup steps (app creation, access tokens, webhooks), Meta's own get-started guide covers registering as a developer, creating a Meta app, and sending your first message worth bookmarking if your team is doing the integration itself rather than through a BSP.

Getting set up with Chakra takes a different path — no code required. Follow our 3-step setup guide to connect your number and send your first broadcast.

Cloud API vs. On-Premises API — this has changed

Older guides (including our own previous version of this page) describe a choice between Meta's Cloud API and an On-Premises API you host yourself. That choice no longer exists. Meta deprecated the On-Premises API in October 2023 and it was fully retired on October 23, 2025 — it can no longer send or receive messages at all. Every WhatsApp Business API integration today, whether built in-house or through a BSP, runs on Cloud API.

If you or a previous developer set this up years ago and it's stopped working, that's very likely why — and migrating to Cloud API is the only fix.

Pricing: what changed in 2025

Pricing used to be based on 24-hour "conversation" windows. That model is deprecated. Since July 1, 2025, WhatsApp bills per message template sent, not per conversation, across three categories:

• Marketing — promotions, offers, re-engagement. Highest cost per message.
• Utility — order updates, delivery notifications, account alerts.
• Authentication — OTPs and login verification.

Two other changes worth knowing: service messages (replies within the 24-hour customer-initiated window) have been free since November 2024, and utility templates sent inside an open service window became free from April 2025. Exact per-message rates vary by recipient country and change periodically — check Meta's current rate card rather than relying on a fixed number in any blog post, including this one. For a full breakdown by category and region, see our dedicated Pricing & Charges guide.

Chakra applies zero markup on template message fees — you pay Meta's rate, nothing added.

What can you actually do with it?

• Order and delivery updates sent automatically from your store or CRM
• Multi-agent support where a whole team shares one number without losing context — see Chakra's shared team inbox
• Chatbots and automated flows for FAQs, lead qualification, and after-hours coverage — see Chakra's chatbot builder
• Broadcast campaigns to opted-in customers for offers, reminders, and re-engagement
• Catalog and commerce messages so customers can browse and buy inside the chat — see WhatsApp Catalog & Commerce
• Authentication — OTPs and login confirmation, often cheaper and faster to open than SMS

Common misconceptions

"You need a developer to use it." Not with a BSP. The raw API requires code; a dashboard like Chakra handles the technical layer so your team sends messages the same way they'd use any support tool.

"It replaces your existing WhatsApp number." It doesn't have to — WhatsApp Coexistence lets you register your current number for the API while still using the consumer app alongside it.

"It's only for large enterprises." The API itself has no minimum size requirement. What determines whether you need it is message volume and team size, not company size — a two-person support team fielding 60+ chats a day outgrows the app just as fast as an enterprise does.

"Setup takes weeks." Business verification through Meta is usually the longest step, and even that has gotten faster. With embedded signup through a BSP, connecting a number typically takes minutes, not weeks.

Getting started

1. Connect your number via Embedded Signup
2. Create your first message template
3. Set up your shared team inbox or chatbot

Related reading: WhatsApp Business Accounts (WABA) explained · Compliance, policies & consent · WhatsApp API Glossary

Sources: Meta for Developers — Get Started guide, On-Premises API sunset notice, Pricing documentation. Page last verified August 2026.