WhatsApp Encrypted Messages API
Payload encryption provides an additional layer of security on top of existing standard TLS/SSL that secures communication between Cloud API and businesses. When enabled, all message requests and message echoes webhooks will undergo encryption using JWE (JSON Web Encryption) format.## Key Features- **Additional Security Layer**: Adds payload-level encryption on top of standard TLS/SSL- **JWE Format**: Uses JSON Web Encryption standard for encrypting message payloads- **Selective Encryption**: Only successful responses are encrypted; errors remain unencrypted- **Standard Compatibility**: Encrypted payloads contain the same structure as `/messages` endpoint- **Phone-Number Level**: Encryption is configured per phone number within a WABA## Setup Requirements1. **Enable Payload Encryption**: Use `POST //settings` to enable encryption2. **RSA Key Pair**: Generate and provide a 2048-bit RSA public key (base64 encoded)3. **Algorithm Support**: Multiple algorithms supported for content and key encryption4. **Access Token**: User Access Token with `whatsapp_business_messaging` permission## Supported Algorithms- **Content Encryption**: A128GCM, A256GCM, A128CBC-HS256, A192CBC-HS384, A256CBC-HS512- **Key Encryption**: RSA1_5, RSA-OAEP- **WhatsApp Standard**: A256GCM + RSA-OAEP for responses and webhooks
WhatsApp Encrypted Messages API is one of 74 APIs that WhatsApp publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 6 JSON Schema definitions.
Tagged areas include Encrypted Messages. The published artifact set on APIs.io includes an OpenAPI specification, a GitHub repository, API documentation, and 6 JSON Schemas.
This API exposes 1 operation across 1 path, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version v23.0.
Requests are made against 4 base URLs: https://graph.facebook.com, https://graph.facebook.com, https://graph.facebook.com, https://graph.facebook.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
WhatsApp Encrypted Messages API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (bearerAuth).
bearerAuth— System user access token with whatsappbusinessmanagement permission. Format: Bearer YOURSYSTEMUSERACCESSTOKEN
Paths & Operations 1
Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.
Payload encryption provides an additional layer of security on top of existing standard TLS/SSL that secures communication between Cloud API and businesses. When enabled, all mess…
Schemas 4
The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are ErrorObject (3 properties), EncryptedMessageRequest (2 properties), EncryptedMessageResponse (1 property), ErrorResponse (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from WhatsApp 12
Other APIs WhatsApp publishes across the network.
This is an independent, third-party profile of WhatsApp Encrypted Messages API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.