> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dodopayments.com/llms.txt
> Use this file to discover all available pages before exploring further.

# app.settings.updated Webhook

> The webhook that Dodo Payments sends to your app after a merchant saves settings. Includes the payload, an example, and handling advice.

> [!WARNING]
>
> App settings are in development. They are not yet available in production, and details can change before release.

Dodo Payments sends `app.settings.updated` to the webhook URL of your app after a merchant saves settings. Your app always receives this event for its own installations. It needs no scope and no event subscription check. The envelope and the signature are the same as for other app events. See [App webhooks](https://docs.dodopayments.com/developer-resources/build-an-app.md#webhooks).

## Payload

```json theme={null}
{
  "livemode": false,
  "business_id": "bus_123",
  "installation_id": "ains_123",
  "app_id": "app_123",
  "type": "app.settings.updated",
  "data": {
    "payload_type": "AppSettings",
    "changed_keys": ["project_name", "api_key"],
    "manifest_version": 1,
    "values": {
      "project_name": "Acme",
      "sample_rate": 100
    },
    "secret_keys": ["api_key"],
    "action_needed": false
  }
}
```

**data.payload\_type** `string`

Always `AppSettings`.

**data.changed\_keys** `string[]`

The keys that this save changed. For a secret, the key shows that it changed, never the value.

**data.manifest\_version** `integer`

The manifest version of the save.

**data.values** `object`

The current non-secret values. This object never has secrets.

**data.secret\_keys** `string[]`

The secret fields that have a value.

**data.action\_needed** `boolean`

`true` if a required field has no value, or a stored value is not valid.

The values in `data` are the values at the time of sending, not at the time of the save. If a merchant saves twice quickly, you can receive the newest values in both events.

## Handle the event

**1. Verify the signature**

Check the `webhook-id`, `webhook-timestamp`, and `webhook-signature` headers on the raw body. See [Verify the signature](https://docs.dodopayments.com/developer-resources/build-an-app.md#verify-the-signature).

**2. Read secrets through the API**

The webhook has no secret values. If a key in `secret_keys` changed, call [`GET /app-installation/settings`](https://docs.dodopayments.com/developer-resources/apps/app-settings/read-settings) to read it.

**3. Return 2xx quickly**

Do the work after you reply, for example in a queue.

> [!TIP]
>
> Use `webhook-id` to skip an event that you already processed, because a retry can deliver the same event more than once. Treat the event as a signal that settings changed. The API is the source of truth, so you can always read the current state.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.