> ## 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. # Upload a supplier PDF catalogue for extraction > Uploads a supplier catalogue PDF and proxies it to the enrichment extraction service, returning the accepted job (202) — poll `GET /catalog/imports/{jobId}` for the proposed products. The request body is either the raw PDF bytes with `Content-Type: application/pdf` (max 10 MiB; the file's `filename` and an optional `supplierHint` ride as query params), OR `multipart/form-data` with a `file` part plus an optional `context` field (the centrale's taxonomy / brands / catalogue index, driving reconcile + classify) and a `supplier_hint` field. This extracts + proposes products for HUMAN REVIEW in the centrale; nothing is written to the catalogue by this call. WHY `avoid` for an agent: it needs a binary file upload a human performs from the back-office. ## OpenAPI ````yaml /openapi.json post /v1/catalog/imports 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/catalog/imports: post: tags: - Catalog summary: Upload a supplier PDF catalogue for extraction description: >- Uploads a supplier catalogue PDF and proxies it to the enrichment extraction service, returning the accepted job (202) — poll `GET /catalog/imports/{jobId}` for the proposed products. The request body is either the raw PDF bytes with `Content-Type: application/pdf` (max 10 MiB; the file's `filename` and an optional `supplierHint` ride as query params), OR `multipart/form-data` with a `file` part plus an optional `context` field (the centrale's taxonomy / brands / catalogue index, driving reconcile + classify) and a `supplier_hint` field. This extracts + proposes products for HUMAN REVIEW in the centrale; nothing is written to the catalogue by this call. WHY `avoid` for an agent: it needs a binary file upload a human performs from the back-office. operationId: createCatalogImport parameters: - schema: type: string in: query name: filename required: false - schema: type: string in: query name: supplierHint required: false responses: '202': description: The PDF was accepted and enqueued; poll the returned job id. content: application/json: schema: type: object properties: job_id: type: string minLength: 1 status: type: string enum: - queued - running - succeeded - failed status_url: type: string minLength: 1 required: - job_id - status - status_url additionalProperties: false description: The PDF was accepted and enqueued; poll the returned job id. example: job_id: b3f1c2a4-0e5d-4c7a-9b2e-1f6a8d3c5e70 status: queued status_url: /jobs/b3f1c2a4-0e5d-4c7a-9b2e-1f6a8d3c5e70 '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' '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. ````