Skip to main content
PUT
Update a production batch

Authorizations

Authorization
string
header
required

Authenticate using a bearer token. To create a token, navigate to /settings/api-tokens and click Create API Token.

Path Parameters

batchId
integer
required

Body

application/json
name
string | null

Name of the production batch.

Maximum string length: 255
vendor_id
integer | null

Vendor associated with the batch.

co_manufacturer_id
integer | null

Alias of vendor_id. When both are sent, vendor_id wins. Sending either key (including an explicit null to clear) updates the vendor; omitting both leaves the existing vendor unchanged.

production_warehouse_id
integer | null

ID of the warehouse where the batch is produced. Omit (or send null) to leave it unchanged; it cannot be cleared through the API.

destination_warehouse_id
integer | null

ID of the warehouse that receives the finished goods. Omit (or send null) to leave it unchanged; it cannot be cleared through the API.

notes
string | null

Free-form notes for the batch.

payment_terms
string | null

Payment terms for the batch. Must exactly match one of Luminous's standard payment term names (e.g. Net 30, 50/50, Due on Receipt, 100% Down); matching is case-sensitive and any other value returns 422. Send null to clear the terms.

Maximum string length: 255
Example:

"Net 30"

expected_completion_date
string<date> | null

The batch's own expected completion date. Can be set in any status. Omit (or send null) to leave it unchanged; it cannot be cleared through the API. This does not change the work orders' dates; use PATCH /production-batches/{batchId}/work-orders/fields for that.

Example:

"2026-11-20"

custom_fields
object | null

Custom field values for the production batch, keyed by field label.

Example:

Response

Successful response

data
object