> ## 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 the commands this institution sent to the câmara > Lists the commands this institution originated towards the câmara, newest first, paged (limit default 50, max 500). Each row carries who authorised it, what was sent, and how far it got — ACCEPTED means Lerian SILOC accepted and QUEUED the command, not that it reached the câmara, and is NOT a settlement claim. RBAC: lbtr:read; the tenant is always derived from the validated request identity, never the payload. ## OpenAPI ````yaml /en/openapi/v3-current/slc.yaml get /v1/lbtr/commands openapi: 3.1.0 info: description: >- API for Lerian SLC — the participant-side rail that connects the institution to Núclea's SLC card settlement. 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's SLC — 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 server-type certificate material used to sign ASLC files (RSA, at least 2048 bits, and valid at the moment of import — all three are enforced); the SLC never receives the private key in cleartext. 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 (client ledgers — optional). name: Webhooks - description: >- Administrative operations — hot-reloadable runtime configuration, dead-letter-queue inspection/replay, and outbox redispatch. name: Admin paths: /v1/lbtr/commands: get: tags: - LBTR summary: List the commands this institution sent to the câmara description: >- Lists the commands this institution originated towards the câmara, newest first, paged (limit default 50, max 500). Each row carries who authorised it, what was sent, and how far it got — ACCEPTED means Lerian SILOC accepted and QUEUED the command, not that it reached the câmara, and is NOT a settlement claim. RBAC: lbtr:read; the tenant is always derived from the validated request identity, never the payload. operationId: listLbtrCommands parameters: - description: Page size (default 50, max 500). explode: false in: query name: limit schema: description: Page size (default 50, max 500). examples: - '50' type: string - description: Row offset (default 0). explode: false in: query name: offset schema: description: Row offset (default 0). examples: - '0' type: string responses: '200': content: application/json: schema: $ref: '#/components/schemas/ListCommandsResponse' description: OK '422': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Unprocessable Entity '500': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Internal Server Error '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: ListCommandsResponse: additionalProperties: false properties: items: description: This page of commands, newest first. items: $ref: '#/components/schemas/CommandResponse' type: array pagination: $ref: '#/components/schemas/LBTRPaginationMeta' description: Pagination metadata for this 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). type: string correlationId: description: Request-scoped correlation identifier echoing X-Request-ID. examples: - req-7a3f9c2e 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. required: - correlationId type: object CommandResponse: additionalProperties: false properties: acceptedAt: description: >- When Lerian SILOC durably accepted this command and queued it for dispatch (RFC3339). It is not the moment the message reached the câmara — that is answeredAt. type: string actorSubject: description: >- The authenticated subject that authorised this command — the durable record of who answered the câmara. type: string actorType: description: Whether a person or a machine authorised this command. type: string answer: description: >- The câmara's answer body, projected exactly as it arrived: dtMovto, an optional dtHrLTR, and for a position query an optional positions array whose entries carry the câmara's own numbers as strings. This rail never computes, nets or rounds one. An absent positions array on a position query means the câmara matched nothing; on the two acknowledgement legs it means that leg carries no positions at all. businessTuple: description: >- The fields sent to the câmara for this message type, as they were sent. Monetary values are decimal strings. closedAt: description: When the command reached a terminal state (RFC3339). type: string id: description: >- The command's id (a UUIDv7). It is also the id of the outbound event and the key every fact about this command joins on. type: string messageType: description: LTR0002, LTR0008 or LTR0009. type: string numCtrlIF: description: >- The identifier Lerian SILOC minted for this message. Opaque here: displayed and logged, never parsed. type: string numCtrlLTR: description: >- The câmara-minted control number, when the answering leg carried one. type: string reason: description: >- Why a REFUSED or FAILED command ended that way, plus the offending tag when the wire supplied one. Diagnostic, never a control value. type: string requestedAt: description: When the institution decided (RFC3339). type: string sourceAggregateId: description: The announcement this command was authorised against. type: string sourceAggregateKind: description: >- Which announcement this command answers. For a position query it names the command row itself, because a query answers no announcement. type: string sourceAggregateVersion: description: The version of that announcement at the moment it was answered. format: int64 type: integer status: description: >- REQUESTED (committed here, nothing has left this service), ACCEPTED (Lerian SILOC durably accepted the command and queued it for dispatch — it is NOT yet on the wire to the câmara and is NOT a settlement claim), ANSWERED (the câmara answered), REFUSED (the câmara said no) or FAILED (it never reached the câmara, and the announcement is open again). FAILED can follow ACCEPTED: Lerian SILOC may give up terminally on a queued message. type: string required: - id - messageType - actorType - actorSubject - sourceAggregateKind - sourceAggregateId - sourceAggregateVersion - businessTuple - status - requestedAt type: object LBTRPaginationMeta: additionalProperties: false properties: hasNext: description: True when the returned page filled the requested limit. examples: - false 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 Upstream: additionalProperties: false 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 securitySchemes: BearerAuth: bearerFormat: JWT description: JWT bearer token issued by the identity provider. scheme: bearer type: http ````