Messenger Platform

Onboard Businesses with Marketing Message API for Messenger

Updated: Mar 31, 2026
The Marketing Message API for Messenger is available exclusively to tech providers with an existing app that has successfully completed Meta App Review for the following permissions:
  • ads_management
  • pages_messaging
  • paid_marketing_messages or marketing_messages_messenger

Currently, tech providers can only serve businesses located in the following regions:
  • Australia
  • Brazil
  • Chile
  • Colombia
  • Hong Kong
  • India
  • Indonesia
  • Israel
  • Malaysia
  • Mexico
  • New Zealand
  • Peru
  • Philippines
  • Saudi Arabia
  • Singapore
  • Taiwan
  • Thailand
  • United Arab Emirates
  • United States
  • Vietnam (VN)
In addition, messages can be sent to users/subscribers in all regions except:
  • European Union
  • Japan
  • South Korea
  • Australia
  • United Kingdom

The Marketing Message API for Messenger is only available for Web applications.
This document shows you how to configure Facebook Login for Business to onboard businesses to your Marketing Messages on Messenger app.
NOTE: In this guide, business refers to the business portfolios onboarding to your app (your app’s user).

Choose Your Onboarding Flow

We provide three onboarding flows for Marketing Messages on Messenger. Please decide which one works for your business needs before starting integration. You can also integrate with multiple onboarding flows to serve different use cases.
Feature Flow 1: Business Portfolio Flow (SUAT) Flow 2: Asset-Based Flow (UAT) Flow 3: Partner Billing Flow (SUAT)
Admin Permission Required
Business Portfolio permission
Full control permission for Pages and Ad Accounts
Business Portfolio permission
Asset Requirement
Ad Account and Page need to be owned by the same Business Portfolio
Ad Account and Page does not need to be owned by the same Business Portfolio
Page only — your client does not provide an ad account
Key Permission
paid_marketing_messages
marketing_messages_messenger
paid_marketing_messages
Access Token Type
System-business access token (non-expiring)
User access token (short-lived, ~1 hour)
System-business access token (non-expiring)
Billed Ad Account
Client’s ad account
Client’s ad account
Your (the partner’s) ad account
Additional Features
Enables subscriber automations
Enables subscriber automations
Enables subscriber automations
Best For
Businesses with Business Manager access
Admins managing Pages and Ad Accounts without Business Manager access
Partners who want to bill marketing message deliveries to their own ad account instead of the client’s
Recommendation: Use Flow 1 (Business Portfolio Flow) if the admin for the Business is onboarding, as it provides higher level of authentication and the token doesn’t expire. Use Flow 2 (Asset-Based Flow) if the admin for the business is not available or the Ad Account and Page are not owned by the same business. Use Flow 3 (Partner Billing Flow) if you, as a partner, want marketing message deliveries to be billed to your own ad account instead of your client’s.

Before You Start

  • Go to Your App⁠ > Messenger > Messenger API Settings > Advanced and accept Terms to use Marketing Message API for Messenger.
  • Read our Get Started Guide for more on setting up Marketing Message API for Messenger.
  • Complete App Review for the following permissions before serving clients:
    • ads_management
    • pages_messaging
    • paid_marketing_messages or marketing_messages_messenger
    • business_management (required for Flow 3: Partner Billing Flow)

Flow 1: Business Portfolio Flow (SUAT)

This flow requires users to have Business Portfolio permission to onboard. It uses the paid_marketing_messages permission and generates a non-expiring system-business access token.

Create a configuration

In the following steps, you are creating a login configuration that requires the business to select the following assets for sending marketing messages:
  • Facebook Pages
  • Meta business portfolio
  • Meta ad account
Note: If the business does not have one of the required assets (Facebook Page, a Meta business portfolio, or a Meta ad account), the business can create any, or all, of these assets during the login flow.
  1. In the Meta App Dashboard, click Configurations under Facebook Login for Business in the menu to the left.
  2. Click Create Configuration.
  3. Add a name for this configuration and click Next.
  4. In the Choose login variation section, select General and click Next.
  5. In the Choose access token section, select System-business access token.
  6. In the Choose token expiration section, select Never and click Next.
  7. In the Choose assets section, select Pages and then Asset Required, and Ad accounts and then Asset Required.
  8. Click Next.
  9. In the Choose permissions section, add the following permissions:
    • ads_management
    • pages_messaging
    • paid_marketing_messages
  10. Click Create.
