> ## 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.

# Trigger an ASLC028 status-relay catch-up drain

> Relays the confirmed or IF-rejected status of the request tenant's operations to the creditor (ASLC028), filtering out the already-relayed ones, the same work the scheduled worker runs. RBAC: connectivity:admin. Window-gated internally: outside the relay window it is a no-op that still returns 202. Outbound (transmits to Núclea): serialized per tenant with the scheduled worker via a shared drain lock — on contention it returns 409, and 503 when the lock backend is unavailable (it never transmits unlocked).



## OpenAPI

````yaml en/openapi/v3-current/slc.yaml post /v1/connectivity/status-relay
openapi: 3.0.3
info:
  title: Lerian SLC API
  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, transmission recovery and connectivity to Núclea, BYOK Model-A
    signing-key import, and tenant-scoped webhooks.
  version: v1.0.0
servers:
  - url: https://slc.sandbox.lerian.net
security: []
tags:
  - name: Admin
    description: Tenant configuration and dead-letter administration.
  - name: Clearing
    description: Deferred-net clearing positions for the settlement institution.
  - name: Connectivity
    description: >-
      Transmission recovery drains, retransmission, and connectivity probes to
      Núclea.
  - name: Operations
    description: Settlement operation intake, lifecycle, and state history.
  - name: Participants
    description: Participant registry for the tenant.
  - name: Arrangements
    description: Card and scheme arrangements per participant.
  - name: SigningKey
    description: BYOK Model-A signing-key import for message signing.
  - name: Webhooks
    description: Tenant-scoped webhook subscriptions, deliveries, and replay.
paths:
  /v1/connectivity/status-relay:
    post:
      tags:
        - Connectivity
      summary: Trigger an ASLC028 status-relay catch-up drain
      description: >-
        Relays the confirmed or IF-rejected status of the request tenant's
        operations to the creditor (ASLC028), filtering out the already-relayed
        ones, the same work the scheduled worker runs. RBAC: connectivity:admin.
        Window-gated internally: outside the relay window it is a no-op that
        still returns 202. Outbound (transmits to Núclea): serialized per tenant
        with the scheduled worker via a shared drain lock — on contention it
        returns 409, and 503 when the lock backend is unavailable (it never
        transmits unlocked).
      operationId: recoveryStatusRelay
      responses:
        '202':
          description: Accepted
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/http.recoveryActionResponse'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/http.ErrorResponse'
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/http.ErrorResponse'
        '409':
          description: Conflict
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/http.ErrorResponse'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/http.ErrorResponse'
        '503':
          description: Service Unavailable
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/http.ErrorResponse'
      security:
        - BearerAuth: []
components:
  schemas:
    http.recoveryActionResponse:
      properties:
        action:
          type: string
        participantIspb:
          type: string
      type: object
    http.ErrorResponse:
      properties:
        code:
          type: string
        details:
          additionalProperties: {}
          type: object
        message:
          type: string
        title:
          type: string
      type: object
  securitySchemes:
    BearerAuth:
      description: 'Bearer token authentication (format: "Bearer {token}")'
      in: header
      name: Authorization
      type: apiKey

````