Confirm Kits Built (3PL Portal)
POST/api/amazon/:integrationInstance/draft-inbound-plans/fulfillment-portal/:token/kits-built
Confirms, from the anonymous 3PL/supplier portal, that the kits on the fulfillment order have been physically assembled. 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.
Side effects: the reserved kit components are converted into finished kit stock and the kits are allocated to their transfer lines; the confirmation is audit-logged as a portal event. The operation is idempotent — lines already built are skipped, and calling it when there is nothing to build is a safe no-op.
Returns the refreshed portal payload (kits_pending_build becomes false; kit_build_manifest still lists what was built). 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
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.