Webhook Reference
Webhook payloads and events
Consume versioned incident and recovery events.
Generic Webhook deliveries contain a schema version, event name, delivery and destination context, monitor context, and event data.
Events
Implemented delivery flows include a test event and selected incident lifecycle events. Branch on the documented event name and schema version. Ignore unknown additive fields so compatible payload additions do not break your consumer.
Keep the delivery identifier for idempotency. If the same delivery is retried, process it once. Display names can change and must not be used as stable identifiers or authorization decisions.
Payload
Verify the request signature before parsing JSON. After verification, validate required fields for the event you handle and store only what your workflow needs.
Use monitor and event context for routing, not for bypassing your own access control. Apply your organization’s retention policy to stored payloads and keep private incident data out of general application logs.
Next: implement signing and replay protection or configure a Generic Webhook.