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"
}

Documentation Index

Fetch the complete documentation index at: https://docs.scrip.dev/llms.txt

Use this file to discover all available pages before exploring further.

Requeues a FAILED event for reprocessing. The event is returned to PENDING status for a fresh set of processing attempts with exponential backoff. Only events in FAILED status can be retried. Events in any other status (RECEIVED, PENDING, PROCESSING, COMPLETED) return 409 Conflict. This is useful after fixing the 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"