Walmart scraper API

E-commerce · v1.1.0 · walmart_search

$0.002 / product

$2.00 / 1K · pay per delivered product

A Walmart scraper API for walmart.com search: one keyword in, one row per product out — item id, title, current and struck-through price, star rating and review count, the seller behind the offer, availability and the sponsored flag. Sort by relevance, price, rating or best seller and paginate to a hundred rows per run.

By Aldo Morese, founder of QuanticData · Published Aug 21, 2026 · Updated Sep 3, 2026

Run in dashboard See the request

$0.002 per delivered product · $2 free every month · Failed runs never billed

What it does

What a Walmart scraper API does

Walmart publishes everything a price-intelligence table needs inside the page's own data payload, and that is what this collector reads — prices arrive as both the displayed string and a numeric column, so $29.99 lands ready for arithmetic. The robot wall Walmart runs in front of that payload is our problem: the fetch retries on fresh US exits until the data answers, and you pay per delivered product, not per attempt.

The seller and sponsored columns are what separate a catalog from a ranking study. Marketplace offers hide behind the same search tiles as Walmart's own stock, and paid placements sit above organic ones — with both flagged per row you can price-match against first-party stock only, or measure how much of a shelf is bought.

Inputs

The whole request. Anything you leave out falls back to the default shown in the catalog.

Input	Type	Required	What it does
`query`	string	yes	What to search, e.g. "coffee maker".
`sort`	string	no	Result order (default best match). One of: `best_match`, `price_low`, `price_high`, `best_seller`, `rating`.
`max_results`	integer	no	How many products to deliver at most (1–100). You pay only for delivered products.

Outputs — 25 fields, one row per product

What one product looks like

Every delivered product carries these fields. Nullable means the source did not publish it — the field stays empty instead of being guessed.

Field	Type	What it holds
`rank`	integer	1-based position across the merged pages.
`page`	integer	Search page the row came from.
`item_id`	string	Walmart US item id.
`title`	string	Product title.
`brand`	string · nullable	Brand when the payload carries it.
`url`	string · nullable	Clean product URL.
`price`	string · nullable	Current price as shown (e.g. $29.99).
`price_value`	number · nullable	Numeric current price.
`list_price`	string · nullable	Struck-through was-price when discounted.
`currency`	string	Always USD.
`rating`	number · nullable	Average star rating (1–5).
`reviews`	integer · nullable	Review count.
`seller`	string · nullable	Seller name (Walmart or marketplace).
`sponsored`	boolean	True for paid placements.
`availability`	string · nullable	Stock line when shown.
`image`	string · nullable	Thumbnail URL.
`in_stock`	boolean · nullable	True when Walmart lists the item as in stock.
`seller_id`	string · nullable	Walmart seller id.
`offer_id`	string · nullable	Offer id of the displayed price.
`product_type`	string · nullable	Walmart catalog product type ("Toaster Ovens").
`has_variants`	boolean	True when the item has variants (size, colour…).
`condition`	string · nullable	New, Restored, Pre-owned or Open box.
`badges`	string[]	Card badges ("Best seller", "100+ bought since yesterday"…).
`fulfillment`	string[]	Fulfilment options offered (delivery, pickup, shipping).
`image_large`	string · nullable	Full-size image URL.

Integration

One POST, typed rows

Base URL https://api.quanticdata.io/v1, Bearer auth, the same key as every other Data API. Endpoint: POST /v1/scraper/collectors/walmart_search/run.

curl -X POST https://api.quanticdata.io/v1/scraper/collectors/walmart_search/run \
  -H "Authorization: Bearer $QD_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"coffee maker","max_results":20}'

import requests

r = requests.post(
    "https://api.quanticdata.io/v1/scraper/collectors/walmart_search/run",
    headers={"Authorization": f"Bearer {QD_API_KEY}"},
    json={
        "query": "coffee maker",
        "max_results": 20
    },
    timeout=120,
)
for row in r.json()["payload"]["results"]:
    print(row)

