WhatsApp Business API in 2026: how it works, what it costs, and how to get access

What is the WhatsApp Business API?

The WhatsApp Business API is the programmable side of the WhatsApp Business Platform: instead of a person typing into a phone, your software sends and receives messages over HTTP and gets notified of new ones through webhooks. Meta's own developer docs call the product the WhatsApp Cloud API, and the account it lives in a "Messaging account" (you will still see "WhatsApp Business account" on buttons).

I build integrations at eesel, and I'll say up front where I'm coming from: I've read these Meta docs the way you read a contract before you sign it. The thing I see trip teams up most is the word "API". People expect to sign up and get a WhatsApp inbox. What you get is a pipe, which you then plug into a helpdesk or an omnichannel inbox.

Is there still an On-Premises API?

No. Meta moved new features to Cloud API only after January 9, 2024, stopped letting numbers register on On-Premises from July 1, 2024, and the last On-Premises client (v2.63) expired on October 23, 2025. Messages to or from numbers still registered there are no longer delivered. Meta's sunset page pitches Cloud API at up to 1,000 messages per second, 99.9% uptime and SOC 2 and SOC 3 certification. If an older guide tells you to pick between "hosted" and "on-prem", it's out of date.

What does the API actually give you, and what doesn't it?

Here is the split that matters for a support team:

The left side is Meta's job. The right side is yours, and it's where the real work is. A support lead in a r/CRM thread put the balance well after connecting WhatsApp through a partner platform:

"Integrating the chat apps is super easy. Getting the AI agent instructions right is an ongoing task to make sure it answers in the way we want it to."

u/CraigInCambodia, Seeking feedback on tools for consolidating online customer chats, Reddit

That matches what I hear in eesel sales calls. One German ecommerce team running several Shopify stores on Zendesk came to eesel needing WhatsApp next to their chat bubble. The rest of their list was about the answers themselves: German replies, several shops, and order questions answered from Shopify. That's the pattern: the knowledge behind the answers and the rules for when to hand off are the big part.

WhatsApp Business app vs WhatsApp Business API: which do you need?

The free WhatsApp Business app is fine while one or two people answer chats from a phone. You need the API the moment you want software involved: a helpdesk, an automation, an AI chatbot, or messages sent outside a live conversation.

Can you keep the app and use the API on the same number?

Yes, and this is the 2026 change I'd point most small teams to first. Meta's coexistence onboarding lets a business connect its existing WhatsApp Business app number to the Cloud API through a partner, keep chatting from the app, and have messages mirrored both ways. Up to 6 months of one-to-one chat history and all WhatsApp contacts can sync.

The trade-offs are concrete. A shared number is capped at a fixed 20 messages per second. Group chats don't sync, disappearing and view-once messages are turned off, and broadcast lists become read-only. You need app version 2.24.17 or later, and only a Solution Partner or Tech Provider can offer the flow, so you can't do it from the Meta dashboard alone.

How do you get access to the WhatsApp Business API?

There are three doors, and they lead to the same Cloud API. What changes is who builds the parts on the right side of that diagram, and who sends you the Meta bill.

1. Go direct with Meta. You create the app, host the webhook server and write the code. Meta bills your card.
2. Use a Solution Partner (what most people still call a BSP). Meta's partners overview says Solution Partners have credit lines and can invoice you for API usage, so you may never enter a payment method with Meta.
3. Use a Tech Provider. Same full range of services, but no credit line: you add your own card, Meta bills you for messages, and the provider bills you only for its software. Most onboard you with Embedded Signup, a pop-up that creates your WhatsApp assets in a few clicks.

If you're a support team rather than a dev shop, door 2 or 3 is the normal pick, and my WhatsApp for business guide compares partner platforms. Door 1 makes sense when you have engineers and a reason to own the code, like an n8n workflow or your own app.

What are the steps to set up the Cloud API directly?

Meta's get started guide (updated June 16, 2026) walks through it. Condensed:

1. Register as a Meta developer with a Facebook or managed Meta account, and have a phone with WhatsApp for testing.
2. Create an app in the Meta App Dashboard with the "Connect with customers through WhatsApp" use case, and attach it to a business portfolio.
3. Connect a Messaging account under API Setup and note its ID.
4. Send a test message with a temporary access token and Meta's test number. The first message is the hello_world template.
5. Set up a webhook endpoint so you receive incoming messages and delivery statuses.
6. Create a system user in Business Settings and generate a permanent token with business_management, whatsapp_business_messaging and whatsapp_business_management. Meta warns the temporary token "expires quickly".
7. Add your real business number and send a free-form reply once a customer has written to you.

That gets messages flowing. It doesn't give a single agent a place to read them.

