Update one order
Replaces THREE legacy routes — patch, resolve-design and resolve-label — because from a seller's point of view they were one act: here is the missing piece, put my order back in the queue. What you send decides which.
Sending image_url to an order that is ON_HOLD releases it back to where it was held from. Sending label_url and tracking_number together attaches a shipment through the same code path the scan stations use, so the seller notification and the audit trail are identical.
Absent means leave it alone. Unknown field names are rejected rather than ignored — a typo you can see beats a silent no-op.
quantity is the one field locked after assignment: it changes what somebody has to make.
Send an Idempotency-Key when you may retry, for example from an offline queue: a replayed label link then returns the first answer instead of attaching again.
Request
- Base URL: https://0.0.0.0:3000/api/v1
- URL: https://0.0.0.0:3000/api/v1/orders/{id}
- Auth: API key in header x-api-key
Path parameters
The order id.
Headers
Optional. Reuse the same value on every retry of the same update; see Idempotency.
Request body
Response
The updated order in full, so you never need a follow-up GET. meta.released says whether a hold was lifted.
Changes
No recorded changes to this operation across all 1 revision of this API.