Skip to main content
POST
/
v1
/
events
/
{id}
/
retry
Retry a failed event
curl --request POST \
  --url https://api.scrip.dev/v1/events/{id}/retry \
  --header 'X-API-Key: <api-key>'
{
  "event_id": "9d5f7d4a-18f8-4b73-9e26-7b5a0b5bb0d1",
  "message": "Event queued for retry",
  "previous_error": "action CREDIT failed: amount exceeds asset scale",
  "previous_status": "FAILED",
  "status": "PENDING"
}
Retries an event that is in FAILED status. The retry count is reset and the event is returned to PENDING for a fresh set of 5 processing attempts with exponential backoff (2s, 4s, 8s, 16s, 32s). Only events with a FAILED status can be retried. Events in PENDING, PROCESSING, or COMPLETED status will be rejected. This is useful after fixing an underlying issue (such as a misconfigured rule or a missing participant) that caused the original failure.
For usage patterns and examples, see the Event Processing guide.

Authorizations

​
X-API-Key
string
header
required

API key passed in the X-API-Key header.

Path Parameters

​
id
string<uuid>
required

Event ID

Response

Event queued for retry

​
event_id
string<uuid>

ID of the event being retried

Example:

"9d5f7d4a-18f8-4b73-9e26-7b5a0b5bb0d1"

​
message
string

Confirmation message

Example:

"Event queued for retry"

​
previous_error
string

Error message from the previous failed attempt

Example:

"action CREDIT failed: amount exceeds asset scale"

​
previous_status
string

Status the event was in before retry (always FAILED)

Example:

"FAILED"

​
status
string

New status after retry (always PENDING)

Example:

"PENDING"