X4 Outbound Webhooks
Events pushed, signed, and replayable.
Polling an API to find out what happened is a tax on both of us. Subscribe to the events you care about and they arrive signed, with retries that back off and a queue holding anything your endpoint refused while it was down.
Signed payloadsRetries with backoffReplay and DLQ
How a delivery behaves.
PropertyWhat it means for your endpoint
SignatureEvery payload is signed. Verify it before you act on it, and reject anything that does not match.An unsigned webhook endpoint is an unauthenticated write path into your system wearing a helpful name.
At least onceYou may receive the same event twice. Each carries a stable event id, so dedupe on it.We would rather deliver twice than lose one, and the id makes the first choice safe.
OrderingNot guaranteed across event types. Each event carries the sequence of the record it describes, so you can order what matters.
RetriesExponential backoff on any non-2xx, for a bounded window, then the event moves to the dead-letter queue.
ReplayAnything in the queue can be replayed once your endpoint is healthy, without us reconstructing it by hand.
What it will not do.
The failure modes worth knowing before your endpoint is the one timing out.
- It will not drop an event silently. A delivery that exhausts its retries lands in the dead-letter queue rather than disappearing.
- It will not send unsigned. There is no configuration that turns signing off, because the first thing anyone disables under time pressure is the thing that was optional.
- It will not treat your 500 as an acknowledgement. Only a 2xx stops the retries.
- It will not block the ledger. Delivery is asynchronous, so an endpoint that is down slows nothing down on our side or yours.
Point it at a sandbox endpoint first.
The simulators can fire the awkward events on demand, including the ones you hope never arrive.