How to Get WhatsApp API Access: 3 Paths Compared
You have decided WhatsApp needs to be wired into your product or support flow, and every search result is a vendor page promising to be "the way in". Some say you need them, some say it takes five minutes, some quote a setup fee. None explain the actual routes.
Here is the plain version of how to get WhatsApp API access. There are three ways into Meta's official WhatsApp Business Platform, and they all end at the same Cloud API. What differs is who bills you, who supports you, how much you build yourself and who owns the account. There is also a fourth route that goes around Meta entirely, which is the right answer for some teams and the wrong one for others.
Key takeaways
- All official paths lead to Meta's Cloud API. Meta hosts it; you never install a server.
- Going direct is cheapest but you build everything. A BSP or a SaaS tool trades fees for a finished product and support.
- You can send a test message the same day. Production depends on your number, display name, payment method and, to scale, business verification.
- Since September 2026 the old "WABA" is split into a WhatsApp account (number and profile) and a Messaging account (templates, billing, webhooks). Older guides use the old name for the same step.
What every path needs before you start
Whichever route you pick, Meta asks for the same building blocks. Getting these ready first saves most of the back and forth.
| You need | Why | Watch out for |
|---|---|---|
| A Facebook account or managed Meta account | To sign in to Meta's tools | Use an account tied to the company, not one person's throwaway |
| A Meta business portfolio | Holds your WhatsApp assets and your verification | Note who is admin; only admins can verify or delete numbers |
| A phone number | The identity customers see | It must take an SMS or voice call, have a country and area code, and not be active on WhatsApp |
| A display name | Shown on your WhatsApp profile | It has to match your real brand or it gets rejected |
| A payment method or partner credit line | Paid messages need billing on the Messaging account | Since October 1, 2026, without one, service messages stop once the 1,000 free per month are used |
| Business verification (optional at first) | Raises your limits and number cap | Not needed for a first test, needed to grow past 250 business-initiated recipients a day |
The number is where most projects stall: one already running WhatsApp or the WhatsApp Business app can't be registered until that account is deleted, unless you onboard through a partner that supports coexistence. Our guide to WhatsApp API phone number requirements covers landlines, toll-free lines and IVR systems in detail.
Path 1: Go direct through Meta for Developers
You build against the Cloud API yourself and pay Meta's per-message rates with nothing on top.
- Register as a developer at developers.facebook.com and create an app with the Connect with customers through WhatsApp use case.
- Pick or create a business portfolio. Meta creates a test WhatsApp account, Messaging account and test phone number for you.
- In API Setup, generate a temporary token and send yourself a test message.
- Add your real number, verify it with an SMS or voice code, then register it with a call to the
registerendpoint. - Create a system user and a long-lived token, add a payment method, and point webhooks at your server.
The whole sequence, with working curl commands, is in our WhatsApp Cloud API setup walkthrough.
Who it suits: teams with a developer to own the integration who want full control. The catch: Meta gives you an API, not a product. Shared inbox, template management screens, assignment, reporting and opt-out handling are yours to build.
Path 2: Sign up through a Business Solution Provider
A Business Solution Provider (BSP, which Meta now calls a Solution Partner) gives you a hosted platform on top of the Cloud API. You usually click a signup link the provider sends, log in with Facebook, choose your business portfolio, verify your number and accept Meta's terms. The provider handles the rest.
Solution Partners have a credit line with Meta, so they can skip the payment-method step and invoice you directly for messages plus their own fees. In return you get an inbox, template tools, chatbots and a support team that knows the platform.
Before you sign, check two things. First, the fee structure: subscription, per-message markup, setup and number fees vary widely, and our breakdown of WhatsApp BSP fees lists the questions to ask. Second, ownership. Meta's documentation says businesses onboarded through Embedded Signup own their WhatsApp assets and keep full access to WhatsApp Manager. If a provider sets your account up some other way, confirm in writing that the account sits in your business portfolio.
Path 3: Connect inside a SaaS tool you already use
Many CRMs, helpdesks and ecommerce tools are Meta Tech Providers. They show a "Connect WhatsApp" button that opens Meta's Embedded Signup popup. You go through the same screens as Path 2, and the tool gets permission to send and receive on your behalf.
The difference is billing. Tech Providers have no credit line, so you add your own card to the Messaging account and Meta bills you directly for messages, while the tool charges its subscription. It suits teams whose customer data already lives in that tool. If you are the one building such a tool, our WhatsApp Embedded Signup guide covers the partner side.
The three official paths side by side
| Direct (Meta) | BSP / Solution Partner | SaaS tool / Tech Provider | |
|---|---|---|---|
| Who bills Meta's message fees | Meta bills you | The BSP, inside its invoice | Meta bills you |
| Extra fees | None | Subscription and often a markup | The tool's subscription |
| Build effort | High: you build the app | Low | Low |
| Support | Meta developer support | The BSP's team | The tool's team plus Meta |
| Account ownership | You | You, if onboarded via Embedded Signup | You |
| Best for | Developer-led teams, custom flows | Teams who want a ready platform | Teams living in one CRM or helpdesk |
How long it takes, and what slows it down
A test message from Meta's test number can go out within minutes of creating the app. A production number can go live the same day when nothing blocks it. These are the usual blockers:
- The number is still on WhatsApp. Delete the app account first (back up chats), or choose a coexistence onboarding.
- The verification code never arrives. Toll-free and IVR lines need the registration call routed to a person.
- Too many registration attempts. Meta allows 10 register calls per number in a moving 72 hours, then blocks it for 72 hours (error
133016). - New portfolio caps. A new business portfolio can register two numbers and message 250 unique users a day outside the customer service window. Verification lifts the number cap to 20 and opens the path to 2,000 a day. See Meta business verification for the WhatsApp API.
- Display name rejection. Names that include a person's name or don't match your branding get declined.
The route around Meta: linked-number APIs
Some teams search for "WhatsApp API" when what they want is narrower: reply as a team from one place, keep the number customers know, and work the groups the business lives in. The official platform makes that hard. It can't touch groups your number is already in, it requires templates outside the 24-hour window, and moving your number on means giving up the app.
Linked-number tools connect to your existing WhatsApp account the way WhatsApp Web does, as a linked device. There's no Meta onboarding, no templates and no per-message fees. They are not Meta's platform, they are not built for OTPs or high volume, and WhatsApp can still ban a number that spams. For a fuller comparison, start with the complete guide to the WhatsApp API.
The step that trips up most first applications is the name customers see, so read our guide to the WhatsApp API display name before you submit one.
Where Tenashi fits
If the reason you went looking for API access is "our team needs to answer customers on our WhatsApp number without passing one phone around", Tenashi is a shorter route. You link your existing WhatsApp or WhatsApp Business number with a QR scan, and the team works one shared inbox with DMs and groups, a CRM under every chat, notes, assignments and follow-ups. Every paid plan includes a developer API, so your systems can send a message to a phone number or into an existing group and get webhooks for replies. Plans start from $18/mo, with no per-message fees and no template approval.
The honest limit: Tenashi runs on your own number, not Meta's official platform. It has no green tick, no interactive buttons or templates, and sends are deliberately paced, so it is the wrong tool for OTPs or thousands of alerts a minute. For that, take one of the three paths above.
Read the API docs · Get started
FAQ
Is WhatsApp API access free to get?
Access itself costs nothing from Meta: creating the app, the test number and the Cloud API are free. Messages are charged per delivered message by category and recipient country. Messages customers send you are free, and from October 1, 2026 each business number gets 1,000 free service replies a month. BSPs and tools add their own fees.
Do I need business verification to get the WhatsApp API?
Not to start. You can create an app, use the test number and register a real number without it. Verification matters when you grow: it is one of the ways to lift the business-initiated limit from 250 to 2,000 unique users a day, it raises the registered number cap from two to 20, and it is required for the green tick.
Can I use the WhatsApp number I already have?
Yes, with conditions. A number on WhatsApp Messenger must have its account deleted before it can be registered. A WhatsApp Business app number can either be deleted and moved, or onboarded through a partner that supports coexistence, which keeps the app working alongside the API. Back up your chats before any of this.
Do I need a BSP to use the WhatsApp Business API?
No. Since the Cloud API launched, any business can go direct through Meta for Developers and pay only Meta's rates. A BSP is worth it if you want a ready-made inbox, template tools and hands-on support instead of building them. Many SaaS tools also connect directly as Tech Providers without a BSP in between.
How many phone numbers can I add to the API?
Two, to begin with. That cap rises to 20 on its own when your portfolio is verified or hits the 2,000 messaging limit. Keep in mind that every number in a portfolio draws on one shared messaging limit, so adding a second number does not double how many people you can reach outside the window.
Pick the path by who will run it: a developer who wants control, a provider who runs it for you, or the tool your team already uses. And if what you really need is a shared inbox on the number you have, see every Tenashi feature first.