> ## Documentation Index
> Fetch the complete documentation index at: https://docs-pos.solya.app/llms.txt
> Use this file to discover all available pages before exploring further.

# List a store's sealed closures

> Lists a register chain's sealed closures, ascending by sequence, optionally filtered by `?kind=` (`daily` / `monthly` / `annual`). `store` (the chain id) is REQUIRED; without it the route 400s.



## OpenAPI

````yaml /openapi.json get /v1/fiscal/closures
openapi: 3.0.3
info:
  title: Solya POS API
  version: 1.0.0
  description: >-
    The Solya POS backend HTTP surface. Every documented operation is
    agent-ready: it carries an `operationId`, an agent-facing `description`, the
    `pos.*` scopes it enforces (`x-required-permissions`) and an `x-agent-tier`.
    Success responses return the payload as raw JSON; failures return the
    `ErrorResponse` envelope (`{ error: { code, message, statusCode } }`).
servers:
  - url: /
    description: The backend, relative to its deployed origin.
security: []
paths:
  /v1/fiscal/closures:
    get:
      tags:
        - Fiscal
      summary: List a store's sealed closures
      description: >-
        Lists a register chain's sealed closures, ascending by sequence,
        optionally filtered by `?kind=` (`daily` / `monthly` / `annual`).
        `store` (the chain id) is REQUIRED; without it the route 400s.
      operationId: listFiscalClosures
      parameters:
        - schema:
            type: string
          in: query
          name: store
          required: false
        - schema:
            type: string
          in: query
          name: kind
          required: false
        - schema:
            type: string
          in: query
          name: period
          required: false
      responses:
        '200':
          description: The store's sealed closures, ascending by sequence number.
          content:
            application/json:
              schema:
                type: array
                items:
                  type: object
                  properties:
                    id:
                      type: string
                    chainId:
                      type: string
                    kind:
                      type: string
                      enum:
                        - daily
                        - monthly
                        - annual
                    period:
                      type: string
                    periodStart:
                      type: string
                    periodEnd:
                      type: string
                    ticketCount:
                      type: integer
                      minimum: -9007199254740991
                      maximum: 9007199254740991
                    grossTotalCents:
                      type: integer
                      minimum: -9007199254740991
                      maximum: 9007199254740991
                    grandTotalCents:
                      type: integer
                      minimum: -9007199254740991
                      maximum: 9007199254740991
                    sequenceNumber:
                      type: integer
                      minimum: -9007199254740991
                      maximum: 9007199254740991
                    closedAt:
                      type: string
                    previousValue:
                      type: string
                    algorithm:
                      type: string
                    value:
                      type: string
                  required:
                    - id
                    - chainId
                    - kind
                    - period
                    - periodStart
                    - periodEnd
                    - ticketCount
                    - grossTotalCents
                    - grandTotalCents
                    - sequenceNumber
                    - closedAt
                    - previousValue
                    - algorithm
                    - value
                  additionalProperties: false
                description: The store's sealed closures, ascending by sequence number.
                example:
                  - id: clo-1
                    chainId: store-close
                    kind: daily
                    period: '2026-07-16'
                    periodStart: '2026-07-16'
                    periodEnd: '2026-07-16'
                    ticketCount: 2
                    grossTotalCents: 7200
                    grandTotalCents: 7200
                    sequenceNumber: 1
                    closedAt: '2026-07-16T18:00:00.000Z'
                    previousValue: GENESIS
                    algorithm: hmac-sha256-v2
                    value: >-
                      c2f3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f4a5b6c7d8e9f0a1b2c3
        '400':
          description: >-
            The request failed schema validation; `error.fieldErrors` lists the
            fields.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ValidationErrorResponse'
        '401':
          description: No valid credential was presented — send a bearer token.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '403':
          description: The actor is authenticated but lacks the required `pos.*` scope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: An unexpected server error — safe to retry idempotent requests.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
      security:
        - bearerAuth: []
components:
  schemas:
    ValidationErrorResponse:
      type: object
      required:
        - error
      additionalProperties: false
      description: >-
        A `VALIDATION_FAILED` envelope carrying the offending fields in
        `fieldErrors`.
      properties:
        error:
          type: object
          required:
            - code
            - message
            - statusCode
          additionalProperties: false
          properties:
            code:
              type: string
              enum:
                - VALIDATION_FAILED
            message:
              type: string
            statusCode:
              type: integer
            fieldErrors:
              type: array
              description: >-
                One entry per rejected field: the field path and why it was
                rejected.
              items:
                type: object
                required:
                  - field
                  - message
                additionalProperties: false
                properties:
                  field:
                    type: string
                    description: Dot-path of the offending field.
                  message:
                    type: string
                    description: Why the field was rejected.
    ErrorResponse:
      type: object
      required:
        - error
      additionalProperties: false
      description: The uniform failure envelope every non-2xx response returns.
      properties:
        error:
          type: object
          required:
            - code
            - message
            - statusCode
          additionalProperties: false
          properties:
            code:
              type: string
              enum:
                - VALIDATION_FAILED
                - UNAUTHORIZED
                - FORBIDDEN
                - NOT_FOUND
                - CONFLICT
                - BUSINESS_RULE_VIOLATION
                - INTERNAL_ERROR
              description: >-
                Machine-readable kernel `ResultCode` — branch on this, not on
                `message`.
            message:
              type: string
              description: >-
                Human-readable explanation. Safe to surface; never leaks server
                internals.
            statusCode:
              type: integer
              description: >-
                The HTTP status, mirrored into the body so a client need not
                read headers.
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        `Authorization: Bearer <token>`. Accepts EITHER a Keycloak access token
        (scopes-in-token) OR an opaque POS session token; both resolve to the
        same `pos.*` scope vocabulary the route guards enforce.

````