> ## 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. # Receive against a purchase order > Books a batch of receipts against an OPEN order, accumulating each line's received quantity and re-deriving the order status (`received` once every line is fully received). Re-runs the receiving guard server-side. 404s for an unknown order or receipt SKU; 422s when the order is already fully received. ## OpenAPI ````yaml /openapi.json post /v1/purchase-orders/{orderId}/receive 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/purchase-orders/{orderId}/receive: post: tags: - Procurement summary: Receive against a purchase order description: >- Books a batch of receipts against an OPEN order, accumulating each line's received quantity and re-deriving the order status (`received` once every line is fully received). Re-runs the receiving guard server-side. 404s for an unknown order or receipt SKU; 422s when the order is already fully received. operationId: receivePurchaseOrder parameters: - schema: type: string minLength: 1 in: path name: orderId required: true requestBody: required: true content: application/json: schema: type: object properties: receipts: minItems: 1 type: array items: type: object properties: skuId: type: string pattern: ^[0-9a-f]{64}$ quantity: type: integer minimum: 0 exclusiveMinimum: true maximum: 9007199254740991 required: - skuId - quantity required: - receipts example: receipts: - skuId: >- e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 quantity: 24 responses: '200': description: The order with accumulated receipts and re-derived status. content: application/json: schema: type: object properties: id: type: string minLength: 1 supplierId: type: string minLength: 1 shopId: type: string minLength: 1 status: type: string enum: - open - received lines: type: array items: type: object properties: skuId: type: string pattern: ^[0-9a-f]{64}$ orderedQuantity: type: integer minimum: 0 exclusiveMinimum: true maximum: 9007199254740991 receivedQuantity: type: integer minimum: 0 maximum: 9007199254740991 unitCostCents: type: integer minimum: 0 maximum: 9007199254740991 required: - skuId - orderedQuantity - receivedQuantity - unitCostCents additionalProperties: false required: - id - supplierId - shopId - status - lines additionalProperties: false description: The order with accumulated receipts and re-derived status. example: id: po-1001 supplierId: nike-fr shopId: shop-paris status: received lines: - skuId: >- e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 orderedQuantity: 24 receivedQuantity: 24 unitCostCents: 4500 '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' '404': description: No resource matches the addressed identifier. 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. ````