Should you get the WhatsApp Business API directly from Meta or through a provider?

Updated on October 28, 2026

You can get the WhatsApp Business API directly from Meta with no access fee: you create the app, add a payment method and pay only for delivered messages, but you take on the infrastructure, tokens and webhook, and support is limited to Meta’s developer channels. A provider adds a paid layer with simpler billing, support, an inbox and, in many cases, coexistence with the WhatsApp Business app. Going direct is usually better for teams with engineers, a single business and no need for coexistence; a provider is better for teams that want to launch fast and not run the integration themselves.

Below is a point-by-point comparison, with no company names, and the criteria to decide.

What “direct from Meta” and “through a provider” mean

In both cases messages go through the same Cloud API, with the same template rules, 24-hour window, limits and per-message prices. Nobody sells a “better API” on the side. The difference is who sits between your system and Meta.

• Direct: your app on Meta, your system user token, your webhook, your payment method on the Messaging account. This is the route in Meta’s get started guide.
• Through a provider: a partner connects your number (usually through Embedded Signup), runs the app and webhooks, and offers its own API, an inbox, or both. Meta groups partners into Solution Partners, Tech Providers and Tech Partners; see what a WhatsApp BSP and Tech Provider are.

For the platform basics, start with WhatsApp Cloud API: what it is, how it works and what it costs.

Side-by-side comparison

Criterion	Direct from Meta	Through a provider
API access fee	None	Subscription, per-message fee or bundle, depending on the provider
Message prices	Meta’s rate card	Meta’s rate card, passed through or built into the provider’s price
Who bills you	Meta, on your Messaging account’s payment method	Depends on the model: the provider or Meta
Currency	Local currency where Meta supports it (e.g. BRL in Brazil, invoiced by Facebook Brasil)	Set by the provider
App, token, permissions	You create and maintain them	The provider maintains them
Webhook	You host, validate, scale and monitor it	Provided, sometimes with retries
Agent inbox	You build it or buy it separately	Usually included
Coexistence with the app	Documented flow for partners	Offered by some providers
Support	Meta developer support and community	Provider support, which escalates to Meta
Platform changes	You update your code	The provider updates its layer
Third-party dependency	Meta only	Meta and the provider

Want to try it while you read? Create a Vectalk account and send your first message through the official API. Create free account →

Going direct in detail

Cost: messages only

Meta does not charge for access to the Cloud API. You pay per delivered message, based on category and the recipient’s country; rates by market are in WhatsApp API pricing by country. As an example, for recipients in Brazil, since October 1, 2026 a marketing message costs R$ 0.3217 (Brazilian reais) and utility, authentication and service messages cost R$ 0.0350. Each business phone number gets 1,000 free service messages per month, and utility templates sent inside the customer service window are now charged.

The cost that never shows up on Meta’s invoice is yours: engineering hours, the webhook server, the database, monitoring and whoever keeps track of the changelog.

Billing: a payment method on the Messaging account

According to the pricing page, billing is handled in Meta Business Suite, and each Messaging account has its own billing relationship, payment method and spend limits. Without a payment method, Meta delivers service messages within the free tier and stops after that.

For Brazilian companies there is a recent change that helps the direct route: since July 2026, eligible customers (with Brazil as the sold-to country) can create Messaging accounts in BRL, invoiced in reais by Meta’s local entity, Facebook Brasil. Meta asks eligible customers to migrate to BRL by June 30, 2027.

Infrastructure: it’s all yours

A direct integration requires:

1. a Meta app with the WhatsApp use case;
2. a system user with a permanent token and the whatsapp_business_messaging, whatsapp_business_management and business_management permissions;
3. an HTTPS webhook endpoint that answers the verification challenge and validates the X-Hub-Signature-256 signature;
4. a queue so events are not lost when the server restarts;
5. send-rate control, because each number sends up to 80 messages per second by default.

At the very least, your webhook has to answer verification:

// GET /webhook: verification required by Meta
app.get("/webhook", (req, res) => {
  const { "hub.mode": mode, "hub.verify_token": token, "hub.challenge": challenge } = req.query;
  if (mode === "subscribe" && token === process.env.VERIFY_TOKEN) {
    return res.status(200).send(challenge);
  }
  res.sendStatus(403);
});

That is the easy part. The ongoing work is keeping the endpoint available, idempotent and fast.

Support: Meta’s developer channels

