ApivomApivom
Get Demo

WhatsApp Embedded Signup API Connector

Meta's Embedded Signup API for WhatsApp Business — the Tech Provider flow that onboards a customer's WhatsApp number: exchange the signup code for a business token, subscribe the app to the WhatsApp Business Account, add system users and share a credit line — the same flow Apivom's onboarding team runs with you to connect your number, without you touching Meta's developer console.

What you can do

  • Code exchange: turn the token returned by Meta's signup dialog into a long-lived business access token
  • Subscribe the Tech Provider app to the customer's WhatsApp Business Account so webhooks start flowing
  • System-user and WABA routes: assigned users, add system user, shared and owned WABAs, debug token
  • Credit-line sharing routes for partners who bill conversations on the customer's behalf
  • Coexistence or classic: a number already used in the WhatsApp Business app can be onboarded without losing it, or a plain Cloud API number connected the classic way

Use cases

  • Connect your WhatsApp number in minutes — Complete Meta's dialog with Apivom's onboarding team; the code exchange, app subscription and number check happen automatically, and the assistant can start on your number.
  • Keep the WhatsApp Business app — Onboard a number that your team already uses in the WhatsApp Business app; coexistence lets both the app and the platform work on it.
  • Run your own partner onboarding — Tech Providers with their own Meta app can use the catalogued routes — code exchange, subscribe, system users, credit lines — through Atlas with per-tenant logging.

Embedded Signup is Meta's guided dialog for bringing a business onto the WhatsApp Business Platform through a partner — a Tech Provider or Solution Provider — instead of Meta's developer console. The customer completes the dialog in the partner's product; the partner then exchanges the returned code for a business access token, subscribes its app to the selected WhatsApp Business Account, optionally adds a system user and, if it pays for messaging, attaches a credit line. Apivom Atlas catalogues 22 of these routes. Apivom's own WhatsApp onboarding follows this sequence: Meta's dialog runs in Apivom's platform console while you sign in to your Meta business, the 30-second code is exchanged once to prove the signup completed (the token is not kept — Apivom's system-user token covers every account shared with it), Apivom's app is subscribed to your WhatsApp Business Account through Apivom Atlas, and the number's state is read back. No phone registration call is made, so the WhatsApp Business app keeps working on the same number (coexistence); a classic Cloud API number connects the same way. The WhatsApp Cloud API connector then carries the messaging.

Authentication

Tech Provider app credentials (app id + secret) for the code exchange, then the business access token as Bearer for WABA operations. In Apivom's onboarding these are Apivom's own Meta app credentials; the exchanged token only confirms the signup and is not stored. Atlas stores nothing.

Frequently asked questions

Do I need a Meta developer account to connect WhatsApp to Apivom?

No. Embedded Signup runs with Apivom's Tech Provider app; you need a Meta Business portfolio and the phone number. Meta's dialog asks you to sign in and confirm the business and the number, and Apivom handles the code exchange and the app subscription.

What exactly does Apivom get access to?

Your WhatsApp Business Account is shared with Apivom's Meta business and Apivom's app is subscribed to it — enough to send and receive messages on the number and read its templates and status. Nothing from the signup itself is stored; removing Apivom as a partner in your Meta Business settings ends the access at any time.

Does Apivom charge per API call for this connector?

No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.

Where are my credentials stored and who can see the traffic?

Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.

More Atlas integrations

AI integration guide (llms.txt)

Machine-readable markdown — feed it to your AI assistant as integration instructions.