Onboarding business customers as a Solution Partner | Developer Documentation
Onboarding business customers as a Solution Partner
Updated: Nov 14, 2025
This document describes the steps Solution Partners must perform to onboard new business customers who have completed the Embedded Signup flow.
If you are a Solution Partner, any business customer who completes your implementation of the Embedded Signup flow will not be able to use your app to access their WhatsApp assets or send and receive messages until you complete these steps.
What you will need
Also, if you wish to test messaging capabilities using the customer’s business phone number, you will need a WhatsApp phone number that can already send and receive messages from other WhatsApp numbers.
Perform all of the requests described below using server-to-server requests. Do not use client-side requests.
Step 1: Exchange the token code for a business token
Use the GET /oauth/access_token endpoint to exchange the token code returned by Embedded Signup for a business integration system user access token (“business token”).
Request
curl --get 'https://graph.facebook.com/v21.0/oauth/access_token' \
-d 'client_id=<APP_ID>' \
-d 'client_secret=<APP_SECRET>' \
-d 'code=<CODE>'
Request parameters
| Placeholder | Description | Example value |
|---|---|---|
<APP_ID> | Required. Your app ID. This is displayed at the top of the App Dashboard. | 236484624622562 |
<APP_SECRET> | Required. Your app secret. You can get this from the App Dashboard > App Secret > Basic panel. | 614fc2afde15eee07a26b2fe3eaee9b9 |
<CODE> | Required. The code returned by Embedded Signup when the customer successfully completed the flow. | |
Response
Upon success:
<BUSINESS_TOKEN>
Response parameters
| Placeholder | Description | Example value |
|---|---|---|
<BUSINESS_TOKEN> | The customer’s business token. | |
Step 2: Subscribe to webhooks on the customer’s WABA
Use the POST /<WABA_ID>/subscribed_apps endpoint to subscribe your app to webhooks on the business customer’s WABA. If you want the customer’s webhooks to be sent to a different callback URL than the one set on your app, you have multiple webhook override options.
Request
curl -X POST 'https://graph.facebook.com/<API_VERSION>/<WABA_ID>/subscribed_apps' \
-H 'Authorization: Bearer <ACCESS_TOKEN>'
Request parameters
| Placeholder | Description | Example value |
|---|---|---|
<BUSINESS_TOKEN> | Required. The customer’s business token. | |
<WABA_ID> | Required. The customer’s WABA ID. | 102290129340398 |
Response
Upon success:
{
"success": true
}
We are currently testing new steps for sharing your credit line with onboarded business customers. These steps will eventually replace this step, so if you wish to implement these steps now, see Alternate method for sharing your credit line.
Note: If you are using the below API i.e.
whatsapp_credit_sharing_and_attach, you would need to add your System User to the shared WhatsApp Business Accounts as a pre-requisite. Please refer to this doc for steps.Once you have added the System user to the WhatsApp Business Account, use the POST /<EXTENDED_CREDIT_LINE_ID>/whatsapp_credit_sharing_and_attach endpoint to share your credit line with an onboarded business customer.
Request
curl -X POST 'https://graph.facebook.com/<API_VERSION>/<EXTENDED_CREDIT_LINE_ID>/whatsapp_credit_sharing_and_attach?waba_currency=<CUSTOMER_BUSINESS_CURRENCY>&waba_id=<CUSTOMER_WABA_ID>' \
-H 'Authorization: Bearer <SYSTEM_TOKEN>'
Request parameters
| Placeholder | Description | Example value |
|---|---|---|
<CUSTOMER_BUSINESS_CURRENCY> | Required. The business’s currency, as a three-letter currency code. Support values are: AUDEURGBPIDRINRUSDThis currency is used for invoicing and corresponds to pricing rates. | USD |
<CUSTOMER_WABA_ID> | Required. The customer’s WABA ID. | 102290129340398 |
<EXTENDED_CREDIT_LINE_ID> | Required. Your extended credit line ID. | 1972385232742146 |
<SYSTEM_TOKEN> | Required. Your system token. | |
Response
Upon success:
{
"allocation_config_id": "<ALLOCATION_CONFIGURATION_ID>",
"waba_id": "<CUSTOMER_WABA_ID>"
}
Response parameters
| Placeholder | Description | Example value |
|---|---|---|
<ALLOCATION_CONFIGURATION_ID> | The extended credit line’s allocation configuration ID. Save this ID if you want to verify that your credit line has been shared with the customer. | 58501441721238 |
<CUSTOMER_WABA_ID> | The customer’s WABA ID. | 102290129340398 |
Step 4: Register the customer’s phone number
Use the POST /<BUSINESS_PHONE_NUMBER_ID>/register endpoint to register the customer’s business phone number for use with Cloud API.
Request
curl 'https://graph.facebook.com/v21.0/<BUSINESS_PHONE_NUMBER_ID>/register' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer <BUSINESS_TOKEN>' \
-d '
{
"messaging_product": "whatsapp",
"pin": "<DESIRED_PIN>"
}'
Request parameters
| Placeholder | Description | Example value |
|---|---|---|
<BUSINESS_PHONE_NUMBER_ID> | Required. The customer’s business phone number ID returned. | 106540352242922 |
<BUSINESS_TOKEN> | Required. The customer’s business token. | |
<DESIRED_PIN> | Required. Set this value to a 6-digit number. This will be the business phone number’s two-step verification PIN. | 581063 |
Response
Upon success:
{
"success": true
}
Step 5: Send a test message
This step is optional.
If you wish to test the messaging capabilities of your business customer’s business phone number, send a message to the customer’s number from your own WhatsApp number (this will open a customer service window, allowing you to respond with any type of message).
Next, use the POST /<BUSINESS_PHONE_NUMBER_ID>/messages endpoint to send a text message in response.
Request
curl 'https://graph.facebook.com/v21.0/<BUSINESS_PHONE_NUMBER_ID>/messages' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer <BUSINESS_TOKEN>' \
-d '
{
"messaging_product": "whatsapp",
"recipient_type": "individual",
"to": "<WHATSAPP_USER_NUMBER>",
"type": "text",
"text": {
"body": "<BODY_TEXT>"
}
}'
Request parameters
| Placeholder | Description | Example value |
|---|---|---|
<BODY_TEXT> | Required. Message body text. Supports URLs. Maximum 4096 characters. | Message received, loud and clear! |
<BUSINESS_PHONE_NUMBER_ID> | Required. The customer’s business phone number ID. | 106540352242922 |
<BUSINESS_TOKEN> | Required. The customer’s business token. | |
<WHATSAPP_USER_NUMBER> | Required. Your WhatsApp phone number that can send and receive messages from other WhatsApp numbers. Note that this cannot be a business phone number already registered for use with Cloud API. | +16505551234 |
Response
Upon success:
{
"messaging_product": "whatsapp",
"contacts": [
{
"input": "<WHATSAPP_USER_NUMBER>",
"wa_id": "<WHATSAPP_USER_ID>"
}
],
"messages": [
{
"id": "<WHATSAPP_MESSAGE_ID>"
}
]
}
Response parameters
| Placeholder | Description | Example value |
|---|---|---|
<WHATSAPP_MESSAGE_ID> | WhatsApp message ID. | wamid.HBgLMTY0NjcwNDM1OTUVAgARGBI1RjQyNUE3NEYxMzAzMzQ5MkEA |
<WHATSAPP_USER_ID> | Your WhatsApp user ID. | 16505551234 |
<WHATSAPP_USER_NUMBER> | Your WhatsApp phone number that the message was sent to. | +16505551234 |
If you were able to successfully send and receive messages using the customer’s business phone number, and if messages webhooks were triggered describing the initial message that you sent, as well as the delivery statuses of the message you sent in response, the customer’s business phone number is working properly.
No comments to display
No comments to display