Meta Verified Tech Provider · 0% markup
Developer guide · WhatsApp Cloud API
How to Get WhatsApp Business API Without a BSP
A developer asks a simple question: "Do we really need to sign up with a provider to use the WhatsApp Business API, or can we go straight to Meta?" Most answers online come from providers, so the reply is usually "sign up with us." The honest answer is that you can go direct. Meta's own Cloud API is open to any business with a Meta developer account. What you skip is the software a provider gives you, and what you take on is building and running it yourself. This guide walks through the direct path step by step, what you'll have to build, what it really costs, and where a third option, a Tech Provider, fits in between.
By the On Cloud API team · First published · Updated
Quick answer: can you get the WhatsApp Business API without a BSP?
Yes. Any business can create a Meta app, add the WhatsApp product and call the Cloud API directly, with no Business Solution Provider involved. Meta still charges its normal per-message rates and you add your own payment method. What you give up is the provider's inbox, template tools and support, so you build and host that layer yourself.
Key takeaways
- Meta's documentation says businesses building an app only for themselves should follow the Cloud API "Get Started" guide. No partner is required.
- Meta's per-message fees are the same on every path. The difference is who builds the software and whether anyone adds a markup.
- Going direct means you own the webhook, the token, the inbox, template management and uptime.
- There's a middle route: with a Meta Tech Provider, you keep the WhatsApp account and pay Meta directly, and the provider charges only for its software.
- Business verification is a Meta requirement on every path. Skipping a provider doesn't skip verification.
What are the three ways to get the WhatsApp Cloud API?
You can go direct through a Meta developer app, onboard through a Tech Provider, or onboard through a Solution Partner, often still called a BSP. All three use the same Meta Cloud API. They differ in who builds the software, who pays Meta, and whether a credit line or markup sits between you and Meta's rates.
| Path | Software | Who pays Meta | Typical fit |
|---|---|---|---|
| Direct (your own Meta app) | You build everything | You, with your own payment method | Teams with developers and a clear, narrow use case |
| Tech Provider | Provider's inbox, templates, campaigns, bots | You, directly. Meta says Tech Providers don't have credit lines, so clients add their own payment method | Businesses that want software but no markup and direct Meta billing |
| Solution Partner (BSP) | Provider's platform and services | Often the partner, through its credit line, then it invoices you | Businesses that want one invoice and managed onboarding |
On every path, the WhatsApp Business Account (WABA) should sit in your own Meta business portfolio. That's what lets you change provider, or move to a direct setup, later. If you're unsure how WABA ID, phone number ID and business ID relate, read WABA ID vs phone number ID vs business ID.
What are the steps to get the WhatsApp Cloud API directly from Meta?
Create a Meta developer app with the WhatsApp product, test with Meta's free test number, generate a permanent system user token, add and register your real number, set up an HTTPS webhook, add a payment method, get templates approved and complete business verification. Most teams start verification on day one, because it often takes longest.
- Business portfolio: create or use your Meta business portfolio with your legal business name and website.
- Meta app: in the Meta developer dashboard, create an app, choose the WhatsApp use case and link it to the business portfolio. Meta creates a test WABA for you.
- Test number: Meta provides a test business number that can message a small number of verified recipient phones, so you can build before your real number is ready. Our test number to production guide covers the switch.
- Permanent token: the token shown in the dashboard expires within about a day. Create a system user, give it the WhatsApp messaging and management permissions, and generate a long-lived token. See how to get a permanent access token.
- Real number: add a number that isn't active on the WhatsApp or WhatsApp Business app, verify it by SMS or call, and register it with a six-digit two-step PIN. Store that PIN safely.
- Webhook: host an HTTPS endpoint, answer Meta's verification challenge, and subscribe to the messages field so incoming messages and delivery statuses reach your server.
- Payment method: add a card or other payment method for the WABA in WhatsApp Manager. Without it, paid template messages won't send.
- Templates: submit your first utility and marketing templates for approval through the API or WhatsApp Manager.
- Verification and display name: complete business verification and get your display name approved. Until then, sending limits stay low.
The full walkthrough, with screenshots, is in our step-by-step WhatsApp Cloud API setup guide.
What do you have to build yourself if you skip a provider?
At minimum: a webhook receiver, a sending service, secure token storage, template syncing and message status tracking. For a real team you also need an inbox where several people can reply, chat assignment, media handling, contact storage, opt-out handling, search and logs. The first part is days of work; the inbox is usually weeks, then ongoing maintenance.
| Component | Why you need it | Effort (our estimate) |
|---|---|---|
| Webhook receiver with signature check | Receives messages and delivery or read statuses | Small |
| Send API wrapper and retry queue | Sends text, media and templates; handles rate limits and failures | Small to medium |
| Token and secrets storage | Keeps the system user token out of source code | Small |
| Template sync and variables | Knows which templates are approved and fills variables correctly | Medium |
| Team inbox, assignment, notes | Lets several agents answer one number without clashing | Large |
| Contacts, tags, opt-in and opt-out | Sends promotions only to people who agreed | Medium |
| Campaign sending and reports | Bulk sends that respect messaging limits | Medium |
| Monitoring and uptime | Missed webhooks mean missed customer messages | Ongoing |
If WhatsApp only needs to send OTPs or order updates from your existing system, the small rows are all you need, and going direct is very reasonable. If a sales or support team will live in WhatsApp all day, the large rows are where the time goes. Our integration guide shows how the pieces connect.
How much does each path cost?
Meta's message fees are identical on every path. Going direct adds hosting and developer time; a Tech Provider adds a monthly software fee; a Solution Partner adds a platform fee and sometimes a percentage on top of Meta's rates. Which is cheapest depends on your volume and whether you already have developers with spare time.
Here's one example: a Pakistani business sending 5,000 utility and 1,000 marketing messages a month, at Meta's rates from 1 October 2026 ($0.0150 utility, $0.0473 marketing):
| Path | Meta fees | Extra charges | Monthly total |
|---|---|---|---|
| Direct | $75.00 + $47.30 = $122.30 | Server hosting plus developer time to build and maintain | $122.30 + your own costs |
| Tech Provider, no markup (example: On Cloud API Growth) | $122.30, paid to Meta directly | $19.99 plan | $142.29 |
| Provider with a 15% markup (hypothetical) | $122.30 + $18.35 markup = $140.65 | Plus that provider's plan | $140.65 + plan |
At this volume, going direct saves about $20 a month against a no-markup Tech Provider, which is less than a few hours of a developer's time. The maths changes at high volume: on 200,000 messages a month, a 15% markup becomes hundreds of dollars, and building your own sending layer can pay off. For current rates in every country, see our country-wise rate guide.
How does going direct compare with using a provider?
Direct gives you full control and no third party between you and Meta, at the price of building and running everything yourself. A provider gives you a ready inbox, templates, campaigns and support, and usually faster setup for non-technical teams. The messaging API, the rates and Meta's policies are the same either way.
| Factor | Direct (no provider) | Through a provider |
|---|---|---|
| Meta message fees | Meta's per-message rates | Same rates, plus plan, and a markup with some providers |
| Inbox and dashboard | You build it | Ready on day one |
| Business verification | You submit through Meta's standard process | Same Meta requirement; some Solution Partners can use a partner-led process that may be faster |
| Templates | API or WhatsApp Manager | Usually a guided editor |
| Hosting and uptime | Your server, your responsibility | The provider's |
| Integrations | Built by you | Some ready connectors; custom work still possible |
| Support when something breaks | Meta's developer docs and support channels | The provider's team |
| Lock-in | None | Low if the WABA is in your portfolio; higher if the provider owns it |
If you're also deciding between the Cloud API and older terms you may have seen, read WhatsApp Cloud API vs WhatsApp Business API.
Who should go direct, and who should use a provider?
Go direct if you have developers, a narrow use case such as OTPs or order alerts from your own system, and you're happy to own uptime. Use a provider if a team will answer customers all day, you need campaigns and bots quickly, or nobody in-house wants to maintain a messaging service at 2 a.m.
- You already run a backend and have a developer who can own the integration.
- WhatsApp is mainly automated messages from your system, not a team inbox.
- You send very high volume and want nothing added to Meta's rates.
- You need full control over where message data is stored.
- You have no developer, or your developers are busy with your core product.
- Sales or support agents need a shared inbox from the first week.
- You want campaigns, chatbots and contact segments without building them.
- You'd rather pay a fixed monthly fee than carry the maintenance risk.
What are the most common mistakes when going direct?
Most direct setups break on the same few things: using the temporary token in production, a webhook that never passed Meta's verification, a number still active on the WhatsApp app, a lost two-step PIN, no payment method on the WABA, and templates rejected for vague or promotional wording in a utility category.
- Temporary token in production: everything stops working the next day. Switch to a system user token. Read temporary vs permanent tokens.
- Webhook not verified or not subscribed: you can send but never receive replies or delivery statuses.
- Number still on the app: delete the WhatsApp account on the phone first, or onboard through Coexistence, which runs through a partner's Embedded Signup flow.
- Lost PIN: keep the two-step verification PIN somewhere safe; you need it to re-register or migrate the number.
- No payment method: template messages fail even though the API accepts the request.
- Wrong template category: a "utility" template with a discount line will be recategorised as marketing or rejected.
What changes by country when you go direct?
The direct path itself is the same everywhere. What changes is the cost per message, which makes markups matter more in some countries, plus local consent rules you must build into your own logic, and a few Meta restrictions, such as the pause on marketing templates to US numbers.
Pakistan
Utility messages to Pakistani numbers cost $0.0150, about eleven times India's $0.0014, and marketing costs $0.0473. Because the base rate is high, any percentage markup costs Pakistani senders more in absolute terms, so high-volume senders have a real reason to compare direct, no-markup and markup options.
UAE
Meta's business verification for UAE companies is usually done with the trade licence, whichever path you take. Arabic and English templates are both common. Dubai real estate teams building their own lead flows still need to follow property-advertising and data-protection rules in their messages; our Dubai real estate playbook covers the workflow, and our UAE cost guide has the rates in AED.
India
India has a large developer community building directly on the Cloud API, helped by Meta retiring the old self-hosted On-Premises API in October 2025, which moved everyone onto the same Cloud API. Utility messages are very cheap, so for many Indian teams the deciding factor is engineering time, not message fees. Meta is also moving India billing to rupees; check the timing in Meta's billing documentation.
United Kingdom
Going direct means your own application must record consent and handle opt-outs in line with UK GDPR and PECR. A provider's tools can help, but the legal responsibility stays with your business either way.
USA
Meta paused delivery of marketing templates to US phone numbers from 1 April 2025, and provider reports in September 2026 said the pause was still in place. That makes US use cases mostly utility and authentication messages, which are simpler to build directly. Check Meta's documentation for the current status before planning US campaigns.
Bangladesh
The number you register must not be active on the WhatsApp or WhatsApp Business app at the time, unless you onboard it through Coexistence. It doesn't need to be a number that was never used on WhatsApp; deleting the app account first is enough. This is a Meta rule on every path.
Australia
Australia's Spam Act covers commercial electronic messages, so a direct build must collect consent, identify the sender and offer an easy unsubscribe for marketing messages. If no provider supplies that logic, it has to live in your own code.
This is general information, not legal advice.
Frequently asked questions
Can you get WhatsApp Business API without a BSP?
Yes. Any business can create a Meta developer app, add the WhatsApp product and use the Cloud API directly. Meta's own documentation points businesses building an app only for themselves to the Cloud API Get Started guide. No Business Solution Provider is required.
Is direct WhatsApp Cloud API access free?
There's no licence fee for the API itself, but Meta charges per delivered template message by country and category, the same as on any other path. You also pay for your own hosting and the developer time to build and maintain the integration.
What does a BSP provide that the direct API doesn't?
Software and support: a shared inbox, template editor, campaigns, chatbots, contact management, reports and help when something breaks. Some Solution Partners also offer credit lines and partner-led business verification. The underlying Cloud API is the same.
How is a Meta Tech Provider different from a Solution Partner or BSP?
Both can onboard businesses to the WhatsApp Cloud API and provide software. Solution Partners have credit lines and can bill clients for Meta usage. Tech Providers don't have credit lines, so clients add their own payment method and pay Meta directly, while the provider bills only for its software.
Do I still need Meta business verification if I skip a BSP?
Yes. Business verification is a Meta requirement on every path. Going direct means you submit your documents through Meta's standard process yourself. Until you're verified, your sending limits stay at the lowest level.
Can I use Meta's test number before my real number is ready?
Yes. When you add WhatsApp to a Meta app, Meta provides a test business number that can message a small number of verified recipient phones. It's useful for building and testing before you register your own number and go live.
Can I use my existing WhatsApp number when going direct?
Only if it isn't active on the WhatsApp or WhatsApp Business app when you register it, so you would delete the app account first. To keep using the app and the API on the same number, Coexistence onboarding runs through a partner's Embedded Signup flow.
Can I self-host the WhatsApp Business API on my own server?
Not the messaging layer. The Cloud API is hosted by Meta, and the older self-hosted On-Premises API was retired in October 2025. You host your own backend and webhook endpoint that sends requests to Meta and receives messages and statuses.
Who should go direct instead of using a provider?
Teams with developers who mainly need automated messages from their own system, such as OTPs or order alerts, and are happy to run the webhook and handle uptime. Very high-volume senders who want nothing added to Meta's rates also benefit.
Who should use a provider instead of going direct?
Businesses without spare developer time, or where sales and support agents need a shared inbox, campaigns and chatbots from the first week. A no-markup Tech Provider keeps Meta billing direct while removing the build and maintenance work.
Sources
- Meta: WhatsApp Cloud API, Get Started
- Meta: Solution Partners, Tech Providers and Tech Partners
- Meta: Pricing on the WhatsApp Business Platform
- Meta: Messaging limits
- WATI: WhatsApp marketing messages to US numbers, status (September 2026)
On Cloud API is a Meta Tech Provider on the same official Cloud API. Your WhatsApp account stays in your Meta portfolio, you pay Meta's rates to Meta, and we charge a monthly plan for the inbox, templates, campaigns and chatbots. If you decide later to go fully direct, nothing stops you. See plans or talk to us.
Published by On Cloud API. Meta's platform terms and pricing change; confirm current details in Meta's developer documentation before relying on them.
