> ## 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. # Take an article in for repair > Opens a repair order in the `intake` state — the article is now in the store's custody. `article.label` is the only required article field; add `skuId` and `serial` when the unit is identifiable and `purchasedAt` when the original sale date is known. `purchasedAt` is RECORDED ONLY — the server derives nothing from it and never adjusts a price; the warranty helper that reads it lives in the till UI, and `quoteAmountCents` is entirely caller-supplied either way. MONEY: `quoteAmountCents` is the price quoted to the customer and `depositAmountCents` the acompte ALREADY captured at the counter (typically 30%; send `0` if none was taken). This endpoint captures nothing itself — take the acompte first, then record it here. There is NO update route: once open, neither the quote nor the acompte can ever be revised, so do not open an order on a provisional estimate. `id` is CALLER-SUPPLIED and is the dedup key: on a timeout retry with the SAME id — a 409 CONFLICT then means your first attempt committed, so read it back with `getRepairOrder` rather than minting a new id. 422 when `depositAmountCents` exceeds `quoteAmountCents`, or when `expectedPickupDate` is not in the future. Note `article.serial` is stored EXACTLY as sent — unlike the sale and warranty paths it is neither upper-cased/trimmed nor IMEI-checksummed here, so send an already-canonical value if you want it to match a serial captured elsewhere. ## OpenAPI ````yaml /openapi.json post /v1/repairs 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/repairs: post: tags: - Repairs summary: Take an article in for repair description: >- Opens a repair order in the `intake` state — the article is now in the store's custody. `article.label` is the only required article field; add `skuId` and `serial` when the unit is identifiable and `purchasedAt` when the original sale date is known. `purchasedAt` is RECORDED ONLY — the server derives nothing from it and never adjusts a price; the warranty helper that reads it lives in the till UI, and `quoteAmountCents` is entirely caller-supplied either way. MONEY: `quoteAmountCents` is the price quoted to the customer and `depositAmountCents` the acompte ALREADY captured at the counter (typically 30%; send `0` if none was taken). This endpoint captures nothing itself — take the acompte first, then record it here. There is NO update route: once open, neither the quote nor the acompte can ever be revised, so do not open an order on a provisional estimate. `id` is CALLER-SUPPLIED and is the dedup key: on a timeout retry with the SAME id — a 409 CONFLICT then means your first attempt committed, so read it back with `getRepairOrder` rather than minting a new id. 422 when `depositAmountCents` exceeds `quoteAmountCents`, or when `expectedPickupDate` is not in the future. Note `article.serial` is stored EXACTLY as sent — unlike the sale and warranty paths it is neither upper-cased/trimmed nor IMEI-checksummed here, so send an already-canonical value if you want it to match a serial captured elsewhere. operationId: createRepairOrder requestBody: required: true content: application/json: schema: type: object properties: id: type: string minLength: 1 article: type: object properties: label: type: string minLength: 1 skuId: type: string pattern: ^[0-9a-f]{64}$ serial: type: object properties: kind: type: string enum: - serial - imei value: type: string minLength: 1 required: - kind - value purchasedAt: 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|([+-](?:[01]\d|2[0-3]):[0-5]\d)))$ required: - label issueDescription: type: string minLength: 1 quoteAmountCents: type: integer minimum: 0 exclusiveMinimum: true maximum: 9007199254740991 depositAmountCents: type: integer minimum: 0 maximum: 9007199254740991 expectedPickupDate: 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|([+-](?:[01]\d|2[0-3]):[0-5]\d)))$ customerId: type: string minLength: 1 storeId: type: string minLength: 1 required: - id - article - issueDescription - quoteAmountCents - depositAmountCents - expectedPickupDate - customerId - storeId example: id: rep-2030-000471 article: label: Smartphone screen skuId: >- d4c81e5b0f7a396248ce15b7d0a83f62915ce4d7b0863af251d94c7e08b3f6a1 purchasedAt: '2029-01-16T09:00:00.000Z' issueDescription: Cracked screen after a drop quoteAmountCents: 12000 depositAmountCents: 3600 expectedPickupDate: '2030-07-20T18:00:00.000Z' customerId: cust-1 storeId: shop-1 responses: '201': description: >- The opened order: `intake`, `updatedAt` equal to `createdAt`, attributed to the calling actor. content: application/json: schema: type: object properties: id: type: string article: type: object properties: label: type: string skuId: type: string serial: type: object properties: kind: type: string enum: - serial - imei value: type: string required: - kind - value additionalProperties: false purchasedAt: type: string required: - label additionalProperties: false issueDescription: type: string quoteAmountCents: type: integer minimum: -9007199254740991 maximum: 9007199254740991 depositAmountCents: type: integer minimum: -9007199254740991 maximum: 9007199254740991 expectedPickupDate: type: string customerId: type: string storeId: type: string status: type: string enum: - intake - in_workshop - ready - collected - unrepairable actorId: type: string createdAt: type: string updatedAt: type: string required: - id - article - issueDescription - quoteAmountCents - depositAmountCents - expectedPickupDate - customerId - storeId - status - actorId - createdAt - updatedAt additionalProperties: false description: >- The opened order: `intake`, `updatedAt` equal to `createdAt`, attributed to the calling actor. example: id: rep-2030-000471 article: label: Smartphone screen skuId: >- d4c81e5b0f7a396248ce15b7d0a83f62915ce4d7b0863af251d94c7e08b3f6a1 purchasedAt: '2029-01-16T09:00:00.000Z' issueDescription: Cracked screen after a drop quoteAmountCents: 12000 depositAmountCents: 3600 expectedPickupDate: '2030-07-20T18:00:00.000Z' customerId: cust-1 storeId: shop-1 status: intake actorId: user-associate-1 createdAt: '2030-07-10T14:05:00.000Z' updatedAt: '2030-07-10T14:05: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. ````