Get 3PL Order Label Settings
GET/api/walmart/:integrationInstance/sww-label-settings
Get the settings for buying Ship With Walmart labels for seller-fulfilled Walmart orders that a 3PL warehouse ships. When on, SKU.io buys the label through Walmart when the order is routed to a 3PL warehouse and hands it to the 3PL with the order.
integrations:readGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token.
Response fields:
purchase_for_3pl_orders(boolean): whether a Ship With Walmart label is bought automatically for each seller-fulfilled Walmart order shipped from a 3PL warehouse. Off by default.service_preference(string):cheapest(the lowest rate that arrives by Walmart's estimated delivery date, else the cheapest overall) ormatch_requested(the cheapest rate in the speed tier the buyer chose: Standard, Express or Value).label_provided_shipping_method(object|null):idandnameof the shipping method the fulfillment order is switched to once its label is bought, so the 3PL ships on the label rather than buying postage. Null until the setting is turned on or a method is chosen.fallback_box(object|null):length,width,heightandunit(inorcm) used to rate a multi-unit order when no box size is known. Without one, such orders wait for a box size.three_pl_warehouses(array): every warehouse fulfilled by a 3PL integration, with how it receives the label:id,name,provider(the name of the 3PL connection the warehouse ships through),integration_instance_id(that integration, or null),attach_to_order(the label is attached to the order sent to the 3PL),email_warehouse(the label PDF is emailed to the warehouse),printed_by_provider(the 3PL prints the label itself on request) andaccepts_channel_labels(false when the 3PL's integration cannot receive a channel label at all). A warehouse with the three delivery switches off, or that does not accept channel labels, needs the label sent to it by hand.
Path parameters:
- integrationInstance (required): Walmart integration instance ID.
Request
Responses
- 200
- 401
- 403
- 404
- 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.
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.