Accept Purchase Order Change
POST/api/spscommerce/sales-orders/:salesOrder/order-changes/:document/accept
Apply the retailer's change to the sales order: new quantities (a decrease cancels the difference), removed lines (cancelled), new prices, added lines (when the item maps to a product), and the ship-by, deliver-by and cancel-after dates. The 3PL is updated the same way as for any edit to the order; decision.fulfillment_note says what happened. All or nothing: if any line can't be applied, nothing changes and the response lists every reason (422). SKU.io does not send a change acknowledgment (865) to the retailer.
orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token and the sales_orders.update permission.
Returns 404 when the change belongs to another order's purchase order, and 409 when someone already accepted or declined it.
Request
Responses
- 200
- 401
- 403
- 404
- 409
- 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
Response Headers
Conflict
Response Headers
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.