const res = await fetch(
  "https://api.quanticdata.io/v1/scraper/collectors/walmart_search/run",
  {
    method: "POST",
    headers: {
      Authorization: `Bearer ${process.env.QD_API_KEY}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({"query":"coffee maker","max_results":20}),
  },
);
const { payload } = await res.json();
console.table(payload.results);

claude mcp add quanticdata \
  -e QUANTICDATA_API_KEY=qd_live_your_key_here \
  -- npx -y quanticdata-mcp

# then, in the chat:
> run the walmart_search collector with query="coffee maker" and max_results=20

Example response

POST /v1/scraper/collectors/walmart_search/run

$ curl $QD/walmart_search/run \
    -H "Authorization: Bearer $QD_API_KEY" \
    -d '{"query": "coffee maker", "max_results": 20}'
{ "status": "done", "count": 20,
  "results": [
    {
      "item_id": "…",
      "title": "…",
      "brand": "…",
      "url": "…" } ],
  "cost": 0.04 }
# 20 products × $0.002 · nothing delivered, nothing charged

Try it

Walmart search, running now

Change the input and run it against the live collector — nothing to install, no sign-up.

Run it from your own code, on your own inputs

Same collector, same rows — $2 of free API credit every month, no card.

Get my free API key

You send query and sort; the run goes out through a residential exit and comes back as products with rank, page and item_id — 25 fields on every row — and you are billed $0.002 for each product actually delivered, nothing for a run that delivers none.

$0.002 / product1,000 products on the free $2 every month

Semantic inputquery, sort, max_results — no URL lists

Up to 100products per run, pagination handled for you

No browserread over HTTP/TLS — cheaper and faster than rendering

Pricing

Walmart scraper API pricing

$0.002 per delivered product. A run that delivers nothing costs nothing: blocked pages, challenges and retries are on us, and the $2 monthly allowance covers about 1,000 products before you spend anything.

$0.002per delivered product$2 per 1,000 delivered products

1,000 productson the free allowance$2 every month, no card

Zero rowszero chargeblocks, captchas and retries are on us

−30%on volume tiersthe catalog returns your key's price

Pay as you go

$0/mo

$2 free credit / month
60 requests / min
List unit prices

Starter

$19/mo

$15 free credit / month
300 requests / min
10% off unit prices

Growth

$79/mo

$50 free credit / month
600 requests / min
20% off unit prices

Scale

$299/mo

$250 free credit / month
1,200 requests / min
30% off unit prices

Same wallet, same key and same $2 monthly allowance as every other Data API. Prices are launch pricing read live from the billing config — GET /v1/scraper/collectors returns the price your key actually pays.

What people build with the Walmart scraper API

Three shapes of work this endpoint was designed around.

Price intelligence

Track your assortment's keywords daily: current price, was-price and availability per item id, diffable run over run — the was-price column dates promotions for you.

Marketplace share analysis

The seller column splits Walmart first-party from marketplace offers, so category share and buy-box behaviour become countable.

Shelf-position monitoring

Rank plus the sponsored flag show where brands actually appear for a query, organic versus paid — the retail-media picture brands pay to see.

Walmart scraper API versus rolling your own

The differences that actually cost time when you build this in-house.

	DIY scraper	This collector
Bot wall	PerimeterX challenges to solve yourself	Retried on fresh US exits until the payload answers
Prices	Strings scraped from tiles	Displayed string + numeric value, current and was-price
Paid placements	Indistinguishable from organic results	sponsored flag on every row

Walmart scraper API: the POST to the walmart_search collector, 20 products delivered and the bill, 20 × $0.002 = $0.04 in usage.cost_usd; zero products would cost $0. — The same call you would paste into a terminal: a Bearer key, query and sort in the body, and back the envelope every QuanticData endpoint returns — type, message, payload — where count is how many products arrived and usage.cost_usd is $0.04, which is 20 × $0.002. A run that delivers nothing costs nothing. The key is good for 60 req/min on the free tier.

Sources and standards

The platform documentation and standards this collector is built against — check any claim on this page against the primary source:

FAQ

Questions we get about the Walmart scraper API.

Something else? Ask us

Which Walmart sites does it cover?

walmart.com — the US catalog, in USD. International Walmart properties run different platforms and are not covered by this collector.

Does it return marketplace sellers or only Walmart stock?

Both, flagged: every row carries the seller name, so filtering to first-party stock (seller = Walmart.com) or to marketplace offers is one predicate on your side.

How fresh are prices?

Each run fetches live search pages — rows reflect what walmart.com showed at run time. For monitoring, schedule the same query and diff by item id.

Is there a free Walmart scraper API?

Every account gets $2 of credit every month with no card, which is about 1,000 delivered products on this endpoint at $0.002 each. It renews monthly, and a run that delivers nothing is never billed — so a failed or blocked attempt does not eat the allowance.

How much does one run cost?

Multiply the rows you actually receive by $0.002. A run capped at 100 products — the maximum for this collector — costs $0.2 if every row comes back, and less when the source has fewer. Volume tiers take up to 30% off, and GET /v1/scraper/collectors returns the price your key actually pays.

Run the Walmart scraper API now

$2 of free credit every month, no card. Your key returns its own prices from GET /v1/scraper/collectors.

Run in dashboard