Webhooks and alert channels
Send events to your own systems with a signed JSON webhook, or straight to Slack, Microsoft Teams, Discord or PagerDuty.
Destinations
| Type | Receives | Notes |
|---|---|---|
| Webhook (JSON) | 15 events | A signed JSON envelope for your own code. Gets every event. |
| Slack | 7 events | A formatted message with a colored status and a link back to the app. |
| Microsoft Teams | 7 events | A formatted message with a colored status and a link back to the app. |
| Discord | 7 events | A formatted message with a colored status and a link back to the app. |
| PagerDuty | 2 events | Pages on downtime (and resolves on recovery) and on new critical findings. Needs a PagerDuty Events API v2 integration key and a region, US or EU. |
A workspace can have up to ten destinations. Each can be switched off without deleting it. URLs must point at public addresses, not private networks. Chat URLs carry their own credential, so the app shows only the start and last characters.
Events
| Event | Meaning | Chat channels |
|---|---|---|
Search finished run.completed | A long-running search or playbook you started (30 seconds or more), or one of your scheduled re-runs, finished. | JSON only |
Search failed run.failed | A search or playbook you started failed. | JSON only |
New watch hits watch.hits | A watch you created or follow collected new items. | JSON only |
Teammate joined member.joined | Someone accepted an invite to your organization (admins). | JSON only |
Access requested access.requested | Someone asked to join your organization (admins). | JSON only |
Exposure changes exposure.findings | A scan of a monitored domain found new issues or assets, or confirmed issues are fixed. | Yes, and PagerDuty |
Domain scan failed exposure.scan_failed | A scheduled scan of a monitored domain could not finish. | Yes |
Downtime alerts uptime.incident | A monitor went down or recovered. | Yes, and PagerDuty |
Monitor suggestions uptime.suggestions | A domain scan found public services that aren't monitored yet. | JSON only |
Monthly report report.monthly | Last month's security and uptime report is ready (admins). | Yes |
Payment problems billing.payment_failed | A subscription payment failed and needs a new card (admins). | JSON only |
Leaked credentials credentials.exposed | A staff address turned up in a new breach, or an infostealer infection was found for one of your domains. | Yes |
Email spoofing alerts dmarc.alert | DMARC reports show someone sending mail as your domain, or a legitimate sender failing authentication. | Yes |
Compliance answers due compliance.attestation_due | Self-attested compliance answers are about to expire and need confirming again (admins). | JSON only |
Dependency advisories dependencies.advisories | A repository scan found new critical or high advisories, or an accepted risk expired and reopened (admins). | Yes |
A test message from the app sends the event ping.
The JSON envelope
{
"id": "evt_…",
"event": "uptime.incident",
"createdAt": "2026-11-18T14:03:21.000Z",
"organizationId": "…",
"data": { }
}data depends on the event. Uptime incidents include the monitor and the incident (with event of opened or resolved). Exposure events include the domain, the scan, and lists of opened, reopened and resolved findings plus newAssets. Credential and DMARC events include the domain and the findings that just opened. Dependency events include the repository and the advisories that opened.
Verifying signatures
JSON webhooks carry a header X-Raddiamond-Signature of the form t=<unix seconds>,v1=<hex>. The value is an HMAC-SHA256, keyed with your whsec_ secret, of the timestamp, a dot, and the raw request body. Reject anything more than five minutes old. The secret is shown once when you create the webhook, and you can rotate it later.
import { createHmac, timingSafeEqual } from "node:crypto";
export function verify(secret, header, rawBody, toleranceSec = 300) {
const parts = Object.fromEntries(header.split(",").map((p) => p.split("=")));
const t = Number(parts.t);
if (!Number.isFinite(t) || !parts.v1) return false;
if (Math.abs(Date.now() / 1000 - t) > toleranceSec) return false;
const expected = createHmac("sha256", secret).update(t + "." + rawBody).digest();
const given = Buffer.from(parts.v1, "hex");
return given.length === expected.length && timingSafeEqual(given, expected);
}Delivery and retries
Any non-success response or timeout is retried, up to 6 attempts in total. The wait before each retry is: 1 min, 5 min, 30 min, 2 h, 6 h. Return a 2xx status quickly and do slow work afterwards. Re-enabling a disabled webhook resets its failure count.
The delivery log shows recent attempts for each destination, newest first. Open one to see what was sent, and redeliver it by hand if you fixed your endpoint.
Setting one up
- Open Settings, Webhooks and choose a type.
- Paste the URL (or the PagerDuty key), pick the events and add a short description.
- Press Send test to check it works.
- For JSON, copy the secret now. It is shown once.
Anyone can also choose how they personally hear about events in notification preferences.
API
| Method | Path | Role | What it does |
|---|---|---|---|
GET | /api/orgs/:orgId/webhooks | admin | List destinations and the events available. |
POST | /api/orgs/:orgId/webhooks | admin | Body: format, url (or routingKey and region), events, description, enabled. Returns the secret once for JSON. |
PATCH | /api/orgs/:orgId/webhooks/:webhookId | admin | Change url, events, description or enabled. |
DELETE | /api/orgs/:orgId/webhooks/:webhookId | admin | Delete. |
POST | /api/orgs/:orgId/webhooks/:webhookId/rotate-secret | admin | JSON only. Returns a new secret. |
POST | /api/orgs/:orgId/webhooks/:webhookId/test | admin | Send a ping. |
GET | /api/orgs/:orgId/webhooks/:webhookId/deliveries | admin | Recent deliveries. Query: limit up to 100. |
POST | /api/orgs/:orgId/webhooks/:webhookId/deliveries/:deliveryId/redeliver | admin | Send a delivery again. |