Webhook events
Use webhooks to react to user consent decisions and privacy request lifecycle changes in near real time.
Overview
Webhooks are useful when your backend must react immediately to a consent or privacy event without polling the API. They send event payloads to a configured endpoint when a state change occurs.
Consent created
Triggered when a new consent record is stored.
Consent updated
Triggered when a consent decision or purpose status changes.
Privacy request changed
Triggered when a request moves through review, approval, or completion.
Event types
| Event | Description |
|---|---|
| consent.created | A new consent record is created. |
| consent.updated | Consent status or metadata changes. |
| consent.revoked | Consent is withdrawn or revoked. |
| consent.expired | Consent validity window ends. |
| privacy_request.created | A new request is submitted. |
| privacy_request.updated | A request is reassigned or resolved. |
Delivery model
Webhooks should be sent from trusted infrastructure to an endpoint that verifies the signature and queues the event for internal processing. Store the payload, acknowledge receipt, and process the event asynchronously if needed.