Meta’s platform support page says Direct Support (tickets) is for enterprise developers, such as partners and managed partners. All developers can use Meta developer support, the community forum and the bug report form. The status page is at metastatus.com/whatsapp-business-api.

In practice, if you integrate directly and run into a restricted number, a blocked template or a billing issue, your path is Meta’s own support. We cover the channels in Meta support for WhatsApp Business.

Coexistence: a flow built for partners

Coexistence lets the same number run on the WhatsApp Business app and the Cloud API. Meta’s coexistence documentation describes onboarding through Embedded Signup, set up by companies that are already Solution Partners or Tech Providers. For a direct integrator that is not a partner, this path is not documented. Coexistence numbers have a fixed throughput of 20 messages per second.

Providers in detail

What you gain

• Faster launch: the provider already has an approved app, webhooks and a number onboarding flow.
• Simpler billing: one invoice, often in your local currency, without adding a payment method on Meta (when the provider bills the messages).
• Support in your language: the provider answers first and escalates to Meta through partner channels.
• Inbox: a shared inbox, templates and campaigns without writing code.
• Coexistence: when offered, the number keeps working on the phone.

What you give up

• An extra cost layer, which you should compare with the cost of running it yourself.
• Provider dependency: if their API goes down, so do you. Prefer providers that use Meta’s payload so you can switch without rewriting code.
• Their product’s limits: Cloud API features the provider doesn’t expose yet are out of reach.

Since September 23, 2026, switching providers is simpler: the WABA was split into a WhatsApp account (the number) and a Messaging account (templates, billing and webhooks), and changing partners means sharing the WhatsApp account with the new one. See the new WABA structure and how to switch WhatsApp API providers without losing your number.

When going direct is the better choice

Direct integration usually wins when:

• you have an engineering team comfortable with REST APIs, queues and observability;
• it’s a single business using its own numbers, not serving third-party clients;
• you don’t need coexistence with the WhatsApp Business app;
• your volume is high enough that any per-message markup from a middleman adds up;
• you want full control over versions, data and latency;
• your customer service already runs on your own platform and only the channel is missing.

When a provider is the better choice

A provider usually wins when:

• there is no dedicated developer or the deadline is tight;
• you need coexistence to keep the phone working;
• you are a SaaS company or agency that needs to connect client numbers without joining Meta’s partner programs;
• you want support in your language and a single bill;
• you need a ready-made agent inbox.

To evaluate vendors, use these 10 criteria for choosing a WhatsApp API provider.

A middle path: a proxy that keeps Meta’s payload

Vectalk works as a proxy for the official Cloud API: your application sends to https://apis.vectalk.com.br/api/messages the same JSON it would send to graph.facebook.com, and Vectalk forwards it to Meta. You pay Vectalk, and Vectalk pays Meta. Webhooks follow the format in Meta’s documentation, and coexistence is available to keep the number on the WhatsApp Business app.

Because the payload is Meta’s, you are not locked in: you can start on the proxy and move to a direct integration later (or the other way around) by changing the base URL and token. The walkthrough is in the quickstart, and you can sign up at apps.vectalk.com.br/register.

Frequently asked questions

Is going directly to Meta cheaper?

For messages, yes: you pay Meta’s rates with no middleman. Overall, it depends on what your team and infrastructure cost. For small operations, maintaining a webhook, tokens and monitoring can cost more than a provider’s fee.

Can I pay Meta in my local currency?

In some markets, yes. In Brazil, for example, since July 2026 companies with Brazil as their sold-to country can create BRL Messaging accounts invoiced by Facebook Brasil, according to Meta’s pricing page.

Does Meta support businesses that integrate directly?

All developers can use Meta developer support, the community forum and the bug report form. Meta describes Direct Support, with tickets, as a channel for enterprise developers such as partners.

Do providers get a different API from Meta?

No. Everyone uses the same Cloud API, with the same limits and per-message prices. What changes is what the provider builds around it: inbox, support, billing and coexistence.

Can I leave a provider and go direct later?

Yes. With the split between the WhatsApp account and the Messaging account, the number can be shared with another partner or with your own app. If your provider uses Meta’s payload, the code change is small.

---

Official sources checked on October 28, 2026: Get started (Cloud API), Pricing, WhatsApp Business Platform support, Coexistence onboarding, Cloud API overview, Account model evolution, WhatsApp Business API status, Vectalk quickstart.