Remove Clearance Plan Products
DELETE/api/v2/clearance-plans/:clearancePlan/products
Take products out of a plan. Their current (clearance) price stays as it is; their open suggestions are skipped with the reason "Removed from the plan". For each removed product the plan had already marked down, the compare-at ("was") price the plan set is cleared on every listing it touched: the clear is pushed to the channels straight away and retried on later price pushes until each channel confirms it. The removal sticks: the products are recorded in the plan's scope.excluded_product_ids, so a filter-scoped plan's daily evaluation does not enrol them again while they still match the filter. Adding a product back with Add Clearance Plan Products lifts its exclusion. Body:
- product_ids (required, array of up to 5000 distinct integer product ids). filters is not accepted for removal.
products:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Response: data.removed (how many were removed) and message.
Requires a Bearer token with the products read/write scope and the products.manage_pricing 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 — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
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.