WhatsApp Business Platform

Access Tokens Guide

Updated: Sep 19, 2026
Copy for LLM
The platform supports the following access token types. The type you use depends on who uses your application, and whether you are a partner.

System user access tokens

System user access tokens (“system tokens”) represent you, your business, organization, or people within your business or organization. The main advantage of these tokens is that they are long-lived and can represent automated services within your business that don’t require any user input.
System tokens rely on system users. Most endpoints check if the user identified by the token has access to the queried resource. If the user doesn’t have access to the resource, the system rejects the request with error code 200 (not to be confused with HTTP status code 200).
System users can be admins or employees.

Admin system users

By default, admin system users have full access to all WhatsApp accounts (WAACs), Messaging accounts, and their assets owned by or shared with you or your business portfolio.
Admin system users are useful if your app needs access to all of the business portfolio’s assets, without having to manually grant business asset access to each asset whenever it is created, or shared with your business portfolio.
You can override an admin system user’s default business asset access by granting partial access per account. Grant it separately for each WhatsApp account and each Messaging account. See Business Asset Access to learn how to set and override access.

Employee system users

Employee system users must be granted access to the individual WhatsApp accounts and Messaging accounts that are owned by, or shared with, your business portfolio. If your app only needs access to a few accounts that you own, an employee system user should be sufficient.
Once created, you must grant Partial or Fullbusiness asset access for both accounts the system user needs to work with: the WhatsApp account and the Messaging account. Access to the Messaging account alone is not sufficient.
How the grant is applied differs by surface:
  • API. Granting business asset access on a Messaging account also applies that grant to the WhatsApp account it is linked to. This cascade exists because the WhatsApp account has no Graph API endpoints of its own yet. Treat it as interim behavior rather than something to depend on.
  • Meta Business Suite. The panel does not cascade. Assign the system user to the WhatsApp account and to the Messaging account explicitly.

Generate system user access tokens

To generate a system token, access the Business settings⁠ panel and then click System Users:
Meta Business Suite Settings panel with System Users selected and no system users added yet, and both WhatsApp accounts and Messaging accounts listed under Accounts in the navigation
Click the +Add button, and in the Create system user window that appears, enter a system user name and assign it an Admin or Employee role:
Create system user dialog with name field and role selector
Once you create the admin system user, it appears in the list of system users. Click the system user’s name to display the asset assignment overlay:
System users list with a system user selected, showing the Assigned assets tab with no assets assigned and an Assign assets button, and both WhatsApp accounts and Messaging accounts listed under Accounts in the navigation
Click the Assign assets button to display the Select assets and assign permissions window:
Select assets and assign permissions dialog
Select your app and grant your system user the Manage app permission, then click the Assign assets button to confirm and dismiss the window.
Back in the System Users panel, reload the page to confirm that your system user has been granted Full control of your app. Granting the permissions may take a few minutes, so reload the page if your app doesn’t appear as an assigned asset. Once the asset has been assigned, it should look like this:
System user with full control of app displayed
Once you see that your system user has been granted full control of your app, in the asset assignment overlay, click the Generate token button. In the window that appears, select your app, choose a token expiration preference, and assign your app these three Graph API permissions:
  • business_management
  • whatsapp_business_management
  • whatsapp_business_messaging
You can search for business to find these permissions quickly:
Token generation dialog showing business permissions search
Click the Generate token button and copy the token when it appears.

Business integration system user access tokens

Business Integration System User access tokens (“business tokens”) are scoped to individual onboarded customers and should be used by Tech Providers and solution partners when accessing onboarded customer data.
These tokens are useful for apps that perform programmatic, automated actions on customer Messaging accounts, without having to rely on input from an app user, or requiring future re-authentication.
To generate a Business Integration System User access token, you must implement Embedded Signup (configured with Facebook Login for Businesses) and exchange the code returned to you when a customer completes the flow.
See Embedded Signup and Business Integration System User access tokens to learn more about these tokens and how to generate them.

User access tokens

Although User access tokens are supported and can be used by all app developers, you typically only use them when you first use the App Dashboard to send your first test message. As you develop your app, however, you switch to a System User access token (and eventually a Business Integration System User access token, if you are a Tech Provider or a partner). This is because user access tokens expire quickly, so you have to keep generating a new one every few hours.
There are several ways to generate a User access token:
  • Access the App Dashboard > WhatsApp > API setup panel. This panel always generates a new User access token whenever you visit it. The token is automatically scoped to your user, since you are signed into your developer account when you access the panel.
  • Use Graph API Explorer.
  • Implement Facebook Login.

Use tokens in requests

When making API requests, include your token in an authorization request header, preceded by Bearer. For example:
curl 'https://graph.facebook.com/v27.0/102290129340398/message_templates' \
-H 'Authorization: Bearer EAAJB...'

Token format

Access tokens are opaque strings. A full token looks like this:
EAAJBsbCmS80BO4hZBf5xYKFaFW7kVMNxAWzIInZB7q1PuZCLiEqKh3gZDZD
Tokens can vary in length, and their internal structure and characteristics can change over time. Do not parse, decode, or make assumptions about the format of an access token — treat it as an opaque string. Use a variable-length data type without a specific maximum size to store access tokens.

Business asset access

After creating a system user, you must set business asset access levels. Many endpoints require the system user whose token is included in API requests to have either Partial or Full business asset access to both the WhatsApp account and the Messaging account being queried (or their assets). If the system user doesn’t have this access, these endpoints return error code 200 (not to be confused with HTTP status code 200).
Granting access on a Messaging account through the API also applies the grant to the WhatsApp account linked to it. Meta Business Suite does not do this — there, assign the system user to each account explicitly. The cascade is interim behavior that exists only until the WhatsApp account has API endpoints of its own, so do not build on it.
If you set a system user’s business asset access on a WhatsApp account or Messaging account to Partial access, you can further restrict access to certain assets or actions on that account. For example, if you have a large business and want a certain department to only have read access to a Messaging account’s template data and a WhatsApp account’s business phone number data, you could create a system user for that department and set granular access to view only for that data.
To set business asset access, follow these steps for the WhatsApp account, then repeat them for the Messaging account:
  1. Sign into Meta Business Suite⁠.
  2. Locate your business portfolio in the dropdown menu at the top of the page and click its Settings (gear) icon.
  3. Navigate to Accounts > WhatsApp accounts, or Accounts > Messaging accounts.
  4. Select the appropriate account.
  5. Select the People subtab.
  6. Click the +Add people button.
  7. Select the appropriate system user and assign appropriate access levels on the account.
Manage assignments dialog for a WhatsApp account, with Partial access toggles for phone numbers and messages and a Full access toggle for everything
Manage assignments dialog for a Messaging account, with Partial access toggles for message templates and a Full access toggle for everything