← Back to Blog
product-update byon embedded-signup whatsapp-cloud-api onboarding

Cloud API Numbers Now Register Themselves After Embedded Signup

Ler em português →

Short version: when you connect a number through Embedded Signup, PipesBot now finishes the job. If the number is new to the Cloud API, we register it with Meta for you, deal with the two-step verification PIN, and only mark the number as active once it is registered or connected with Coexistence. Your customers can complete all of it on the public onboarding link, without a PipesBot account.

The problem we fixed

Most numbers connected to PipesBot use Coexistence: the number stays on the WhatsApp Business app on the phone and also works through the API. Meta says those numbers must not be registered again, so our signup flow never called Meta’s register endpoint.

The same Meta dialog also lets someone connect a plain Cloud API number, one that isn’t on the WhatsApp Business app. Those numbers need one extra call, POST /{phone-number-id}/register, before WhatsApp routes anything to them. We skipped it. The number showed up as Active in the dashboard, the WABA was subscribed to webhooks, and nothing worked: no inbound messages, and sends failed with Meta error 133010 (account not registered).

That’s the kind of failure that costs a support ticket and an afternoon, so we closed it.

What happens now

When Embedded Signup completes, PipesBot checks the number with Meta before calling it ready:

What Meta reportsWhat PipesBot doesNumber status
The number is on the WhatsApp Business app (Coexistence)Nothing. Registering would be wrongActive
The number is already registered on the Cloud APINothingActive
The number is not registeredCalls register with a generated 6-digit PINActive once Meta accepts

The generated PIN becomes the number’s two-step verification PIN. You, the App owner, can reveal it in the dashboard (Numbers → Reveal PIN). The person who completed signup never sees it.

When the number already has a PIN

If two-step verification is already on, Meta rejects our generated PIN with error 133005. Instead of failing, the flow asks for the existing PIN:

  • Enter the 6-digit PIN and click Finish.
  • Don’t know it? Open “I don’t know the PIN” for the steps to turn off two-step verification in WhatsApp Manager, then click “I turned it off, try again”. PipesBot registers the number with a new PIN.

Meta allows 10 register attempts per number in a 72-hour window. Going over blocks registration for 72 hours (133016). PipesBot counts attempts on its side, shows how many are left, and stops calling Meta before you burn the budget. Too many wrong PINs in a row (133008, 133009) pause retries for an hour, and a number that was just deleted (133015) gets a “try again in 5 minutes” instead of an error.

A lot of you don’t connect numbers yourselves. You send your customer a signup link, and they go through Meta’s flow on their own. That person has no PipesBot login, so a “finish this in the dashboard” step would have been a dead end.

The public onboarding page now handles registration end to end:

  • If a PIN is needed, the page asks for it right there.
  • Progress is kept in a signed ticket on the URL, valid for 7 days. Your customer can reload the page or come back tomorrow without redoing Embedded Signup.
  • If something fails, the error screen retries from where it stopped instead of restarting the whole signup.

Fewer confusing states for your code

Two smaller changes follow from this:

  • A number that isn’t registered yet stays inactive. Sending from it returns 409 Number registration pending from PipesBot instead of a cryptic Meta error.
  • Billing and the number.onboarded webhook wait for a usable number. You aren’t charged the BYON add-on, and your system isn’t told a number is ready, until it is registered or connected with Coexistence.

Also in this round: Embedded Signup v4

In September we moved the dashboard, the onboarding link and admin flows to Meta’s Embedded Signup v4. Along the way we made sure every flow keeps the Coexistence option on, so a number already on the WhatsApp Business app is offered “connect your existing app” instead of getting rejected. As of October 3 the v4 flow is the only one, with no per-App rollout flag left.

Try it

Connect a number from your PipesBot dashboard or generate a signup link through the API. The Embedded Signup docs cover both paths. If you’re choosing between keeping the WhatsApp Business app and a full migration, read the Coexistence guide first.