WhatsApp Business API: Pricing, Options, Setup
· DigifyNow
The WhatsApp Business API is an interface from Meta with no user interface of its own. You connect a verified number to software such as a shared team inbox, a CRM or your own application. When a customer messages you, you can reply freely within a service window. After that, you can only send templates Meta has approved in advance. Meta bills per delivered template. Licensing or development and ongoing operation come on top.
What is the WhatsApp Business API, and how is it different from the app?
The WhatsApp Business API lets businesses send and receive WhatsApp messages from their own software. You don't need a phone running the app, and as many employees as you like can reply from the same number. According to Meta's developer documentation (as of November 2026), you can reply freely for 24 hours after a customer messages you. Outside that window, you can only send templates Meta has approved. Those templates are billed per delivery.
The WhatsApp Business API, which Meta officially calls the WhatsApp Business Platform, isn't an app you install. It's a programming interface. Your software sends messages to Meta via HTTP requests, and incoming messages arrive as webhooks on your server or at your provider. You only get a screen for reading and replying once a shared team inbox, a CRM or your own application is connected. How this works technically, meaning endpoint, token and JSON response, is covered in our article on what an API is, with an example.
The free WhatsApp Business app is built for one device or a handful of devices. You need the API when several people answer on one number, when messages should go out automatically from your inventory or booking system, or when a bot should triage incoming chats first. For a business with one person on the phone and a few chats a day, the app is usually the more honest choice. Moving to the API means getting templates approved, paying per message and having someone who maintains the software.

How does the Meta WhatsApp Business API work in practice?
The Meta WhatsApp Business API comes with a few rules you should know before you pick a tool. The details are in Meta's developer documentation for the WhatsApp Business Platform (information as of November 2026).
- Service window: When a customer messages you, Meta opens a 24-hour window. Within it, you can send free-form replies. Every new customer message restarts the window.
- Templates: Outside that window, you can only send template messages that Meta has reviewed and approved in advance. Meta sorts templates into categories such as Marketing, Utility and Authentication. The price depends on the category.
- Opt-in: Under Meta's policies, you need the recipient's consent before you message them first. That rules out a purchased list of phone numbers.
- Quality rating: Meta rates numbers and templates based on how recipients react. If many people block or report you, Meta can pause a template or cap how many messages the number can send.
Common problems we see in practice: templates get rejected because a placeholder sits at the very beginning or end. Or a template is submitted as Utility but reads like a promotion, and Meta reclassifies it as Marketing. Incoming messages get lost when the webhook receiver responds too slowly or becomes unreachable after a certificate change. What matters for receiving webhooks and verifying signatures is covered in our article on webhooks, testing and security.
WhatsApp Business API examples: what do businesses use it for?
The workflows below are typical patterns from small and mid-sized businesses and the trades. They are not customer results. Each example shows the trigger, the template category and the point where things tend to break in practice.
- Appointment reminders for a trade business: The day before a customer appointment, the job management system sends a Utility template with placeholders for name, date and time, plus two buttons, "Works for me" and "Reschedule". When the customer taps a button, that counts as an incoming message. This opens the service window, and the dispatcher can reply freely. It goes wrong when a canceled appointment isn't deleted in the system and the reminder goes out anyway.
- Shipping status for an online store: When an order is marked as shipped, a Utility message with the tracking number goes out. This requires an opt-in checkbox at checkout. The most common mistake is the phone number: the API expects it in international format with the country code. A mobile number entered in the form with a leading zero has to be converted first, or delivery fails.
- One-time codes for a customer portal: At login, the portal sends a code as an Authentication template. If WhatsApp is down or the user doesn't have WhatsApp, you need a fallback via SMS or email. Without that fallback, the user can't get into the portal.
- Job applications via chat: A wa.me link with your number sits on your careers page. The applicant messages first, so everything runs inside the service window and needs no template. A bot asks about availability and driver's license, then hands off to HR. If HR only replies after more than 24 hours, the window has closed and the conversation can only continue with a template.
- Where it isn't worth it: A café or a small business with a handful of inquiries a day, answered by one person. There, the API adds template upkeep, per-message costs and software someone has to look after, without any workflow triggering automatically. The Business app is enough.
How much does the WhatsApp Business API cost?
We don't quote amounts here. Meta's rates depend on the recipient's country and the template category, and they change regularly. The current pricing page in Meta's developer documentation is what counts. Several pricing overviews in search results (as of November 2026) describe the model consistently: since July 1, 2025, Meta has billed per delivered template message rather than per conversation window. Some of these overviews also report a pricing change effective October 1, 2026, that affects service messages as well. Check the current status directly with Meta before you plan.
These components determine your total cost:
- Message volume and mix: Marketing templates have their own price category. A business that mainly sends shipping confirmations and appointment reminders runs different numbers than one sending newsletters.
- Software license: Providers with a shared team inbox usually charge per user or per plan, on top of Meta's message pricing.
- Integration: Every connection to a CRM, store, ERP or calendar takes development or setup work. How clean the data in those systems is also affects the effort.
- Operation: Servers, monitoring webhook delivery, maintaining templates and making changes when Meta updates the API version.
- Bot or AI assistant: Language models are billed by usage. Rules and the knowledge base also need ongoing maintenance.
Here's how you get a reliable figure: multiply your expected volume per template category by Meta's current price list, and list licensing, integration and operation separately next to it.

