Skip to main content
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.

Payload

string
Always AppSettings.
string[]
The keys that this save changed. For a secret, the key shows that it changed, never the value.
integer
The manifest version of the save.
object
The current non-secret values. This object never has secrets.
string[]
The secret fields that have a value.
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.
2

Read secrets through the API

The webhook has no secret values. If a key in secret_keys changed, call GET /app-installation/settings to read it.
3

Return 2xx quickly

Do the work after you reply, for example in a queue.
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.
Last modified on November 16, 2026