How to Get the WhatsApp Business API (Step by Step)

A founder emails their provider asking to turn on the API, expecting a single switch. What comes back is a checklist: a verified Meta business, a dedicated number, an approved display name, and templates Meta still has to sign off on. Getting the WhatsApp Business API isn't one form, it's a short sequence of approvals, and knowing the order saves you a week of back-and-forth.

None of the steps are hard on their own. They just have to happen in the right sequence, and a few of them wait on Meta's review clock. This walkthrough covers both ways in, what you need before you start, and where setups usually stall.

Two ways to get access

There are two routes to the API, and the right one depends on whether you have engineering time to spare.

The first is going direct on Meta's Cloud API. You create a Meta developer app, add the WhatsApp product, register your number, generate access tokens, wire up webhooks, and submit templates yourself. Meta hosts the infrastructure for free, so you only pay for messaging. It's the cheapest path on paper and the most work in practice.

The second is going through a partner platform, often called a Business Solution Provider. They use Meta's streamlined onboarding to get you connected in minutes, then hand you a dashboard for templates, contacts, and automation. You pay a platform fee on top of Meta's messaging charges. For most teams, going direct just to save that fee is a false economy, because you end up rebuilding the dashboard the platform already gives you.

One note on infrastructure: Meta has retired the older self-hosted on-premise API, so the Cloud API is the only path for any new setup. If a guide mentions on-premise hosting, it's out of date.

What you need before you start

Gather these first. Missing one is the most common reason a setup stalls on day one:

• A Meta Business Account: also called Business Manager, set up at business.facebook.com. This is the container everything else lives in.
• A dedicated phone number: one you own that is not currently active on the regular WhatsApp or Business App. It can send and receive an OTP during setup.
• Business documents: a legal business name, address, and ideally a website and an email on your own domain. Meta uses these for verification.
• A display name in mind: the name customers will see, which has to follow Meta's naming rules and clear a review.

If you're still deciding whether the API is even the right move, our breakdown of the WhatsApp Business App and the API covers who each one is for. Assuming you've settled on the API, here's the sequence.

Step 1: Set up your Meta Business Manager

Go to business.facebook.com and create a Business Manager account if you don't already have one. Add your business name, your details, and confirm your email. This account is the root of your WhatsApp setup, so use a company account rather than a personal profile you might lose access to.

Step 2: Create your WhatsApp Business Account

Inside Business Manager you'll create a WhatsApp Business Account, usually shortened to WABA. This is the object that holds your phone numbers, templates, and messaging limits.

On the direct path, you create the WABA through your Meta developer app by adding WhatsApp as a product. On the partner path, the platform's onboarding flow creates it for you and links it to your Business Manager automatically. Either way, one WABA can hold multiple numbers later if you grow.

Step 3: Add and verify your phone number

Add the number you set aside earlier and verify it with the code Meta sends by SMS or call. The number has to be clean, meaning it isn't already registered on the consumer WhatsApp or the Business App. If it is, you'll have to delete it from that app first and migrate it, which wipes that number's old chat history.

This is why many teams start the API on a brand-new number instead of migrating the one their customers already know. It avoids the disruption and lets you run both in parallel during a pilot.

Step 4: Complete Meta business verification

Think of Meta's business verification as a passport check. Nothing else moves until it clears. You'll submit your business documents, and Meta confirms your business is real and that you're authorized to represent it.

Verification can take anywhere from a few minutes to several days depending on how clean your documents are. Give it the time it needs, because your messaging limits and your ability to get a verified badge both depend on passing it. A business address that matches your documents and a website on your own domain speed this up more than anything else.

Step 5: Set your display name and get it approved

Honestly, the step that stalls people isn't technical. It's the display-name review, which Meta rejects for reasons it doesn't always explain.

Your display name is what customers see at the top of the chat. Meta reviews it against a naming policy: it generally has to match your actual business name and can't be a generic term or misleading. If it gets rejected, you'll usually need to bring it closer to your registered brand name and resubmit. Get this right early, because a pending name can block you from sending certain message types.

Step 6: Create and submit message templates

Outside of a live 24-hour conversation window, you can't message a customer with free text. You send a template message, and every template has to be approved by Meta before you can use it.

Templates fall into categories that affect both approval and cost:

• Utility: transactional messages tied to an action, like an order confirmation or a shipping update.
• Marketing: promotions, offers, and re-engagement, which face the strictest review and the highest per-message cost.
• Authentication: one-time passcodes and login verification.

Write templates that are specific and genuinely useful, avoid anything that reads as spam, and submit a few core ones during setup so you're not waiting on approvals the day you launch.

Step 7: Connect the API to a platform and add automation

At this point you have API access, but access alone doesn't answer a single customer message. What you connect next decides what the channel can actually do.

On the direct path, this is where your engineers build against the Cloud API, handle incoming messages through webhooks, and maintain the logic themselves. On the partner path, you're already in a dashboard, and you connect your knowledge base, your order system, and optionally a WhatsApp AI agent to handle conversations automatically. This is the layer that turns a messaging pipe into something that can actually run customer service on WhatsApp.

The Embedded Signup shortcut

The reason partner onboarding is measured in minutes now is a Meta feature called Embedded Signup. It's a hosted flow, similar to a login-with-Google popup, that walks you through creating the WABA, connecting your Business Manager, and registering your number in one guided sequence.

Instead of clicking through half a dozen Meta screens and copying IDs between tabs, you approve a few permissions and land connected. Most modern platforms use it, and it's the single biggest reason getting on the API stopped being a developer-only job.

Common reasons access gets delayed or rejected

If your setup stalls, it's almost always one of these:

• The number was already on WhatsApp: you can't register a number that's active in the consumer or Business App without migrating it first.
• Business verification incomplete: mismatched documents or a missing website slow the review or fail it.
• Display name rejected: a generic or off-brand name gets bounced and has to be resubmitted closer to your legal name.
• Templates written like ads: vague or promotional-sounding utility templates get rejected on category grounds.

Clear all four before you promise anyone a launch date, and the timeline usually compresses to days rather than weeks.

What to do once you're live

Getting access is the setup. Getting value is what happens after. Once your number is verified and your templates are approved, the question becomes how much of the incoming volume a human still has to touch.

Robylon's WhatsApp agent connects on top of your API and resolves 60 to 80 percent of routine conversations on its own, across 40-plus languages, escalating to a human the moment a chat needs judgment. With 60-plus write-access integrations, it can pull an order status, process a return, or update a record inside the chat rather than just replying with text. Deployment runs in the 3 to 7 day range on usage-based credits pricing. The API gets you the channel. What you run on it is what customers actually feel.

Ready to put the API to work once it's live? Robylon AI resolves 60 to 80 percent of customer conversations autonomously with AI agents that take action across your order system, CRM, and 60+ other integrations. Start free at robylon.ai