Set Up Listings for WFS
POST/api/walmart/:integrationInstance/wfs/conversions
Sends the ready listings to Walmart to be set up for WFS, in one "Convert existing item to WFS" feed. Walmart keeps the seller-fulfilled offer: it ships from WFS while WFS has stock and sends orders back to the seller when WFS runs out.
integrations:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Listings that aren't ready, are already on WFS or have no Walmart listing are left out and returned under skipped with what they need. When Walmart finishes the feed, accepted listings are marked WFS-fulfilled (so the Send Planner can send to them) and rejected ones keep Walmart's reason; read both back from List Listings to Set Up for WFS.
Body:
skus(array, required, 1-100 distinct seller SKUs)compliance(object, required), Walmart's safety answers applied to every listing:battery_technology_type(string, required): must beDoes Not Contain a Batteryelectronics(boolean, required)chemical,aerosol,pesticide(boolean, required): must be falseprop65_warning_required(boolean, required)prop65_warning_text(string, nullable, max 2000): required whenprop65_warning_requiredis true
Items with batteries, chemicals, aerosols or pesticides need a safety data sheet and label images that Walmart only accepts in Seller Center, so those answers are rejected with 422.
Returns 429 when the integration's feed rate limit is exhausted. Requires a Bearer token and the integrations.update permission.
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.