> ## 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 cancellation repasses awaiting manual reconciliation > Lists the ASLC063/067 acquirer repasses (repasse ao acquirer) whose delivery to Núclea was never established, for the request tenant, oldest first. RBAC: connectivity:admin. This is the population every "MANUAL RECONCILIATION REQUIRED" log line and every cancellation_relay_manual_reconciliation_total increment on this leg points at: a repasse submitted whose conclusion marker was not written, an earlier attempt whose intention was already unresolved, or an attempt that provably never reached the wire whose release failed. Each row BLOCKS its (operationId, aslcType) pair from relaying again — that refusal is what stops a duplicate regulatory notification — so an operator reconciles the reported controlNumber with Núclea and closes it with POST /v1/connectivity/cancellation-relay-intents/resolve, which is the ONLY way to clear one. An empty page is the healthy day, not an error. Offset/limit pagination WITHOUT a total count; the tenant is always derived from the validated request identity. ## OpenAPI ````yaml /es/openapi/v3-current/slc.yaml get /v1/connectivity/cancellation-relay-intents 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/connectivity/cancellation-relay-intents: get: tags: - Connectivity summary: List cancellation repasses awaiting manual reconciliation description: >- Lists the ASLC063/067 acquirer repasses (repasse ao acquirer) whose delivery to Núclea was never established, for the request tenant, oldest first. RBAC: connectivity:admin. This is the population every "MANUAL RECONCILIATION REQUIRED" log line and every cancellation_relay_manual_reconciliation_total increment on this leg points at: a repasse submitted whose conclusion marker was not written, an earlier attempt whose intention was already unresolved, or an attempt that provably never reached the wire whose release failed. Each row BLOCKS its (operationId, aslcType) pair from relaying again — that refusal is what stops a duplicate regulatory notification — so an operator reconciles the reported controlNumber with Núclea and closes it with POST /v1/connectivity/cancellation-relay-intents/resolve, which is the ONLY way to clear one. An empty page is the healthy day, not an error. Offset/limit pagination WITHOUT a total count; the tenant is always derived from the validated request identity. operationId: listCancellationRelayIntents parameters: - description: >- Page size (default 50, max 500). A non-positive/non-numeric value is rejected with 400. explode: false in: query name: limit schema: description: >- Page size (default 50, max 500). A non-positive/non-numeric value is rejected with 400. examples: - '50' type: string - description: >- Row offset (default 0). A negative/non-numeric value is rejected with 400. explode: false in: query name: offset schema: description: >- Row offset (default 0). A negative/non-numeric value is rejected with 400. examples: - '0' type: string responses: '200': content: application/json: schema: $ref: '#/components/schemas/ListCancellationRelayIntentsResponse' 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: ListCancellationRelayIntentsResponse: additionalProperties: false properties: items: description: Unresolved repasse intentions in this page, oldest first. items: $ref: '#/components/schemas/RelayIntentResponse' type: array pagination: $ref: '#/components/schemas/RelayIntentPaginationMeta' 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 RelayIntentResponse: additionalProperties: false properties: aslcType: description: >- Relay family: ASLC063 (credit) or ASLC067 (debit). The other half of the key — one operation can carry a separate repasse per family. enum: - ASLC063 - ASLC067 examples: - ASLC063 type: string attempts: description: >- How many control numbers this repasse has burnt. It is also the attempt budget's counter (SCHEDULE_DISPATCH_MAX_TRANSMIT_ATTEMPTS). examples: - 3 format: int64 type: integer controlNumber: description: >- NumCtrlEmis burnt by the latest attempt. This is the value to reconcile with Núclea: "did you receive control number X?". examples: - '2026052800019' type: string createdAt: description: When the FIRST attempt registered its intention (RFC3339 UTC). examples: - '2026-05-28T06:30:00Z' type: string operationId: description: >- Id of the ORIGINAL movement the confirmed cancellation correlates to. Half of the key the resolution verb takes. examples: - 018f8a3e-4b2c-7c1a-9e5d-2f6a1b3c4d5e type: string state: description: >- Lifecycle state of the intention. This listing reports only IN_FLIGHT — an outcome that was never established — because that is the state that blocks the pair from relaying again. enum: - IN_FLIGHT examples: - IN_FLIGHT type: string updatedAt: description: >- When the row last changed state or recorded a new attempt (RFC3339 UTC). The listing is ordered by it, oldest first. examples: - '2026-05-28T07:50:00Z' type: string required: - operationId - aslcType - controlNumber - attempts - state - createdAt - updatedAt type: object RelayIntentPaginationMeta: additionalProperties: false properties: hasNext: description: >- Whether another page likely exists (page-full heuristic; no total count). examples: - false type: boolean page: description: 1-based page number. examples: - 1 format: int64 type: integer perPage: description: 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 ````