When an outbound webhook fails, the questions are the same: did it go out, what did the endpoint say, and how do I recover?
We wrote a walkthrough that uses Centrali's outbound webhook views in the console for that job.
What the walkthrough covers
Create a webhook subscription and Centrali delivers signed events to your endpoint. The delivery log shows status, HTTP code, attempts and errors.
In the walkthrough you will:
- Send a signed test event to a disposable receiver and read back what it captured
- Point a second subscription at an endpoint that cannot succeed, and see the delivery enter Retrying
- Inspect the attempt so far and the pending retry, then cancel it
- Fix the endpoint, then use Replay on the cancelled delivery
A failed delivery is retried automatically. Replay is different: it creates a new delivery from the cancelled one and preserves the original in the log. With the working receiver in the walkthrough, the new delivery ends as Success / 204.
The walkthrough uses synthetic data and covers outbound delivery only. It does not cover receiving inbound webhooks or dead-letter-queue behavior.
Retry and Replay can repeat side effects
Both Retry and Replay can repeat side effects at the receiving end, so make your receiver's operations idempotent. A replay arrives with a new webhook-id and the same body, so do not deduplicate on webhook-id.
Try the walkthrough
Follow Send test deliveries, then retry and replay in the docs. You will need a Centrali workspace, curl, and console access that lets you build webhooks. New to Centrali? Start building free.
For the full reference on outbound subscriptions, deliveries and signature verification, see the Webhooks guide.
Send is one way into Centrali, a composable backend for application builders.