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
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!
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
[dead]