Webhooks and audit logs

Webhooks let your backend react to changes without polling every resource. Register endpoints at the organization level, use the test operation before production traffic, and retain your own idempotency record for deliveries.

Configure a webhook

1. Create a registry entry for the organization.
2. Point it to a public HTTPS endpoint you control.
3. Trigger the registry test operation and verify your handler returns a successful response.
4. Process events asynchronously and make duplicate deliveries safe.

Inspect deliveries

Use webhook-logs for delivery history and activity-logs for organization activity. These endpoints are useful for support, reconciliation, and operational auditing.

Receive safely

Respond quickly, enqueue expensive work, and record the event identifier before applying side effects. A webhook handler should not expose secrets or allow untrusted payload data to become a command.