We are rolling out a change where shared API access will be granted in the Embedded Signup flow upon token save. For unexpected issues or impact in the embedded signup flow, please reach out to support.
Embedded Signup is an authentication and authorization desktop- and mobile-compatible interface that makes it easy for your business customers to generate the assets you will need to successfully onboard them to the WhatsApp Business Platform.
The Embedded Signup flow gathers business-related information from your business customers, automatically generates all WhatsApp assets needed by the platform, and grants your app access to these assets, so you can quickly provide your business customers with WhatsApp messaging services.
Customers onboarded via Embedded Signup own all of their WhatsApp assets and can leverage these assets with other Meta solutions such as Ads that Click to WhatsApp.
Embedded Signup leverages the Facebook Login for Business product and our JavaScript SDK. Once configured, you can add a link or button to your website or portal that launches the flow.
Business customers who click the link or button will be presented with a new window where they can:
Upon successful completion, Embedded Signup returns the customer's WABA ID, business phone number ID, and an exchangeable token code, to the window that spawned the flow. You must send this data to your server and use it in a server-to-server call to:
When these steps are complete, if you are a Solution Partner or are partnered with one, the customer can begin using your or your partner's app for messaging immediately. If you are not a Solution Partner, or not partnered with one, the customer must first attach a payment method to their WABA before they can begin messaging.
By default, you can onboard up to 10 new business customers in a rolling 7-day window. Only newly onboarded customers count against this limit. You can see your current onboarded customer count in the WhatsApp Manager > Partner overview panel. You will be notified by email if you approach this limit.
If you complete Business Verification, App Review, and Access Verification, we will automatically increase your limit to 200 new business customers in a rolling 7-day window. If you need to onboard more than 200 customers per week, apply to become a Meta Business Partner.
Business customers onboarded via Embedded Signup start with standard messaging limits, which can be increased through API usage.
See Default Flow for descriptions of each screen that your business customers will be presented with as part of the default implementation of Embedded Signup.
Note that if you know information about your customer's business, you can inject this data, which can significantly reduce the number of screens that your customers have to interact with.
Embedded Signup generates business integration system user access tokens ("business tokens"). When a business customer completes the Embedded Signup flow, an exchangeable token code will be returned as a message event and captured by the JavaScript SDK. You must exchange this code for a business token using a server-to-server call.
If you are a Tech Provider, you will use business tokens exclusively.
If you are a Solution Partner, you will use your system user access token ("system token") to share your credit line with onboarded business customers, and business tokens for everything else. Note that the system user who the token represents must have granted your app the business_management permission, and must have been granted an Admin or Financial Editor role on your business portfolio, in order to be able to share your credit line.
Embedded Signup can be configured to request most permissions from your business customers, but you are likely only going to need:
You can specify which permissions your app needs during the implementation process.
Note that while your app is in development mode, these permissions will appear in Embedded Signup's authorization screen to anyone who has an admin, developer, or tester role on your app. However, once you switch your app to live mode, only permissions that have been approved for advanced access through the App Review process will appear in the flow.
If you are a Solution Partner, you must already have a line of credit and have accepted the Credit Allocation API terms in the Business Settings > Payments panel in the Meta Business Suite. In addition, you must share your line of credit with any customers as part of the onboarding process.
If you are a Tech Provider or Tech Partner, your onboarded business customers must add a payment method to their WhatsApp Business Account. They can do this by following the steps described in our Add a credit card to your WhatsApp Business Platform account Help Center article.
Sandbox accounts are being release gradually, so this feature may not be available to you yet.
You can test the Embedded Signup flow using your own Facebook account, but this can result in additional business portfolios, WABAs, and business phone numbers. If you don't want to clutter your account with test data, you can claim a sandbox test account instead, and use it to simulate a business customer completing the flow.
When you complete the flow using the sandbox test account, the sandbox test account's WABA ID, business phone number ID, and an exchangeable token code will be returned, just as if it were a real customer completing the flow.
To claim your sandbox test user, navigate to the App Dashboard > WhatsApp > Quickstart panel, locate the Testing Integrations section, then click the Claim sandbox account button.
Business customers with verified businesses or businesses that have had their Cloud API messaging limits increased are eligible for up to two 555 business phone numbers.
These numbers behave the same way as standard business phone numbers (display names must be reviewed and approved, subject to conversation-based pricing rules, impacted by quality ratings, etc.), with the following key differences:
If your business customers are eligible for 555 numbers and want to register one as an additional number, instruct them to go through your implementation of Embedded Signup again. When asked to select a business phone number, they will automatically be given the option to choose a 555 number:
Embedded Signup can be used to migrate onboarded business customer assets in several ways. See Migrating business customer assets.
You will not be able to onboard business customers until your app has been approved for advanced access for each of the permissions it requires.
See App Review to learn more about App Review and what you must provide in order to complete the process successfully.
The Embedded Signup Integration Helper is a setup and testing tool within the App Dashboard. The tool allows you to:
You can access the integration helper by navigating to App Dashboard > WhatsApp > ES Integration.
As part of the onboarding process, you must subscribe your app to webhooks on the WABA of each business customer who completes the Embedded Signup flow.
Webhooks will be triggered and sent to the callback URL configured on your app, according to the webhook fields you have subscribed to. This means that all webhooks for all of your onboarded business customers will be sent to your app's callback URL. However, you can override the callback URL on an individual WhatsApp Business Account or business phone number. See Webhook Overrides to learn how to do this.
The Embedded Signup flow is available in 30 languages. The localized flow is automatically triggered based on the language that the business customer uses Facebook in.
Arabic, Czech, Danish, Greek, English (UK), Spanish (Spain), Spanish, Finnish, French (France), Hebrew, Hindi, Hungarian, Indonesian, Italian, Japanese, Korean, Norwegian (bokmal), Dutch, Polish, Portuguese (Brazil), Portuguese (Portugal), Romanian, Russian, Swedish, Thai, Turkish, Vietnamese, Simplified Chinese (China), Traditional Chinese (Hong Kong), Traditional Chinese (Taiwan).
Learn how to implement Embedded Signup into your website or portal.