Skip to main content
POST
Enable WhatsApp Voice

Authorizations

Authorization
string
header
default:App
required

This is the most secure authorization type and the one with the most flexibility.

API keys can be generated by calling the dedicated API method. Furthermore, API keys can have a limited scope and cover only some API methods. Lastly, they can be revoked at any time. This range of possibilities makes API keys well suited for separating the API access rights across multiple applications or use cases. Finally, the loss of an API key is easily manageable.

You can manage your API keys from GUI, or programmatically with dedicated API.

API key Authorization header example:

Path Parameters

sender
string
required

Registered WhatsApp sender number. Must be in international format.

Required string length: 1 - 15
Pattern: [0-9]+

Body

application/json
callIconVisibility
enum<string>

Visibility of the call icon in the WhatsApp app.
DEFAULT - The call icon is shown according to Meta defaults.
DISABLE_ALL - The call icon is hidden.

Available options:
DEFAULT,
DISABLE_ALL
Example:

"DEFAULT"

callbackPermissionStatus
enum<string>

Status of the sender's permission to call end users back.
ENABLED - The sender is permitted to call end users back.
DISABLED - The sender is not permitted to call end users back.

Available options:
ENABLED,
DISABLED
Example:

"ENABLED"

Response

WhatsApp Voice enabled successfully.