Launch the Graph API Explorer
Your Marketing Message API for Messenger login configuration for Flow 1 is complete.

Flow 2: Asset-Based Flow (UAT)

This flow does not require Business Portfolio permission. Users can onboard their Ad Accounts and Pages as long as they have full control permission for those assets. It uses the marketing_messages_messenger permission.

Create a configuration

In the following steps, you are creating a login configuration that allows your business to select the necessary assets for sending marketing messages:
  • Facebook Pages
  • Meta ad account
Notes:
  • If your business does not have either a Facebook Page or a Meta Ad Account, you must create them before starting the onboarding process.
  • The logged in user needs to have full control / manage permission for the Facebook Page and the Ad Account.
  • The generated tokens in this flow will be short-lived tokens and will expire in about 1 hour. You can use instructions here to get a long-lived token which expires in 60 days.
  1. In the Meta App Dashboard, click Configurations under Facebook Login for Business in the menu to the left.
  2. Click Create Configuration.
  3. Add a name for this configuration and click Next.
  4. In the Choose login variation section, select General and click Next.
  5. In the Choose access token section, select User access token and click Next.
  6. In the Choose permissions section, add the following permissions:
    • ads_management
    • pages_messaging
    • marketing_messages_messengerImportant: Do NOT add paid_marketing_messages permission for this flow.
  7. Click Create.
Launch the Graph API Explorer
Your Marketing Message API for Messenger login configuration for Flow 2 is complete.

Flow 3: Partner Billing Flow (SUAT)

This flow is a variation of Flow 1 (Business Portfolio Flow) where you, the partner, are billed for marketing message deliveries instead of your client. It uses the same paid_marketing_messages permission and generates a non-expiring system-business access token, but your client only needs to grant access to their Page. After login, you connect your own ad account to the system user created at login, and use that ad account when creating message campaigns.

Create a configuration

In the following steps, you are creating a login configuration that requires the business to select the following assets for sending marketing messages:
  • Facebook Pages
  • Meta business portfolio
Note: Unlike Flow 1, do not mark Ad accounts as a required asset — you provide your own ad account in a later step.
  1. In the Meta App Dashboard, click Configurations under Facebook Login for Business in the menu to the left.
  2. Click Create Configuration.
  3. Add a name for this configuration and click Next.
  4. In the Choose login variation section, select General and click Next.
  5. In the Choose access token section, select System-business access token.
  6. In the Choose token expiration section, select Never and click Next.
  7. In the Choose assets section, select Pages and then Asset Required. Do not select Ad accounts.
  8. Click Next.
  9. In the Choose permissions section, add the following permissions:
    • ads_management
    • pages_messaging
    • business_management
    • paid_marketing_messages
  10. Click Create.
Launch the Graph API Explorer

Connect your ad account to the client’s system user

After your client completes the login, the SUAT is associated with a Business Integration System User (BISU) created on your client’s business portfolio. To bill marketing message campaigns to your own ad account, connect that ad account to the BISU.

Step 1: Get the BISU ID

Call GET /me with the SUAT to retrieve the BISU ID.
curl -X GET "https://graph.facebook.com/<API_VERSION>/me?fields=id" \
     -H "Authorization: Bearer <SYSTEM_USER_ACCESS_TOKEN>"
On success, the response contains the BISU ID:
{
  "id": "<BUSINESS_INTEGRATION_SYSTEM_USER_ID>"
}

Step 2: Connect your ad account to the BISU

Send a POST request to the asset connections endpoint with your ad account ID.
Important: This endpoint differs from other Marketing Messages endpoints in three ways. Calling it with the wrong pattern will fail.
  • The host is api.facebook.com, notgraph.facebook.com.
  • The URL has no API version segment.
  • The request body must be sent as multipart/form-data (--form in curl), not JSON.
