Portal: Acknowledge
POST/api/walmart/:integrationInstance/wfs/inbound-shipments/fulfillment-portal/:token/acknowledge
Acknowledge the shipment as ready to ship. Requires box contents to have been submitted first — otherwise returns 422. On success it backstops any unconfirmed component-sourced kit builds (idempotent), marks the packet 'acknowledged' with acknowledged_at set, records an 'acknowledged' portal event, and returns the refreshed portal payload.
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
No request body is required.
Public, token-gated endpoint — no bearer auth. The {token} in the path gates packet access; tenant is resolved by host.
Errors:
- 404 {"message": "This portal link is no longer valid."} when the token is invalid.
- 422 {"message": "Submit your box contents before confirming the shipment is ready."} when box contents have not been submitted yet.
Response: { data: <full portal payload with status 'acknowledged' and acknowledged_at set>, message: "Thank you — the shipment has been confirmed as ready." }.
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.
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.