WhatsApp · Authentication Profile

Whatsapp Authentication

Authentication

WhatsApp secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.

MessagingAnalyticsWhatsAppBusiness MessagingMeta

Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

bearerAuth http

scheme: bearer

Source

Authentication Profile

generated: '2026-11-05'
method: searched
source:
- https://developers.facebook.com/documentation/business-messaging/whatsapp/access-tokens
- https://developers.facebook.com/documentation/business-messaging/whatsapp/permissions
summary:
  types:
  - http
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  description: System User Token with whatsapp_business_management permission
  sources:
  - openapi/whatsapp-analytics-api-openapi.yml
  - openapi/whatsapp-assets-api-openapi.yml
  - openapi/whatsapp-assigned-users-api-openapi.yml
  - openapi/whatsapp-business-accounts-api-openapi.yml
  - openapi/whatsapp-business-messaging-api-openapi.yml
  - openapi/whatsapp-business-profile-api-openapi.yml
  - openapi/whatsapp-flows-api-openapi.yml
  - openapi/whatsapp-lifecycle-api-openapi.yml
  - openapi/whatsapp-media-api-openapi.yml
  - openapi/whatsapp-message-templates-api-openapi.yml
  - openapi/whatsapp-messages-api-openapi.yml
  - openapi/whatsapp-phone-numbers-api-openapi.yml
  - openapi/whatsapp-product-catalogs-api-openapi.yml
  - openapi/whatsapp-qr-codes-api-openapi.yml
  - openapi/whatsapp-registration-api-openapi.yml
  - openapi/whatsapp-subscribed-apps-api-openapi.yml
  - openapi/whatsapp-two-step-verification-api-openapi.yml
derived_from: openapi/ (derive-authentication.py, 2026-11-05)
docs: https://developers.facebook.com/documentation/business-messaging/whatsapp/access-tokens
token_types:
- name: System User access token
  use: direct developers accessing their own data
  notes: long-lived; system user must be granted Partial or Full business asset access to both the WhatsApp account and the Messaging account
- name: Business Integration System User access token
  use: Tech Providers and solution partners accessing onboarded customer data
  obtained_via: Embedded Signup (Facebook Login for Businesses) code exchange
- name: User access token
  use: first test message from the App Dashboard > WhatsApp > API setup panel; replaced by a system token in development
transport: 'Authorization: Bearer <ACCESS_TOKEN> request header'
token_format: 'Opaque string; Meta: "Do not parse, decode, or make assumptions about the format of an access token — treat it as an opaque string."'
introspection: GET /<API_VERSION>/debug_token?input_token=... returns granted permissions in the scopes property (documented; not called by us)

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact 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 security artifact

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

All security posture

curl "https://apis.io/api/v1/security?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.