Ship an order across multiple packages

POST

/orders/v4/orders/:purchaseOrderId/multi-package-shipping

Walmart-specific extension of /shipping. Each package carries its own tracking number, carrier, dimensions, and the order lines it covers. Maps onto FMS’s existing shipments[] envelope (one FMS shipment per v4 package). Inspired by gmp-orders-mono’s shipOrderV2 (multiPackageShipping) operation; we hoist packages[] to the top level rather than nesting it under each line so the request stays self-evidently package-oriented.

Walmart-specific extension of `/shipping`. Each package carries its own tracking number, carrier, dimensions, and the order lines it covers. Maps onto FMS's existing `shipments[]` envelope (one FMS shipment per v4 package). Inspired by gmp-orders-mono's `shipOrderV2` (multiPackageShipping) operation; we hoist `packages[]` to the top level rather than nesting it under each line so the request stays self-evidently package-oriented.

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

Path parameters

purchaseOrderIdstringRequired

Request

This endpoint expects an object.

packageslist of objectsRequired

Response

Success

purchaseOrderIdstringOptional

shippedAtdatetimeOptional

packagesAcceptedintegerOptional

Number of packages[] entries successfully forwarded to FMS — echoed back so callers can sanity-check against what they sent.

Errors

400

Bad Request Error

403

Forbidden Error

404

Not Found Error

429

Too Many Requests Error

500

Internal Server Error

503

Service Unavailable Error