Webhook endpoints

Settings → Webhook endpoints, needing webhook_endpoint.manage. The consumer-side contract — payloads, signature verification, delivery semantics — is in Outbound webhooks.

Creating one

Provide an HTTPS URL and select the events to subscribe to. Verity generates a signing secret used for the X-Verity-Signature header.

An endpoint receives only its subscribed events, and only while active. Deactivating stops delivery without deleting the endpoint or its history.

Deliveries

Webhook deliveries (webhook_delivery.view) lists every attempt with its status, attempt count, timestamps, response status and body, and any error.

Any 2xx is a success; anything else is recorded as failed.

No automatic retry

A failed delivery stays failed. Watch this list, and if your system must not miss a decision, reconcile periodically against the API. Failures are recorded rather than silent, so a gap is visible.

Testing an endpoint

Point it at a request-inspection service first and trigger a real review decision in a non-production account. Verify the signature end to end before trusting it — an endpoint that accepts unsigned requests is an endpoint anyone can post to.

Audit

Endpoint creation and updates emit webhook_endpoint.created and webhook_endpoint.updated.