What is the WhatsApp Business API? Features, pricing and how to get access

What is the WhatsApp Business API?

The WhatsApp Business API, now called the WhatsApp Business Platform, is the way companies connect their own software to WhatsApp so they can send and receive messages at scale. There is no app to open and no phone to hold. Your CRM, helpdesk, online store or product talks to WhatsApp through an interface, and customers see an ordinary chat with a verified business name.

That makes it a different thing from the free WhatsApp Business app, even though both carry the same logo. The app is built for a shop owner answering questions from a phone. The API is built for a company that wants order updates sent automatically, support conversations shared across a team, and one-time passwords delivered to people who would rather use WhatsApp than wait for a text.

In short: if you need more than one device, any automation, templates, or integration with your own systems, you need the API. We run it as one channel inside the same account as SMS, RCS and voice, which makes fallback between channels simple; the product page for WhatsApp on Telnxo has the details.

WhatsApp Business app vs WhatsApp Business API

A common mistake is trying to run campaigns from the app. It works for a week, then the number is restricted. If you are sending to more than a few hundred people, move to the API.

What can you do with it?

Most companies start with one of four jobs and add the others later.

• Notifications. Order confirmed, shipped, out for delivery, refund processed. These are utility templates and usually the highest-value messages you send. See our e-commerce solution.
• Support. Customers message you; agents or a bot reply inside the free 24-hour window. Our support solution covers routing and handover.
• Authentication. One-time passwords sent as authentication templates with a copy-code button. Pair them with an SMS fallback using the OTP product.
• Marketing. Offers, abandoned-cart reminders and launches to people who opted in. These are marketing templates and carry the highest per-message charge.

Messages can also carry images, documents, location, quick-reply buttons, call-to-action buttons and list menus, which is where WhatsApp pulls away from plain text. Conversations are protected with end-to-end encryption between the customer and the business platform.

How the 24-hour window and templates work

Two rules shape almost everything you build on WhatsApp.

The service window. When a customer messages you, a 24-hour window opens. Inside it you can reply with any content, including free text, images and buttons, and these service messages are free. When the window closes you cannot send free-form messages until the customer writes again.

Templates. To start a conversation, or to write after the window has closed, you must use a pre-approved message template. A template is fixed text with placeholders such as {{1}} for a name or order number. You write it, choose a category and submit it for review. Our guide to templates and the 24-hour window goes through the rules, and the post on templates that get approved shows examples that pass.

How WhatsApp Business API pricing works

Pricing has two parts: what Meta charges, and what your provider charges. Since mid-2025 Meta bills per delivered template message instead of per 24-hour conversation. The rate depends on the template category and the country of the recipient, and Meta publishes the current rate card on its pricing page.

• Marketing templates cost the most, authentication and utility less.
• Free-form replies inside the 24-hour service window are free.
• Utility templates sent inside an open window are not charged.
• Rates differ widely by country; India, the UAE, the UK and the US are all priced separately.

Providers then add their own fee: a monthly platform fee, a small per-message markup, or both. Ask for the all-in cost per delivered message in your main countries, not the Meta rate alone. We publish ours on the pricing page, and the cost calculator lets you model the mix of categories you expect.

How to get access, step by step

1. Set up your Meta business portfolio. Create or find your business in Meta Business Suite. Verification may be requested, which means uploading legal documents that match your website and domain.
2. Choose a number. It must be able to receive a call or SMS for the verification code. It cannot already be in use on a regular WhatsApp account, unless you migrate it.
3. Connect it. Either connect directly to Meta's Cloud API, documented on Meta for Developers, or link it through a Business Solution Provider such as us.
4. Get your display name approved. The name customers see should match your brand. Generic names are refused.
5. Create templates and test. Submit your first templates, send yourself a test and check delivery receipts through your webhook.
6. Record opt-in, then go live. Decide how customers consent, store the proof, and only then send to your list.

Allow a few days for the first setup. Most delays come from documents that do not match the business name, or from a display name that does not look like the company.

Opt-in, quality rating and sending limits

WhatsApp is stricter than SMS about consent. You need clear permission to message a person on WhatsApp, collected in a form, at checkout, in a chat or by a click-to-WhatsApp ad, and you should be able to show when and how. Our help article on opt-in and quality rating covers wording and storage.

Meta scores your number on how recipients react. Blocks and reports push the rating down; replies and reads help it. A low rating can cap the number of customers you can message and, in the worst case, disable the number. New numbers start with a limit on how many unique customers you can contact in 24 hours and move up in tiers as quality and volume allow.

Building on the API: what developers need to know

Technically it is straightforward. You send a request with the recipient, a template name and the variables; incoming messages and status updates come back as webhooks. The things that trip teams up are rarely the API call.

{
  "channel": "whatsapp",
  "to": "+919812345670",
  "template": "order_shipped",
  "language": "en",
  "variables": { "1": "Asha", "2": "#4821" },
  "fallback": { "channel": "sms", "after": "30m" }
}

• Treat webhooks as the source of truth for status, and make your handler idempotent because events can arrive twice or out of order.
• Store the customer's last inbound timestamp so your system knows when the window is open.
• Handle template rejection as a normal event, with an owner who rewrites it.
• Plan a fallback to SMS for critical messages. Not every recipient is reachable on WhatsApp at every moment. Our SMS gateway guide explains the other side of that setup.

Full field lists are in the API reference. If you already use another provider, the guides for Gupshup and Twilio show how templates and numbers move across.

WhatsApp rewards the businesses that message less and more usefully.

Is the WhatsApp Business API right for you?

It is a good fit when customers already use WhatsApp, which in India, the Middle East, Latin America and much of Europe is common, and when your messages have a clear purpose: an update, an answer or a code. It is a poor fit if you want to blast a purchased list, or if your audience mostly prefers email or has little data access. In that case SMS, or RCS where it is supported, may be the better first channel.