Skip to main content
POST
Repair Transfer Ledger Scope

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

Path Parameters

transferId
string<uuid>
required

The unique identifier of the transfer.

Body

application/json

The ledger that the operator asserts, the justification, and an optional evidence reference.

ledgerId
string<uuid>
required
Example:

"22222222-2222-4222-8222-222222222222"

reason
string
required
Required string length: 10 - 500
Example:

"stranded row from the pre-routing backlog; CRM ticket 8812 names this ledger"

evidenceReference
string
Maximum string length: 200
Example:

"CRM ticket 8812"

Response

Indicates that the transfer's ledger scope was repaired.

transferId
string<uuid>
Example:

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

ledgerId
string<uuid>
Example:

"22222222-2222-4222-8222-222222222222"

repairedAt
string<date-time>
Example:

"2026-09-18T09:30:00Z"