WhatsApp Business API: how it works, what it costs and how to set it up
The WhatsApp Business API, officially the WhatsApp Business Platform, is Meta's programmatic interface for sending and receiving WhatsApp messages from your own software. It has no inbox of its own: you connect it to a CRM, a help desk or a chatbot through the Cloud API and webhooks. Meta charges per delivered message, with rates that depend on the message category and the recipient's country.

What the WhatsApp Business API is
“WhatsApp Business API” is the name most people search for. Meta’s documentation calls the product the WhatsApp Business Platform. It is a set of APIs that let software, not a person with a phone, send and receive WhatsApp messages for a business.
According to Meta’s developer documentation, the platform has three main parts:
- Cloud API. Hosted by Meta. Used to message and call on WhatsApp programmatically.
- Marketing Messages API for WhatsApp. A separate API for sending marketing template messages.
- Business Management API. Used to manage accounts, phone numbers and templates, and to read analytics.
The platform has no inbox. If your team needs a screen to read and answer chats, that screen is your own software, your help desk, or a solution provider’s product. This is the main fact to understand before starting: the API is plumbing, and the product on top of it is yours to choose or build.
WhatsApp Business app vs WhatsApp Business API
| WhatsApp Business app | WhatsApp Business API (Platform) | |
|---|---|---|
| Interface | Phone and desktop app | None. Your software or a provider’s inbox |
| Who sends messages | A person | Software, or people through software |
| Automation | Greeting and away messages, quick replies | Full: chatbots, AI, order and CRM integration |
| Integration | Limited | Any system that can call an API |
| Outbound messages at scale | Not what the app is for, and WhatsApp’s terms prohibit bulk and automated messaging | Allowed with approved templates and opt-in |
| Cost | Free app | Per delivered message, plus your build or provider cost |
| Setup effort | Minutes | A business portfolio, a number, a webhook and engineering |
The app fits a small team answering by hand. The API fits a company that wants WhatsApp connected to its order system, its CRM or a chatbot, or that has more conversations than a few people can type.
Cloud API directly, or through a solution provider
There are two ways onto the platform.
Direct integration. Your engineers, or a firm like ours, connect your systems to the Cloud API. Messages are billed by Meta to your own account. You own the integration and can shape it to your process. You also carry the engineering: webhook handling, retries, template management and an agent interface if you need one.
A solution provider. Meta’s terms use the term Solution Provider for a third party that gives a business access to the platform. Providers usually offer an inbox, campaign tools and onboarding, and many add their own subscription or per-message markup. This is faster to start and less flexible.
A practical rule: if WhatsApp is one more support channel for a team that already works in a help desk, a provider is often enough. If WhatsApp is where orders, bookings or account actions happen, direct integration gives you control over the logic and the data. Goldenroz is an independent engineering firm, not a Meta Business Partner or solution provider. Our WhatsApp Business API integration work is direct Cloud API integration into the client’s own systems and Meta account.
What you need before you start
Meta’s documentation lists the required assets:
- A business portfolio. Meta states that you must have one to use the platform.
- A WhatsApp account and a Messaging account under that portfolio. These hold your phone numbers, display name, templates, billing and payment method. Older guides call this the WhatsApp Business Account, or WABA.
- A business phone number. Real or virtual.
- A webhook endpoint. Meta says the platform “relies heavily on webhooks”. Incoming messages and delivery statuses arrive there, so you need a public HTTPS endpoint that answers quickly and reliably.
Business verification
Verification of the business portfolio is not required to send a first message, but Meta’s documentation says verification status factors into improved functionality, including higher limits and eligibility for Official Business Account status. Plan for it early. It needs legal business documents, and it is the step most often delayed by paperwork, not code.
Messaging limits
A messaging limit is the maximum number of unique users you can message outside a customer service window in a moving 24-hour period. As of November 2026, Meta’s messaging limits documentation states that a new business portfolio starts at 250, and that the limit can rise to 2,000, 10,000, 100,000 and then unlimited. The limit is set at the portfolio level, so all your numbers share it. Verifying the business is one of the paths to the 2,000 level. Above that, limits rise automatically when message quality is high and you use at least half of your current limit.
Replies inside a customer service window do not count against this limit. It matters for outbound notifications and campaigns.
Templates and message categories
There are two kinds of messages.
Free-form messages can be sent only while a customer service window is open. The window lasts 24 hours from the user’s last message or call, and it resets each time the user writes again.
Template messages are pre-approved formats with variables, such as an order confirmation with the customer’s name and order number. Meta’s documentation states that templates are the only type of message that can be sent outside a customer service window. Templates are reviewed automatically when created or edited, and Meta notes that review can take up to 24 hours.
Every template has a category:
| Category | Purpose | Example |
|---|---|---|
| Marketing | Promotions, offers, re-engagement | “Our winter range is in stock” |
| Utility | Follow-up on a transaction or request the user made | Order confirmation, delivery update |
| Authentication | One-time passcodes | Login code |
Replies that are not templates fall into the service category. Since July 2026, Meta’s pricing page also lists a separate category for messages produced by its own Meta Business Agent product.
Templates have a quality rating based on usage and customer feedback. A template with recurring negative feedback can be paused or disabled. This is the mechanism that punishes messages people did not want, which is why opt-in and relevance are engineering concerns and not only legal ones.
Opt-in and escalation rules
Meta’s Business Messaging Policy requires opt-in permission from the recipient before you message them, and an easy way to opt out. It also says that a business using automation must offer “prompt, clear, and direct escalation paths”, such as a transfer to a human agent, a phone number or a support form. A chatbot with no way out breaks the policy.
How WhatsApp Business API pricing works
We do not publish Meta’s rates here because they differ by country and change on a schedule. The model, as described in Meta’s pricing documentation as of November 2026, is this:
- Billing is per delivered message. Meta moved from per-conversation to per-message billing on July 1, 2025.
- The rate depends on two things: the message category and the recipient’s country calling code.
- Messages from users to the business are not charged.
- Marketing and authentication templates are charged for each delivered message.
- Utility templates are charged per delivered message. They were free inside an open customer service window until October 1, 2026. Meta’s page states that they are charged from that date.
- Service messages (free-form replies) are free for the first 1,000 per business phone number per month, and charged above that, as of October 1, 2026.
- Volume tiers lower the rate for utility and authentication messages as monthly volume grows. Marketing has no volume tiers.
Two consequences follow. First, a support operation that used to treat replies as free now has a usage cost that grows with conversation volume, so it belongs in the budget. Second, the category of a template is a cost decision. A utility template that reads like a promotion can be recategorized as marketing, which changes the rate.
Before you forecast, read the current rate card on Meta’s pricing page for the countries you serve. Your total cost has three layers: Meta’s message charges, the AI model usage if a chatbot answers, and the build or provider fee. Our post on how much a chatbot costs covers the last two.
Setup checklist
- Create or confirm the Meta business portfolio and decide who in the company owns it.
- Start business verification.
- Choose the phone number and display name. A number already used in the WhatsApp Business app needs a migration plan.
- Create the WhatsApp account and add a payment method.
- Build and host the webhook endpoint. Verify signatures, respond fast, and process messages from a queue.
- Send and receive a first test message through the Cloud API.
- Write templates for every outbound message, pick the right category and submit them for review.
- Build opt-in capture and store proof of consent.
- Connect the agent inbox and the handoff to a person.
- Set up monitoring: delivery failures, template status changes, quality rating and messaging limit.
Steps 1 to 4 are administration. Steps 5 to 10 are engineering, and they are where projects succeed or fail.
AI on WhatsApp: what the terms allow
Meta’s terms for the platform restrict “AI Providers” from using it when the AI itself is the primary functionality offered. In plain words, a general-purpose assistant distributed over WhatsApp is not allowed. A business that uses AI to serve its own customers, for example to answer support questions or take orders, is using AI as a means, which is the normal case. If your product is close to the line, read the current terms with your lawyer before building.
The steps for adding a bot on top of the API are in how to build a WhatsApp chatbot, and the service page is WhatsApp chatbot development.
Common mistakes
- Treating the webhook as a simple endpoint. Meta retries failed deliveries, so the same message can arrive twice. Deduplicate by message ID.
- No plan for the closed window. A customer who replies after 30 hours cannot be answered with free text. Have a template ready for that case.
- One admin user owning everything. If that person leaves, access to the portfolio leaves with them.
- Ignoring quality signals. A paused template stops order confirmations as surely as a server outage.
- Automating a personal or Business app number with unofficial tools. WhatsApp’s terms prohibit bulk and automated messaging outside the official platform, and accounts are suspended for it.
What to do next
Write down the three message flows that matter most, for example order updates, support replies and appointment reminders, and note for each whether the user or the business starts the conversation. That tells you which templates you need and what the usage cost will look like. If you want the integration built into your own systems, see WhatsApp Business API integration. If the goal is an assistant across several channels, see AI chatbot development. Build projects start at $25,000 at a fixed price per phase, and the first one-hour consultation is free.