> ## 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. # Save the current taxonomy as an internal preset > Captures every LIVE axis (archived ones are excluded) into a named preset in the merchant's own library, shared across every store of the network. The result is a FROZEN SNAPSHOT: later edits to the taxonomy do not reach it, and `capturedAt` records when it was taken — a preset that tracked the live vocabulary would be a mirror, and importing a mirror installs nothing. Reads and writes in one transaction under the taxonomy lock, so a snapshot can never freeze a half-finished import. 409s on a duplicate name, 422 when the taxonomy has no live axis to capture (an empty preset would list and preview like any other and install nothing). Needs `pos.catalog.manage`. ## OpenAPI ````yaml /openapi.json post /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: post: tags: - Catalog summary: Save the current taxonomy as an internal preset description: >- Captures every LIVE axis (archived ones are excluded) into a named preset in the merchant's own library, shared across every store of the network. The result is a FROZEN SNAPSHOT: later edits to the taxonomy do not reach it, and `capturedAt` records when it was taken — a preset that tracked the live vocabulary would be a mirror, and importing a mirror installs nothing. Reads and writes in one transaction under the taxonomy lock, so a snapshot can never freeze a half-finished import. 409s on a duplicate name, 422 when the taxonomy has no live axis to capture (an empty preset would list and preview like any other and install nothing). Needs `pos.catalog.manage`. operationId: captureTaxonomyPreset requestBody: required: true content: application/json: schema: type: object properties: name: type: string minLength: 1 description: >- Display name of the snapshot (e.g. `Notre réseau`); must be unique. description: default: '' description: Optional free text explaining what this snapshot is for. type: string required: - name example: name: Notre réseau description: La taxonomie validée en comité produit. responses: '201': description: The captured snapshot. content: application/json: schema: type: object properties: id: type: string name: type: string description: type: string origin: type: string enum: - internal axes: type: array items: type: object properties: id: type: string minLength: 1 name: type: string minLength: 1 scope: type: string enum: - product - variant - movement source: type: string enum: - managed - local roots: type: array items: 0b9af605-5326-40a0-b983-a6c8db046bf5 valueType: type: string enum: - text - color - size - number - measure unit: type: string minLength: 1 multiValued: type: boolean active: type: boolean required: - id - name - scope - source - roots additionalProperties: false capturedAt: type: string required: - id - name - description - origin - axes - capturedAt additionalProperties: false description: The captured snapshot. example: id: internal-notre-reseau name: Notre réseau description: La taxonomie validée en comité produit. origin: internal axes: [] capturedAt: '2026-08-07T09:12:00.000Z' '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' '409': description: >- The request conflicts with current state (duplicate id or stale version). content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '422': description: The request is well-formed but violates a domain rule. 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. ````