Walmart Data Extractor
Walmart product data from a listing URL, a product URL or a plain keyword as typed JSON: item ID, name, brand, seller, price and canonical URL, enriched from each product page. 1 credit per page. No Walmart login.
Free API key · 1 credit per page of products · failed calls free
// GET /api/v2/walmart-data-extractor/?urls=laptop · sample from the catalog { "success": true, "data": { "urls": "https://www.walmart.com/search?q=laptop", "page": 1, "page_size": 58, "details_fetched": 56, "products": [ { "name": "Acer Chromebook 315 15.6” Full HD Laptop, 8GB RAM 128GB, ChromeOS", "us_item_id": "20349310960", "brand": "Acer", "seller_name": "Walmart.com", "price_info": { "current_price": { "price": 199.0, "price_string": "$199.00", "currency_unit": "USD" } }, "canonical_url": "/ip/Acer-Chromebook-315-.../20349310960", "detail_fetched": true, "input_url": "https://www.walmart.com/search?q=laptop", "scraped_at": "2026-09-15T00:00:00.000Z" } ], "next_cursor": "eyJ1IjoiaHR0cHM6Ly93d3cud2FsbWFydC5jb20vc2VhcmNoP3E9bGFwdG9wIiwicCI6Mn0" } }
| field | value | type | Has a value✓ |
|---|
Scrapier's Walmart Data Extractor returns product data from a Walmart listing, product URL or keyword as JSON, a page at a time: us_item_id, name, brand, seller_name, price_info, canonical_url and detail_fetched. It costs 1 credit per successful call. No Walmart login is needed.
Walmart Data Extractor reads a Walmart listing page, one page per call, and enriches each product from its own product page: item ID, name, brand, seller, price and canonical URL. Feed it a search, browse or shop URL, a product URL or a plain keyword, and page through with a cursor. Every response is structured JSON, ready to pass directly to an LLM. It is one of 5 Walmart endpoints on the same API key used by 12,000+ developers. Next, follow next_cursor for page two.
What data can I extract with Walmart Data Extractor?
Using this Walmart Data Extractor, you can extract the following data from public Walmart pages of products:
Want the exact field names? See the example output.
Try Walmart Data Extractor Live
Press Run to see the catalog sample. Add your API key and it runs a real call to the Scrapier API from your browser. The key is sent only to proxy.scrapier.io and never stored.
+ Run live with your API key
How to use Walmart Data Extractor
Hand it to your AI assistant, or run it yourself in five steps.
Copy to your AI assistant
Paste this into ChatGPT, Claude or Cursor and it knows how to call the scraper.
Use the Scrapier Walmart Data Extractor to get public Walmart pages of products. Endpoint: GET https://proxy.scrapier.io/api/v2/walmart-data-extractor/?urls={urls} with header "X-API-Key: YOUR_API_KEY" and a 210-second timeout. Send one value per call in urls; for a list, make one call per value, at most 3 in parallel. It returns JSON under data.products: name, us_item_id, brand, seller_name, price_info, canonical_url, detail_fetched, input_url, scraped_at. Each successful call costs 1 credit; failed calls are free. If you support MCP, run: claude mcp add -t http scrapier https://mcp.scrapier.io/mcp --header "X-API-Key: YOUR_API_KEY" and call run_scrape with endpoint "walmart-data-extractor" (find it with search_endpoints).Use this scraper from ChatGPT, Claude or Cursor. Point your assistant at Scrapier and it reads Walmart pages of products on its own: no glue code, no scraping logic in your prompts.
Run it yourself
- Get your free Scrapier API keySign up at app.scrapier.io; the free tier lets you try it first.
- Open Walmart Data Extractor in the catalogIt lives under Scrapers / Walmart, next to the other Walmart tools.
- Enter the listing, product or keywordFor example
laptopinurls, a Walmart/search?q=,/browse/or/shop/URL, or a product/ip/URL. Addinclude_detailsorinclude_reviewsif you need them. - Send your API requestOne GET with your key in the
X-API-Keyheader, or onerun_scrapecall from your agent. This is how to scrape Walmart data without a browser. Set a 210-second client timeout. - Save your resultsEach page comes back as JSON in
data.products: store it as is, or flatten it to CSV. Passdata.next_cursorback ascursorto get the next page until it is null.
How to scale to bulk Walmart pages of products
urls takes one value per call, so for a list you loop: one request per value. Within an input, pass back data.next_cursor unchanged to read the next page. Run up to 3 requests in parallel per API key; above that the API answers 429 with a Retry-After header, and throttled calls cost nothing. Each call is 1 credit and failed calls are free, so 1,000 pages of products cost 1,000 credits, inside the Hobby plan's 15,000.
Features
This Walmart data extractor turns a Walmart listing or product page into rows you can rank, filter and store. It suits price and seller monitoring, catalog building, product research and any workflow that needs enriched Walmart product data without parsing HTML.
- Any inputA listing URL, a product URL or a plain keyword in
urls - EnrichedEach product is read from its own product page;
detail_fetchedsays if that worked - Price
price_infoholds the current price, its display string and the currency - Seller
seller_nameandbrandon every product - Optional
include_detailsandinclude_reviewsadd more per product - Paging
next_cursorreads the next page of products
Proxies, retries and parsing run on Scrapier's side, so you send one request and get JSON back, at 1 credit per page of products and 0 credits for a failed call.
Use cases
- Pricing analyst extracts products for a keyword each day and stores
price_infoandseller_nameper item ID to build a price history. - Catalog manager feeds in a listing URL and collects item IDs, names, brands and canonical URLs to build or check a product catalog.
- Seller researcher lists the products in a listing and reads
seller_nameto see which third-party sellers carry them. - Market researcher runs a list of product keywords and compares brands and prices across the first page of each.
- AI engineer gives an agent a tool that takes any Walmart link or keyword, so it can answer product questions from current data and cite the URLs.
Running these from an agent? Use the MCP integration and let Claude or Cursor call the scraper directly.
Why choose this Scraper API?
Each product on a listing page is read from its own product page, so one call gives you more than the listing card shows.
A search URL, a browse URL, a product URL or a plain keyword all go in the same urls input, so you do not switch endpoints per input type.
The same key and response envelope work across Scrapier's endpoints, so extracted products can feed a reviews call without new code.
Input
The scraper takes one Walmart listing URL (/search?q=, /browse/, /shop/), one product URL (/ip/) or one plain keyword per call in urls. It is required on the first call. Send parameters in the query string (GET) or as a JSON body (POST).
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
urls | string | Yes | — | A Walmart listing URL (/search?q=, /browse/, /shop/), a product URL (/ip/) or a plain keyword. One per call. Required on the first call. Aliases: url, query, q, search, keyword |
cursor | string | No | — | Pass back data.next_cursor from the previous response, unchanged, to get the next page; null means the last page |
include_details | boolean | No | false | Also fetch each product page for seller, UPC, variants and full description. Much heavier; default false returns listing-card data. Locked in the cursor |
include_reviews | boolean | No | false | Attach reviews to each product, default false. Locked in the cursor |
zip_code | string | No | — | 5-digit US delivery ZIP hint. Locked in the cursor |
use_proxy | boolean | No | true | Route through Scrapier's residential proxy pool, on by default. Leave as is |
raw_data | boolean | No | false | Return Walmart's raw upstream payloads under raw_responses instead of the formatted items |
One input per call: to extract ten keywords, make ten calls and page each with cursor. Booleans are the strings true or false.
Example input
{
"urls": "laptop",
"include_details": "false",
"include_reviews": "false",
"zip_code": "",
"use_proxy": "true",
"raw_data": "false"
}Error codes
| Status | Meaning | Billed | Fix |
|---|---|---|---|
| 200 | Page of products data returned in data.products | Yes | — |
| 400 | Bad or missing input | No | Check urls: one value per call |
| 401 | X-API-Key header missing | No | Add the header |
| 402 | Out of credits (body has balance) | No | Top up; retrying will not help |
| 403 | Invalid or revoked API key | No | Check the key in your dashboard |
| 429 | Throttled | No | Wait Retry-After seconds, then retry |
| 5xx | Upstream failure or timeout | No | Retry with backoff; set a 210 s client timeout |
From the error reference. Any non-2xx response costs 0 credits.
Output
Typed JSON with the same schema on every call. One call returns a page of products under products, each with 9 fields, inside the standard data envelope. Field names stay the same on every call. Set raw_data to true if you want Walmart's raw payload instead.
Example output
{
"success": true,
"data": {
"urls": "https://www.walmart.com/search?q=laptop",
"page": 1,
"page_size": 58,
"details_fetched": 56,
"products": [
{
"name": "Acer Chromebook 315 15.6” Full HD Laptop, 8GB RAM 128GB, ChromeOS",
"us_item_id": "20349310960",
"brand": "Acer",
"seller_name": "Walmart.com",
"price_info": {
"current_price": {
"price": 199.0,
"price_string": "$199.00",
"currency_unit": "USD"
}
},
"canonical_url": "/ip/Acer-Chromebook-315-.../20349310960",
"detail_fetched": true,
"input_url": "https://www.walmart.com/search?q=laptop",
"scraped_at": "2026-09-15T00:00:00.000Z"
}
],
"next_cursor": "eyJ1IjoiaHR0cHM6Ly93d3cud2FsbWFydC5jb20vc2VhcmNoP3E9bGFwdG9wIiwicCI6Mn0"
}
}The catalog's sample response for urls=laptop, labelled as a sample: live calls return the account's current values.
Product
| Field | Type | Example | Description |
|---|---|---|---|
products.us_item_id | string | "20349310960" | Walmart item ID of the product |
products.name | string | "Acer Chromebook 315 15.6” Full HD Laptop, 8…" | Product name as Walmart shows it |
products.brand | string | "Acer" | Brand name |
products.seller_name | string | "Walmart.com" | Name of the seller |
products.price_info | object | {…} | Object with current_price: price, price_string and currency_unit |
products.canonical_url | string | "/ip/Acer-Chromebook-315-.../20349310960" | Canonical product path on walmart.com |
products.detail_fetched | boolean | true | true if the product page was fetched, false if it missed the time budget |
Row context
| Field | Type | Example | Description |
|---|---|---|---|
products.input_url | string | "https://www.walmart.com/search?q=laptop" | Your input, echoed on the row |
products.scraped_at | string | "2026-09-15T00:00:00.000Z" | UTC time the row was scraped |
Response envelope and paging
| Field | Type | Example | Description |
|---|---|---|---|
success | boolean | true | true on every 200 response |
data.urls | string | "https://www.walmart.com/search?q=laptop" | Your input, echoed back |
data.page | integer | 1 | Page number of this response |
data.page_size | integer | 58 | Products per page |
data.details_fetched | integer | 56 | How many products had their product page fetched |
data.next_cursor | string | "eyJ1IjoiaHR0cHM6Ly93d3cud2FsbWFydC5jb20vc2V…" | Pass back as cursor for the next page; null on the last page |
How does it work?
Scrapier sends each request through its residential proxy pool (use_proxy, on by default), so you never manage IPs or proxy accounts.
Retries and parsing of Walmart's pages happen on Scrapier's side. You send one HTTP request and get typed JSON back.
Only publicly visible data is returned: the listings and product pages any visitor sees on Walmart without signing in. No Walmart account or cookie is used.
The schema is stable. When Walmart changes its pages, Scrapier updates the scraper; the field names in the result stay the same.
How do you integrate Walmart Data Extractor into your stack?
It works with what you already use: any HTTP client, AI agents over MCP, and no-code automation tools. Code samples for cURL, Python and Node.js are on the API tab.
MCP integration for AI agents
This registers the Scrapier MCP server, whose tools reach every Scrapier scraper, including walmart-data-extractor: the agent finds it with search_endpoints and calls it with run_scrape. Works with Claude Code, Cursor and Windsurf. MCP calls are billed like REST: 1 credit per successful call. Full MCP setup →
No-code tools (n8n, Make, LangChain)
Use the HTTP Request node with your Scrapier API key in an X-API-Key header and point it at /api/v2/walmart-data-extractor/ with a urls query parameter. Map the result list into the next node.
Add an HTTP "Make a request" module with the same header and URL, and parse the response as JSON. Map name, brand and seller_name straight into Sheets, Airtable or your CRM.
Wrap the endpoint in a requests-based tool, or load the Scrapier MCP server through LangChain's MCP adapters so the agent finds walmart-data-extractor with search_endpoints itself.
Pricing and Rate Limits
One Walmart page of products costs 1 credit, so 1,000 pages of products cost 1,000 credits: $1.58 on the Pro plan. Failed and empty calls are not billed. Run up to 3 requests in parallel per key; above that the API answers 429 with a Retry-After header.
| Plan | Monthly price | Credits | Pages of products included | Per 1,000 pages of products |
|---|---|---|---|---|
| Hobby | $29 | 15,000 | 15,000 | $1.93 |
| Pro | $79 | 50,000 | 50,000 | $1.58 |
| Scale | $299 | 250,000 | 250,000 | $1.20 |
| Enterprise | Custom volume and terms | |||
Prices from the live billing page. See all plans and limits.
Call cost and timing
How we measure this
Credit cost, pagination and the sample come from the live catalog (GET /api/v2/endpoints, /walmart-data-extractor/, checked 9 Nov 2026). Concurrency and timeout guidance come from the rate limits page of the docs. Scrapier does not publish latency or success-rate figures for this endpoint, so none are shown here.
Walmart Data Extractor vs the Official Walmart API
| Feature | Scrapier Walmart scraper | DIY Walmart scraping |
|---|---|---|
| Access needed | One Scrapier API key | Your own proxies, parser and servers |
| Which data | Products from any listing, product URL or keyword | Whatever your parser extracts |
| Fields returned | 9 fields per product: item ID, name, brand, seller, price and canonical URL | Whatever you build and maintain |
| Setup | Sign up, copy a key, send a request | Write selectors, handle blocks and retries |
| Cost | 1 credit per page, from $1.20 per 1,000 calls | Proxy, server and engineering time |
If you need a fully custom crawler or already run your own scraping stack, DIY gives more control; Scrapier suits teams that want one key and one JSON shape across many platforms.
Is it legal to scrape Walmart data?
Scraping publicly available web pages is generally lawful in many countries, but the answer depends on what you collect, where you are and how you use it. In the US, hiQ Labs v. LinkedIn is the case most often cited on public-data scraping. Scrapier returns only data any visitor can see without logging in. Under GDPR and similar laws, collecting public data can be permissible, but how you store and use personal data must still comply with local data-protection rules, and Walmart's terms apply. Consult legal counsel if your use case involves bulk storage of personal data. This is not legal advice; see our Terms of Use.
Frequently asked questions
What fields does Walmart Data Extractor return?
Each product has us_item_id, name, brand, seller_name, price_info, canonical_url and detail_fetched, plus input_url and scraped_at: 9 fields in data.products. The envelope adds urls, page, page_size, details_fetched and next_cursor. Each call costs 1 credit.
Is there a Walmart data extractor API?
Scrapier's Walmart data extractor API is a REST endpoint at /api/v2/walmart-data-extractor/: send a listing URL, product URL or keyword and your key in the X-API-Key header, and get product data as JSON. It costs 1 credit per page.
What can I send as input?
Send a Walmart listing URL (/search?q=, /browse/ or /shop/), a product URL (/ip/) or a plain keyword in urls. One value per call. The response echoes your input in urls and on each row as input_url.
What does detail_fetched mean?
Each product on the page is enriched from its own product page. detail_fetched is true when that worked and false when the product page missed the time budget. data.details_fetched counts how many products were enriched on the page.
What does include_details do?
include_details also fetches each product page for seller, UPC, variants and full description. It is much heavier, so leave it off unless you need those fields. include_reviews attaches reviews to each product. Both are locked into the cursor.
How do I get the next page?
Take data.next_cursor from the response and send it back unchanged as cursor. Repeat until next_cursor is null, which means you have reached the last page. Each page is one call and costs 1 credit.
Can I extract several keywords in one call?
No. urls takes one listing URL, product URL or keyword per call. To extract ten keywords, make ten calls, up to 3 in parallel per API key, and page each with cursor. Throttled calls return 429 and cost nothing.
Does Walmart Data Extractor require a Walmart account or login?
No. Walmart Data Extractor uses no Walmart account or cookies: you send your Scrapier API key in the X-API-Key header and your input, and get JSON back. Only publicly visible data is returned.
How fast does Walmart Data Extractor run?
Scrapier does not publish a latency figure for this endpoint. Each call reads Walmart live, so timing depends on the page. Set a client timeout of 210 seconds, as the docs recommend for every endpoint.
What happens if the input is wrong or Walmart returns nothing?
If a call fails, the API returns a non-2xx status and costs 0 credits. In code, check the status, then skip that input or retry it later. Throttled calls (429 with a Retry-After header) are free as well, so retry loops cost nothing.
Does Walmart Data Extractor work with Claude, ChatGPT and other AI agent tools?
Yes. Connect the Scrapier MCP server with claude mcp add -t http scrapier https://mcp.scrapier.io/mcp and your API key in an X-API-Key header; it works in Claude Code, Cursor and Windsurf. The agent finds walmart-data-extractor with search_endpoints and calls it with run_scrape. Any agent that can call an HTTP endpoint can use the REST API directly.
How much does it cost to run Walmart Data Extractor 1,000 times?
1,000 credits, because each call is 1 credit. That is about $1.93 on Hobby, $1.58 on Pro and $1.20 on Scale, at the plans' price per credit. Failed calls are free.
How do I use Walmart Data Extractor with Python?
For a Walmart data extractor in Python, send a GET request with the requests library to https://proxy.scrapier.io/api/v2/walmart-data-extractor/ with params={"urls": "laptop"}, your key in the X-API-Key header and timeout=210. Read r.json()["data"]["products"]: it is already JSON, so no HTML parsing is needed.
Your feedback
Found a bug or missing a field? Let us know. Write to support@scrapier.io and the team replies to every report.
Start Scraping Walmart Pages Of Products
Public Walmart pages of products as JSON, 1 credit each, from REST or MCP.