Hacker News new | ask | show | jobs
Show HN: I got tired of rewriting webhook verification for every provider (tern.hookflo.com)
4 points by ontern 112 days ago
Every webhook provider has a different signature algorithm and header format and you end up rewriting the same verification boilerplate for each one. Tern absorbs that pain.

Zero-dependency TypeScript SDK. Handles signature verification for Stripe, Polar, Clerk, Shopify, Sentry, Grafana and 15+ more. Works with Express, Next.js and Cloudflare Workers.

Also now Tern opens source supports complete inbound webhook event reliability layer including Queuing, retries, deduplication, replay, dead letter queue and Slack/Discord alerting — all opt-in,
1 comments
tasn 112 days ago
Tip: if you implemented support for Clerk, you also support all the rest of Svix customers, and compatible with https://www.standardwebhooks.com/

So you support many more than you realize!

link
ontern 112 days ago
thank you for calling this out. Tern does implement the Svix/Standard Webhooks format internally the svix-style payload ({id}.{timestamp}.{body}) and header conventions are handled as a first-class config in the SignatureConfig type, so yes, any Standard Webhooks compatible provider works out of the box. there is custom config in which you can choose algorithm, signature header, signature format... covering all types of svix style webhooks

Will make sure this is more visible in the docs. Thanks for the tip

link