Send WFS Inbound Shipping Details Email (stage 2)
POST/api/walmart/:integrationInstance/wfs/inbound-shipments/:shipment/fulfillment/shipping-details-email
Stage 2 of the two-stage handoff: send the carrier / pickup details the stage-1 invite promised. The WFS carrier label only exists once a Preferred Carrier is booked against the shipment, so it cannot ride along with the initial email. Uses its own tenant-editable template (wfs_inbound_shipping_details) and attaches the late-stage documents. Does NOT restamp sent_at — that timestamp is the 3PL turnaround clock and belongs to stage 1. Requires the stage-1 email to have been sent (packet.sent_at set) AND late-stage paperwork to exist (packet.can_send_shipping_details true). Same body fields as the stage-1 send.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
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 Content
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.