post
https://api.lirium-sandbox.com/v1/webhooks/events//resend
Resend a webhook event
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…
Manually trigger a resend of a specific webhook event to its subscription endpoint.
Request
POST /webhooks/events/{event_id}/resend
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
event_id | string | Yes | The ID of the event to resend. Obtain it from Search Events. |
Only finished events can be resentThe event must be in state
completedorerror. Resending an event that is stillpendingreturns a400with error codeinvalid_event_state.
Example Request
POST /webhooks/events/2/resendExample Response
{
"id": "2",
"created_at": "2025-01-05T12:00:30.000000+00:00",
"delivery_url": "https://partner.example.com/webhooks",
"delivery_tries": 0
}Response Fields
| Field | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Unique event identifier. |
created_at | timestamp | Yes | When the event was originally created. |
delivery_url | string | Yes | The subscription URL the event will be delivered to. |
delivery_tries | integer | Yes | Number of delivery attempts made before this resend. |
Nostatein the responseThe event is moved to an internal queue for redelivery, so the
statefield returned by Search Events is not included in this response. Call Search Events afterwards to check the outcome.
Errors
| Status | Error code | Description |
|---|---|---|
| 400 | invalid_event_state | The event is not in completed or error state. |
| 404 | not_found | No event with that ID exists for your Partner. |
Use Cases
- Recovering from temporary endpoint failures
- Debugging webhook integration issues
- Replaying events after fixing your webhook handler
Notes
- The event payload will be identical to the original delivery
- A new
X-JWT-SIGNATUREwill be generated with a current timestamp - The resent event counts as a new delivery attempt