Send one delivery again, now
POST/admin/webhooks/:id/retry
Re-POSTs the stored payload to the casino's endpoint, synchronously, and answers what happened. An operator who presses this learns the verdict instead of refreshing a list.
A non-2xx is an OUTCOME, not an error: the response is 200 with
delivered: false and the status the backend answered with. The attempt is
recorded either way, attributed to the signed-in operator.
A delivery the backend already accepted is refused with 409 — there is nothing
to repair. Anything else can be re-sent, including a dead one, which is what
this button mostly exists for: on failure the delivery goes back to pending
with a fresh attempt budget.
A casino that has no webhook endpoint configured is also a 409, naming that as
the cause: it is the most common reason a delivery is sitting here unsent, and
re-sending cannot help until an endpoint exists.
Permission: webhooks.write
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 503
The verdict, and the delivery as it now stands
X-Tenant-Id is missing, or the id is not a number
No session cookie, or it expired
The role lacks webhooks.write, or the caller is not a member of this casino
No such delivery for this casino
This webhook was already delivered, or this casino has no webhook endpoint configured
No webhook sink on this instance, or it is shutting down