Business verification is the step people underestimate. You need it to lift your messaging limit past 250 a day (more on that below), and Meta's review clock doesn't always match its own estimate:

"It took me over 14 days to get verified. When they say it takes 10 business days max it’s bs. It’s always been like this, be patient"

u/BasteinOrbclaw09, Meta Business Verification stuck “In Review” for 8+ days, Reddit

Start verification on day one, even before your code is ready.

How much does the WhatsApp Business API cost in 2026?

Meta charges per delivered message, by message category and by the recipient's country code. Messages customers send you are free. Hosting the Cloud API is free. Partners and software add their own fees on top, which is where the real spread between tools lives (see Wati's pricing or respond.io's for two very different models).

What changed on October 1, 2026?

Two things, both on Meta's pricing page:

• Service replies are paid again. They had been free since November 1, 2024. Now each business phone number gets 1,000 free per month, with no roll-over, and Meta charges from the 1,001st.
• Utility templates sent inside an open window are paid again. They had been free since July 1, 2025.

One detail to put in your runbook: if there is no payment method on the Meta account, service messages still deliver inside the free 1,000 but stop delivering after that. For a support team, that's a silent outage on the 1,001st reply of the month.

Support teams felt that change straight away. One reaction from the thread where it was announced:

"Paying to talk to your customer is insane! Whatsapp team at Meta clearly are far from understading the many uses of its app."

u/IntroductionOk8688, Meta is about to start charging for Service Messages, Reddit

Here are Meta's list rates in USD for a few markets, effective October 1, 2026:

In each market listed here, the service rate equals the utility rate. Meta can only change prices on January 1, April 1, July 1 and October 1, with a month's notice for rate changes. I track each round in my platform updates post.

What will your support replies cost in Meta fees?

Pick your customers' main market and how many service replies one WhatsApp number sends in a month. The number shown is Meta's fee only, after the 1,000 free replies, at October 1, 2026 list rates.

The takeaway: in the US or India, Meta's fee is a rounding error next to the software you put on top. In the UK and most of Europe it's a real line item, and every back-and-forth message counts, so an assistant that answers in one clear message instead of four saves money as well as patience.

What is the 24-hour window, and why does it decide your setup?

The 24-hour customer service window is the rule that shapes everything else. When a customer messages or calls you, a 24-hour timer starts, and every new message from them resets it. While it's open you can send any free-form reply. Once it closes, you can only send a pre-approved template.

For support, this has a practical consequence: answer fast, or pay to restart the conversation. If a ticket sits in a queue over a weekend and the customer hasn't written again, your Monday reply has to be a template, billed at the utility or marketing rate. That's one of the strongest arguments for an AI first reply on WhatsApp: the answer lands while the window is open.

Someone who has run WhatsApp both directly and through partners made the same point in a direct vs BSP thread:

"your real constraint isn't inbox ui, it's the 24 hour customer service window plus template approval cycles. once a conversation goes cold you can only send approved templates, and template rejection loops will wreck launch timelines more than any bsp fee."

u/Deep_Ad1959, WhatsApp automation, Meta Cloud API directly vs BSP, Reddit

How do message templates work?

Templates are "the only type of message that can be sent to WhatsApp users outside of a customer service window", per Meta's template docs. The rules worth knowing:

• Every template is categorized as marketing, utility or authentication, and the category sets the price.
• Review is automatic, and WhatsApp Manager says it "can take up to 24 hours". Only approved templates can be sent.
• You can create 100 templates per hour, and hold 250 if your business portfolio is unverified or up to 6,000 once verified with an approved display name.
• Meta doesn't translate templates. You submit each language yourself.
• If your WhatsApp queue runs through Zendesk, my Zendesk WhatsApp channel guide covers how it connects.
• Meta can re-categorize an approved template, for example from utility to marketing, with notice. Your "order update" that sneaks in a discount code can end up billed as marketing.

How many messages can you send?

Two separate limits apply, and people mix them up.

Messaging limits cap how many unique customers you can message with templates (outside the window) in a moving 24 hours. Per Meta's messaging limits page, the limit is set per business portfolio and shared by every number in it.

• New portfolios start at 250.
• You reach 2,000 by verifying your business, having your partner verify it, or delivering 2,000 high-quality template messages to unique users in 30 days.
• From there Meta scales you to 10,000, 100,000 and Unlimited automatically, once you keep quality high and use at least half your current limit in 7 days. Each step lands within 6 hours.

You can watch your level in WhatsApp Manager under Account tools:

Throughput is speed. Each number handles 80 messages per second by default, counting inbound and outbound, and gets a free automatic upgrade to 1,000 once the portfolio is unlimited, the number has messaged 100,000+ unique users in 24 hours, and quality is at least medium. Numbers shared with the Business app stay at 20.

