Retry Failed NuORDER Send
POST/api/nuorder/instances/:integrationInstance/fulfillments/failures/:shipment/retry
Retries a failed attempt. A failed shipment re-sends its fulfillment if NuORDER still does not have it; a failed cancellation re-runs the order's cancellation passback, which only sends quantities NuORDER does not already show cancelled. A manual retry is sent even when the portal's tracking sync switch is off; it is refused (422) when sending cancelled quantities is turned off for the portal, or when this environment may not write to NuORDER.
integrations:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Bearer token (integrations scope) and the sales_orders.fulfill permission.
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.