WhatsApp Cloud API: direct from Meta or via a provider?

Short answer: the WhatsApp Cloud API is Meta's hosted WhatsApp Business API, and you can connect to it yourself or through a provider. Going direct suits teams with developers who want to build their own inbox and run their own webhook server; a provider suits most other businesses because onboarding, a team inbox, AI and support come ready. Meta charges message fees from its published rate cards either way, and a provider adds its own platform fee.

Updated 29 October 2026.

What the WhatsApp Cloud API is

The Cloud API is the part of Meta's WhatsApp Business Platform that lets you send messages and make calls from your own software. Meta's comparison page describes it as "hosted on Meta servers and supported by Meta data centers", so there is no WhatsApp server for you to install. Around it sit WhatsApp Manager (a web app for accounts, phone numbers, templates and analytics), webhooks that deliver incoming messages and status updates to your server, and the Business Management API.

The older On-Premises API, which businesses hosted themselves, has been retired. Meta stopped shipping new features to it in January 2024, allowed new numbers to register only for Cloud API from 1 July 2024, and the final On-Premises version expired on 23 October 2025. So the real choice today is not where the API runs, but who builds and runs everything around it.

Going direct to Meta: what you take on

A Meta developer app. You create an app with the WhatsApp use case in Meta's App Dashboard and connect it to your business portfolio and WhatsApp Business Account.
Access tokens. The temporary token from the setup screen expires quickly. For production, Meta recommends a system user access token, created in Business Settings and given the right permissions. You store it securely and manage it.
A webhook endpoint. Meta sends incoming messages, delivery statuses, call events and template quality changes as JSON to a server you nominate. If your endpoint does not return HTTP 200, Meta retries for up to seven days, which can produce duplicates. Your server needs to stay up and handle repeats safely.
Templates. You create them in WhatsApp Manager or through the Message Templates API. Meta reviews each one automatically and only approved templates can be sent. Templates are the only messages allowed outside a customer service window.
Your own inbox. The Cloud API is an API. If staff need to read, assign and answer chats, you build or buy that interface, along with any chatbot, reporting and user permissions.
Billing. You add a payment method to your WhatsApp Business Account and Meta bills you for messages.
Support. Meta's Direct Support tickets are described as being for enterprise developers such as partners. Other developers can use Meta's developer support, the developer community forum and bug reports.

One more point: if you want to keep using the WhatsApp Business app on the same number (Meta calls this Coexistence), Meta's documentation lists being a Solution Partner or Tech Provider among the requirements for the developer doing the onboarding.

Going through a provider: what changes

Embedded Signup. You complete Meta's onboarding inside the provider's platform: select or create a business portfolio and WhatsApp Business Account, verify your phone number and enter a display name.
No token or webhook hosting. The provider uses a token scoped to your business and runs the webhook endpoint for you.
A ready inbox. Shared chats, assignment, roles and reports from the first day.
Templates without code. A screen to write, submit and track templates.
AI and automation. Chatbots and AI agents that reply and hand over to a person.
Support from a person you can reach. Ideally in your own time zone.

The trade-offs are a monthly fee and relying on the provider's features. A good provider still gives you APIs and webhooks so your developers can connect your own systems.

Cost: what you pay either way

Meta charges per delivered template message, by category (marketing, utility or authentication) and by the recipient's country, and publishes its rate cards. It does not charge for undelivered messages. Replies inside an open customer service window are service messages; for Sri Lanka, the first 1,000 per number each month are free and a small per-message fee applies above that. Meta's pricing documentation sets rates by market and category, not by how you connect. When you onboard through a Tech Provider, you add your own payment method and Meta bills you directly for API usage, while the provider bills you separately for its own service.

Direct: Meta's message fees, plus your developers' time, hosting, monitoring and maintenance.
Through a provider: Meta's message fees, plus the provider's platform fee. Ask whether the provider adds a markup to Meta's fees.

With Bloomwire, Meta's fees are paid directly to Meta from the card on your WhatsApp Business Account. We add no markup and do not collect Meta fees. Plans start at LKR 8,500 a month; AI agent replies are a separate prepaid, token-based service at about US$0.002–0.015 per reply. See our pricing page and the October 2026 pricing guide for current Sri Lankan rates.

Direct or provider: a quick decision table

Your situation	Direct from Meta	Through a provider
Developers who can run a webhook server around the clock	Needed	Not needed
Team needs a shared inbox now	You build it	Ready
Keep the WhatsApp Business app on the same number	Needs partner status per Meta's requirements	Available if the provider supports Coexistence
Chatbot in Sinhala, Tamil and English	You build or integrate it	Check the provider
Fully custom workflows	Full control	Through the provider's API and webhooks
Support	Meta's developer channels	The provider's team
Running cost	Meta fees plus engineering and hosting	Meta fees plus platform fee

What Bloomwire's platform adds

Bloomwire is an official Meta Tech Provider. Our Unecast platform connects to the Cloud API through Meta Embedded Signup, with two paths: Coexistence, to keep the WhatsApp Business app on your number, or a new dedicated Cloud API number. Most businesses complete onboarding within 10 to 30 minutes, depending on the path, Meta verification requirements and number verification.

Shared team inbox on web and mobile, with assignment and canned replies.
AI agents trained on your prices, schedules and FAQs, in Sinhala, Tamil and English, handing over to a person when needed.
Templates and broadcasts to opted-in customers, a live dashboard and an audit trail.
WhatsApp calling and a cloud call center.
APIs and webhooks to connect your website, CRM, online store or payment gateway, documented on the Unecast developer hub.
Hosted on AWS, encrypted in transit and at rest, with role-based access and audit logging.

If you need something bespoke, our software engineering team builds WhatsApp, SMS and AI integrations.

Frequently asked questions

Do I pay Meta more if I use a provider?

Meta sets its rates by country and message category. What can differ is whether a provider adds a markup, so ask. Bloomwire adds none, and you pay Meta directly.

Can I still use the On-Premises API?

No. Meta's final On-Premises version expired on 23 October 2025, and it can no longer send messages. The Cloud API replaces it.

Do I need a developer to use the Cloud API directly?

Yes. You need to create a Meta app, manage access tokens, host a webhook endpoint and build any interface your staff will use.

Which access token should I use if I go direct?

Meta recommends a system user access token for businesses that access only their own data. Temporary tokens expire quickly and are meant for testing.

Can I use a provider and still build my own integrations?

Yes, if the provider offers APIs and webhooks. Unecast does, so your developers can connect your systems while your team uses the ready inbox.

Sources

AI ChatbotBusiness MessagingSri LankaWhatsAppWhatsApp APIWhatsApp Business API

Bloomwire team

Notes on messaging, voice and AI from the team building Sri Lanka's communication platform.

More insights

WhatsApp Cloud API: direct from Meta or through a provider?