Skip to content

Webhook providers

Webhook providers Hooksmith verifies

Hooksmith checks the signature on each incoming webhook, drops the events you do not want, rewrites the JSON and delivers it to your endpoint with retries. Pick a provider for its exact signing rules, setup steps and an example hook.

Verify first, then transform

A webhook URL is public, so anyone can post to it. Providers prove a request is theirs with a signature, usually an HMAC of the raw body made with a secret you share. Hooksmith checks that signature against the exact bytes it received, before it stores or processes anything. A bad signature gets a 401 and never becomes an event.

After the check, a hook can skip events with conditions, rewrite the JSON with a template, and deliver the result to your endpoint. Each provider below has a preset that fills in the verification settings, so the YAML only holds your filter and your template. The details of every preset are on the docs page, and the pricing page lists plan limits.

Providers

Standard Webhooks

Standard Webhooks is an open specification for signed webhooks: three headers (webhook-id, webhook-timestamp, webhook-signature), an HMAC-SHA256 over the id, the timestamp and the raw body, and a whsec_ secret. Svix uses the same scheme with svix- header names, and so does Resend. Hooksmith verifies all of them with one verification type, and rejects timestamps more than 5 minutes off by default.

If your sender follows the spec, use the Standard Webhooks preset. For Resend, see the Resend page.

Testing against localhost

The Hooksmith desktop app for Mac tunnels stored events to a server on your machine, with the original body and the provider's signature headers, so your local verification code sees what production sees. See the download page.