post · webhooks:write
Replay a delivery
Replay a delivery
Write
REST
post
/api/v1/webhooks/deliveries/{id}/replaycurl "https://herculeradar.com/api/v1/webhooks/deliveries/:id/replay" \ --request POST \ --header "Authorization: Bearer hr_live_…"
MCP
Tool name replay_webhook_delivery. It takes the same input and returns the same { data, meta } envelope as REST, because both call the same function.
POST the original payload again. Does not invent a new mention.
Parameters
| idrequired | string | Delivery id |
Response
{
"data": {
"replayed": true
},
"meta": {
"capability": "replay_webhook_delivery",
"requestId": "req_9f2b4a8c1d0e",
"idempotencyReplayed": false,
"docs": "https://herculeradar.com/docs/reference/replay_webhook_delivery"
}
}Authorization
Requires the webhooks:write scope. A credential without it gets 403 FORBIDDEN. Resources in projects the credential cannot reach answer 404 NOT_FOUND rather than 403, so ids cannot be probed across tenants.
Send an Idempotency-Key header. A completed response is replayed for 24 hours, so a retry after a timeout cannot create a duplicate.