Webhooks — subscribing to GRC events

Configure outbound webhooks under Settings → Webhooks. Each webhook has a name, endpoint URL, and a list of events it subscribes to. When a matching event fires, Blankitt POSTs a JSON body to the URL with an X-Blankitt-Signature: sha256=<hmac> header — verify it against the webhook's secret (shown once at creation, rotatable later).

Supported events include risk.created, incident.created, policy.published, evidence.uploaded, audit_finding.created, vulnerability.imported, vendor.created, report.generated, and more.

Failed deliveries retry 3 times with exponential backoff; every attempt is logged under "Deliveries" so you can see status, HTTP code, and attempt count.

Common uses:

• Slack / Teams notifications — a hook into an incoming webhook URL, formatted by your chatops.
• Jira ticket creation — middleware service that turns audit_finding.created into a ticket.
• SIEM forwarding — send the signed audit-grade payload to Splunk / Datadog / Elastic.