Run Amazon Min/Max Fix
POST/api/v2/sales-channels/:integrationInstance/prices/amazon-allowed-price/fix
Send a bulk Amazon min/max fix as a background job and record it as a price push run with trigger amazon_limits_fix. The job waits for any running price push on the channel, then sends one limits-only feed per marketplace and re-reads the sent offers about 2 minutes later. Returns 422 when no row has anything to send.
integrations:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token. Requires the integrations.update permission.
Targets, exactly one of: ids (row ids from List Amazon Min/Max Listings), product_listing_ids (every marketplace offer of those listings, narrowed by optional country_codes), or filter (the same keys as the list's filter, e.g. {"status":"above_max"}). At most 5,000 rows; a filter matching more returns 422.
Actions: fit_to_price (raise the max / lower the min to the price, only on the side(s) the price breaks), apply_managed (send what SKU.io's Amazon min/max settings resolve to), clear (remove the chosen side(s); the minimum is kept while an Automate Pricing rule is attached), send_held (send the price SKU.io held and widen the side it breaks).
sides: ["min","max"] by default. Every fix except send_held keeps our_price at the price Amazon holds now (the last read of the offer, in the marketplace's currency). An offer Amazon was never read for uses the price the last live push sent to that marketplace, in that marketplace's currency (never converted at today's rate); with neither, the row is skipped with the reason. Grade and Resell (amzn.gr.) offers, offers whose price is mastered on Amazon, and marketplaces SKU.io doesn't price are never sent; each row says why.
A limits-only fix keeps the price Amazon holds; a row Amazon was last read for before SKU.io's latest price was sent there is skipped ("Amazon hasn't confirmed SKU.io's latest price for this offer yet"). The fix re-reads the targeted offers from Amazon before sending.
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 Content
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.