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

# Read the rail's operational-calendar competência window

> Proxies consultar-calendario-trabalhador (Manual 005 v1.13 §3.1): the start/end dates of one payroll competência plus the rail's own notion of the CURRENT competência. It answers a competência WINDOW ONLY — Manual 005 §3.1 has zero occurrences of "feriado" and publishes no business-day field, so this route never claims a date is or is not a business day. Cached for up to one hour per (tenant, competência), because the read spends the rail's own request quota on every call; a cache hit answers with no rail round trip at all.



## OpenAPI

````yaml en/openapi/v3-current/consignado.yaml get /v1/consignado/calendar
openapi: 3.1.0
info:
  contact:
    email: contact@lerian.studio
    name: Lerian Studio
    url: https://lerian.studio
  description: >-
    OpenAPI 3.1 surface for Lerian Consignado — Dataprev. The API covers tenant
    credentials and rail configuration, worker margin, loan auctions and bids,
    contract registration and lifecycle, disbursement confirmation, portability,
    refinancing, renegotiation, FGTS guarantees, reconciliation, funds,
    assignments, usage, throughput, and event subscriptions. Secret material is
    written to the tenant secret store and is never returned by any operation.
  license:
    name: Lerian Studio General License
  title: Lerian Consignado API
  version: v1.0.0
servers:
  - url: https://consignado.sandbox.lerian.net
security:
  - BearerAuth: []
tags:
  - description: >-
      Per-tenant Dataprev credential custody and public rail configuration
      (upload, status, rotation, revoke, requester code, and worker portal base
      URL)
    name: Credentials
  - description: >-
      Tenant-scoped consignado gateway usage: priced billable-unit aggregation
      per competência
    name: Consignado Usage
  - description: >-
      Per-tenant streaming-hub subscription control-plane (list, create, get,
      rotate, revoke, and test delivery)
    name: Subscriptions
  - description: >-
      Dataprev payroll-rail surface: FGTS balance and authorization reads, the
      FGTS guarantee execution, contract suspension, reactivation and term
      changes, the rail's own contract documents, and the on-demand reads of
      leilão solicitações, escriturações, repasses and employment terminations
    name: Consignado Rail
  - description: >-
      Synchronous rail command surface: the operations a bancarizador without
      the lender drives over HTTP. Each shares its command implementation with
      the equivalent lender event trigger.
    name: Consignado Rail Commands
  - description: >-
      Gateway-owned disbursement confirmation: a client bank recording money it
      has ALREADY paid to a worker. It crosses no government boundary and
      proxies no Dataprev operation.
    name: Consignado Disbursement
  - description: >-
      Per-tenant self-service outbound Dataprev rail throughput: read and set
      this tenant's own requests-per-second, including a deliberate pause at
      zero
    name: Consignado Throughput
paths:
  /v1/consignado/calendar:
    get:
      tags:
        - Consignado Rail
      summary: Read the rail's operational-calendar competência window
      description: >-
        Proxies consultar-calendario-trabalhador (Manual 005 v1.13 §3.1): the
        start/end dates of one payroll competência plus the rail's own notion of
        the CURRENT competência. It answers a competência WINDOW ONLY — Manual
        005 §3.1 has zero occurrences of "feriado" and publishes no business-day
        field, so this route never claims a date is or is not a business day.
        Cached for up to one hour per (tenant, competência), because the read
        spends the rail's own request quota on every call; a cache hit answers
        with no rail round trip at all.
      operationId: getConsignadoCalendar
      parameters:
        - description: >-
            OPTIONAL payroll competência to query, yyyyMM (Manual 005 v1.13
            §3.1.1, código CT). Omit it and the rail answers for its own current
            competência.
          explode: false
          in: query
          name: competencia
          schema:
            description: >-
              OPTIONAL payroll competência to query, yyyyMM (Manual 005 v1.13
              §3.1.1, código CT). Omit it and the rail answers for its own
              current competência.
            examples:
              - '202410'
            pattern: ^[0-9]{6}$
            type: string
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetCalendarResponse'
          description: OK
        default:
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Detail'
          description: Error
      security:
        - BearerAuth: []
components:
  schemas:
    GetCalendarResponse:
      additionalProperties: false
      properties:
        competencia_atual:
          description: >-
            The rail's own current competência, yyyyMM (Número). It can differ
            from competencia_consulta on ANY call.
          examples:
            - '202603'
          type: string
        competencia_consulta:
          description: >-
            The competência this read resolved to: your competencia filter, or
            the rail's current competência when you omitted it.
          examples:
            - '202410'
          type: string
        data_fim_competencia:
          description: End date of competencia_consulta (yyyy-MM-dd).
          examples:
            - '2024-09-20'
          type: string
        data_inicio_competencia:
          description: Start date of competencia_consulta (yyyy-MM-dd).
          examples:
            - '2024-08-21'
          type: string
      required:
        - competencia_atual
        - competencia_consulta
        - data_inicio_competencia
        - data_fim_competencia
      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
        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.
      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

````