Embedded signup is Meta's in-browser flow that creates or connects your WhatsApp Business Account (WABA), registers your phone number to the API, and links it to the platform you are using — in one popup, in about five minutes. You need a Meta Business account, a phone number that can receive an OTP and is not active on personal WhatsApp, and your business details. No paperwork, no BSP application queue: that world ended when the Cloud API opened.
Half the articles about 'getting WhatsApp API access' still describe a weeks-long application process. That is history. Here is exactly what happens in an embedded signup flow, what to prepare so it takes five minutes instead of fifty, and how to fix the errors that actually stall people.
What is embedded signup, exactly?
A Meta-hosted OAuth-style popup that platforms integrate. When you click 'Connect WhatsApp number' on a platform like Waaru, the popup walks you through: logging into Meta, choosing or creating a Business portfolio, choosing or creating a WABA, adding and verifying your phone number via OTP, and granting the platform permission to operate the number.
At the end, the platform holds tokens to send and receive messages on the number's behalf — and you hold ownership of everything: the Business Manager, the WABA, and the number stay yours, which is what makes switching platforms later a five-minute affair rather than a hostage negotiation.
What do you need before you start?
A Meta (Facebook) account with admin access to — or the ability to create — a Meta Business portfolio.
A phone number that can receive an SMS or voice OTP right now. Landlines work via the voice option.
The number must not be registered on personal WhatsApp or the WhatsApp Business app — delete the account in-app first (Settings → Account → Delete), or use a fresh number.
Your legal business name and website/address as you want them on record.
Ten uninterrupted minutes — the OTP step has a timer, and abandoning mid-flow is the most common source of weird states.
The flow, step by step.
1. Start from the platform, not from Meta. The platform's 'Connect number' button launches the popup with the right permissions pre-configured.
2. Log into Meta and pick your Business portfolio (or create one inline — takes a minute).
3. Create or select the WABA. First-timers: create new. Migrating: select the existing WABA that owns your number.
4. Set the display name. This is customer-visible and reviewed against Meta's naming policy — use your real brand name, no keyword stuffing, no ALL CAPS.
5. Enter the phone number and verify via OTP (SMS or voice call).
6. Grant permissions and finish. The platform confirms the connection; you can usually send a test message within a minute.
What goes wrong, and how to fix it?
'Number already in use' — the number is registered on personal WhatsApp or another WABA. Delete the WhatsApp account from the app (not just uninstall), wait a few minutes, retry. If it is stuck on an old WABA you control, remove it there first.
OTP never arrives — use the voice-call option; DND-listed Indian numbers often block the SMS route.
Display name rejected — align it with your legal or clearly established brand name; Meta's review compares against your public presence.
'Business not eligible' — your Business portfolio is brand new with no history. Complete business details, add a website, and if prompted, run business verification in Business Manager.
Popup blocked or closes silently — allow popups for the platform domain; corporate browsers with strict tracking protection are frequent culprits.
What happens after signup?
Three things matter after signup. Messaging access and limits depend on the account and sender state. Business verification and display-name review are separate processes. Templates, webhook delivery, inbound replies, quality state, opt-out handling, and the first workflow should all be tested before production traffic. Waaru onboarding connects flows, inbox, integrations, and any approved AI or MCP access; launch timing still depends on Meta and provider state.
FAQ
Questions worth answering.
About five minutes if your number is OTP-ready and not registered on personal WhatsApp. The weeks-long version of 'getting API access' you may have read about — BSP applications, manual review queues — predates the open Cloud API era.
Research notes
Evidence checked for this article.
Embedded signup creates/connects a WABA, registers the number via OTP, and grants the platform messaging permissions; WABA ownership remains with the business's Meta portfolio.
Meta — WhatsApp embedded signup documentation · Accessed 4 July 2026
