> ## 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. # Listar operaciones de liquidación > Lista las operaciones de liquidación del tenant de la solicitud, filtradas y paginadas. Filtros: state, operationType, batchId, externalId, dateFrom/dateTo (sobre created_at). Paginación por offset/limit. ## OpenAPI ````yaml es/openapi/v3-current/slc.yaml get /v1/operations openapi: 3.1.0 info: description: >- API de Lerian SLC — el rail del lado del participante que conecta la institución con la liquidación de tarjetas por neto diferido SLC de Núclea. Cubre la admisión y el ciclo de vida de las operaciones de liquidación, las posiciones de compensación, el registro de participantes y arreglos, los informes generados, la consulta de esquemas XSD integrados, la recuperación de transmisión y la conectividad con Núclea, la importación de clave de firma BYOK Modelo A y los webhooks con alcance al tenant. title: Lerian SLC API version: 1.0.0 servers: - url: https://slc.sandbox.lerian.net security: - BearerAuth: [] tags: - description: >- Ciclo de vida de las operaciones de liquidación — crea, lista, consulta y controla las operaciones de tarjeta rastreadas por NUliquid (NUliquid = el id de 21 posiciones que Núclea asigna a cada operación aceptada) a través de la máquina de estados. name: Operations - description: >- Catálogo de participantes — los adquirentes, subadquirentes, IF Domicílio (banco donde el establecimiento recibe sus ventas) y las IF de liquidación (instituciones financieras) que participan en la liquidación de tarjetas. name: Participants - description: >- Arreglos de tarjeta (configuraciones de bandeira/esquema, p. ej. Visa/Master/Elo) asociados a un participante. name: Arrangements - description: >- Orquestación de transporte regulado hacia Núclea/SILOC (la cámara de compensación privada de tarjetas que opera el sistema de liquidación SILOC) — despacho, recuperación, retransmisión y prueba de conectividad sobre transferencia de archivos gestionada, broker de mensajes y REST. name: Connectivity - description: >- Posiciones de compensación de neteo multilateral — el monto neto que cada participante liquida por ciclo STR (STR = sistema de transferencia de reservas del Banco Central). name: Clearing - description: >- Aprovisionamiento de clave de firma SaaS BYOK (Bring Your Own Key) — importa parámetros y registra el material del certificado ICP-Brasil A1 del cliente (certificado de servidor de la PKI brasileña, validez de 1 año) usado para firmar archivos ASLC; la clave privada nunca sale del HSM/KMS/Vault del cliente. name: SigningKey - description: >- Admisión y estado de archivos ASLC — envío en modo passthrough y estado de procesamiento de los archivos XML oficiales de liquidación de tarjetas de Núclea (ASLC = Arquivo do Sistema de Liquidação de Cartões). name: Files - description: >- Introspección de solo lectura de los esquemas XSD ASLC/RSFN (Red del Sistema Financiero Nacional) integrados de Núclea usados para validar los mensajes salientes y entrantes. name: XSD Schemas - description: >- Informes de liquidación regulatorios, de cumplimiento y operativos, de solo lectura. name: Reports - description: >- Suscripciones a webhooks de eventos de negocio salientes y gestión de entrega para los consumidores (Midaz, ledgers del cliente, Cabine — todos opcionales). name: Webhooks - description: >- Operaciones administrativas — configuración de tiempo de ejecución recargable en caliente, inspección/reenvío de la cola de mensajes muertos y redespacho del outbox. name: Admin paths: /v1/operations: get: tags: - Operations summary: Listar operaciones de liquidación description: >- Lista las operaciones de liquidación del tenant de la solicitud, filtradas y paginadas. Filtros: state, operationType, batchId, externalId, dateFrom/dateTo (sobre created_at). Paginación por offset/limit. operationId: listOperations parameters: - description: Filter by lifecycle state. explode: false in: query name: state schema: description: Filter by lifecycle state. type: string - description: Filter by operation type. explode: false in: query name: operationType schema: description: Filter by operation type. type: string - description: Filter by batch id. explode: false in: query name: batchId schema: description: Filter by batch id. type: string - description: Filter by external id. explode: false in: query name: externalId schema: description: Filter by external id. type: string - description: Filter created_at >= (RFC3339). explode: false in: query name: dateFrom schema: description: Filter created_at >= (RFC3339). type: string - description: Filter created_at <= (RFC3339). explode: false in: query name: dateTo schema: description: Filter created_at <= (RFC3339). type: string - description: Page size (default 50, max 500). explode: false in: query name: limit schema: description: Page size (default 50, max 500). type: string - description: Row offset (default 0). explode: false in: query name: offset schema: description: Row offset (default 0). type: string - description: >- Filter operations HELD out of the outbound drains, by reason. "parked" — the attempt budget was exhausted and nothing reached Núclea; recover with POST /v1/connectivity/unpark. "in_flight" — the file IS at Núclea and the local transition failed; reconcile with Núclea, then POST /v1/operations/{operationId}/advance, and NEVER un-park these (it re-submits an accepted file). explode: false in: query name: transmitHold schema: description: >- Filter operations HELD out of the outbound drains, by reason. "parked" — the attempt budget was exhausted and nothing reached Núclea; recover with POST /v1/connectivity/unpark. "in_flight" — the file IS at Núclea and the local transition failed; reconcile with Núclea, then POST /v1/operations/{operationId}/advance, and NEVER un-park these (it re-submits an accepted file). examples: - parked type: string responses: '200': content: application/json: schema: $ref: '#/components/schemas/ListOperationsResponse' description: OK '501': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: >- Not Implemented: this capability is not part of this deployment. Operations are registered unconditionally so the published contract is identical across deploy shapes; when the capability behind one did not compose here (authentication disabled, no database, no outbound transport, or the feature switched off) it answers this coded SLC-0012 problem. It is definitive for this deployment: retrying does not help, and the `detail` is deliberately scrubbed (any status >= 500 is). default: content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Error components: schemas: ListOperationsResponse: additionalProperties: false properties: items: description: Page of operation summaries for the request tenant. items: $ref: '#/components/schemas/OperationSummary' type: - array - 'null' pagination: $ref: '#/components/schemas/PaginationMeta' description: Pagination envelope for the returned page. required: - items - pagination type: object Detail: additionalProperties: false properties: code: description: >- Stable, machine-readable domain error code scoped to the emitting service (format: -NNNN). examples: - ERR-0001 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 type: object OperationSummary: additionalProperties: false properties: arrangementCode: description: Payment arrangement (arranjo) code. examples: - '0245' type: string batchId: description: Batch id when created via the NDJSON batch endpoint. examples: - 018f8a3e-4b2c-7c1a-9e5d-2f6a1b3c4d5e type: string createdAt: description: Creation timestamp (RFC3339). examples: - '2026-06-15T10:50:00Z' type: string currency: description: ISO 4217 currency code. examples: - BRL type: string externalId: description: Client-side external identifier. examples: - acq-ext-2026-06-0001 type: string id: description: Operation id (UUID). examples: - 018f8a3e-4b2c-7c1a-9e5d-2f6a1b3c4d5e type: string intakeMode: description: Intake mode the operation was received through. examples: - api_jsonl type: string nuliquid: description: Núclea-assigned NUliquid (21 positions); null until assigned. examples: - '202606150000000000001' type: - string - 'null' operationType: description: Operation type. examples: - CREDIT type: string participantRole: description: Participant role in the settlement. examples: - ACQUIRER type: string state: description: Lifecycle state. examples: - SETTLED type: string transactionDate: description: Business transaction date (RFC3339). examples: - '2026-06-15T00:00:00Z' type: string value: description: Operation amount in minor units (centavos). examples: - 150000 format: int64 type: integer required: - id - externalId - operationType - state - nuliquid - value - currency - intakeMode - participantRole - transactionDate - createdAt type: object PaginationMeta: additionalProperties: false properties: hasNext: description: >- True when the returned page filled the requested limit (page-full heuristic). examples: - true type: boolean page: description: 1-based page number derived from the offset. examples: - 1 format: int64 type: integer perPage: description: Requested page size. examples: - 50 format: int64 type: integer required: - page - perPage - hasNext type: object ErrorDetail: additionalProperties: false 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 securitySchemes: BearerAuth: bearerFormat: JWT description: JWT bearer token issued by the identity provider. scheme: bearer type: http ````