API Documentation

Signed webhooks

Starter, Pro, and Business users can add HTTPS endpoints under Dashboard → Signed webhooks. A webhook receives email.received only for inboxes created with one of that account’s API keys. Use Test to send a webhook.test event.

Payload

{ "id": "event-uuid", "event": "email.received", "created_at": "2026-07-18T12:00:00.000Z", "data": { "id": "email-uuid", "subject": "Verification code" } }

Verify the signature

Read the raw request body before parsing JSON. Compute HMAC-SHA256 over timestamp + "." + rawBody with the signing secret shown once when the endpoint is created. Compare it with the hex value after v1= in X-InboxBurn-Signature and reject timestamps older than five minutes.

import crypto from "node:crypto"; export function verifyInboxBurn(rawBody, headers, secret) { const timestamp = headers["x-inboxburn-timestamp"]; const received = headers["x-inboxburn-signature"]?.replace(/^v1=/, ""); if (!timestamp || !received || Math.abs(Date.now() / 1000 - Number(timestamp)) > 300) return false; const expected = crypto.createHmac("sha256", secret) .update(timestamp + "." + rawBody).digest("hex"); return expected.length === received.length && crypto.timingSafeEqual(Buffer.from(expected, "hex"), Buffer.from(received, "hex")); }

Delivery rules

Endpoints must use public HTTPS without credentials or a custom port. Private and unresolved IP addresses are rejected. Requests time out after 10 seconds and redirects are not followed. Failed deliveries are retried by a background worker. The latest 50 attempts, HTTP status, and errors are visible under webhook History.

Use Rotate secret in the Dashboard if a signing secret may have leaked. The replacement is shown only once and new deliveries use it immediately; update your receiver before relying on later events.

Plan limits: Starter 1 endpoint, Pro 3 endpoints, Business 10 endpoints. Signing secrets cannot be shown again; delete and recreate the endpoint if a secret is lost.