Re-process Shipment
POST/api/shiprush/instances/:integration_instance/shipments/:shipment/re-process
Re-process a failed shipment writeback. For a row in the error state this resets its writeback status to "processed" and clears the error so it drops off the error KPI. For a true re-mint of the fulfillment, replay the underlying shipnotify from the Webhooks tab instead. A row not in the error state is returned unchanged.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
Path parameter:
- instance: the numeric ID of the ShipRush integration instance.
- shipment: the shipment id.
No request body is required. A shipment id / instance mismatch returns 404.
Authenticate with a Bearer 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
Response Headers
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
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.