> ## 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. # Export the signed fiscal journal > Exports a register chain's full, ordered signature journal plus its FRESHLY recomputed integrity verdict (tamper / gap / broken-link detection). `store` (the chain id) is REQUIRED; without it the route 400s. An empty chain exports an empty, vacuously-valid journal. This is the inalterable archive an auditor exports for offline review. ## OpenAPI ````yaml /openapi.json get /v1/fiscal/journal 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/journal: get: tags: - Fiscal summary: Export the signed fiscal journal description: >- Exports a register chain's full, ordered signature journal plus its FRESHLY recomputed integrity verdict (tamper / gap / broken-link detection). `store` (the chain id) is REQUIRED; without it the route 400s. An empty chain exports an empty, vacuously-valid journal. This is the inalterable archive an auditor exports for offline review. operationId: exportFiscalJournal parameters: - schema: type: string in: query name: store required: false - schema: type: string in: query name: day required: false responses: '200': description: The ordered signature chain plus its recomputed integrity verdict. content: application/json: schema: type: object properties: chainId: type: string signatures: type: array items: type: object properties: id: type: string transactionId: type: string storeId: type: string total: type: integer minimum: -9007199254740991 maximum: 9007199254740991 itemCount: type: integer minimum: -9007199254740991 maximum: 9007199254740991 chainId: type: string sequenceNumber: type: integer minimum: -9007199254740991 maximum: 9007199254740991 signedAt: type: string previousValue: type: string algorithm: type: string value: type: string required: - id - transactionId - storeId - total - itemCount - chainId - sequenceNumber - signedAt - previousValue - algorithm - value additionalProperties: false verification: type: object properties: valid: type: boolean length: type: integer minimum: -9007199254740991 maximum: 9007199254740991 brokenAt: type: integer minimum: -9007199254740991 maximum: 9007199254740991 reason: type: string enum: - SEQUENCE_GAP - BROKEN_LINK - TAMPERED_VALUE - UNKNOWN_ALGORITHM required: - valid - length additionalProperties: false required: - chainId - signatures - verification additionalProperties: false description: >- The ordered signature chain plus its recomputed integrity verdict. example: chainId: store-fiscal signatures: - id: sig-1 transactionId: fx-1 storeId: store-fiscal total: 3600 itemCount: 2 chainId: store-fiscal sequenceNumber: 1 signedAt: '2026-07-16T09:30:00.000Z' previousValue: GENESIS algorithm: hmac-sha256-v2 value: >- b1e2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f4a5b6c7d8e9f0a1b2 verification: valid: true length: 2 '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 `. 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. ````