Facebook Login for Business is the preferred authentication and authorization solution for tech providers building integrations with Meta’s business tools to create marketing, messaging, and selling solutions.
Facebook Login for Business allows you to create a login experience in the Meta App Dashboard based on the needs of your app. You can specify the access token type, assets, and permissions your app needs, and save it as a configuration. During login your app users are presented with this configuration that allows them to grant your app access to their business assets.
email
and public_profile
permissions are automatically granted to all apps but at least one other supported permission must be included for each app installation.The following table shows the available permissions for Facebook Login for Business.
|
|
|
You can use Facebook Login for Business to get either Business Integration System User access tokens or User access tokens.
User access tokens should be used if your app takes actions in real time, based on input from the user. For example, use a user access token if your app requires a user to input text and click a button in order to post content to their Page. User access tokens should also be used if you require an API that requires admin permissions on a business portfolio.
Business integration system user access tokens should be used if your app performs programmatic, automated actions on your business clients' assets without having to rely on input from an app user, or require re-authentication at a future date. For example:
To get business integration system user access tokens from your business clients:
To test the business integration system user access token flow, the tester must have a role on the app and full control of the client business.
If you need different access setups for different purposes or departments, you can use multiple granular business integration system user access tokens per client business to improve the scalability and security of your integrations.
Granular access tokens are still specific to a client business portfolio. They are not shareable and accessible across different client businesses. Their scope and asset list are a subset of the original business integration system user access token.
To isolate potential security incidents in the event of a compromised token, only that specific client business will be impacted, instead of impacting all business portfolios across all client businesses.
When a client business installs an app through Facebook Login for Business and generates a business integration system user access token, the token includes a client business ID. This ID represents the client business and is used by your app to make API calls.
The /<CLIENT_BUSINESS_ID>/system_user_access_tokens
endpoint allows you to manage your existing business integration system user access tokens. Actions include:
Object | Description |
---|---|
| Required. This access token requires the |
| Required.
The |
| Optional.
When you want to generate a more granular token, you can set a list of |
| Optional. The flag you want to use to fetch the existing token and indicate this operation is read only |
| Optional.
When you want to generate a more granular token, you can set a list of |
| Optional.
When you generate a new token, set to |
| Optional. The ID for the system user included in the access token. |
Formatted for readability.
curl -i -X POST "https://graph.facebook.com/v21.0
/<CLIENT_BUSINESS_ID>/system_user_access_tokens
?appsecret_proof=<APPSECRET_PROOF_HASH>
&access_token=<ACCESS_TOKEN>
&system_user_id=<SYSTEM_USER_ID>
&fetch_only=true"
On success your app receives a JSON response with a new access token to be used in subsequent API calls.
{ "access_token": "<NEW_ACCESS_TOKEN>" }
Business Integration System User access tokens | User access tokens | |
---|---|---|
Access Designations | Access is explicitly delegated at the time of authorization. Your app can only access the assets that were designated by your business client when they completed the Facebook Login for Business flow. Tech Providers only. | Access is inherited from your app user's current account access; your app can access the same business assets that the app user currently has access to. |
Account association | Associated with your business client's business portfolio rather than a specific user. Any admin in your business client's admin group can grant your app a system user access token. | Associated with your app user's personal Facebook account. |
Expiration and refresh | Defaults to never expire for the common offline server-to-server communication. | A short-lived token for online activities such as web browsers. |
OAuth grant type | Authorization Code grant only. | Implicit grant by default, and can support authorization code grant for improved security. Mainly used for user-agent based clients such as web browsers and mobile apps. |
Representation | Part of the Tech Provider integration's infrastructure, initialized by a client business through Tech Provider’s app installation. | Represents servers or software making API calls to assets owned or managed by a Business Manager. |
Token Invalidation | Your business clients can invalidate business integration system User access tokens by going to Business Manager > Settings > Business Settings > Integrations > Connected apps and removing your app. | Your business clients can invalidate User access tokens by going to Facebook and navigating to Settings & privacy > Settings > Security and login > Business Integrations and removing your app. |
User access token login flow | Business integration system user access token login flow |
---|---|
The following are the steps required to set up Facebook Login for Business if you don't already have an app.
You will receive a Configuration ID that you will use in your code to invoke the login dialog.
To create a WhatApp Embedded Signup configuration, visit our WhatsApp Embedded Signup guide.
To create a Conversions API for Business Messaging configuration, visit our Marketing API – Conversions API for Business Messaging guide.
To create an Instagram Graph API configuration, visit our Instagram Graph API documentation.
Invoke a login dialog using one of our SDKs (recommended) or manually build your login flow.
You can use any of our SDKs to invoke the login dialog by replacing the list of scopes (permissions) your app needs with your configuration ID and the access token's required OAuth grant type.
If you are unfamiliar with our SDKs, we recommend that you first install the JavaScript SDK and get it working with the consumer Facebook Login product before proceeding, as the following examples reference the SDK.
Here's an example of the JavaScript SDK's FB.login()
method modified to use a configuration for a System User access token. Note that config_id
has replaced scope
(which should not be used), the response_type
has been set to code
, since SUAT's require the authorization code grant type, and override_default_response_type
must be set to true
. When true, any response types passed in the response_type
will take precedence over the default types.
FB.login( function(response) [ console.log(response); ], [ config_id: '<CONFIG_ID>', response_type: 'code', override_default_response_type: true ] );
When the user completes the login dialog flow we will redirect the user to your redirect URL and include a code. You must then exchange this code for an access token by performing a server-to-server call to our servers.
GET https://graph.facebook.com/v21.0
/oauth/access_token?
client_id=<APP_ID>
&client_secret=<APP_SECRET>
&code=<CODE>
See Exchanging Code for an Access Token for more information about this step.
Here's an example of the JavaScript SDK's FB.login()
method modified to use a configuration for a User access token. Note that config_id
has replaced scope
(although scope
can still be included, we recommend that you do not use it).
FB.login( function(response) { console.log(response); }, { config_id: '<CONFIG_ID>' // configuration ID goes here } );
Here's an example of the JavaScript SDK's login button modified to use a User access token configuration:
<fb:login-button config_id="<CONFIG_ID>" onlogin="checkLoginState();"> </fb:login-button>
See Manually Building the Login Flow to learn how to invoke the login dialog manually. When invoking the login dialog and setting the redirect URL, include your configuration ID as an optional parameter (although scope can still be included, we recommend that you do not use it).
config_id=<CONFIG_ID>
It is recommended you conduct testing and learn about potentially encountered problems before switching to Facebook Login for Business.
Facebook Login for Business is available to Business type apps.
If your app is eligible to switch to Facebook Login for Business, you should be able to see an opt in banner by the following steps:
Note that your current access tokens will not be impacted upon switching to Facebook Login for Business. Additionally, any test app(s) associated with this app will also switch to Facebook Login for Business.
After switching, your app type will be under Business type. If your app is not functioning as intended, each app is allowed to roll back to Facebook Login within 30 days after the switch.
Business clients might encounter error messages for the following reasons:
Potential breaking changes:
email
and/or public_profile
from your business clients, switching the app to Facebook Login for Business will lead to the invalidation of all previously installed tokens for these clients. config_id
parameter and you need to replace the config_id
parameter with the scope
parameter instead.Learn more about Meta Business Extension.
Only available when an existing app has switched to Facebook Login for Business; Newly created Business Type apps cannot switch back to Facebook Login.
After switching to Facebook Login for Business, if your app is not functioning as intended after switching to Facebook Login for Business, you can roll back to Facebook Login by going to the App Dashboard > Facebook Login for Business > Settings and clicking the Switch to Facebook Login link. You will be presented with a survey which helps us improve the Facebook Login for Business configuration experience. Each app is allowed to roll back to Facebook Login within 30 days after the switch.
The easiest way to add Facebook Login for Business is to create a new Business Type app, where Facebook Login for Business is automatically available, and request supported business permissions through Meta App Review. If you want to use it for an existing None type app, your app must have advanced access to at least one supported business permission.
If you are not a Tech Provider building solutions using Meta’s business APIs, Facebook Login is recommended for consumer authentication.
Only request the minimum permissions necessary for your app's functionality. Be transparent with users about why you need each permissions and features. Note that the email
and public_profile
permissions must be requested with at least one other supported business permission.
Yes, advanced access to the public_profile
permission is required for Facebook Login for Business apps before they go live. This requirement is crucial to ensure that the app can support authorization from users who do not have an app role, commonly referred to as external users.