Retry Lifecycle Sell-out
POST/api/v2/product-lifecycle/sell-outs/retry
Queue the sell-out action again for products whose last sell-out run failed or was stopped, once the channel problem behind it is fixed, instead of waiting for the nightly sweep. The sell-out action is what ends or deletes channel listings and archives a product when it sells out in a state whose policy says so. This call only queues the runs; each one re-checks the product and its listings when it runs.
products:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Body:
- product_ids (required, array of 1–500 distinct integer product ids): the products to retry
Response fields:
- message: a sentence saying what happened - every product queued, none queued ("Nothing to retry: ..."), or some of them
- queued: product ids whose sell-out run was queued again
- skipped: product ids with nothing to retry — the last sell-out run did not fail or stop, the product has never had one, or it is not in a state the sell-out action covers
Returns 422 when product_ids is missing or empty ("Select at least one product."), has more than 500 entries ("Retry up to 500 products at a time."), or contains duplicates or non-integers.
Requires a Bearer token with the products read/write scope and the products.manage_lifecycle permission.
Request
Responses
- 200
- 401
- 403
- 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.
Unprocessable Entity
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.