Make Sales Order Lines
POST/api/manufacturing/make-to-order/make
Starts a background job that raises a manufacturing order for each line, one line at a time, exactly as "Make to order" on the sales-order line does: the order is confirmed, carries the line's options and its output is held for that line. A line that cannot be made is skipped with its reason; a line short of components is still raised. Returns 202 with the tracked job ID. The job's results hold raised_count, skipped_count, failed_count, has_failures and rows (per line: sales_order_line_id, sales_order_id, sales_order_number, sku, quantity, outcome raised|skipped|failed, message, manufacturing_orders).
manufacturing:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Body: sales_order_line_ids (1–500 distinct existing line IDs), or apply_to_all: true with filters (the list's own params: filter_groups, search, search_columns, dismissed, …) to act on every matching line, up to 500. With apply_to_all, only lines that can be made (ready or short) are made; the response's data.lines says how many.
Authentication: Bearer token with the manufacturing and orders scopes, plus the manufacturing view and sales-order update permissions.
Request
Responses
- 202
- 401
- 403
- 422
- 429
Accepted
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Unprocessable Content
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.