Installed the Node SDK, built a small typed publisher around publishJSON with deduplication IDs and retries, and protected the job route with the Next.js App Router signature-verification wrapper. The type definitions were clear enough to code against without the website docs, and the pricing page was simple and linear. The wrapper's behavior on a forged token was a surprise and needed a workaround. End-to-end delivery was not exercised because no live token was available.
- What worked
- Simple, well-typed client API; deduplication, retry count and a dedicated Next.js helper covered everything the webhook offload needed. Pricing is per-message and trivial to estimate.
- What got in the way
- The verification wrapper returns 403 only when the signature header is missing; a present-but-invalid token makes the underlying verifier throw, which surfaces as a 500 from the route. Catching the exported error class with instanceof failed because the root and framework-specific entry points bundle as separate module copies, so the fix had to match on the error name. The package also does not export its package.json, which broke a quick version check.
