> ## 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 settlement operations

> Lists settlement operations for the request tenant, filtered and paginated. Filters: state, operationType, batchId, externalId, dateFrom/dateTo (over created_at). Offset/limit pagination.



## OpenAPI

````yaml en/openapi/v3-current/slc.yaml get /v1/operations
openapi: 3.1.0
info:
  description: >-
    API for Lerian SLC — the participant-side rail that connects the institution
    to Núclea's SLC deferred-net card settlement. It covers settlement-operation
    intake and lifecycle, clearing positions, the participant and arrangement
    registry, generated reports, embedded XSD schema introspection, transmission
    recovery and connectivity to Núclea, BYOK Model-A signing-key import, and
    tenant-scoped webhooks.
  title: Lerian SLC API
  version: 1.0.0
servers:
  - url: https://slc.sandbox.lerian.net
security:
  - BearerAuth: []
tags:
  - description: >-
      Settlement operation lifecycle — create, list, query, and control the
      NUliquid-tracked card operations (NUliquid = the 21-position id Núclea
      assigns each accepted operation) through the state machine.
    name: Operations
  - description: >-
      Participant catalog — the acquirers, sub-acquirers, IF Domicílio (bank
      where the merchant receives its sales), and settlement FIs (financial
      institutions) that take part in card settlement.
    name: Participants
  - description: >-
      Card arrangements (bandeira/scheme configurations, e.g. Visa/Master/Elo)
      attached to a participant.
    name: Arrangements
  - description: >-
      Regulated transport orchestration to Núclea/SILOC (the private card
      clearing house that operates the SILOC settlement system) — dispatch,
      recovery, retransmission, and connectivity testing over managed
      file-transfer, message-broker, and REST.
    name: Connectivity
  - description: >-
      Multilateral netting clearing positions — the net amount each participant
      settles per STR cycle (STR = Banco Central reserves-transfer system).
    name: Clearing
  - description: >-
      SaaS BYOK (Bring Your Own Key) signing-key provisioning — import
      parameters and register the client's ICP-Brasil A1 (Brazilian PKI server
      certificate, 1-year validity) certificate material used to sign ASLC
      files; the private key never leaves the client's HSM/KMS/Vault.
    name: SigningKey
  - description: >-
      ASLC file intake and status — passthrough submission and processing status
      of the official Núclea card-settlement XML files (ASLC = Arquivo do
      Sistema de Liquidação de Cartões).
    name: Files
  - description: >-
      Read-only introspection of the embedded Núclea ASLC/RSFN (National
      Financial System Network) XSD schemas used to validate outbound and
      inbound messages.
    name: XSD Schemas
  - description: Read-only regulatory, compliance, and operational settlement reports.
    name: Reports
  - description: >-
      Outbound business-event webhook subscriptions and delivery management for
      consumers (Midaz, client ledgers, Cabine — all optional).
    name: Webhooks
  - description: >-
      Administrative operations — hot-reloadable runtime configuration,
      dead-letter-queue inspection/replay, and outbox redispatch.
    name: Admin
paths:
  /v1/operations:
    get:
      tags:
        - Operations
      summary: List settlement operations
      description: >-
        Lists settlement operations for the request tenant, filtered and
        paginated. Filters: state, operationType, batchId, externalId,
        dateFrom/dateTo (over created_at). Offset/limit pagination.
      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: <SERVICE>-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

````