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
The keys that this save changed. For a secret, the key shows that it changed, never the value.
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.