Webhooks
One alert per site, signed with your webhook’s secret.
The body
{
"id": "…",
"genre": "faille",
"le": "2026-10-21T13:41:00.000Z",
"titre": "…",
"sonde": "snd_…",
"faille": "CVE-…",
"severite": "elevee",
"exploitee": true,
"lien": "https://app.manicou.dev/…"
}The kinds
panne, retour, echeance, faille, a_verifier, ordre_sans_effet, corrigee, rappel, stack_ancienne, preuve_perdue, essai, protection.
Severity and exploitation
severite gives the vulnerability’s impact, critique, elevee, moyenne or faible. exploitee says whether it is being exploited right now, according to the CISA list or its source. Sort on exploitee first, as Manicou does. An alert about no vulnerability, a downtime for example, has null for both.
The secret
Each webhook has its own, whsec_ then 32 bytes in base64, shown only once when you add it. A new secret is drawn in its settings.
The signature
In the Standard Webhooks format, signature v1: the HMAC-SHA256 of id.timestamp.body with the secret decoded from base64. webhook-id stays the same at each attempt.
webhook-id: …
webhook-timestamp: 1792590180
webhook-signature: v1,…Verifying the address
Before the first alert, Manicou sends a signed challenge, the webhook-challenge header. Answer 2xx with webhook-challenge-response: v1, then the HMAC-SHA256 of the challenge with the key HMAC-SHA256(secret, wev-v1), in base64. This is the Standard Webhooks endpoint verification extension, and without it the webhook receives nothing.
webhook-challenge: …
webhook-challenge-response: v1,…The attempts
As long as your address does not answer 2xx: after 1, 5 and 30 minutes, 2 hours then 6 hours. Six attempts, ten seconds each, without following redirects.
Slack, Discord and Teams
They receive the same content, in the format of their incoming webhooks.