Skip to main content

List Prep Details

POST 

/api/amazon/:integrationInstance/draft-inbound-plans/:draft_inbound_plan/list-prep-details

Fetch Amazon's prep requirements (prep category + prep types) for every MSKU on a draft inbound plan. SKU.io sends all of the plan's MSKUs to Amazon's listPrepDetails operation and returns the per-MSKU results. Backs the plan configuration step's "Fetch Amazon Prep Requirements" action.

Resilient to invalid MSKUs: Amazon 400-rejects the whole batch if any single MSKU is not recognised for the seller account. When that happens, SKU.io parses the rejected MSKUs, drops them, and retries with the remaining valid SKUs — so one bad SKU no longer dead-ends the whole step. The rejected SKUs are returned in the top-level invalid_mskus array (excluded from data) so the UI can prompt the user to remove or remap them.

A 400 that is NOT an invalid-MSKU error (or that names SKUs we did not send) surfaces as a 422 ValidationException.

Authentication: requires Bearer token.

No request body — the MSKU list is derived from the plan's line items.

Response: data is an array of prep detail items (msku, prepCategory, prepTypes[], labelOwnerConstraint, prepOwnerConstraint, allOwnersConstraint); invalid_mskus is an array of the MSKU strings Amazon rejected as "not valid".

Authorization

Any valid API token can call this endpoint — no specific scope required. Manage tokens.

Request

Responses

OK

Response Headers
    Content-Type