Webhooks are in private beta. Configure them via the Sigilix dashboard (coming soon) or via the API once published.
Event catalog
| Event | When it fires |
|---|---|
review.completed | A review has been posted to GitHub (success or failure-fallback) |
review.failed | A review couldn’t run (quorum failure, internal error) |
finding.created | A finding was posted (one event per finding, batched) |
installation.created | Sigilix was installed on a new repo |
installation.deleted | Sigilix was uninstalled |
Payload shape
All webhooks POST a JSON body to your endpoint with these common fields:Content-Type: application/json and HMAC-sign with X-Sigilix-Signature: sha256=<hex> using the secret you provide at registration.
Per-event payloads
review.completed
finding.created
Findings are batched into a single finding.created event per review (not one event per finding).
review.failed
reason values:
quorum_failure— fewer than the required number of specialists succeededrate_limit— review skipped due to rate limitstale_head— head SHA changed during executioninternal_error— see telemetry for the specific error class
Signing
Sigilix signs every webhook with HMAC-SHA256 using the secret you provided at registration:Delivery semantics
- Each event is delivered at-least-once to your endpoint
- Sigilix retries on non-2xx responses with exponential backoff: 1m, 5m, 30m, 2h, 12h
- After 5 failed retries, the delivery is marked
dead-letteredand the event is dropped - Use the
delivery_idfor idempotency on your side
Use cases
- Dashboards — feed reviews into your engineering metrics platform (Linear, Datadog, Honeycomb)
- Alerting — page on-call when a Critical finding is posted on a production service
- Compliance — log every Critical security finding to your audit trail
- CI integration — trigger downstream jobs after a review completes (e.g., post the verdict to Slack)
Read next
Endpoints
REST API for reviews and findings.
Authentication
PAT scopes for the endpoints that webhooks reference.

