Retry Transfer Reconciliation

Use this endpoint to return an outbound TED parked in manual review to the reconciliation queue, so the worker queries its settlement again. No transfer is re-sent and no hold is touched: only the reconciliation state moves back to AWAITING, with a zeroed attempt counter. The return of a TED IN cannot be sent back to the queue. The operator reason is required and is recorded in the audit trail.

POST /v1/transfers/{transferId}/reconciliation/retry

Retry Transfer Reconciliation

cURL

curl --request POST \
  --url https://api.example.com/v1/transfers/{transferId}/reconciliation/retry \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'X-Idempotency: <x-idempotency>' \
  --header 'X-Organization-Id: <x-organization-id>' \
  --data '
{
  "reason": "JD cabine confirms the settlement; requeueing for a fresh query"
}
'

200

{
  "transferId": "770e8400-e29b-41d4-a716-446655440003",
  "reconciliationStatus": "AWAITING",
  "requeuedAt": "2026-08-28T15:04:05Z"
}

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._-]+$

Parámetros de ruta

transferId · string<uuid> · requerido

The unique identifier of the transfer.

Cuerpo

application/json

Operator justification for the requeue.

reason · string · requerido

Maximum string length: 500

Ejemplo:

"JD cabine confirms the settlement; requeueing for a fresh query"

Respuesta

200

application/json

Indicates that the transfer returned to the reconciliation queue.

transferId · string<uuid>

Ejemplo:

"770e8400-e29b-41d4-a716-446655440003"

reconciliationStatus · string

Ejemplo:

"AWAITING"

requeuedAt · string<date-time>

Ejemplo:

"2026-08-28T15:04:05Z"