> ## 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 effective tenant config

> Lists the request tenant's effective per-tenant runtime configuration: every fenced connectivity key with its overridden value or the catalog default, ordered by key. RBAC: config:read. The tenant is always derived from the validated request identity, never a path or payload value. Selection and policy only — no secret material.



## OpenAPI

````yaml en/openapi/v3-current/slc.yaml get /admin/config
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:
  /admin/config:
    get:
      tags:
        - Admin
      summary: List effective tenant config
      description: >-
        Lists the request tenant's effective per-tenant runtime configuration:
        every fenced connectivity key with its overridden value or the catalog
        default, ordered by key. RBAC: config:read. The tenant is always derived
        from the validated request identity, never a path or payload value.
        Selection and policy only — no secret material.
      operationId: listTenantConfig
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/http.configListResponse'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/http.ErrorResponse'
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/http.ErrorResponse'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/http.ErrorResponse'
      security:
        - BearerAuth: []
components:
  schemas:
    http.configListResponse:
      properties:
        items:
          items:
            $ref: '#/components/schemas/http.configEntryResponse'
          type: array
      type: object
    http.ErrorResponse:
      properties:
        code:
          type: string
        details:
          additionalProperties: {}
          type: object
        message:
          type: string
        title:
          type: string
      type: object
    http.configEntryResponse:
      properties:
        key:
          type: string
        value:
          type: string
      type: object
  securitySchemes:
    BearerAuth:
      description: 'Bearer token authentication (format: "Bearer {token}")'
      in: header
      name: Authorization
      type: apiKey

````