Delivery behaviour
Read from the vendor's own documentation, last checked 2026-08-06. Where the vendor states no number, this table carries none.
| Response budget | not published by the vendor |
|---|---|
| Retry | not published by the vendor |
| Gives up | not published by the vendor |
Signature
Verified against a working verifier proven by a test suite, not read from documentation. Last verified 2026-08-20.
| Algorithm | HMAC-SHA256 |
|---|---|
| Signed payload | raw body |
| Encoding | hex |
| Header | x-signature + x-event-name |
| Tolerance | none enforced |
Verify it
The raw request body, byte for byte, before any JSON parsing. Every scheme on this page breaks the moment a framework re-serializes the payload.
const crypto = require("node:crypto");
// hex(HMAC-SHA256(signing secret, raw body)); event name rides x-event-name
const expected = crypto
.createHmac("sha256", signingSecret)
.update(rawBody)
.digest("hex");
const valid = crypto.timingSafeEqual(
Buffer.from(req.headers["x-signature"]),
Buffer.from(expected),
);What bites
No timeout, retry schedule, or disable behaviour is published. Plan for the pessimistic case: treat every delivery as possibly the only one, and keep your own log of what arrived.
Read more
AnyHook sits in front of endpoints that receive from Lemon Squeezy: it answers inside the budget above, retries on its own schedule when your server is down, and keeps every event replayable. Change one URL, keep your code.