Webhooks
Signed events, retries, idempotent processing — how to consume Baynoy webhooks safely.
Not live yet — api.baynoy.com does not resolve, so the examples below will not run today. They describe the contract we are building to, and the shapes on this page may still change.
Signed, at-least-once
Each delivery carries Baynoy-Signature: t=<unix seconds>,v1=<hex HMAC-SHA256 of "<t>.<raw body>"> made with the endpoint's whsec_ secret. Deliveries are at least once with backoff. Verify the signature, and that t is recent, before trusting anything.
Process idempotently
Store the event id and skip duplicates; never treat delivery order as meaningful. Respond 2xx quickly and do real work asynchronously — slow endpoints get their connection closed.
Delivery log
Developers → Webhooks shows every delivery with its attempt number and response code, so a failing endpoint is visible rather than silent.