Send NuORDER Fulfillments
POST/api/nuorder/instances/:integrationInstance/fulfillments/submit
Sends fulfillments NuORDER does not have yet as NuORDER shipments. Pass ids to send specific fulfillments; omit ids to send every pending fulfillment of the portal (up to 500 per request) — the List Pending NuORDER Fulfillments set, so a failed or unconfirmed send is not re-sent (use Retry Failed NuORDER Send). With nothing pending, the call returns 422 "Nothing is waiting to be sent to NuORDER. Retry failed shipments from the Failed tab." Fulfillments NuORDER already has are skipped, so repeating the call never duplicates a shipment. Work runs in the background, one job per NuORDER order.
integrations:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Bearer token (integrations scope) and the sales_orders.fulfill permission.
Body: ids (optional, array of integer fulfillment ids, max 500).
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 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.