/walmart/sellers

POST /api/walmart/sellers

Price: 10 credits

Get Walmart marketplace seller (storefront) details by seller id (or storefront URL): store name, type, Pro Seller status, rating and review counts, logo and banner, about description, location and contact info.

How to use it

Fetch a single Walmart marketplace seller by catalogSellerId (numeric) or a /seller/ storefront URL. Returns one item with name (storefront) and legal_name, type (EXTERNAL=third-party marketplace, INTERNAL=Walmart), is_pro_seller, description, rating, review_count, text_review_count, image (logo), banner, address (street), location/city/state/country/postal_code, email, phone and status/is_active.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• seller string required — Walmart seller catalogSellerId or a seller storefront URL containing it (examples: "102720383", "https://www.walmart.com/seller/102720383"; minLength: 1)

Response

• @type string (default: "WalmartSeller")
• id string required
• url string required
• name string nullable
• legal_name string nullable
• type string nullable
• is_pro_seller boolean nullable
• description string nullable
• rating number nullable
• review_count integer nullable
• text_review_count integer nullable
• image string nullable
• banner string nullable
• location string nullable
• address string nullable
• city string nullable
• state string nullable
• country string nullable
• postal_code string nullable
• email string nullable
• phone string nullable
• status string nullable
• is_active boolean nullable
• is_alcohol_seller boolean nullable
• is_qsr_seller boolean nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Seller not found (well-formed but nonexistent seller id, or page has no seller) Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.