> ## 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. # Bulk delete lots > Best-effort bulk soft-delete of lots. Each lot follows the same UI-parity behavior as `DELETE /lots/{lotId}`: its regular on-hand stock is auto-cleared (via an inventory adjustment posted by the authenticated user) and the lot is soft-deleted. A per-lot failure — an unknown ID, or a lot whose stock could not be cleared first (picklist-committed stock, no base unit of measure, or stock remaining after the auto-clear adjustment) — is captured in that lot's `results` row and does **not** abort the rest of the batch, so the call returns `200` even on a partial failure. Inspect `deleted`, `failed`, and `results` for per-lot outcomes. ## OpenAPI ````yaml /api-reference/build.yaml post /lots/bulk-delete 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: Purchase Orders description: Get and modify purchase orders - 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: /lots/bulk-delete: post: tags: - Lots summary: Bulk delete lots description: > Best-effort bulk soft-delete of lots. Each lot follows the same UI-parity behavior as `DELETE /lots/{lotId}`: its regular on-hand stock is auto-cleared (via an inventory adjustment posted by the authenticated user) and the lot is soft-deleted. A per-lot failure — an unknown ID, or a lot whose stock could not be cleared first (picklist-committed stock, no base unit of measure, or stock remaining after the auto-clear adjustment) — is captured in that lot's `results` row and does **not** abort the rest of the batch, so the call returns `200` even on a partial failure. Inspect `deleted`, `failed`, and `results` for per-lot outcomes. operationId: bulkDeleteLots requestBody: required: true content: application/json: schema: type: object required: - lot_ids properties: lot_ids: type: array description: > Lot IDs to delete. 1–200 per call; duplicates are de-duplicated. minItems: 1 maxItems: 200 items: type: integer minimum: 1 responses: '200': description: > Batch processed. Always returned even when some lots failed — check the per-lot `results`. content: application/json: schema: type: object properties: message: type: string example: Deleted 2 of 3 lot(s). deleted: type: integer description: Number of lots successfully deleted example: 2 failed: type: integer description: Number of lots that could not be deleted example: 1 results: type: array description: Per-lot outcome, one row per requested lot ID items: type: object properties: lot_id: type: integer example: 1234 status: type: string enum: - deleted - failed description: '`deleted` on success, `failed` otherwise' message: type: string description: Outcome detail (e.g. the reason a lot failed) example: Lot deleted. '401': description: Unauthorized content: application/json: schema: type: object properties: message: type: string '422': description: > Validation error — e.g. `lot_ids` missing, empty, over 200 entries, or containing a non-integer. 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. ````