Skip to content
nofeb

What is Standard Webhooks?

Standard Webhooks is an open specification for sending webhooks safely: each delivery carries webhook-id, webhook-timestamp and webhook-signature headers, and the receiver verifies an HMAC signature over the id, timestamp and raw body with a shared secret, rejecting stale timestamps to stop replays.

Checked against the engine on .

How does Standard Webhooks work?

The value of a shared specification is that one verification routine works for every sender that follows it, and the failure modes are documented: verify against the raw body exactly as received, not a re-serialized JSON object; compare signatures in constant time; refuse timestamps outside a small window.

The id header doubles as an idempotency key. Senders retry on failure, so a receiver should record the ids it has processed and skip duplicates.

Verify a delivery (TypeScript)
import { verifyWebhook } from "@nofeb/sdk";
const event = await verifyWebhook(rawBody, headers, process.env.NOFEB_WEBHOOK_SECRET!);

How does nofeb use Standard Webhooks?

  • nofeb signs every webhook delivery per Standard Webhooks, retries failures and keeps a delivery log you can read. The SDKs verify signatures and refuse timestamps more than five minutes off.
  • Every subscription must name its scope (organization, pod or inbox); one without a scope is refused rather than widened, so a missing field cannot send one customer's events to another's endpoint.
  • nofeb's HTTPS hooks, which run inside the pipeline, are signed the same way.

Frequently asked questions

Why must I verify against the raw body?

The signature covers the exact bytes sent. Parsing and re-serializing JSON can reorder keys or change whitespace, and the signature then fails.

How do I handle duplicate webhook deliveries?

Store the webhook-id of each processed delivery and skip repeats. Retries reuse the id.

Status of everything on this page

Every capability named above, with its status as reconciled against the engine.

CapabilityWhat it doesStatus
Signed webhooks with required scope Standard Webhooks signatures, retries and a delivery log. Scope (organization, pod or inbox) is required, so a subscription never silently widens to everything. Shipped
HTTPS hooks in the pipeline Signed HTTPS callouts that change what happens: create or reject an inbox for an unknown recipient, accept, reject or quarantine a message before delivery, and allow, deny or hold a send, each with a timeout and a fail-open or fail-closed mode. Shipped
TypeScript and Python SDKs Official clients generated from the OpenAPI document: @nofeb/sdk for Node, Deno, Bun and edge runtimes, and nofeb for Python with sync and asyncio clients. Both chain long polls for waitForEmail, retry idempotent requests, page through lists and verify webhook signatures. Shipped