WhatsApp Cloud API vs BSP: Go Direct or Use a Partner?
Meta lets any business use its WhatsApp Cloud API directly. So why do so many businesses pay a Business Solution Provider to sit in the middle, and why do some engineering teams refuse to? The WhatsApp Cloud API vs BSP question comes down to who does the work around the API: onboarding, billing, support, and the inbox your team actually types into.
The answer also shifted this autumn. Meta's new account model separates your phone number from templates and billing, which changes what owning your WhatsApp setup means and makes a hybrid of direct and partner possible on one number. Here is how to choose.
The short answer
Go direct if you have engineers who will own the integration and you mainly need an API. Use a BSP if you need a ready-made inbox, a partner credit line or invoice, faster business verification, or a support desk to call. Use both if you already have a direct integration and want a partner for one job, such as marketing campaigns, on the same number.
Meta's per-message charges are identical in all three cases. What you're choosing is who builds and runs everything else.
What going direct actually involves
Direct means Meta charges only its message rates, and you build and run the rest. The setup itself is a few hours; the ongoing ownership is the real commitment.
- Create a Meta app with the WhatsApp use case, connected to your business portfolio.
- Register your business phone number and get the display name approved.
- Create a system user and a long-lived token with
whatsapp_business_messagingandwhatsapp_business_management. - Subscribe to webhooks, check the
X-Hub-Signature-256header on every delivery, and store messages and statuses. - Add a payment method in Billing Hub. Since October 1, 2026, a number with no payment method stops delivering service messages once its 1,000 free ones for the month are used.
- Build the inbox, template management, opt-out handling and reporting your team needs.
A direct send is a single authenticated call. Use the current Graph API version from Meta's changelog in place of v23.0:
curl -X POST "https://graph.facebook.com/v23.0/PHONE_NUMBER_ID/messages" \
-H "Authorization: Bearer $WHATSAPP_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"messaging_product": "whatsapp",
"to": "919811122233",
"type": "template",
"template": { "name": "order_shipped", "language": { "code": "en" } }
}'
For support, Meta's support page offers every developer its developer support channel, a community forum, bug reports and the API status page. Direct Support tickets, with a target first response within 24 hours on business days, are aimed at partners and managed enterprise developers.
What a BSP adds, and what it can't change
A provider can add software, billing and a support layer. It can't change Meta's rules, and any BSP that implies otherwise is overselling.
| A BSP can add | A BSP can't change |
|---|---|
| Agent inbox, campaign builder, chatbot tools | Meta's per-message rates |
| A credit line and invoicing (Solution Partners only) | Template approval and categorization |
| Partner-led business verification (Select and Premier Solution Partners) | Messaging limits and quality rating |
| Faster onboarding through Embedded Signup | The 24-hour customer service window |
| A support desk that escalates to Meta | Policy enforcement and bans |
It also helps to know which kind of partner you're talking to. Meta's partner overview describes Solution Partners, which have credit lines and can invoice you for API usage, and Tech Providers, whose clients add their own card so Meta bills them directly while the provider bills for its software. Plenty of tools marketed as BSPs are Tech Providers, so ask who will bill you for messages.
Ownership and lock-in under Meta's new account model
You always own the WhatsApp account that holds your number. The Messaging account that holds templates, billing and webhook subscriptions can be yours or the partner's, and that's where lock-in now lives. Meta says the model reached all businesses by mid-October 2026 (account model overview).
- WhatsApp account. One phone number, plus profile and catalog. Owned by your business and shareable with up to five Solution Partners.
- Messaging account. Templates, payment method, webhooks. Each partner working with you gets its own, and one can be shared with up to two partners.
- Credit line trap. If a partner attaches its credit line to a Messaging account you own, that Messaging account can't then be shared with another partner.
- Templates stay put. Templates belong to the Messaging account they were created in. Meta's Template Migration API only copies between Messaging accounts owned by the same business.
- Any partner can deregister your number. Meta lists this as unchanged in the new model. Share access only with partners you trust, and remove old ones promptly.
- Shared ceilings. Throughput stays per phone number and messaging limits per business portfolio, so a partner and your own integration draw on the same capacity.
If the account names are new to you, our explainer on what a WhatsApp Business Account (WABA) is maps the old terms to the new ones.
Decision table
| Your situation | Go direct | Use a BSP | Hybrid on one number |
|---|---|---|---|
| Engineering team, API-only use (alerts, codes from your app) | Best fit | Works, costs more | Rarely needed |
| Non-technical team needs an inbox and campaigns this month | Heavy build | Best fit | Not applicable |
| Finance wants to pay a partner by invoice | Card in Billing Hub | Solution Partner | Partner handles billing for its traffic |
| Direct integration exists, marketing wants a campaign tool | Build it yourself | Re-platform everything | Best fit: add a partner for marketing |
| Strict in-house data handling | Best fit | Depends on the partner's processing | Possible, with a narrow partner scope |
| Business verification is stuck | Self-serve review | Select or Premier partner can submit for you | Possible |
The hybrid column is new. Meta's documentation describes a direct developer outsourcing part of its messaging, such as marketing, to a partner on the same phone number, with each side billed through its own Messaging account. If one access token can send from both, include messaging_account_id in sends; Meta says the newest API version will require it in that case from the first half of 2027.
The cost comparison people get wrong
Meta's charges are the same either way, so the real comparison is a provider's fees against your engineering and support time. Most teams underestimate the second number because they price the build and forget the upkeep.
A direct integration has to keep up with Graph API version changes, the new account model's later phases (Meta schedules a mandatory move from phone number IDs to WhatsApp account IDs in the first half of 2028), and the Marketing Messages API, which takes over all marketing sends when Cloud API stops supporting them on October 13, 2027. A good provider absorbs that work. A weak one passes it to you anyway.
On the other side, provider fees scale with volume or numbers. Our roundup of the best WhatsApp API providers prices one sample month across four of them, and the guide to BSP fees shows how to read a quote line by line.
Where Tenashi fits
Some teams arrive at this question because they want a shared inbox on WhatsApp, not an API. If that's you, there is a third route outside the direct or BSP choice. Tenashi links your existing WhatsApp or WhatsApp Business number by QR scan, so your team works DMs and groups in one inbox, with a CRM under every chat, notes, assignments and follow-ups. It's a flat plan from $18/mo, with no per-message fees and no templates to get approved.
The limit is real: Tenashi isn't Meta's platform and isn't a BSP. There are no templates, interactive buttons or verified badge, and sends are paced for safety, so OTPs and bulk alerts belong on the Cloud API or with a BSP. WhatsApp can still ban numbers that spam; Tenashi's pacing lowers that risk but can't rule it out.
See every feature · Get started
FAQ
Is the WhatsApp Cloud API free to use directly?
Access is free; messages aren't. Meta charges per delivered message by category and recipient country, and service replies beyond 1,000 per number per month are charged as of October 1, 2026. Messages users send you stay free. Going direct avoids provider fees, but you pay for the integration in engineering time instead.
Do I own my WhatsApp number if I use a BSP?
Under Meta's new account model, the WhatsApp account holding your number is owned by your business even when a partner onboards you. The Messaging account holding templates and billing can be owned by you or the partner. Check both in Meta Business Suite under Settings, Accounts before you sign a contract.
Can I use Cloud API directly and a BSP on the same number?
Yes, under the new account model. You share your WhatsApp account with the partner, and each integration gets its own Messaging account with separate templates and billing. Throughput and messaging limits are shared, so coordinate volume, and send messaging_account_id whenever one token can reach more than one Messaging account.
Does a BSP get templates approved faster?
No. Meta reviews templates the same way whoever submits them. Where a partner can speed things up is business verification: Select and Premier Solution Partners can submit it on your behalf, which Meta says has a much faster turnaround. A good partner also catches template mistakes before you submit them.
What support do direct developers get from Meta?
Direct developers can use Meta's developer support channel, the developer community forum and bug reports, and watch the WhatsApp Business API status page. Direct Support tickets are aimed at partners and managed enterprise developers, and Meta tells end clients of a Solution Partner to contact that partner first.
Go direct when your team wants to own the plumbing; pick a partner when you'd rather own the outcome. For the full picture start with the complete guide to the WhatsApp API and the steps in how to get WhatsApp API access. If the real need is a team inbox on your existing number, get started with Tenashi.