Resume a replay job
POST
/v1/replays/{id}/resume
Continue a stopped or failed replay from where it stopped. It keeps its cursor and its replay_id, and within one run each (event, destination) pair is delivered once: a pair the run has already attempted — delivered, failed, retrying, or held for a paused destination — is not sent again. That is why resuming is the right move after a failure, rather than starting a fresh replay of the same window, which WOULD re-send everything.
Authorizations
apiKey
Scoped API key. Scopes are read ⊂ write ⊂ admin. A call needing more scope than the key holds returns 403 insufficient_scope.
Type
HTTP (bearer)
Parameters
Path Parameters
id*
Type
Requiredstring
Responses
The replay job, queued again.
application/json
JSON "id": "rpj_01M2Y", "endpoint": "ep_01JX9", "state": "string", "since": "string", "until": "string", "status": "string", "destinations": [ "string" ], "replay_id": "string", "stop_requested": true, "total_estimate": 0, "scanned": 0, "replayed": 0, "enqueued": 0, "skipped": 0, "excluded": 0, "resumed_from": 0, "destinations_used": [ "string" ], "error": "string", "created_at": "string", "started_at": "string", "finished_at": "string"
{
}