Bulk Update NuORDER Products
POST/api/nuorder/instances/:integrationInstance/products/bulk
Runs map (link by UPC / SKU only), create_products (link, then create SKU.io products for the rest), unmap, archive, unarchive, delete or revenue (map to a revenue line) over selected size IDs or every size matching the product filters. Up to 50 selected sizes are unmapped, archived, unarchived, deleted or revenue-mapped immediately; everything else runs in the background and returns its tracked job ID. Selected IDs that belong to another integration are ignored.
products:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
archive hides sizes from the list and stops their inventory push; unarchive restores them; delete removes the sizes and their SKU.io mapping from SKU.io (the SKU.io products and orders stay). revenue maps each size to a revenue financial line type, so future NuORDER orders book it as a revenue line instead of a sales order line (no SKU.io product is created; a size already linked to a product keeps that link); pass financial_line_type_id: null to clear the revenue mapping. Sizes already on the chosen type, or with no revenue mapping to clear, are skipped and not counted in changed. None of these change anything in NuORDER — a deleted size still listed there comes back on the next full catalog refresh.
Body: action (required: map, create_products, unmap, archive, unarchive, delete, revenue), selection.type (required: selected, filtered), selection.ids (integer[], required when selected), selection.filters (object, same keys as List NuORDER Products filters), field_mappings (array, optional, create_products only — one-off {listing_field, sku_field, parsers} rules applied to the products the run creates, over the saved ones; see Get NuORDER Field Mappings), financial_line_type_id (integer or null, must be present when action is revenue; must be a revenue-classified financial line type, null clears the mapping).
Authentication: Bearer token (Personal Access Token).
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
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.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Entity
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.