Skip to main content
Webhooks let you receive a callback whenever a Review Queue decision is made, instead of polling Gegentic for status.

Creating a webhook endpoint

  • Endpoint URL (required) — must be HTTPS
  • Description (optional)
  • Events to subscribe (required) — at least one of:
    • review.approved
    • review.rejected
    • review.failed
By default, a new endpoint subscribes to all three events.

Verifying webhook payloads

Each delivery includes a signature header computed as an HMAC-SHA256 of the raw request body, using a signing secret generated when you create the endpoint:
x-gegentic-signature: sha256=<hmac>
The signing secret is shown only once, at creation time. Store it securely — you’ll need it to verify incoming deliveries.
Your endpoint must respond with a 2xx status within 15 seconds. Failed deliveries are retried automatically.

Delivery history

Each webhook endpoint’s delivery attempts — including the linked Review Queue request, response status, and timestamp — are visible from the Webhooks page, so you can debug missed or failed deliveries.