Webhooks
Updated 15 Nov 2026
Webhooks let List79 tell your server the moment something happens: a new request, a vote, a comment, a status change. Use them to post to Slack, update your CRM, or tell the customer who asked.
Add an endpoint
- Open your product's Keys and portal page and choose Manage webhooks. Owners and admins can do this.
- Enter your endpoint's URL. It must start with
https://and be on the public internet. - Choose the events it should get: all of them (including ones added later), or a few.
- Choose Add endpoint, copy its signing secret into your server, and choose Send test event.
A product can have up to 10 endpoints. Test mode has its own; see Test mode.
Events
| Event | When |
|---|---|
request.created | A request is created, from the widget, portal, API or your team. |
request.status_changed | A request's status changes. Includes previousStatus and the public reason, if any. |
request.merged | A request is merged into another as a duplicate. |
vote.created | Someone votes for a request. |
vote.deleted | Someone takes their vote back. |
comment.created | Someone, or your team, comments on a request. |
webhook.test | You chose Send test event. |
What List79 sends
A POST with a JSON body:
{
"id": "evt_01a1dcea…",
"type": "request.status_changed",
"createdAt": "2026-11-15T09:30:00Z",
"livemode": true,
"product": { "slug": "acme", "name": "Acme" },
"data": {
"request": { "number": 12, "title": "Export to CSV", "status": "shipped", "votes": 48, … },
"previousStatus": "inProgress",
"reason": null
}
}
The request has the same fields as in the API. Vote events add the user, and comment events add the comment. Email addresses are never included.
Headers:
List79-Signature: the signature, below.List79-Event-Id: the event's ID, the same on every retry. Use it to skip events you've already handled.List79-Event-TypeandList79-Delivery-Id.
Check the signature
So you know a call really came from List79, check its signature before trusting it. The header looks like t=1731663000,v1=5f2c…:
- Take
t(a Unix time) andv1from the header. - Compute an HMAC-SHA256, in hex, of
t, a full stop and the raw request body, using your endpoint's signing secret. - Compare it with
v1using a constant-time comparison, and reject calls whosetis more than 5 minutes old.
import crypto from "node:crypto";
function verify(header, rawBody, secret) {
const { t, v1 } = Object.fromEntries(header.split(",").map(p => p.split("=")));
const mac = crypto.createHmac("sha256", secret).update(`${t}.${rawBody}`).digest("hex");
const fresh = Math.abs(Date.now() / 1000 - Number(t)) < 300;
return fresh && mac.length === v1.length && crypto.timingSafeEqual(Buffer.from(mac), Buffer.from(v1));
}
Use the raw body exactly as received: parsing and re-encoding the JSON changes it. If the secret leaks, choose Make a new secret on the endpoint's page; deliveries are signed with the new one at once.
Answering, retries and switching off
- Answer with any
2xxstatus within 10 seconds. Do slow work after you've answered. - Anything else is retried after 1 minute, 5 minutes, 30 minutes, then 2, 5, 10 and 10 hours: 8 attempts over about a day.
- An endpoint whose deliveries have failed for 3 days with no success is switched off, and your account's owners and admins get an email. Fix it, then choose Switch on.
- Events can occasionally arrive more than once or out of order, so use the event ID and the request's
updatedAt.
The delivery log
Each endpoint's page lists its last 50 deliveries from the past 30 days: whether each was delivered, the HTTP status, how long it took, the attempts so far and the next retry. Open one to see the exact payload and the start of your server's answer, and choose Send again to resend it with the same event ID.