Skip to main content
POST
Replay TED IN Backlog

Authorizations

Authorization
string
header
required

JWT Bearer token authentication. The tenantId is derived from the bearer token or authenticated request context and is not supplied through X-Organization-Id.

Headers

X-Organization-Id
string<uuid>
required

Midaz organization scope for the request, used for downstream CRM, Fees, and Midaz calls. Required on org-scoped transfer routes in every deployment mode; a missing or non-UUID value returns 400. This is not the tenant identifier — tenantId is derived from the bearer JWT or authenticated context, never from this header. Background workers (TED IN poller, reconciliation) have no request header and, in single-tenant mode, fall back to the deployment's ORGANIZATION_ID env.

X-Idempotency
string
required

Required idempotency key for safe retries. Use a UUID v4 or unique business identifier. If the same key is sent again and the original request was already processed, the cached response is returned.

See Retries and idempotency for details.

Maximum string length: 255

Response

Indicates that the replay pass completed. The outcome field reports the cycle result and replayed is the number of backlog rows reprocessed.

outcome
string
required

The replay outcome, for example success, empty, or held. held means that the pass replayed nothing and left at least one inbound credit held.

Example:

"success"

replayed
integer
required

Number of persisted backlog rows reprocessed during this pass.

Required range: x >= 0
Example:

2

held
integer
required

The number of inbound credits that this pass left held, because no ledger binding covers them. They are neither credited nor failed.

Required range: x >= 0
Example:

0

claimed
integer
required

The number of messages that another process is already carrying, so this pass left them alone. They are replayed when that claim expires.

Required range: x >= 0
Example:

0