What it does
Returns the webhook configuration that is currently active for the application — the destination URL, the custom headers the Gateway attaches when it calls you, and which event types you are subscribed to. Read-only; nothing is changed. Use it to verify a configuration after an update, or to check which events an app is receiving before you debug a missing payload.GET and the update call share the same path. Sending the path with no body reads the configuration; sending a body updates it — see Update Webhook.Endpoint
Headers
string
required
Secret key in
Bearer sk_... format. See Secret Key authentication.Path parameters
string
required
Application ID. Must belong to the organization (otherwise
404).Response
boolean
true when the configuration was read successfully.object
The active webhook configuration.
Examples
Demo 1 — read the active webhook
Demo 1 — read the active webhook
Demo 2 — app not in the organization → 404
Demo 2 — app not in the organization → 404
Errors
object
Error details with
code, group, and description; isSuccess is false.Next steps
Update Webhook
Change the URL, headers, or event subscriptions.
Webhook payloads
What each event body looks like and how retries work.