> ## Documentation Index > Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt > Use this file to discover all available pages before exploring further. # List pending rail fact reviews (operator) > Lists, oldest first, the `PENDING` reviews of rail (STR) facts that need an operator decision: facts that arrived with no matching transfer, facts with a contradictory state, or facts whose ledger effect stayed pending. Filter by `reason`, `transfer_id`, or `nuop`. `NUM_CTRL_STR_UNUSABLE` reviews have no associated transfer, and you can only find them by `nuop`. Cursor pagination (`next_cursor`). This list only moves forward. Each review has `detail` in operations language and `eventKey`, the key of the event that created it. Resolve it with `POST /v1/reconciliation/reviews/{reviewId}/resolve`. ## OpenAPI ````yaml /es/openapi/v3-current/ted-lerian.yaml get /v1/reconciliation/reviews openapi: 3.1.0 info: description: >- API of **TED Lerian**, the interface over Lerian SPB. Your institution uses it to send TEDs, make internal transfers, track incoming TEDs, and operate returns, queues, and policy on its Midaz ledger. The [API overview](/es/reference/interfaces/ted-lerian/ted-lerian-api-overview) gives the concepts, the roles, and the conventions. title: TED Lerian API version: v1.0.0 servers: - url: https://api.example.com description: >- Replace the example host with the URL provided during environment onboarding. security: - BearerAuth: [] tags: - description: >- Outgoing TEDs and internal transfers: fee quote, creation, query, timeline, and cancellation. Every integration starts here. name: Transfers - description: >- Incoming TEDs from other institutions: query, timeline, and operator actions (full return and manual review resolution). name: Incoming Transfers - description: >- STR participant list, to resolve COMPE code ↔ ISPB and validate the destination bank before you create a transfer. name: Participants - description: >- Back office: operations queue, inconsistency findings between the ledger and the STR, reviews of rail facts, held returns, and manual unblock with evidence. name: Reconciliation - description: >- Operations dashboard: daily aggregates, regulatory deadlines (30/60/60 min), and the closing balance that the STR reported. name: Operations - description: >- Institution configuration (editor): operating window and cut-off, usage limits, holiday calendar, and ISPB → organization bindings. name: Policy paths: /v1/reconciliation/reviews: get: tags: - Reconciliation summary: List pending rail fact reviews (operator) description: >- Lists, oldest first, the `PENDING` reviews of rail (STR) facts that need an operator decision: facts that arrived with no matching transfer, facts with a contradictory state, or facts whose ledger effect stayed pending. Filter by `reason`, `transfer_id`, or `nuop`. `NUM_CTRL_STR_UNUSABLE` reviews have no associated transfer, and you can only find them by `nuop`. Cursor pagination (`next_cursor`). This list only moves forward. Each review has `detail` in operations language and `eventKey`, the key of the event that created it. Resolve it with `POST /v1/reconciliation/reviews/{reviewId}/resolve`. operationId: listReconciliationReviews parameters: - description: Review reason explode: false in: query name: reason schema: description: Review reason enum: - EMPTY_SIT_LANC_STR - UNKNOWN_SIT_LANC_STR - UNHANDLED_FACT_KIND - NUM_CTRL_STR_UNUSABLE - TRANSFER_NOT_FOUND - AMBIGUOUS_CORRELATION - UNEXPECTED_SOURCE_STATE - TERMINAL_CONTRADICTION - LEDGER_EFFECT_PENDING - RETURN_NOT_APPLICABLE type: string - description: Related transfer (UUID) explode: false in: query name: transfer_id schema: description: Related transfer (UUID) format: uuid type: string - description: >- NumCtrlIF (23 digits) — NUM_CTRL_STR_UNUSABLE reviews have no associated transfer and can only be found by this value explode: false in: query name: nuop schema: description: >- NumCtrlIF (23 digits) — NUM_CTRL_STR_UNUSABLE reviews have no associated transfer and can only be found by this value pattern: ^[0-9]{23}$ type: string - description: Maximum items per page explode: false in: query name: limit schema: default: 20 description: Maximum items per page format: int64 maximum: 100 minimum: 1 type: integer - description: Opaque cursor returned in next_cursor explode: false in: query name: cursor schema: description: Opaque cursor returned in next_cursor maxLength: 512 type: string - $ref: '#/components/parameters/XRequestId' responses: '200': content: application/json: example: items: - 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 status: PENDING transferId: 6f1c2b3a-4d5e-4f60-8a9b-0c1d2e3f4a5b limit: 20 next_cursor: null schema: $ref: '#/components/schemas/RailFactReviewPageDTO' description: Page of pending reviews, from oldest to newest. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' '400': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: >- Invalid query parameter: cursor, date range, status, or filter in the wrong format (`TED-0001`). headers: X-Request-Id: $ref: '#/components/headers/XRequestId' '401': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: 'Not authenticated: token missing, invalid, or expired (`TED-0070`).' headers: X-Request-Id: $ref: '#/components/headers/XRequestId' '403': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: >- No permission: the token's role does not authorize this action, or the product license is not valid for the organization (`TED-0071`). headers: X-Request-Id: $ref: '#/components/headers/XRequestId' '422': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: >- Parameter outside the declared format (for example, a `date` that is not YYYY-MM-DD): framework validation, with no TED code. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' '500': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: >- Unexpected failure (`TED-9000`). If it continues, contact support and give the `X-Request-Id` of the response. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' '503': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Institution configuration missing (`TED-0080`). headers: X-Request-Id: $ref: '#/components/headers/XRequestId' components: parameters: XRequestId: description: >- 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. in: header name: X-Request-Id schema: format: uuid type: string schemas: RailFactReviewPageDTO: additionalProperties: false description: >- Page of rail fact reviews, from oldest to newest, with cursor pagination. properties: items: description: Reviews on the page. items: $ref: '#/components/schemas/RailFactReviewResponse' type: array limit: description: Actual page size, already limited to the contract maximum. format: int64 type: integer next_cursor: description: Token of the next page; null when there is none. type: - string - 'null' required: - items - limit - next_cursor type: object Detail: additionalProperties: true description: >- Standard error body (RFC 9457, `application/problem+json`) for every `/v1` operation. Use `code` (TED-NNNN) to handle the error in code, `detail` for the readable message, and `errors` for the invalid fields of a 422. The `X-Request-Id` of the response identifies the occurrence for support. properties: code: description: >- Stable, machine-readable domain error code scoped to the emitting service (format: -NNNN). type: string detail: description: >- A human-readable explanation specific to this occurrence of the problem. examples: - Property foo is required but is missing. type: string errors: description: Optional list of individual error details items: $ref: '#/components/schemas/ErrorDetail' type: - array - 'null' instance: description: >- A URI reference that identifies the specific occurrence of the problem. examples: - https://example.com/error-log/abc123 format: uri type: string status: description: HTTP status code examples: - 400 format: int64 type: integer title: description: >- A short, human-readable summary of the problem type. This value should not change between occurrences of the error. examples: - Bad Request type: string type: default: about:blank description: A URI reference to human-readable documentation for the error. examples: - https://example.com/errors/example format: uri type: string upstream: $ref: '#/components/schemas/Upstream' description: >- RFC 9457 extension member: the error a proxied third-party provider reported. Absent unless the emitting service explicitly surfaced one. type: object RailFactReviewResponse: additionalProperties: false description: >- Pending review of a fact received from the rail (STR) that the system could not apply on its own. Examples: a fact without a matching transfer, or a ledger effect that stayed pending. properties: createdAt: description: Timestamp (UTC) when the review was opened. format: date-time type: string detail: description: Description of the review for the operator type: string eventKey: description: Key of the event that created the review type: string id: description: Review identifier format: uuid type: string nuop: description: NumCtrlIF of the fact, when known type: string occurredAt: description: Time (UTC) of the fact in the rail. format: date-time type: string reason: description: Review reason type: string resolvedAt: description: Time (UTC) of the resolution. format: date-time type: string resolvedBy: description: Operator who resolved the review type: string status: description: PENDING waits for an operator decision; RESOLVED is already closed. enum: - PENDING - RESOLVED type: string transferId: description: Associated transfer. Missing when the fact was not correlated format: uuid type: string required: - id - status - reason - eventKey - detail - occurredAt - createdAt type: object ErrorDetail: additionalProperties: false description: >- An invalid field inside a validation error: where it is (`location`), what is wrong (`message`), and the value received. properties: location: description: >- Where the error occurred, e.g. 'body.items[3].tags' or 'path.thing-id' type: string message: description: Error message text type: string value: description: The value at the given location type: object Upstream: additionalProperties: false description: >- Error reported by an upstream system (ledger or rail), when the service chooses to expose it. Absent in most errors. properties: code: description: The upstream provider's own error code, verbatim. examples: - E4001 type: string message: description: >- The upstream provider's own error message, verbatim (bounded, never its raw response body). examples: - account not found at provider type: string type: object headers: XRequestId: description: >- Echo of the request X-Request-Id: the value that the client sent, or the UUID that the platform generated when the client sent none. Present in every response, success or error. schema: format: uuid type: string securitySchemes: BearerAuth: bearerFormat: JWT description: >- JWT token that the Lerian Access Manager issues for your institution. Send it in `Authorization: Bearer ` 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`. scheme: bearer type: http ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.