Confirm AWD Inbound Order
POST/api/amazon/:integrationInstance/awd/inbound-orders/:awd_inbound_order/confirm
Confirm a DRAFT order at Amazon. Amazon then creates the order's AWD shipment, which is fetched and linked straight away; a purchase order the plan came from is pointed at the AWD warehouse. Labels and tracking become available once the shipment exists.
integrations:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Errors. A refused action answers with {message, code, errors: [{msku, message, code}], details}: 422 when SKU.io refuses it before calling Amazon (wrong status, plan not ready) or Amazon rejects it (code: rejected); 403 not_authorized when Amazon has not granted the AWD role (reconnect the account); 404 not_found when Amazon no longer knows the order; 409 conflict while Amazon is still validating the order or refuses the change (details.amazon_reason); 429 rate_limited; 504 timeout. A 409, 429 or 504 changed nothing and can be retried.
Requires the integrations.sync permission.
Returns 404 when the order belongs to a different Amazon account than the one in the URL.
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
Response Headers
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Conflict
Response Headers
Unprocessable Entity
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.