Confirm Content Update Preview
POST/api/amazon/:integrationInstance/draft-inbound-plans/:draft_inbound_plan/shipments/:plan_shipment/content-updates/:contentUpdatePreviewId/confirm
Apply a previously generated content update preview via the async SP-API confirmShipmentContentUpdatePreview operation. Dispatches the tracked job "Confirm FBA Content Update: {plan name}" and returns its tracked_job_log_id for the tracked job log endpoints. No request body — the preview id comes from List Content Update Previews (contentUpdatePreviewId).
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
The job only starts the async Amazon operation; the tracked job log is completed (or failed) by the operation poller once Amazon reaches a terminal state. On SUCCESS the shipment items are re-synced from Amazon first, so quantity_shipped reflects the accepted deltas, and discrepancy statuses are recomputed.
Errors:
- 404 — the shipment does not belong to this draft inbound plan
- (async) an invalid/expired preview id fails on the tracked job, not the HTTP response
Authentication: Bearer token (PAT).
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.
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
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.