Is the WhatsApp Business API free?
Not once you're running it. The pricing overviews in search results (as of November 2026) agree: access to the Cloud API costs nothing at Meta itself. That covers signing up, connecting the number and sending test messages. Costs are charged per delivered template message. The only things that stay free are what Meta explicitly exempts, such as replies within the service window under the rules in effect at the time. You still need an interface. Either you build it yourself or you use a provider's software, and both cost money. When a provider advertises "free", it usually means an entry-level plan. Meta's message fees are added on top or passed through. So always ask whether Meta's fees are included in the price or billed separately, and whether the provider adds a markup.
Which option fits: the app, a provider inbox, automation or your own integration?
Three questions decide it: How many people will reply? Which systems should trigger messages? And who takes care of operation? The table compares the options using the same criteria. A provider here means a Business Solution Provider (BSP) that offers Meta's API with its own software, for example Superchat, respond.io or Wati. Features and pricing vary widely, so the provider's own documentation is what counts. Disclosure: DigifyNow is a partner of Superchat and a partner of Make and receives a referral commission from both. The full list is on our system recommendations page.
| Option | Fits when | Who runs it | Limit |
|---|---|---|---|
| WhatsApp Business app | one or a few people reply, no system needs to send automatically | Meta, you only handle the device | no real integration with a CRM or store, very little automation |
| BSP with shared team inbox (e.g. Superchat, respond.io, Wati) | several employees on one number, standard workflows, quick start | the provider | license per user or plan, integrations limited to the ones offered, data sits with the provider |
| Automation platform (e.g. Make, n8n, Zapier) | individual triggers such as an order or appointment should send a template | the platform, or you yourself with n8n on your own server | no inbox for people, you have to build error handling yourself |
| Your own integration with the Cloud API | WhatsApp should be part of your own back office, CRM or portal | you or your service provider | development, hosting, monitoring and API version changes are on you |
What often doesn't work: a bot doesn't replace a team. Questions that don't fit the rules go nowhere if there's no handoff to a human. Typical pitfalls are covered in our article Customer service automation: options and limits. If you run n8n yourself, you'll find the WhatsApp nodes in the n8n documentation.

How do I set up the WhatsApp Business API?
This is how setup works, whether you go directly through Meta or through a provider that bundles the steps in its interface:
- Create a Meta business account (Business Portfolio) or use an existing one. Your company name and address should match your commercial register entry or business registration exactly.
- Complete business verification with Meta, using documents such as an extract from the commercial register. Without verification, you can only send within tight limits.
- Choose a phone number: it must be able to receive SMS or calls for the verification code. If it's already active in the Business app, remove it there or use Coexistence if your provider supports it. Then the app and the API run on the same number.
- Set your display name. Meta reviews it, and it has to be clearly tied to your business.
- Add a payment method in your Meta account or with your provider, or no templates will go out.
- Set up the webhook: you need a reachable HTTPS address that answers Meta's verification request and accepts incoming messages. With a provider, they handle this step.
- Submit your first templates: a clear category, placeholders with sample values, no promotional content in Utility templates.
- Build your opt-in path, for example a checkbox in the order form or booking flow, and store the consent with a date.
- Test with internal numbers first, then start with low volume and keep an eye on your quality rating.
Things usually get stuck in two places: verification, when your company details don't match, and the phone number, when it's still tied to an app. Plan time for both, and don't kick off with a big marketing campaign right away.
What about data privacy with the WhatsApp Business API?
Whether a setup holds up under data protection law depends on how you run it, not on the tool. Neither Meta nor a provider nor we can promise compliance. The GDPR requires, among other things, a legal basis for every processing activity, information for the people affected and contracts with data processors. You should clarify the following points with your data protection officer:
- Who is the data processor? Meta provides its own data processing terms for the Business Platform. A provider with an inbox is an additional processor and needs its own contract.
- Where are chat histories stored? With the Cloud API, Meta processes the messages. With a provider inbox, copies sit in the provider's data center; with your own integration, on your server.
- Transfers to third countries: Meta is a US company. Clarify the legal basis on which data is transferred.
- Opt-in and withdrawal: consent has to be stored in a way you can prove, and a "Stop" has to end sending.
- Retention periods: don't keep chat histories indefinitely; set retention periods and enforce them technically.
- No address book uploads from employees' phones: unlike the app, the API doesn't access contacts. That's another reason businesses switch to it.
If you use an AI assistant in the chat, the EU AI Act comes into play as well. Its transparency obligations now apply: people should be able to tell that they're talking to an AI system, unless that's obvious anyway. In addition, deployers take measures to support the development of AI literacy among the employees who work with the system. They aren't required to guarantee a specific level of competence. In practice, that means the bot introduces itself as a bot, and the team knows when it has to take over.

