> ## 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 age-verification attestations > Reads the durable age-verification compliance trail (justificatif de contrôle d'âge) — the append-only legal record that a restricted-item check was performed. Reach for this to produce the evidence a regulator asks for, or to audit a given transaction or operator. Every facet is OPTIONAL and combined as AND: `transactionRef` (one sale), `operatorId` (one cashier), `outcome` (`pass`/`block`/`needs_check`), and the inclusive instant range `from`/`to` (ISO-8601). With no filter it returns the WHOLE trail, ordered newest-first. The rows carry NO customer identity — by construction the trail cannot hold a date of birth, name or document number. There is deliberately no `store` filter (the row has no store column). Gating: the router rides the till scope `pos.checkout.operate`. ## OpenAPI ````yaml /openapi.json get /v1/age-attestations 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/age-attestations: get: tags: - Compliance summary: List age-verification attestations description: >- Reads the durable age-verification compliance trail (justificatif de contrôle d'âge) — the append-only legal record that a restricted-item check was performed. Reach for this to produce the evidence a regulator asks for, or to audit a given transaction or operator. Every facet is OPTIONAL and combined as AND: `transactionRef` (one sale), `operatorId` (one cashier), `outcome` (`pass`/`block`/`needs_check`), and the inclusive instant range `from`/`to` (ISO-8601). With no filter it returns the WHOLE trail, ordered newest-first. The rows carry NO customer identity — by construction the trail cannot hold a date of birth, name or document number. There is deliberately no `store` filter (the row has no store column). Gating: the router rides the till scope `pos.checkout.operate`. operationId: listAgeAttestations parameters: - schema: type: string minLength: 1 in: query name: transactionRef required: false description: >- Filter to the check(s) recorded for one transaction/ticket reference. - schema: type: string minLength: 1 in: query name: operatorId required: false description: Filter to the checks a single operator (cashier) recorded. - schema: type: string enum: - pass - block - needs_check in: query name: outcome required: false description: 'Filter to one decision: `pass`, `block` or `needs_check`.' - schema: type: string minLength: 1 format: date-time in: query name: from required: false description: Inclusive lower bound on the instant (`at >= from`). - schema: type: string minLength: 1 format: date-time in: query name: to required: false description: Inclusive upper bound on the instant (`at <= to`). responses: '200': description: >- The matching attestations, newest first (empty array when none match). content: application/json: schema: type: array items: type: object properties: id: type: string operatorId: type: string transactionRef: type: string at: type: string format: date-time pattern: >- ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$ outcome: type: string enum: - pass - block - needs_check required: - id - operatorId - transactionRef - at - outcome additionalProperties: false description: >- The matching attestations, newest first (empty array when none match). example: - id: corr-9a02:ageVerification:sale-58:2026-07-16T18:12:00.000Z operatorId: user-camille transactionRef: sale-58 at: '2026-07-16T18:12:00.000Z' outcome: block - id: corr-8f21:ageVerification:sale-42:2026-07-16T09:00:00.000Z operatorId: user-camille transactionRef: sale-42 at: '2026-07-16T09:00:00.000Z' outcome: pass '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. ````