WhatsApp · OAuth Scopes

WhatsApp OAuth Scopes

OAuth 2.0 searched

WhatsApp publishes 5 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the WhatsApp API on a user’s behalf.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

MessagingAnalyticsWhatsAppBusiness MessagingMeta

Scopes: 5 Flows: Method: searched

Scopes (5)

Scope	Description	Flows
whatsapp_business_management	needed to access metadata on your Messaging account, template management, getting business phone numbers associated with your Messaging account, all analytics, and to receive webhooks notifying you of changes to your WhatsApp account
whatsapp_business_messaging	needed to send any type of message to WhatsApp users, and to receive incoming message and message status webhooks
business_management	only needed if you need to programmatically access your business portfolio
whatsapp_business_manage_events	only needed if you are sending marketing templates with Marketing Messages API for WhatsApp, in conjunction with the Conversions API, for event tracking.
ads_read	only needed if you are using Marketing Messages API for WhatsApp in conjunction with the Insights API to get conversion metrics.

📄 Provider scope reference: https://developers.facebook.com/documentation/business-messaging/whatsapp/permissions

Source

OAuth Scopes

generated: '2026-11-05'
method: searched
source: https://developers.facebook.com/documentation/business-messaging/whatsapp/permissions
docs: https://developers.facebook.com/documentation/business-messaging/whatsapp/permissions
note: The OpenAPI declares only http bearer; Meta documents Graph API permissions granted to the app (via system user token creation or Embedded Signup / Facebook Login for Businesses) and reported in the
  debug_token scopes property.
scopes:
- name: whatsapp_business_management
  description: needed to access metadata on your Messaging account, template management, getting business phone numbers associated with your Messaging account, all analytics, and to receive webhooks notifying
    you of changes to your WhatsApp account
  required: true
- name: whatsapp_business_messaging
  description: needed to send any type of message to WhatsApp users, and to receive incoming message and message status webhooks
  required: true
- name: business_management
  description: only needed if you need to programmatically access your business portfolio
  required: false
- name: whatsapp_business_manage_events
  description: only needed if you are sending marketing templates with Marketing Messages API for WhatsApp, in conjunction with the Conversions API, for event tracking.
  required: false
- name: ads_read
  description: only needed if you are using Marketing Messages API for WhatsApp in conjunction with the Insights API to get conversion metrics.
  required: false
access_levels: Partners whose clients use the app must pass App Review and hold Advanced access; without Advanced access on whatsapp_business_management for accounts not owned by your business, calls return
  error code 200. Direct developers accessing only their own data need neither.

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/whatsapp-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.