WhatsApp Embedded Signup for your customers: your own Tech Provider app or a hosted page
A SaaS can connect its customers' WhatsApp Business app numbers to the Cloud API through Meta's Embedded Signup in two ways. It can become a Meta Tech Provider itself, which takes business verification, App Review with two videos and its own Embedded Signup build, or send customers to a hosted Embedded Signup page run by a provider that already is one, and receive the finished connection.
easyCoexistence runs Meta's Embedded Signup with Coexistence on a hosted page that carries your name, so your customers connect their numbers without you becoming a Tech Provider.
New business customers a Tech Provider may onboard per rolling 7 days: 10 by default, 200 after verification and review.
Screen recordings App Review asks a Tech Provider for: a message sent and received, and a template being created.
Meta's stated average turnaround for the App Review of a WhatsApp app.
The oldest WhatsApp Business app version a customer can connect through Coexistence.
How long the code Embedded Signup returns stays valid for the server to exchange it for the customer's business token.
What are the two ways to onboard your customers' numbers?
Both use Meta's Embedded Signup with Coexistence and end in the same place: the customer's number on the Cloud API, still working in the WhatsApp Business app, and your backend holding the customer's own business token. What differs is who carries Meta's requirements and the code around the popup.
| Your own Tech Provider app | easyCoexistence's hosted page | |
|---|---|---|
| Before the first customer | Business verification, App Review and your own Embedded Signup build | An API key and a card on the account |
| Name in Meta's popup | Your app | easyCoexistence, with your name on the page around it |
| Code you maintain | The popup, the token exchange, webhook subscriptions and the history sync | A session request and a return page |
| The 14-day rule | A PARTNER_REMOVED webhook for your app to handle | connection.disconnected with PRIMARY_INACTIVITY |
| Meta's message charges | On the customer's WhatsApp Business Account | On the customer's WhatsApp Business Account |
What does Meta require to become a Tech Provider?
Meta lists the steps in its Become a Tech Provider guide, which the App Dashboard opens under the WhatsApp use case's Tech Provider onboarding:
- A Meta app with the WhatsApp use case, connected to your business portfolio.
- Business verification, which comes first: Meta starts App Review only for a verified business.
- App settings such as an icon, a privacy policy and a category.
- Advanced access to
whatsapp_business_messagingandwhatsapp_business_management, granted through App Review with a written explanation and a screen recording for each. - Two recordings in all: a message sent from your app and received in WhatsApp, and your app creating a message template.
What do you build once approved?
The onboarding itself, which Meta's Embedded Signup guides describe step by step:
- The flow on your site, through Facebook Login for Business and Meta's JavaScript SDK, on HTTPS domains you allow in the app.
- Coexistence enabled in the flow's configuration, with session logging, which Meta requires for it.
- A server call that trades the returned code for the customer's business token within 30 seconds.
- Webhooks: your app subscribed to each customer's account, with the
account_update, history,smb_app_state_syncandsmb_message_echoesfields. - The contacts and history sync within 24 hours of onboarding; after that, the customer has to offboard and run the flow again.
What does the hosted page take on?
The whole popup side. easyCoexistence runs Embedded Signup with Coexistence through its own Meta app as a Tech Provider, on a page at easycoexistence.com that shows your name. The token exchange, the webhook subscription and the history request happen there, and your backend receives a connection id. With a webhook_url on the session, Meta delivers the number's messages straight to your server, along with the one-time import of contacts and, when the customer shares it, up to 180 days of chats. Your code then calls Meta's Graph API directly with the customer's token, while easyCoexistence watches the number and posts signed events when it changes.
What does your customer see?
A page with your name and one Connect button. Before Meta's popup opens, a checklist asks the customer to confirm five things: an up-to-date WhatsApp Business app, a number in real use for at least 7 days, no other API provider or automation tool on it, no unofficial apps, and the phone at hand with a Facebook login. No account, email or card is asked of them.
What happens inside Meta's popup?
Meta's flow signs the customer in with Facebook, asks them to authorise the app and to enter the number, and shows the number's WhatsApp Business app profile for them to confirm. They pick or create a business portfolio, then scan a QR code from inside the WhatsApp Business app; Meta also sends the number a WhatsApp message with a link to the code. In the app they tap Connect and choose whether to share chat history. Last come the account name, a time zone and Meta's terms. The order can vary while Meta rolls out its phone-number-first flow.
Whose name does Meta's popup show?
The name of the app that asks for access. On the hosted page that is easyCoexistence, and it cannot be renamed, while the page around the popup shows your name from partner_name. A Tech Provider app of your own shows your app's name instead, at the price of the verification, review and build described above.
What is the 14-day rule?
Meta disconnects a Coexistence number once the phone holding the WhatsApp Business app has been inactive for about 14 days, and reports the reason as PRIMARY_INACTIVITY. The customer reconnects by running the flow again with the same number. Through the hosted page, easyCoexistence watches each number and sends your events URL connection.disconnected with that reason, so a new connect link for the customer can bring the number back.
Common mistakes
- Building on Embedded Signup v2 or v3. Meta deprecated both on October 15, 2026 and serves requests for them as v4.
- Requesting permissions the app does not use. Meta names unnecessary permissions as a common reason App Review rejects a submission.
- Recording one video for both permissions. Meta wants a separate screen recording and written explanation for each, and may reject a video that shows several.
- Asking customers to connect from the phone that holds the number. Meta's popup opens as a new tab there, and that same phone has to scan the QR code, so a computer is easier.
Your backend receives each customer's own token, Meta delivers messages straight to your webhook, and drops reach you as signed events. US$ 9 to US$ 0.75 per connection per month, falling as you add connections, with the first 3 days free.
easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.
Frequently asked questions
Do I need to be a Meta Tech Provider to onboard my customers' WhatsApp numbers?
Only to run Embedded Signup from your own Meta app. Sending customers to a hosted page run by a Tech Provider connects their numbers without your own business verification or App Review.
How long does Meta's App Review take for a WhatsApp app?
Meta puts the average at about 24 hours. Business verification has to be complete before review can start, and each rejected submission adds another round.
Does my customer keep using the WhatsApp Business app?
Yes. The app keeps working on their phone beside the API, and messages are mirrored between the two. Some app features change: broadcast lists become read-only, and disappearing and view-once messages are turned off.
Who pays Meta for the messages?
The customer. Meta bills messages sent through the API to the customer's own WhatsApp Business Account, on a payment method they add there, while messages sent from the WhatsApp Business app stay free.
Keep reading
Connect your first channel in two minutes.
No platform reviews to wait for. Connect WhatsApp, Instagram, TikTok or another channel, then ask your AI to post, reply or report, and watch it work.
- 3 days free
- Cancel any time
- Official APIs only
- Monitored 24/7
Verified on