> ## 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. # Report an operation's transmission status > Reports the transmission/transport status of an operation: its lifecycle state, the tenant's active outbound transport (REST / CD), the in-flight transmit-claim marker (transmitClaimedAt), and the derived transport diagnostics (waitingFor / stuckSince / lastError). Every field is derived from existing columns/state and the append-only state log. RBAC: connectivity:admin. The tenant is ALWAYS taken from the validated request context. ## OpenAPI ````yaml en/openapi/v3-current/slc.yaml get /v1/connectivity/operations/{id}/transmission-status 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/connectivity/operations/{id}/transmission-status: get: tags: - Connectivity summary: Report an operation's transmission status description: >- Reports the transmission/transport status of an operation: its lifecycle state, the tenant's active outbound transport (REST / CD), the in-flight transmit-claim marker (transmitClaimedAt), and the derived transport diagnostics (waitingFor / stuckSince / lastError). Every field is derived from existing columns/state and the append-only state log. RBAC: connectivity:admin. The tenant is ALWAYS taken from the validated request context. operationId: connectivityOperationTransmissionStatus parameters: - description: Operation id (UUID). in: path name: id required: true schema: description: Operation id (UUID). examples: - 0190b5a0-0000-7000-8000-0000000000aa type: string responses: '200': content: application/json: schema: $ref: '#/components/schemas/TransmissionStatusResponse' 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: TransmissionStatusResponse: additionalProperties: false properties: lastError: description: Last recorded transport error; omitted when none. examples: - transport connection timeout type: string operationId: description: Operation id (UUID). examples: - 0190b5a0-0000-7000-8000-0000000000aa type: string state: description: Current operation lifecycle state. examples: - SENT type: string stuckSince: description: >- Timestamp since which the operation has been stuck (RFC3339 UTC); omitted when not stuck. examples: - '2026-06-15T08:00:00Z' type: string transmitClaimedAt: description: >- In-flight transmit-claim timestamp (RFC3339 UTC); omitted when no claim is held. examples: - '2026-06-15T07:50:00Z' type: string transportKind: description: Active outbound transport. examples: - REST type: string waitingFor: description: >- What the operation is waiting on, and therefore which recovery verb applies. transport/nuclea_ack/if_confirmation are external waits. parked means the outbound attempt budget was exhausted and nothing reached Núclea: recover with POST /v1/connectivity/unpark. in_flight means the file IS at Núclea and the local transition failed: reconcile, then POST /v1/operations/{operationId}/advance, and NEVER un-park it. Omitted when no external dependency is named for the state: the operation is terminal, the wait is internal (CREATED/ACCEPTED, where advance/requeue applies), or it awaits a counterpart this vocabulary does not name yet (CONFIRMED, SETTLED). An omitted value names no verb. enum: - transport - nuclea_ack - if_confirmation - parked - in_flight examples: - nuclea_ack type: string required: - operationId - state - transportKind 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 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 ````