Run a past export or bulk fulfill again
POST/order-jobs/:id/rerun
Starts a new job with a new record from a past one, and returns that record with status pending. An export is run again from its parameters against the current orders, exactly as posting them to POST /order-exports would — its file can differ from the original. A bulk fulfill is run again on the very rows it was given, which are stored for 90 days after it was started; once they are gone the request is refused and the file has to be uploaded again. Every shipment the original recorded is skipped as a duplicate, so re-running a bulk fulfill only records what it did not get to. Takes the permission that starting the kind takes. One job of each kind runs at a time per merchant account; a re-run while one is running is refused.
Request
Responses
- 201
- 202
- 400
- 401
- 403
- 404
- 429
- 500
- 503
- 504
The merchant is entitled but its OMS environment is not provisioned yet. Provisioning has been kicked off (exactly once) and is in progress; retry the request — it succeeds once the environment is ready. Returned only for identity-token (dashboard) requests bound to an active-entitled merchant, not for secret-key API calls; any such endpoint can return it while provisioning is underway.
The request was rejected. type is invalid_request_error; when the failure is a validation failure code is validation_failed and errors lists every problem found, with field-attributable entries prefixed by the field’s path.
No credentials were supplied, or the identity token / secret key is not valid for the target merchant. type is authentication_error.
The credentials are valid but lack the permission this operation requires. type is permission_error.
No resource exists with the requested identifier. type is not_found_error.
Too many requests. The rate limit is applied per client across all operations. type is rate_limit_error.
The request could not be completed because of an unexpected error. type is api_error.
A dependency needed to serve the request is temporarily unavailable — for every operation the auth service that verifies credentials and resolves entitlement, and on the provisioning routes also the ODUS API the OMS reconciles against. type is api_error. Unlike a plain 500 the condition is transient rather than a fault in the request, so it is worth retrying with backoff.
The request exceeded the processing time limit and was abandoned. type is api_error and code is timeout — unlike a plain 500 the request may still have taken effect.