Here's my honest read for support teams: neither limit is likely to bite you. Replies inside the window don't count toward messaging limits, and 80 messages a second is far beyond any support queue. The limits matter for outbound campaigns. For support, the window and the price matter far more.

Can you run an AI chatbot on the WhatsApp Business API?

Yes, with one line you shouldn't cross. Section 4.7 of Meta's WhatsApp terms bars AI providers from the platform when AI is "the primary (rather than incidental or ancillary) functionality" on offer. Meta's AI Providers page dates that from January 15, 2026, with exceptions where the law requires access (Brazil, Italy and the EEA, and Türkiye from October 15, 2026).

What it does not ban is a business using AI to answer its own customers. Meta's pricing page says service messages "can be powered by a 3rd-party AI solution or people", and the terms say you "may retain an AI Provider as your Solution Provider". So a bot that answers your order, shipping and product questions is fine. A general ChatGPT-on-WhatsApp product is what Meta shut out. My Meta policy explainer goes deeper, and the builders in r/n8n asked exactly the right question when it landed:

"So my Ai based appointment setter chatbot (chatgpt in the backend) will still work, right?"

u/Then_Treat4366, Meta's new WhatsApp API rule kills general chatbots!, Reddit

It will, because it serves one business.

Should you use Meta Business Agent instead?

Meta now sells its own option. Since July 1, 2026, Meta Business Agent replies are a separate category billed at $2.00 per 1M tokens, which Meta estimates at about 4 to 5 cents per message, and they are charged even in the free 7-day window from click-to-WhatsApp ads. Meta's own comparison puts 10,000 Brazilian AI replies at roughly $400 to $500 on its agent against about $968 for a third-party AI on service messages, though that's Meta's estimate of its competitors' costs, not a neutral benchmark.

Early users are split. One operator in r/WhatsappBusinessAPI flagged grounding as the problem:

"Consistency is a problem. I saw the same product come back at two different prices in two replies. If you don't ground it properly, it just makes things up."

u/Kira_SENPAI_1, Meta Business Agent after getting access, Reddit

I've seen the same thing in three-plus years of eesel putting AI on live support queues: the model is the easy part, the knowledge behind it is the hard part. It's why every eesel rollout is tested against a team's past tickets before it answers a real customer. For a wider comparison of options, my WhatsApp AI chatbot guide and best AI for WhatsApp support cover the tools.

Common mistakes when setting up the WhatsApp Business API

These are the ones I'd check before go-live:

1. Shipping with the temporary token. It expires quickly. Production needs a system user token.
2. No payment method on the Meta account. After 1,000 service replies in a month, replies stop delivering. Tech Provider customers pay Meta directly, so check whose card is on file.
3. Moving an app number without planning for coexistence. If your team lives in the Business app, use a partner that supports coexistence rather than migrating the number outright, and know that group chats and broadcast lists won't come along.
4. Treating limits as per number. Messaging limits are per business portfolio. One noisy marketing number can use up the capacity your support number needed.
5. Letting tickets age past 24 hours. Every late reply becomes a paid template. If your WhatsApp queue sits in a helpdesk like Zendesk, set an SLA under 24 hours, plan the human handoff, or put an AI agent on first reply.
6. Forgetting languages. WhatsApp audiences are often multilingual, and templates need a version per language. Replies inside the window don't, if your agent or bot can answer in the customer's language.

If you'd rather see this done inside a helpdesk you already run, I've written up connecting Zendesk to WhatsApp, routing WhatsApp tickets in Freshdesk, and automating WhatsApp support end to end.

Put eesel on your WhatsApp Business number

The API gets messages to your number. eesel is the AI helpdesk teammate that answers them: it connects to your WhatsApp Business number, learns from your help center, docs, helpdesk and Shopify store, replies in 80+ languages, and hands anything you choose (refunds, complaints, low-confidence answers) to your team through email, Zendesk, Freshdesk or another helpdesk. You set the rules by chatting with it, the same way you'd brief a new hire.

What that looks like on a messaging queue: Question Beauty gets short, multilingual social messages ("price?", "do you ship to my country?") in Gorgias. eesel answers them in the customer's language, checks Shopify before any order answer, and assigns refunds and complaints to a person with a note. In one month it handled about 990 tickets and looked up about 290 orders. ClutchLoop runs the same pattern on chat and email, and its agent stays out of any thread a teammate is already in.

To be straight about scope: eesel answers incoming WhatsApp conversations. It doesn't send marketing templates or campaigns, so keep your partner platform for that. Pricing is simple, $299 a month for 500 credits, where one credit covers a whole WhatsApp conversation however many messages it takes, and there's a free plan with 100 credits to test it on your own questions. Try eesel on your WhatsApp number and see how it handles last week's questions before a single customer does.