Updated on October 25, 2026
To choose a WhatsApp Business API provider, first confirm it uses Meta’s official API (the Cloud API), then compare how it charges (Meta’s rate passed through or with a markup), who owns the account and the number, whether it supports coexistence, how it delivers webhooks and what support it offers. The ten criteria below let you compare any provider with the same questions, regardless of each one’s sales pitch.
Before you start: every serious provider is built on the same WhatsApp Cloud API. Template rules, the 24-hour window, limits and per-message prices come from Meta and apply to everyone. What changes from one provider to another is what they build around it.
The 10 criteria at a glance
| # | Criterion | Question to ask the provider |
|---|---|---|
| 1 | Official API | Do you use Meta’s Cloud API for every number? |
| 2 | Pricing model | Is Meta’s rate passed through at list price or with a margin? |
| 3 | Who pays Meta | Do I add a card at Meta, or do you bill me and pay Meta? |
| 4 | Asset ownership | Are the business portfolio, messaging account and number in my name? |
| 5 | Coexistence | Can I keep the number on the WhatsApp Business app and use the API at the same time? |
| 6 | Webhooks | Is the payload Meta’s or your own format? Can I have several URLs? |
| 7 | API and docs | Are send payloads the same as Meta’s? Are the docs public? |
| 8 | Limits and scale | Do you add your own limits on top of Meta’s? |
| 9 | Support | Who helps me with verification, display name, templates and errors? |
| 10 | Exit | If I leave, do I keep the number and the templates? |
Here’s what to look for in each one.
1. Uses the official API
It sounds obvious, but it isn’t. Some services sell a “WhatsApp API” based on a WhatsApp Web session opened with a QR code. That breaks WhatsApp’s Terms of Service and puts the number at risk of being banned. Signs a service is official: the number is connected through Meta’s Embedded Signup, there are Meta-approved templates and the 24-hour window rule applies. If the service asks you to scan a QR code and lets you send free-form messages to anyone at any time, it isn’t the official API. The difference is explained in official vs unofficial WhatsApp API.
2. Pricing model: pass-through or markup
Total cost has two parts: Meta’s rate per delivered message, and what the provider charges for its service. The most common models in the market:
- Pass-through rate + subscription: messages cost Meta’s list price, and the provider charges a subscription or a per-number fee.
- Markup: the provider charges a per-message price above Meta’s rate card, sometimes with no subscription.
- Bundles: monthly allowances of messages or conversations.
None of these is wrong, but you can only compare them if you know Meta’s rates. Meta publishes rate cards per market on its pricing page. In Brazil, for example, since October 1, 2026 the rates are R$ 0.3217 (Brazilian reais) per marketing message and R$ 0.0350 per utility, authentication or service message (after 1,000 free service messages per number per month). Ask each provider for its price per category and compare line by line. Be wary of “per conversation” pricing: Meta has charged per message since July 2025.
A quick way to compare proposals against your real volume (rates below are Meta’s BRL rates for Brazil; swap in your market’s):
META_RATES = {"marketing": 0.3217, "utility": 0.035, "authentication": 0.035, "service": 0.035}
def monthly_cost(volume, provider_price, subscription=0.0, numbers=1):
"""volume and provider_price: dicts per category. Service already net of 1,000 free per number."""
volume = dict(volume)
volume["service"] = max(0, volume.get("service", 0) - 1000 * numbers)
meta = sum(volume[c] * META_RATES[c] for c in volume)
offer = sum(volume[c] * provider_price.get(c, META_RATES[c]) for c in volume) + subscription
return {"meta_only": round(meta, 2), "offer": round(offer, 2), "difference": round(offer - meta, 2)}
print(monthly_cost({"marketing": 5000, "utility": 20000, "authentication": 0, "service": 3000},
provider_price={"marketing": 0.3217, "utility": 0.035, "service": 0.035},
subscription=0.0))The “difference” is what you pay for the provider’s service. Run the same math for each proposal.
3. Who pays Meta
Meta describes two paths in its solution provider documentation: some partners extend their own credit line to the client, who doesn’t need to add a payment method; in other cases, the client adds its own payment method and Meta bills it directly. What those partner types are is covered in what BSPs and Tech Providers are.
For you, the practical question is: will I get one invoice or two? In which currency? Who issues it? Brazilian businesses, for instance, can now be billed by Meta in reais, but that only matters if Meta bills you directly.
4. Asset ownership
Ask whose name the business portfolio, the messaging account (WABA) and the number are under. Ideally they sit in your company’s portfolio, with the provider only authorized to operate them. That makes business verification easier, keeps the number’s quality history and lets you switch providers later. Also ask who owns the templates: they belong to the messaging account.
5. Coexistence
If the number is already on the WhatsApp Business app, coexistence lets you connect it to the API without removing it from the app, syncing contacts and up to six months of history, according to Meta’s coexistence documentation. There are limits: a fixed throughput of 20 messages per second, and some app features stop working, such as broadcast lists. Not every provider supports it. Details in what syncs and what doesn’t with coexistence.
6. Webhooks
This is where your code depends most on the provider. Check:
- Format. Is the payload Meta’s (
entry[].changes[].value) or a proprietary format? Meta’s format means the official docs apply to you and switching providers costs less. - Several URLs. Can you send events to more than one system (CRM, data warehouse, bot)?
- Retries. What happens if your endpoint is down?
- Security. Is there a signature or token to validate the source?
7. API and documentation
Same principle: if send payloads are Meta’s, the examples in the official docs work with the provider, and so do off-the-shelf libraries. Proprietary APIs may be simpler at first and more expensive when you leave. Check whether the docs are public, have copy-paste examples, list errors and keep up with Meta’s new features (Flows, calling, groups, catalog).
A 15-minute test: send a message using Meta’s payload and check that the response includes the wamid.
curl -X POST "$BASE_URL/messages" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{"messaging_product":"whatsapp","to":"5511999999999","type":"text","text":{"body":"test"}}'8. Limits and scale
The limits that matter are Meta’s: up to 80 messages per second per number by default, and a per-portfolio recipient limit that starts at 250 in 24 hours outside the service window and grows with verification and quality, according to the throughput and messaging limits pages. Ask whether the provider imposes its own limits below those, charges per extra number, and whether a single token gives access to several numbers and accounts, which matters for SaaS companies and agencies.
9. Support
The technical part of the integration is usually quick. What stalls projects is the Meta side: business verification, display name approval, rejected templates, quality drops. Ask which channels the provider uses, in which language, how fast it replies and whether it helps with those steps. Look at the help center before you sign.
10. Exit
Ask how leaving works. With the number in your portfolio and an API in Meta’s format, switching providers means sharing the WhatsApp account (and the Messaging account) with the new partner, under the Meta account model in place since September 23, 2026, and changing the base URL and token. With assets in the provider’s portfolio and a proprietary API, switching may mean rewriting integrations and recreating templates. The process is in how to switch providers without losing your number.
How Vectalk answers these criteria
Vectalk is a proxy for Meta’s official WhatsApp Cloud API. On the verifiable points of the checklist:
- Official API: yes, the Cloud API, connected through Meta’s Embedded Signup.
- Who pays Meta: you pay Vectalk, and Vectalk pays Meta.
- Coexistence: yes, the number stays on the WhatsApp Business app and also works on the API.
- Webhooks: in the format of Meta’s documentation, with several URLs per instance registered via API.
- API: payloads identical to Meta’s; only the base URL (
https://apis.vectalk.com.br/api) and the token change. One organization token accesses every instance. - Documentation: public at docs.vectalk.com.br (in Portuguese).
To compare against your volume, reach the team through the contact page or sign up at apps.vectalk.com.br/register. If you’re just starting, how to get access to the WhatsApp API explains what comes before choosing a provider.
Frequently asked questions
Do I need a provider to use the WhatsApp API?
No. You can integrate directly with Meta’s Cloud API by creating the app, token and webhook and adding a payment method. A provider makes sense when you want to cut that work, get support or avoid adding a payment method at Meta.
Is the cheapest provider per message always the best?
Not necessarily. Compare the total cost at your volume (messages per category, numbers, subscription) and what comes with it: support, webhooks, coexistence and how easy it is to leave.
Can a provider guarantee template or display name approval?
No. Templates and display names are reviewed by Meta. The provider can guide you and review before you submit, but Meta decides.
Can I switch providers later?
Yes, especially if the number and the messaging account are in your portfolio. Plan the switch so you don’t stop sending during the transition.
How do I know if a service uses an unofficial API?
If you connect by scanning a QR code and the service lets you send free-form messages to any contact at any time, without templates, it isn’t using the official API.
Official sources checked on October 25, 2026: WhatsApp Business Platform pricing, Solution providers overview, Coexistence: onboarding WhatsApp Business app users, Throughput, Messaging limits, WhatsApp Terms of Service, Vectalk documentation.