> ## 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 void or delete invoices > Void or delete up to 50 invoices in one call. Each invoice follows the same rules as the single-invoice endpoints (`POST /invoices/{invoiceId}/void` and `DELETE /invoices/{id}`). Invoices are handled one at a time, so one refusal or failure does not stop the rest. The response is `200` whenever the request itself is valid. Check each entry in `results` for its outcome. An ID that does not match an invoice is returned as `skipped` with the reason `Invoice not found.`. Requires the API token user to have the invoice update permission (`invoices.update`). ## OpenAPI ````yaml /api-reference/build.yaml post /invoices/bulk-void-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: Freight description: >- Freightview LTL freight — quotes, booking and documents for fulfillment orders - 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 Warehouse description: >- Warehouse-floor lookups for PickFlow — barcode resolution, bin and product stock, bin search, and receivables - 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: Drive description: > Browse, upload, tag and manage files in your Luminous Drive. An API token sees the shared drive only, never My Files or restricted folders and files. Every write and download made through the API is recorded in the file's activity log (`GET /file-cabinet/files/{id}/activity`) with `actor_kind: api_token`. - name: Integration Mappings description: Manage integration mappings for external systems - name: Integration Field Mappings description: Manage field-level mappings between Luminous and external systems - name: Automations description: Create, test, and inspect automation rules and their runs paths: /invoices/bulk-void-delete: post: tags: - Invoices summary: Bulk void or delete invoices description: > Void or delete up to 50 invoices in one call. Each invoice follows the same rules as the single-invoice endpoints (`POST /invoices/{invoiceId}/void` and `DELETE /invoices/{id}`). Invoices are handled one at a time, so one refusal or failure does not stop the rest. The response is `200` whenever the request itself is valid. Check each entry in `results` for its outcome. An ID that does not match an invoice is returned as `skipped` with the reason `Invoice not found.`. Requires the API token user to have the invoice update permission (`invoices.update`). operationId: bulkVoidDeleteInvoices requestBody: required: true content: application/json: schema: type: object required: - action - ids properties: action: type: string enum: - void - delete description: Whether to void or delete the listed invoices ids: type: array minItems: 1 maxItems: 50 items: type: integer minimum: 1 description: >- IDs of the invoices to process (1 to 50). Duplicates are processed once. delete_sales_order: type: boolean default: false description: > `void` only. Also delete each invoice's linked sales order. Only a sales order that Luminous created from the invoice is deleted. example: action: void ids: - 101 - 102 - 103 delete_sales_order: false responses: '200': description: Request processed; one result per invoice ID, in the order given content: application/json: schema: type: object properties: data: type: object properties: action: type: string enum: - void - delete summary: type: object description: Count of invoices per result properties: voided: type: integer deleted: type: integer skipped: type: integer failed: type: integer results: type: array items: type: object properties: id: type: integer description: Invoice ID result: type: string enum: - voided - deleted - skipped - failed reason: type: string nullable: true description: >- Why the invoice was skipped, or the error if it failed. `null` on success. example: data: action: void summary: voided: 2 deleted: 0 skipped: 1 failed: 0 results: - id: 101 result: voided reason: null - id: 102 result: voided reason: null - id: 103 result: skipped reason: Invoice is already void. '401': description: Unauthorized content: application/json: schema: type: object properties: message: type: string '403': description: Token user lacks the invoice update permission content: application/json: schema: type: object properties: message: type: string '422': description: >- Validation error (missing or invalid `action`, or `ids` empty or longer than 50) content: application/json: schema: type: object properties: message: 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. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.