> ## 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 the importable taxonomy presets (librairie d'axes) > Returns one page of the presets a merchant can import: the SOLYA library (shipped with the product, read-only) and — once persisted — the merchant network's own INTERNAL library, each tagged by `origin`. Reach for this FIRST when a merchant has no taxonomy: `taxonomy_axes` starts empty on a real first boot (the 12-axis merchandising set is a demo seed, refused under `NODE_ENV=production`), so importing a preset is the only way a production taxonomy comes into existence. Summaries only — `axisCount`/`nodeCount` let you present a preset without pulling hundreds of nodes; call the preview for the detail. ## OpenAPI ````yaml /openapi.json get /v1/taxonomy/presets 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/taxonomy/presets: get: tags: - Catalog summary: List the importable taxonomy presets (librairie d'axes) description: >- Returns one page of the presets a merchant can import: the SOLYA library (shipped with the product, read-only) and — once persisted — the merchant network's own INTERNAL library, each tagged by `origin`. Reach for this FIRST when a merchant has no taxonomy: `taxonomy_axes` starts empty on a real first boot (the 12-axis merchandising set is a demo seed, refused under `NODE_ENV=production`), so importing a preset is the only way a production taxonomy comes into existence. Summaries only — `axisCount`/`nodeCount` let you present a preset without pulling hundreds of nodes; call the preview for the detail. operationId: listTaxonomyPresets parameters: - schema: default: 1 type: integer minimum: 1 maximum: 9007199254740991 in: query name: page required: false description: 1-based page index to return. Defaults to 1. - schema: default: 20 type: integer minimum: 1 maximum: 100 in: query name: pageSize required: false description: Rows per page, 1..100. Defaults to 20. responses: '200': description: A page of importable presets. content: application/json: schema: type: object properties: items: type: array items: type: object properties: id: type: string minLength: 1 name: type: string minLength: 1 description: type: string origin: type: string enum: - solya - internal axisCount: type: integer minimum: 0 maximum: 9007199254740991 nodeCount: type: integer minimum: 0 maximum: 9007199254740991 required: - id - name - description - origin - axisCount - nodeCount additionalProperties: false description: The rows on this page, in the query's sort order. total: type: integer minimum: 0 maximum: 9007199254740991 description: >- Total rows matching the filter across ALL pages, not just this one. page: type: integer minimum: 0 exclusiveMinimum: true maximum: 9007199254740991 description: The 1-based page number served. pageSize: type: integer minimum: 0 exclusiveMinimum: true maximum: 9007199254740991 description: Rows requested per page. pageCount: type: integer minimum: 0 maximum: 9007199254740991 description: >- Total number of pages; stop walking when `page` reaches it. required: - items - total - page - pageSize - pageCount additionalProperties: false description: A page of importable presets. example: items: - id: solya-fashion name: Mode & prêt-à-porter description: >- Taxonomie marchande complète pour l'habillement et la chaussure… origin: solya axisCount: 12 nodeCount: 219 total: 2 page: 1 pageSize: 20 pageCount: 1 '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. ````