Returns the shipping label for an existing shipment
Deprecated
Returns the purchased shipping label for a shipment in the requested file format for printing.
Authorization
walletAuth In: header
Path Parameters
Query Parameters
"PDF"Value in
- "PDF"
- "PNG"
- "ZPL"
- "ZPL300"
- "ShippingServiceDefault"
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/mfn/v4/shipments/string/label"{ "customTextForLabel": "string", "dimensions": { "length": 0, "width": 0, "unit": "inches" }, "fileContents": { "contents": "string", "fileType": "application/pdf", "checksum": "string" }, "labelFormat": "PDF", "standardIdForLabel": "WalmartOrderId"}Purchases shipping and returns a shipping label POST
Creates a shipment for an order, purchases a shipping label from the selected carrier, and returns the label for printing.
Returns orders created or updated during the specified time period GET
Returns orders matching the given filters. Orders are fulfilled by sellers (WFS or seller-fulfilled). Maps to Walmart OMS order queries. ### Current limitations (roadmap) The underlying the Orders service backend does not yet support every filter declared below. Calls using any of the following will return `400 Bad Request` with `code=FILTER_NOT_SUPPORTED` and a human-readable `message` explaining the specific rejection. Phase 2 will lift these one-by-one as the underlying service adds capability. | Filter | Status today | Reason | |---|---|---| | `createdAfter`, `createdBefore` | Rejected (400) | the Orders service does not accept date-range filters at the order level. | | `lastUpdatedAfter` | Rejected (400) | the underlying service has no order-level update-date index. | | `orderStatuses` with >1 value | Rejected (400) | the underlying service accepts one status per call; pass a single value or omit to match all. | | `fulfillmentTypes` | Rejected (400) | the underlying service accepts one shipNodeType per call; multi-type fan-out is Phase 2. | These parameters remain in the contract (rather than being removed) so that SDKs generated today stay forward-compatible with the the roadmap surface — your code keeps compiling, only the runtime behaviour changes when Phase 2 ships. Until then, omit them or handle the documented 400 gracefully. The `tools/loadgen-orders.sh --contract` smoke sweep exercises the rejection contract on every run.
