Replay TED IN Backlog

Use this endpoint to force one immediate replay pass over persisted, unprocessed JD inbound messages for the current tenant. Unlike /ted-in/poll, this route does not read JD’s destructive queue — it only reprocesses durable backlog rows already persisted locally.

Use the X-Idempotency header for guaranteed deduplication.

POST /v1/transfers/ted-in/replay

Replay TED IN Backlog

cURL

curl --request POST \
  --url https://api.example.com/v1/transfers/ted-in/replay \
  --header 'Authorization: Bearer <token>' \
  --header 'X-Idempotency: <x-idempotency>' \
  --header 'X-Organization-Id: <x-organization-id>'

200

{
  "outcome": "success",
  "replayed": 2,
  "held": 0,
  "claimed": 0
}

Autorizaciones

BearerAuthOAuth2ClientCredentialsOAuth2Password

Authorization · string · header · requerido

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

Scopes

api · OAuth2ClientCredentials

TED transfer API access

api · OAuth2Password

TED transfer API access

Encabezados

X-Organization-Id · string<uuid> · requerido

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 · requerido

Required idempotency key for safe retries. Use a UUID v4 or a unique business identifier, made of letters, digits, ., _, and -. 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

Pattern: ^[a-zA-Z0-9._-]+$

Respuesta

200

application/json

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

outcome · string · requerido

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

Ejemplo:

"success"

replayed · integer · requerido

Number of persisted backlog rows reprocessed during this pass.

Rango requerido: x >= 0

Ejemplo:

2

held · integer · requerido

The number of inbound credits that this pass left held on purpose. They are neither credited nor failed.

Rango requerido: x >= 0

Ejemplo:

0

claimed · integer · requerido

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

Rango requerido: x >= 0

Ejemplo:

0