Application Settings


Update, retrieve, or reset your application settings using the WhatsApp Web Business Tool or by using API calls to the /v1/settings/application endpoint.

This document covers using API calls in order to:

The complete list of valid application settings is listed under the Parameters section.

You must use the admin account to access the application settings.

Update Application Settings

To configure settings for the WhatsApp Business API Client, use the /v1/settings/application endpoint with a JSON message body containing the field names and values to be set.


If a field is not present in the request, no change is made to that setting. For example, if callback_persist is not sent with the request, the existing configuration for callback_persist is unchanged.

PATCH /v1/settings/application
    "callback_persist": true | false,
    "max_callback_backoff_delay_ms": "max-delay-in-ms",
    "media": {
        "auto_download": ["audio", "document", "voice", "video", "image", "sticker"]
    "callback_backoff_delay_ms": "delay-in-ms",
    "pass_through": false | true,
    "sent_status": false | true,
    "heartbeat_interval": heartbeat-interval-in-secs,
    "unhealthy_interval": unhealthy-interval-in-secs,
    "webhooks": { 
        # see Webhooks Settings below
        "max_concurrent_requests": max-num-of-callback-requests,
        "url": "webhook.your-domain"
    "axolotl_context_striping_disabled": false | true


Some settings require that the Coreapp be restarted in order for the changes to go into effect. Those settings are callback_persist, pass_through and webhooks: max_concurrent_requests.




Options: true (default), false
Stores callbacks on disk until they are successfully acknowledged by the Webhook or not. Coreapp restart required.
Messages and callbacks are both stored in a local database to ensure that they are delivered successfully before being removed from the local database. This protects the callbacks in the event the WhatsApp Business API Client or server goes down.



Default: 900000
Maximum delay for a failed callback in milliseconds
For more information, read the description for callback_backoff_delay_ms below.



List of media to auto-download
See Auto-download Media Settings for more information.



Default: 3000
Backoff delay for a failed callback in milliseconds
This setting is used to configure the amount of time the backoff delays before retrying a failed callback. The backoff delay increases linearly by this value each time a callback fails to get a HTTPS 200 OK response. The backoff delay is capped by the max_callback_backoff_delay_ms setting. For example, if a callback fails the first time, it will try again in 3000ms (3 sec). A second failure will result in a 6000ms (6 sec) delay before retry. This continues until the callback is successful or the delay reaches 900000ms (15 min) after which the callback will continue to be retried but the delay will not increase.

The on_call_pager will be deprecated in v2.29. The same alerts are sent with Webhook callbacks and monitoring dashboard alerts. Please use these channels for critical errors.


Set to valid WhatsApp Group with users who wish to see alerts for critical errors and messages.

Please follow steps as per the Groups documentation to create valid WhatsApp Group. Here is the summary of those steps:



Options: true, false
Default: true
The pass_through parameter only applies to individual messages; group messages are not affected by this parameter.
When messages are sent, they are stored in a local database. This database is used as the application's history. Since the business keeps its own history, you can specify whether you want message pass_through or not.
When true, removes messages from the local database after they are delivered to or read by the recipient. When false, saves all messages on local storage until they are explicitly deleted. Coreapp restart required.



Options: true (default), false
Receive a notification that a message is sent to server. When true (default), you will receive a message indicating that a message has been sent. If false, you will not receive notification.


Webhooks Object

URL for your Webhook
If the Webhook URL is not set, then callbacks will be dropped. Callbacks are an important channel to deliver, both timely notifications as well as out-of-band errors, and it is thus highly recommended to configure the Webhook URL endpoint.
For details on the Webhook fields, see the Webhooks Settings.



Default: 30
Multiconnect: Maximum amount of seconds a Master node waits for a Coreapp node to respond to a heartbeat before considering it unhealthy and starting the failover process.



Default: 5
Multiconnect: Interval of the Master node monitoring of Coreapp nodes in seconds



Options true, false (default)
Affects database connection limits
v2.25.x improves outbound and inbound performance over previous releases. This optimization relies on creating additional database connections. For some deployments, this can cause database connection limits being reached. If that is the case, set the axolotl_context_striping_disabled configuration to true to disable this performance improvement feature. Restarting the Coreapp is required for the configuration change to take effect. There is no other effect on any functionalities of the Coreapp.

Webhooks Parameters

The following table describes fields in the webhooks object in more detail.




Inbound and outbound notifications are routed to this URL. A HTTPS-based endpoint is required; HTTP will not work. This URL may look like this: For more information, read the Webhooks documentation.



Configures the maximum number of inflight callback requests that are sent out. Can be set to 6 (default), 12, 18, or 24. Restart required.

Auto-download Media Parameters

The following table describes the media object in more detail.




An array specifying which types of media to automatically download. Can contain any or all of the following: audio, document, voice, video, image, sticker.


A successful response is the HTTP status code 200 OK with a null or {} message body.

If you encounter any errors, see Error and Status Messages.

Retrieve Application Settings

Use the /v1/settings/application endpoint to retrieve all the current application settings.


GET /v1/settings/application


If successful, your request returns 200 OK and a message body containing an application object. For example, the complete response, including the application object, might look like this:

    "settings": {
        "application": {
            "callback_backoff_delay_ms": 2000,
            "callback_persist": true,
            "heartbeat_interval": 5,
            "max_callback_backoff_delay_ms": 800000,
            "media": {
                "auto_download": [
            "pass_through": true,
            "sent_status": true,
            "unhealthy_interval": 30,
            "wa_id": "16315558011",
            "webhooks": {
                "max_concurrent_requests": 12, 
                "url": ""

Reset Application Settings

Use the /v1/settings/application endpoint to reset the application settings to their default values.


DELETE /v1/settings/application


A successful response is 200 OK with null or {}.

If you encounter any errors, see Error and Status Messages.