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

# Update notification configuration

> Replaces the notification configuration under optimistic locking; the update applies only if expectedVersion still matches the stored version (else 409).



## OpenAPI

````yaml pt/openapi/v3-current/siloc.yaml put /api/v1/siloc/notifications/config
openapi: 3.1.0
info:
  description: >-
    Interface OpenAPI 3.1 do Lerian SILOC, o trilho do lado do participante que
    conecta a instituição à liquidação interbancária diferida por compensação
    SILOC da Núclea. Abrange as capacidades de cobertura de liquidação, o
    registro de participantes e seu status operacional, o ciclo de vida dos
    certificados regulados, o relay de mensagens do domínio de cartões e seu
    status, o reenvio administrativo de falhas de relay estacionadas, os ciclos
    OT e as rodadas de recálculo, as instruções de liquidação, a ingestão de
    ROC, os alertas operacionais, as mudanças de agenda de contingência, a
    leitura do calendário de dias úteis e a trilha de auditoria.
  title: Lerian SILOC API
  version: 1.0.0
servers:
  - url: http://localhost:9820
security: []
paths:
  /api/v1/siloc/notifications/config:
    put:
      tags:
        - Integration
      summary: Update notification configuration
      description: >-
        Replaces the notification configuration under optimistic locking; the
        update applies only if expectedVersion still matches the stored version
        (else 409).
      operationId: updateNotificationConfig
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/UpdateNotificationConfigInputBody'
        required: true
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/NotificationConfigResponse'
          description: OK
        default:
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Detail'
          description: Error
      security:
        - BearerAuth: []
components:
  schemas:
    UpdateNotificationConfigInputBody:
      additionalProperties: false
      properties:
        channels:
          description: Enabled channels; non-empty, unique, subset of {WEBHOOK, EMAIL}.
          items:
            type: string
          maxItems: 20
          type:
            - array
            - 'null'
          uniqueItems: true
        expectedVersion:
          description: >-
            The version last read; the update applies only while it still
            matches (optimistic lock).
          format: int64
          minimum: 1
          type: integer
        windowLeadMinutes:
          description: Lead time (minutes), 1-120.
          format: int64
          maximum: 120
          minimum: 1
          type: integer
      required:
        - expectedVersion
        - windowLeadMinutes
        - channels
      type: object
    NotificationConfigResponse:
      additionalProperties: false
      properties:
        channels:
          description: Enabled notification channels (WEBHOOK, EMAIL).
          items:
            type: string
          type:
            - array
            - 'null'
        version:
          description: >-
            Optimistic-concurrency version; pass as expectedVersion on the next
            update.
          format: int64
          type: integer
        windowLeadMinutes:
          description: >-
            Lead time (minutes) before a deposit-window close at which to fire
            the alert.
          format: int64
          type: integer
      required:
        - windowLeadMinutes
        - channels
        - version
      type: object
    Detail:
      additionalProperties: false
      properties:
        code:
          description: >-
            Stable, machine-readable domain error code scoped to the emitting
            service (format: <SERVICE>-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

````