Acknowledge Fulfillment Order (3PL Portal)
POST/api/amazon/:integrationInstance/draft-inbound-plans/fulfillment-portal/:token/acknowledge
Confirms, from the anonymous 3PL/supplier portal, that the fulfillment order is packed and ready to ship. Access is granted solely by the opaque :token in the URL (the packet's portal token from the emailed link) — no bearer auth. No request body.
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
Gating: box contents must have been submitted first, and pallet details as well when the shipment moves LTL/freight — otherwise a 422 with error key not_ready_to_confirm explains what is missing (the same gating is exposed as can_confirm / confirm_blocked_reason on the portal payload).
Side effects on success: any component-sourced kits not yet explicitly confirmed built are realized (idempotent backstop — confirming ready-to-ship implies the kits were built), the packet status moves to acknowledged with an acknowledged_at timestamp, and the confirmation is audit-logged as a portal event. Returns the refreshed portal payload.
Returns 404 when the token is expired, rotated, or revoked.
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
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.