Skip to main content

Send test results to your own systems with Webhooks

Configure outbound webhooks, verify signatures, and pick the events that matter.

J
Written by Jakka Pranav swaroop Naidu

Add a webhook endpoint

  1. Open the project Integrations page and click Connect Webhook.

  2. Enter a Webhook Name (any label that helps you identify it later).

  3. Enter the Webhook URL where Jakka should POST events.

  4. Optionally enter a Secret. When provided, Jakka signs every payload with HMAC-SHA256 and includes X-Webhook-Signature and X-Webhook-Timestamp headers.

  5. Pick the events to subscribe to (see below).

  6. Click Add Webhook.

Available events

  • Scan completed (default on): fires when a test run finishes.

  • Critical issues found (default on): fires when critical-severity issues are detected.

  • Health score regression: fires when health score drops significantly.

  • Uptime alerts: fires when uptime monitoring detects issues.

  • Issue resolved: fires when an issue is marked Fixed.

Verify signatures

When you set a Secret, every webhook delivery includes two headers:

X-Webhook-Signature: <hex-encoded HMAC-SHA256 of the raw body using your secret>

X-Webhook-Timestamp: <unix epoch seconds when Jakka generated the request>

Recompute the HMAC on your end and compare. Reject requests where the timestamp is more than 5 minutes old to mitigate replay.

Read the Delivery Logs

The Delivery Logs page (top right of the Integrations screen) shows every webhook delivery: status code, retry count, payload preview, and a replay action. Failed deliveries auto-retry with backoff.

Related articles

Did this answer your question?