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

Events are signed (per-endpoint secret, timestamped signature with a tolerance window) and delivered at least once with exponential backoff. Verify the signature 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.

Replay

The dashboard shows every delivery with response code and duration, and lets you replay an event with its original id — a replay never creates a new event.

← Docs