Apply Clearance Suggestions
POST/api/v2/clearance-plans/:clearancePlan/suggestions/apply
Approve markdown suggestions and apply their prices in the background. For each suggestion the price is written to its tier, the compare-at ("was") price is locked at the first reduction, and the product advances to that step; the new prices are then pushed to the plan's channels. Returns 202 with a tracked job id to follow progress.
products:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Body:
- suggestion_ids (required, array of 1–5000 distinct integer suggestion ids): pending or held suggestions of this plan. Ids of other plans or of already-resolved suggestions are not applied.
- price_overrides (optional, object): suggestion id => price to apply instead of the proposed price (number > 0).
A price may never be higher than the current price. A price that breaks the plan floor or a pricing guardrail is not applied: the suggestion becomes held with the reason. Ended plans return 422.
Response (202): data.tracked_job_log_id and message.
Requires a Bearer token with the products read/write scope and the products.manage_pricing permission.
Request
Responses
- 202
- 401
- 403
- 404
- 422
- 429
Accepted
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.