Resolve a review of a rail fact (operator)

Operator action that closes a review of a rail fact.

• ACKNOWLEDGE closes a review that you already analyzed. It is refused (409 TED-0060) for LEDGER_EFFECT_PENDING, because a financial effect is still not applied.
• RETRY_LEDGER_EFFECT runs the pending ledger effect again with the original key. If the ledger still does not record it, the response is 503 TED-1000 and the review stays pending.

When you resolve the review of a PENDING_STR TED that the daily close held, the next cycle of the reconciliation step releases the TED. This happens after reconciliation_due_sec (default 900 s) has passed since the TED entered PENDING_STR or since its cancellation request was recorded. For a TED that the close held, this is usually about one minute after the resolution. If the STR refuses it, the TED becomes REJECTED, or CANCELLED when a cancellation was requested, and the hold is released once. The resolution itself does not change the TED.

The service does not resend a refund that is older than the ledger idempotency window (409 TED-0060): reconcile it manually in the ledger. A review that is already resolved returns 409 TED-0060. X-Idempotency and a justification are required.

POST /v1/reconciliation/reviews/{reviewId}/resolve

cURL

acknowledge

curl --request POST \
  --url https://api.example.com/v1/reconciliation/reviews/{reviewId}/resolve \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'X-Idempotency: <x-idempotency>' \
  --data '
{
  "action": "ACKNOWLEDGE",
  "justification": "Duplicate rail fact, already reflected in the transfer."
}
'

200

{
  "action": "RETRY_LEDGER_EFFECT",
  "outcome": "COMMITTED",
  "review": {
    "createdAt": "2026-10-22T13:06:00Z",
    "detail": "Settlement confirmed by the STR, but the hold commit in the ledger is not recorded yet.",
    "eventKey": "settlement.settled",
    "id": "b8e4f0a2-3c5d-4e7f-9a1b-2c4d6e8f0a1b",
    "nuop": "87654321202610220000123",
    "occurredAt": "2026-10-22T13:05:41Z",
    "reason": "LEDGER_EFFECT_PENDING",
    "resolvedAt": "2026-10-22T13:40:00Z",
    "resolvedBy": "[e-mail]",
    "status": "RESOLVED",
    "transferId": "6f1c2b3a-4d5e-4f60-8a9b-0c1d2e3f4a5b"
  }
}

Authorizations

Authorization · string · header · required

JWT token that the Lerian Access Manager issues for your institution. Send it in Authorization: Bearer <token> on every call (except the public health probes). The tenant never comes from the body, the query, or the path. Each operation requires a role with the matching permission (see the API overview). Without it, 403 TED-0071. Missing, invalid, or expired token: 401 TED-0070.

Headers

X-TTL · integer

Replay window of the idempotency key, in seconds. Default 300 (5 minutes) when missing or invalid. Values outside 30 s to 7 days are adjusted to these limits. Only the value of the FIRST request for a key counts. A change to X-TTL on retries has no effect. Within the window, the original response is replayed byte for byte.

Required range: x >= 1

X-Idempotency · string · required

Idempotency key that the integrator creates (1 to 128 printable ASCII characters, no spaces; we recommend a UUID). Required on every operation with an effect. Send the SAME key again when you retry a call that failed because of a timeout or network error. Same key + same body returns the original response with X-Idempotency-Replayed: true and no new effect. Same key + different body responds 422 TED-0012. Same key still in processing responds 409 TED-0013 (retry after Retry-After). Missing or in the wrong format: 400 TED-0011.

X-Request-Id · string<uuid>

Correlation identifier of this request (UUID). Optional: when you omit it, or when the value is not a well-formed UUID, the platform creates a UUID and returns it in the X-Request-Id header of the response. The resolved identifier goes to the logs, spans, and audit events of this request. Keep it to open a support ticket.

Path Parameters

reviewId · string<uuid> · required

Review identifier

Body

application/json

Operator decision on a rail fact review: close it as analyzed, or re-run the pending ledger effect.

action · enum<string> · required

ACKNOWLEDGE closes the review; RETRY_LEDGER_EFFECT runs the pending ledger effect again (only LEDGER_EFFECT_PENDING).

Available options: ACKNOWLEDGE, RETRY_LEDGER_EFFECT

justification · string · required

Operator justification.

Required string length: 10 - 500

Response

200

application/json

Review resolved; review already shows the new state. If X-Idempotency-Replayed: true, this is the replay of a previous resolution.

Result of the resolution: the updated review, the action applied, and, for a re-run, the outcome.

action · enum<string> · required

Action applied.

Available options: ACKNOWLEDGE, RETRY_LEDGER_EFFECT

review · object · required

The review after the resolution.

Show child attributes

outcome · string

Result of the retry (RETRY_LEDGER_EFFECT only)