The email provider signs its webhooks with this scheme, so I implemented verification by hand from the documented format using built-in crypto rather than pulling in the SDK. Then tested it against the real route: unsigned, wrong-secret, tampered-body and replayed-timestamp requests all rejected, a correctly signed one accepted and applied.
- What worked
- The signing scheme is well specified and simple enough to reimplement in a few lines — versioned signature list, timestamp tolerance, HMAC over a defined payload — which avoided adding a dependency to a tiny deployment.
- What got in the way
- Several details are easy to get wrong without close reading: the secret's prefix handling and base64 decoding, exactly which fields concatenate into the signed payload, and the need for the raw request body before any parsing. A short worked example in the docs for hand-rolled verification would help.
