LinkedIn
Word lid van de Slack-gemeenschap Inhoudsopgave
Basisprincipes
Categories & speed
Build & evaluate
Oplossing & Veelgestelde Vragen
WhatsApp API
WhatsApp API Aanbieders: Cloud API, BSP, or Connected Account
Meta's WhatsApp On-Premises API stopped delivering messages on 23 October 2025. The only paths left in 2026 are Meta's Cloud API directly, a Business Solution Provider reselling it, or a connected-account API that authenticates an existing WhatsApp number. This guide compares setup time, Meta verification, cost and limits across all three, for developers integrating WhatsApp into their own product.
Bouwen met Unipile See the WhatsApp API docs
# link an existing WhatsApp account
curl -X POST "https://<subdomain>.unipile.com:<port>/api/v1/accounts" -H "X-API-KEY: <ACCESS_TOKEN>" \
-F provider=WHATSAPP
// response: scan or pair, no Meta Business step
{
"voorwerp": "Checkpoint".",
"qrCodeString": "2@AbC..."),
"account_id": "ACo_9F21"
}Linked in under a minute, no Meta Business verification
Definitie
What is a WhatsApp API provider?
A WhatsApp API provider is any party that gives your software programmatic access to WhatsApp messaging. In 2026, that means one of three categories: Meta itself through the Cloud API, a Meta-approved Business Solution Provider (BSP) reselling that same Cloud API, or a connected-account API that authenticates an already-active WhatsApp number on behalf of its owner.
In shortA WhatsApp API provider is whoever sits between your product and WhatsApp: Meta's own Cloud API, a BSP reselling it, or a connected-account API that links an existing number instead of creating a new business identity.
The three categories are not interchangeable, and mixing them up is a common cause of stalled WhatsApp integrations. Meta's Cloud API puts a business phone number under a WhatsApp Business Account (WABA) that the business owns, with Meta billing per message directly. A BSP resells that same Cloud API, adding onboarding support, tooling and its own margin or subscription on top. A connected-account API skips the WABA path entirely: it authenticates a WhatsApp number that is already active, the way WhatsApp Web does, without creating a new business identity on Meta's platform.
For a marketing team buying one WhatsApp tool, the difference mostly shows up as a line on an invoice. For a developer shipping WhatsApp as a feature inside a SaaS product, it changes which onboarding flow a customer has to complete before the first message goes out, which is the question the rest of this guide answers for each of the three WhatsApp API provider types. Some teams search for a WhatsApp conversation API provider instead: it is the same three categories under a different name, since every WhatsApp integration is, underneath, a way to send and receive conversations.
The 2026 landscape
What are the three ways to access the WhatsApp API in 2026?
Since Meta sunset the On-Premises API, only three access paths remain: Meta's Cloud API directly, a BSP reselling the Cloud API, or a connected-account API. The choice is no longer between cloud and on-premise hosting, it is about who owns the WhatsApp Business Account and how fast a first message can go out.
Why "Cloud API vs Business API" is the wrong question now
9 Jan 2024 New WhatsApp features ship on the Cloud API only. The On-Premises client gets bug fixes, nothing else.
1 Jul 2024 New business phone numbers can only be registered on the Cloud API.
23 Oct 2025 The last On-Premises version (v2.63) expires. Messages to numbers still on it are no longer delivered.
Source: Meta, WhatsApp On-Premises API sunset, consulted 6 August 2026.
Criterium
Cloud API direct
BSP
Gekoppelde account
Who owns the WABA
U
The BSP, in most cases
No WABA
Meta Business verification
Vereist
Required, handled by the BSP
Niet vereist
Time to first message
Dagen tot weken
Uren naar dagen
Notulen
Sjablonen voor berichten
Required outside the service window
Vereist
Niet van toepassing
Facturering
Meta, per message
Meta pass-through, plus margin or subscription
Provider pricing
Groepsberichten
Official Business Account only, 8-participant cap
Same Meta requirement passes through
Native, no separate cap
Inbound history
Webhook only, from connection
Webhook only
Existing conversations accessible
Het beste voor
Teams that need an official brand identity
Teams that want onboarding handled
Products that embed a user's own account
Group messaging works differently across all three paths, and the participant cap trips up more integrations than any other row in this table. See the full breakdown in WhatsApp group messaging.
Build the connected-account path Optional layer
Do you need a BSP to use the WhatsApp API?
No. Since the Cloud API became generally available in 2022, a business can onboard directly with Meta without going through a Business Solution Provider. A BSP is optional, and it adds onboarding support, tooling and often a margin on top of Meta's per-message price.
Going direct means dealing with Meta's own developer console, WABA setup and Business verification without a guided flow, which suits a team with the engineering time to build its own template management and webhook handling. A BSP exists to remove that friction: it pre-fills much of the verification paperwork, ships a dashboard on top of the raw API, and often bundles support. A Meta-approved BSP is sometimes called an official WhatsApp API provider, since it operates inside Meta's own Business Solution Provider program rather than reselling access informally. None of that changes the underlying Cloud API, its per-message billing, or Meta's verification requirement: a BSP handles the process, it does not replace it.
What a BSP typically adds
Guided onboarding for WABA creation and Business verification
A dashboard on top of the raw Cloud API endpoints
Template management tooling and approval tracking
Support and account management, billed as a subscription or a margin on Meta's price
What stays the same either way: the WABA, Meta's per-message pricing underneath, and Business verification for the number.
The category that matters
What is a third-party WhatsApp API, and which ones are safe to build on?
A WhatsApp third-party API covers two very different things. Meta-approved BSPs and connected-account APIs operate within WhatsApp's terms of service. Reverse-engineered libraries that emulate the WhatsApp client do not, and they put the underlying phone number at risk of being blocked. A WhatsApp unofficial API search usually means one of these three categories, rarely all of them at once.
Conform
Meta-approved BSP
Resells the official Cloud API under Meta's Business Solution Provider program. A WABA and Meta Business verification are still required, the BSP just manages the process and adds a layer of tooling on top.
Conform
Connected-account API
Authenticates an existing WhatsApp account through a QR code or a pairing code, namens de geauthenticeerde gebruiker. No WABA, no Meta Business verification. This is the category Unipile operates in. Searches for an "unofficial WhatsApp API" usually mean this category, even though it authenticates the same client WhatsApp Web uses rather than bypassing WhatsApp's own systems.
High risk
Reverse-engineered libraries
Open-source projects that reimplement WhatsApp's protocol without any involvement from Meta or WhatsApp. Frequently broken by client updates, unmaintained, and in violation of WhatsApp's Terms of Service, which puts the connected number at risk of being blocked. Not linked from this guide.
For a developer deciding where to build, the practical test for any WhatsApp third party API is simple: does the provider authenticate through WhatsApp's own client behavior (QR code, pairing code, Meta's Cloud API), or does it reimplement WhatsApp's protocol independently? The first two categories answer yes and stay inside WhatsApp's terms. The third does not, and no amount of feature parity makes up for a number that can be blocked without notice.
Build your connected-account integration Speed comparison
How long does each provider type take to reach a first message?
Direct Cloud API onboarding takes days to weeks because Meta Business verification runs in parallel with WABA setup. A BSP compresses that to hours or days by pre-filling much of the paperwork. A connected-account API reaches a first message in minutes, because there is no WABA to create and no verification to pass.
Days-weeks
Cloud API direct
Hours-days
BSP
Notulen
Gekoppelde account
The gap comes entirely from what has to happen before the first message, not from any technical limit. For the full checklist Meta requires before a Cloud API number can send anything, see WhatsApp API access requirements.
Prijzen
What does the WhatsApp API cost with each provider type?
Meta has billed per message since 1 July 2025, priced by template category: marketing, utility or authentication. The 24-hour customer service window still exists, but it now determines which messages are free rather than what gets billed. A BSP adds a subscription or a margin on top of that per-message price.
Both Cloud API paths, direct and through a BSP, sit on the same Meta price list underneath: a BSP cannot make Meta's per-message cost disappear, it can only add its own fee for onboarding and tooling, or absorb part of it into a flat subscription. A connected-account API works on a different model entirely. There is no WABA and no template requirement, so there is nothing for Meta to bill by message: pricing comes from the provider itself, typically a flat subscription rather than a per-message charge.
Source: Meta, WhatsApp Business Platform pricing, consulted 6 August 2026.
For the full breakdown of template categories, free windows and Meta's price list, see WhatsApp Zakelijke API-prijzen.
Integration effort
Which WhatsApp API provider is easiest to integrate?
Integration effort is driven by four things: the authentication model, whether webhooks work without extra setup, whether a sandbox exists, and how many channels the same API covers. Of the three paths, a connected-account API is the easiest WhatsApp API provider to integrate for messaging and verification, because authentication is a QR code or pairing code rather than a Meta verification process.
1Send the first message
# start a chat and send text in one call
curl -X POST "https://<subdomain>.unipile.com:<port>/api/v1/chats" -H "X-API-KEY: <ACCESS_TOKEN>" \
-F account_id=<ACCOUNT_ID> \
-F aanwezigen_ids=<ATTENDEE_ID> \
-F tekst="Hello, this is my first message"
// 201 Created
{
"voorwerp": "ChatStarted",
"chat_id": "cWh_18a2",
"message_id": "mWh_77e0"
}2Receive it as a webhook
// POST to your registered webhook URL
{
"gebeurtenis": "message_received",
"account_id": "ACo_9F21",
"account_type": "WHATSAPP",
"chat_id": "cWh_18a2",
"message_id": "mWh_77e2",
"tijdstempel": "2026-08-06T10:32:04Z",
"bericht": "On my way, 10 minutes",
"afzender": { "naam": "..." }
}Both calls run against the same account once it is linked: no separate webhook subscription step, no template to submit for approval, no sandbox number to graduate out of. Where a direct Cloud API integration means registering a Meta developer app, creating a WABA, submitting for Business verification and building a webhook listener before the first template message can go out, a connected-account integration is two calls: authenticate the account, then send.
Full request and response reference: send WhatsApp messages via API en de WhatsApp API-documentatie.
Start building in minutes Evaluation criteria
How do you evaluate a WhatsApp API provider as a developer?
Evaluate a WhatsApp API provider on seven criteria: authentication model, verification requirements, time to first message, webhook reliability, message type coverage, billing transparency, and whether the same API also covers your other channels.
There is no single best WhatsApp API provider for every product. Whether it gets called a WhatsApp API provider or a WhatsApp message provider depends on who is asking, not on what it does, and the seven criteria below apply either way. Most lists of the best WhatsApp API providers rank tools for a marketing team choosing a chatbot, not an API for a developer to build on, which is why they rarely help here.
1
Authenticatiemodel
QR code, pairing code, or a full Meta Business verification flow before anything can be tested.
2
Verification requirements
Whether a WABA and Meta Business verification are mandatory before the first message, or not required at all.
3
Time to first message
Minutes, hours or weeks, tested end to end rather than measured from "API access granted".
4
Webhook reliability
Real-time delivery for inbound messages and status changes, without a separate subscription step to configure first.
5
Message type coverage
Text, media, templates, voice notes, and groups if the product needs them.
6
Billing transparency
Per message, flat subscription, or a margin on top of Meta's own price, disclosed upfront rather than discovered on the first invoice.
7
Cross-channel coverage
Whether the same account and API also handle LinkedIn, Instagram, Telegram or email, so WhatsApp is not a one-off integration to maintain alone.
Gekoppelde account
Can you connect an existing WhatsApp account instead of creating a WABA?
Yes. A connected-account API authenticates an existing WhatsApp account through a QR code or a pairing code, namens de geauthenticeerde gebruiker. No WhatsApp Business Account is created, and no Meta Business verification is required.
This is how Unipile's WhatsApp API works: it acts as an independent technical intermediary between a product and WhatsApp, and every call executes on behalf of the account holder who authorized the connection, not as a standing business integration with Meta. Once linked, existing chats and groups become reachable through the same unified messaging API used for LinkedIn, Instagram, Telegram and email, so WhatsApp does not need a separate integration path from the rest of a product's messaging surface.
Gegevensbeheer
Data retrieved through a connected WhatsApp account is not stored in a parallel system or kept as an independent archive. Access stays scoped to the session of the authenticated user who linked the account.
Platformlimieten
Unipile relays WhatsApp's own native rate limits rather than imposing a separate one. How often the account sends messages remains a customer-side decision, made within WhatsApp's own limits for that number.
This is a different path from a Cloud API number: see using the WhatsApp API with an existing account for how the pillar guide frames both options side by side.
Bouw het met Unipile By use case
Which WhatsApp API provider fits your use case?
If WhatsApp is one channel among several, a single API covering WhatsApp, LinkedIn, Instagram, Telegram, Gmail, Outlook and IMAP removes the need to maintain one integration per provider.
CRM and sales tools
Log WhatsApp conversations next to LinkedIn messages and email threads in the same contact timeline, instead of a WhatsApp-only silo bolted onto the CRM.
Helpdesk and support
Route WhatsApp, Instagram and Telegram conversations into one shared inbox, with the same ticket and reply model across all three.
AI-agenten
Give an agent one API to read and reply across channels instead of a separate SDK per provider, from WhatsApp through to IMAP mailboxes.
ATS and recruiting
Reach candidates over WhatsApp or LinkedIn, then sync confirmed interviews straight to Google Calendar or Outlook Calendar.
WhatsApp API providers, frequently asked questions
Meta verification, pricing, group messaging and where Unipile fits between Cloud API, BSP and connected-account paths.
No, not for business use. Meta has billed the Cloud API per message since 1 July 2025, by template category: marketing, utility, or authentication. Messages sent inside the 24-hour customer service window are free, and so are Free Entry Point windows opened from ads or page buttons. A connected-account API is priced separately by the provider, typically a flat subscription rather than a per-message fee from Meta.
Only for the Cloud API path, direct or through a BSP: both require a WhatsApp Business Account and Meta Business verification before the first message. A connected-account API is different, it authenticates an existing WhatsApp account namens de geauthenticeerde gebruiker through a QR code or pairing code, with no Meta Business verification at all.
Yes, two ways. A business can onboard directly with Meta's Cloud API, without a Business Solution Provider, since it became generally available in 2022. A connected-account API skips both the BSP and the WABA entirely, by authenticating an existing WhatsApp number instead.
Meta sunset it. New features stopped shipping to it on 9 January 2024, new business phone numbers could no longer register on it from 1 July 2024, and the final version, v2.63, expired on 23 October 2025: messages exchanged with a number still running it are no longer delivered. Meta's own documentation recommends migrating to the Cloud API. Source: Meta, WhatsApp On-Premises API sunset.
It depends on the path. The Cloud API's Groups API requires an Official Business Account and caps groups at 8 participants, with no endpoint to add a participant directly. A connected account follows WhatsApp's native group mechanics instead, with no separate participant cap.
No. Unipile is an independent technical intermediary that connects an existing WhatsApp account on behalf of the authenticated user, by QR code or pairing code. Unipile is not affiliated with, endorsed by, or sponsored by Meta or WhatsApp.
Heb je nog vragen? Ons team staat klaar om te helpen.
Beginnen met bouwen
Build with the WhatsApp API provider that fits your product
Link an existing WhatsApp account by QR code or pairing code, on behalf of the authenticated user, and send the first message through the same API that covers LinkedIn, Instagram, Telegram, Gmail, Outlook and IMAP.
Bouwen met Unipile Read the WhatsApp API docs
NL 
EN 
FR 
ES 
DE 
IT 
BR 
PL 
TR