> ## Documentation Index > Fetch the complete documentation index at: https://docs.joinluminous.com/llms.txt > Use this file to discover all available pages before exploring further. # Complete picking for a picklist > Mark a picklist's lines as picked and move the picked stock into the picklist's WIP bin. Each item must name the product (`rfq_id`), the bin the stock is deducted from (`location_id`), and — for a lot-tracked product — the lot (`lot_id`) that was picked (CS-10083). camelCase keys (`picklistItemId`, `rfqId`, `locationId`, `lotId`, `quantityPicked`, `toteBarcode`) are still accepted and normalized. **Retries are safe.** A picklist that is already `picked` or `packed` returns `200` with `already_completed: true`, `transfers_completed: 0` and no stock movement — use it to distinguish "my earlier call landed" from "this ran now". A retry is never an error. Caller-correctable refusals (wrong lot, wrong bin, short pick, an item from another picklist) answer `422` in the same `{ message, errors }` shape as a validation failure, keyed by field path; every bad line is reported in one response. ## OpenAPI ````yaml /api-reference/build.yaml post /pickflow/picklists/{id}/complete openapi: 3.0.0 info: title: Luminous API version: 1.0.0 description: API documentation for Luminous servers: - url: https://{companyName}.api.joinluminous.com/external/api/v1 variables: companyName: default: companyName description: Your company-specific subdomain security: [] tags: - name: Products description: Get and manage products - name: Pricing description: Manage price schedules, levels, and customizations - name: BOMs description: Manage Bills of Materials (BOMs) - name: Labels description: Label rendering via Labelary ZPL service - name: Companies description: Manage business accounts and their associated data - name: Contacts description: Manage contact information for individuals - name: Suppliers description: Manage suppliers (factories) — vendors used on purchase orders - name: Supplier SKUs description: Manage per-supplier SKU and unit-cost overrides for products - name: Locations description: Manage warehouses and locations - name: Inventory description: Get and adjust product stock levels - name: Lots description: Create, update, and delete product lots (batches) - name: Transfer Orders description: Manage transfer orders - name: Fulfillment Orders description: Manage fulfillment orders and picklists - name: Fulfillment Priority Lists description: Configure fulfillment routing priority lists - name: Purchase Orders description: Get and modify purchase orders - name: Supplier Portal description: >- Read a supplier's response to a purchase order and control the one-click portal link - name: Receiving Reports description: Manage receiving reports - name: Payment Obligations description: Manage payment obligations for purchase orders - name: Sales Orders description: Manage sales orders and sales order shipments - name: Purgatory description: >- Inspect and resolve non-posted sales orders in the purgatory staging workflow - name: PickFlow Shipping description: >- Provider-agnostic shipping rates, services, packages, and label purchase for PickFlow - name: Cycle Counts description: >- Create, drive, and post PickFlow cycle counts — batches, per-warehouse sessions, and CSV import/export - name: Print Stations description: List paired print stations and enqueue print jobs to them - name: Invoices description: Get and manage invoices - name: Work Orders description: >- Manage work orders — production lifecycle, steps, materials, links, shipments, and comments - name: Production Batches description: Group and manage work orders as production batches - name: Bills description: >- Accounts payable bill management, payments, attachments, allocations, and variance - name: Prepayments description: Manage vendor prepayments and applications - name: Vendor Credits description: Manage vendor credits and applications - name: Vendor Returns description: Manage vendor returns and credit generation - name: Customer Returns description: Manage customer returns (sales returns), receiving, and restock behavior - name: Stock Snapshot description: Point-in-time stock snapshots with export support - name: Consumption description: Consumption reports and exports - name: Inventory Aging description: Cost-layer-based inventory aging reports - name: Bills Reports description: Accounts payable bills aging reports - name: Forecast description: Materialized forecast data - name: Reports description: Close the books, inventory discrepancy, transaction COGS, and EDI reports - name: Tags description: Add/remove tags across various resources - name: Custom Fields description: Get and set custom fields across various resources - name: Currency description: Currency configuration, exchange rates, and conversion - name: Integration Mappings description: Manage integration mappings for external systems - name: Integration Field Mappings description: Manage field-level mappings between Luminous and external systems paths: /pickflow/picklists/{id}/complete: post: tags: - Picklists summary: Complete picking for a picklist description: >- Mark a picklist's lines as picked and move the picked stock into the picklist's WIP bin. Each item must name the product (`rfq_id`), the bin the stock is deducted from (`location_id`), and — for a lot-tracked product — the lot (`lot_id`) that was picked (CS-10083). camelCase keys (`picklistItemId`, `rfqId`, `locationId`, `lotId`, `quantityPicked`, `toteBarcode`) are still accepted and normalized. **Retries are safe.** A picklist that is already `picked` or `packed` returns `200` with `already_completed: true`, `transfers_completed: 0` and no stock movement — use it to distinguish "my earlier call landed" from "this ran now". A retry is never an error. Caller-correctable refusals (wrong lot, wrong bin, short pick, an item from another picklist) answer `422` in the same `{ message, errors }` shape as a validation failure, keyed by field path; every bad line is reported in one response. operationId: completePicklist parameters: - in: path name: id required: true schema: type: integer description: The picklist ID. requestBody: required: true content: application/json: schema: type: object required: - items properties: items: type: array minItems: 1 items: type: object required: - picklist_item_id - picked_quantity - rfq_id - location_id properties: picklist_item_id: type: integer description: Must belong to this picklist. picked_quantity: type: number description: Must equal the line's available quantity. rfq_id: type: integer description: >- Product (RFQ) ID; must be the product on that picklist line. The stock transfer cannot infer it. location_id: type: integer description: >- The bin the stock is deducted from; must be the line's pick location. lot_id: type: integer nullable: true description: >- Required when the product is lot-tracked; must belong to that product and hold on-hand in `location_id`. tote: type: string maxLength: 255 nullable: true description: Optional free-text tote barcode. responses: '200': description: Picklist completed (or already completed on a safe retry). content: application/json: schema: type: object properties: success: type: boolean example: true message: type: string example: Picklist completed successfully picklist_id: type: integer example: 4821 already_completed: type: boolean description: >- `true` when the picklist was already `picked`/`packed` and this call moved no stock. example: false items_updated: type: integer example: 3 transfers_completed: type: integer description: '`0` on an already-completed retry.' example: 3 wip_location_id: type: integer nullable: true example: 9903 wip_location_name: type: string nullable: true example: WIP-PICKLIST-4821 '401': description: Authentication credentials were missing or invalid content: application/json: schema: type: object properties: error: type: string example: Unauthorized message: type: string example: Authentication credentials are missing or invalid status_code: type: integer example: 401 '404': description: Picklist not found. content: application/json: schema: type: object properties: message: type: string '422': description: >- Validation error or a caller-correctable pick refusal (wrong lot, wrong bin, short pick, over-pick, missing `rfq_id`/`location_id`, or an item from another picklist). Keyed by field path — e.g. `items.0.lot_id`, `items.0.location_id`, or `items` for line-level refusals. content: application/json: schema: type: object properties: message: type: string errors: type: object additionalProperties: type: array items: type: string security: - BearerAuth: [] components: securitySchemes: BearerAuth: type: http scheme: bearer description: >- Authenticate using a bearer token. To create a token, navigate to /settings/api-tokens and click Create API Token. ````