Webhooks
How to set up webhook endpoints to receive real-time incident events in your own systems.
Webhooks let you receive real-time event notifications from Revnoxa in your own systems - dashboards, Slack bots, internal ticketing tools, or custom workflows.
What webhooks deliver
Every time a significant event happens in Revnoxa - an incident is created, acknowledged, resolved, an approval is approved or rejected, a hijacker threat is detected - Revnoxa can send a JSON payload to any HTTPS endpoint you configure.
Setting up a webhook
Go to Settings > Webhooks and click "Add Endpoint." Enter the HTTPS URL where you want events delivered. Select the event types you want to receive - you can subscribe to all events or only specific ones (e.g., incident.created, incident.resolved, approval.approved). Click Save.
Revnoxa immediately sends a test event to verify that your endpoint is reachable. If it responds with a 2xx status, the webhook is active.
Security - request signing
Every webhook request includes an X-Revnoxa-Signature header - an HMAC-SHA256 signature of the request body using your endpoint's secret key. Validate this signature on your server to confirm the request came from Revnoxa and was not tampered with. The secret key is shown once when you create the endpoint - store it securely. You can rotate it at any time from the webhook settings.
Delivery and retries
Revnoxa expects your endpoint to respond with a 2xx status within 10 seconds. If delivery fails - timeout, non-2xx response, or network error - Revnoxa retries with exponential backoff: immediately, then after 30 seconds, 5 minutes, 30 minutes, and 2 hours. After 5 failed attempts, the delivery is marked as failed.
Viewing delivery history
Go to Settings > Webhooks and click on any endpoint to see its delivery history. Each entry shows the event type, delivery timestamp, HTTP status code, and response body - useful for debugging integration issues.
Rotating the secret
If your endpoint secret is ever compromised, click "Rotate Secret" on the endpoint page. A new secret is generated immediately and all subsequent requests will use the new signature.