curl -X POST "https://api.facebook.com/system_accounts/<BUSINESS_INTEGRATION_SYSTEM_USER_ID>/asset-connections" \
     -H "Authorization: Bearer <SYSTEM_USER_ACCESS_TOKEN>" \
     --form 'asset_id=<PARTNER_AD_ACCOUNT_ID>'
On success, the response is HTTP/2 202 with:
{"success": true}
After the connection succeeds, create marketing message campaigns using your own ad account ID (act_<PARTNER_AD_ACCOUNT_ID>) as the campaign target. All messages are billed to your ad account instead of your client’s.
Your Marketing Message API for Messenger login configuration for Flow 3 is complete.

Test your login flow

We recommend testing the login flow in Meta’s Graph API Explorer.
  1. On the right side of the explorer, select your marketing messages app from the Meta App dropdown menu.
  2. Click Configurations then select your marketing messages configuration from the dropdown menu. The access token type, permissions, and assets required by this configuration are listed.
  3. Click Generate Access Token to trigger the login flow.
  4. After you complete the login flow in the pop-up window, a new access token is shown in the Graph API Explorer.
Launch the Graph API Explorer
For Flow 1: Upon successful login, your app creates a non-expiring system business access token for the business.
For Flow 2: Upon successful login, your app creates a short-lived user access token (expires in ~1 hour). To get a long-lived token (expires in 60 days), follow the instructions here.
For Flow 3: Upon successful login, your app creates a non-expiring system business access token scoped to your client’s selected Page(s). After receiving the token, complete the Connect your ad account to the client’s system user steps before sending campaigns.

View token details

Click the triangle icon to view the following access token information:
  • App name and Meta ID
  • Business ID (Flow 1 and Flow 3 only)
  • Validation status
  • Scopes
  • Graph domain
Click Open in Access Token Tool to view more information about this access token.

Invoke the login dialog in your app

We recommend implementing the Javascript SDK from Meta in your web app to invoke the login dialog flow.

Embed your login button or URL in your web app

Set the config_id attribute to your configuration’s ID in the fb:login-button element to invoke your configuration during login
<fb:login-button config_id="<CONFIG_ID>" onlogin="checkLoginState();">
</fb:login-button>
Use the JavaScript SDK from Meta’s FB.login() method in your web app to use a specific configuration to get a system user access token.
  • Set config_id to your configuration’s ID
  • Set response_type to code – authorization code grant type required for system user access tokens
  • Set override_default_response_type to true – any response types passed in take precedence over the default types

Example code

FB.login(
  function(response) [
    console.log(response);
  ],
  [
    config_id: '<CONFIG_ID>',
    response_type: 'code',
    override_default_response_type: true
  ]
);
When your app user completes the login dialog flow, Meta redirects the user to your redirect URL and includes the authorization code. You must then exchange this code for an access token by performing a server-to-server call to Meta servers.
curl https://graph.facebook.com/<API_VERSION/oauth/access_token?
  client_id=<APP_ID>
  &client_secret=<APP_SECRET>
  &code=<AUTHORIZATION_CODE>
See Exchanging Code for an Access Token for more information about this step.

Best practices

Implement the following recommendations to help businesses discover and onboard to your app.
  • Use “Marketing Messages” in the name for the marketing messages product in your app and explain its benefits.
Marketing Messages on Messenger
Increase customer retention, and boost engagement and sales by sending personalized updates and promotions on Messenger.
  • Re-engage with customers anytime, beyond a 24-hour limit.
  • Automatically get people to subscribe to marketing messages. Subscriptions do not expire.
  • Send messages to everyone subscribed, or segment customers based on the subscription source or custom tag.
  • Pay per message delivered and measure down-funnel conversions.
  • Place the entry point to Marketing Messages in your app’s primary navigation, or near the relevant messaging flows, with an informational banner or a contextual guidance card.
  • Link your Marketing Messages onboarding flow to your app’s Get started action button.
  • When integrating multiple flows, provide clear guidance to help users choose the appropriate flow based on their permission level and business needs.

Next steps

Now that you have onboarded businesses to your app, get a list of subscribers to send paid marketing messages.