List Orders Affected by a Correction
GET/api/v2/products/:product/component-revisions/:revision/affected-orders
Paginated sales orders affected by a corrective (back-dated) revision's window, with a before -> after component diff and a shipped/unshipped summary. Bundles only — for a kit the response is { supported:false } with an explanatory message (kits have no per-order components). Filter with status=all|unshipped|shipped.
products:readGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token.
Each order carries skip_reason (null when it will be rewritten in place; otherwise why the rewrite job will skip it, e.g. fulfillment activity or tax/discount allocations). Component rows are grouped per bundle occurrence on the order via sales_channel_line_id, and order_date is the calendar day in the account's timezone.
Request
Responses
- 200
- 401
- 403
- 404
- 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.
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.