How DigifyNow connects the WhatsApp Business API
DigifyNow doesn't have its own WhatsApp product. We connect the Cloud API to the systems a business already works with: its own back office, a CRM or a booking or ordering workflow. To do that, we set up webhook receiving, store the opt-in on the contact record, trigger templates from events in the system and monitor whether messages are delivered or fail. If you want, we add an AI assistant. It triages inquiries and hands off to a person when it can't go further. If you already have a provider inbox, we'd rather connect to its API than rebuild everything. You'll find an overview of our software development and AI services on our services page.
When outside help is worth it
For one number with a shared team inbox and standard workflows, setup through a provider is usually enough. Outside help pays off when WhatsApp should trigger messages from your CRM, store or ERP, when replies should flow back into your own data, or when an AI assistant should be part of the conversation. Have the following ready: the number and its current status, the workflows that should trigger messages, a rough estimate of volume per message type and the systems involved. In a free initial assessment via our contact form, we look at which option fits your project.

Frequently asked questions
What is the WhatsApp Business API?
The WhatsApp Business API, officially the WhatsApp Business Platform, is Meta's programming interface that lets businesses send and receive WhatsApp messages from their own software. Outgoing messages are HTTP requests to Meta; incoming ones arrive as webhooks. The API has no interface of its own. To read and reply, you need a provider's shared team inbox, a CRM or your own application.
What's the difference between the WhatsApp Business app and the API?
The app runs on one phone and a few linked devices. It's operated by hand and has no real integration with a CRM or store. The API has no interface of its own, lets any number of employees access one number through software and can send automatically. In return, it requires approved templates outside the 24-hour window and charges per delivered template.
How much does the WhatsApp Business API cost?
Access at Meta is free. According to several pricing overviews in search results (as of November 2026), Meta has billed per delivered template message since July 1, 2025, tiered by recipient country and category: Marketing, Utility, Authentication. On top of that come a provider's license or your own development, integration with your CRM or store, and operation. Current rates are on Meta's pricing page.
Can I use my existing WhatsApp number for the API?
Yes, but normally a number is only active in one place: the Business app or the API. Either you remove it from the app, in which case the chat history stays behind there. Or you use Coexistence if your provider supports it. Then the app and the API run on the same number. The number must be able to receive SMS or calls for the verification code.
Do I need a provider (BSP), or can I go directly through Meta?
Going directly through Meta works, because Meta hosts the Cloud API itself. But you won't get an interface: messages arrive as webhooks, and you need your own software to read and answer them. A BSP provides that interface for a license fee. Building your own integration mainly makes sense when WhatsApp should become part of an existing system.
Can I send newsletters through the WhatsApp Business API?
Technically yes, as a Marketing template. Meta has to approve it, and every delivery is billed. Under Meta's policies, you need each recipient's consent beforehand. Whether that's sufficient under German law is something to clarify with your data protection officer. If many recipients block you, your quality rating drops and Meta can pause templates.
What happens if a template gets rejected?
The template gets the status "rejected", usually with a reason, and you can submit a revised version. Common reasons are placeholders at the beginning or end, missing sample values and promotional wording in a Utility template. Meta reclassifies a template like that as Marketing, and then a different price applies too.