Submit NuORDER Tracking
POST/api/nuorder/instances/:integrationInstance/orders/:order/submit-tracking
Queues a background job that sends the order's fulfillments NuORDER does not have yet (or the one given) to NuORDER, one NuORDER shipment per fulfillment, and returns the job's tracking id.
integrations:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Each shipment carries the carrier (fedex, ups, usps, dhl, otherwise the carrier name in lowercase), every tracking number on the fulfillment, and the shipped sizes grouped by NuORDER product, in NuORDER quantities (packs for prepacks; a quantity that is not a whole number of packs is left out and reported). NuORDER emails the retailer unless the instance suppresses shipment emails, and moves the order to shipped once every unit has shipped.
A manual submit ignores the instance's Tracking sync switch. Outside production, shipments only go to a simulated portal unless explicitly enabled; the job then completes with the reason. A fulfillment already sent is never sent again (NuORDER cannot edit it through SKU.io).
Body:
sales_order_fulfillment_id(integer, optional) — send only this fulfillment of the order.
Errors: 404 when the order belongs to another instance; 422 when the order has no SKU.io sales order yet or nothing is left to send.
Authentication: Bearer token (Personal Access Token) with permission to fulfill sales orders.
Without a fulfillment id it sends only fulfillments waiting to be sent; fulfillments whose earlier send failed or has an unknown outcome are left to the failed-sends retry/dismiss endpoints.
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
Response Headers
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.