Walmart Reviews Scraper avatar

Walmart Reviews Scraper

Pricing

from $0.10 / 1,000 reviews

Go to Apify Store
Walmart Reviews Scraper

Walmart Reviews Scraper

Export public Walmart US and Canada product reviews, ratings, dates, reviewer labels, media, and product provenance.

Pricing

from $0.10 / 1,000 reviews

Rating

0.0

(0)

Developer

Fetch Cat

Fetch Cat

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

1

Monthly active users

11 days ago

Last modified

Features

Limited permissions

Share

Export available public product reviews for selected Walmart US or Canadian products. Keep product and review identity, public review text, rating and dates, exposed reviewer labels and helpfulness signals, optional media and available product-rating context. This provides review records for your own quality and feedback research rather than sentiment analysis or verified customer identities.

Quick start

Choose one known product and the matching market, then inspect a bounded review sample. The existing US example uses newest order with review media enabled:

{"productUrls":["https://www.walmart.com/ip/771934678"],"country":"US","maxReviewsPerProduct":100,"sort":"newest","includeReviewMedia":true}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

What you get

One public review row with product identity, source context and available review fields. Missing upstream fields remain omitted or null rather than guessed. Products without matching public reviews do not produce fabricated reviews. RUN_STATS records requested, accessible, blocked and no-matching-review counts, actual emitted and charged review counts, and a reason for each processed product. Partial pagination, unavailable targets and an exhausted review charge limit are reported separately from a completed extraction with no matching usable reviews.

Who is it for?

  • Product-quality researchers inspecting bounded source-linked feedback.
  • Retail analysts keeping US and Canadian review contexts distinct.
  • Support and category teams grouping low-star complaints in their own analysis tools.
  • Data developers joining public review samples to known product identifiers.

How you can use the data

  • Review recent US feedback. Use the existing product 771934678 newest-review recipe with a small cap. Keep submittedAt and sourceUrl beside the text rather than claiming the returned sample represents every buyer or a complete time window.
  • Inspect Canadian product context. Use the existing Canadian 6000206618756 URL with country CA. Retain market and available aggregate ratings separately from the selected review sample, without joining product identities across countries solely by name.
  • Prepare a low-star complaint sample. Apply the existing one-star filter and newest order, keeping titles, text and review IDs for your own topic review. A filtered sample cannot establish the overall product rating distribution or customer sentiment.
  • Retain provenance for repeated exports. Store reviewId, productId, market and collection time in your destination before comparing observations. Public purchase-verification badges are source labels rather than independent identity checks, and the Actor does not contact reviewers or generate alerts.

Input settings

SettingAPI keyMeaning
Product URLsproductUrlsKnown public Walmart US or Canadian product links.
Product identifiersproductIdsNumeric product IDs within the selected market. URLs and IDs can be combined.
MarketcountryUS or CA. Each URL must match. Runtime default US, while the current form prefills CA.
Review cap per productmaxReviewsPerProductFrom 1 to 5,000. Runtime default 100, while the form prefills 15.
Review ordersortrelevant, newest, highest or lowest. Default relevant. Sorting applies to collected records rather than proving global coverage.
Rating filterratingOptional exact star rating from 1 to 5.
Review mediaincludeReviewMediaInclude exposed public media URLs. Runtime default true, current form prefill false.
ConnectionconnectionModeAutomatic (default) preserves the current direct-first setup with a managed proxy challenge fallback. Direct has no paid fallback. See the field help for costs and compatible saved settings.

Malformed or cross-market targets fail before scraping and before the start event. Use explicit known products instead of searching for a keyword in this Actor.

Input options

Copy a recipe into the Actor input editor and replace the product URL when needed.

Monitor latest Walmart US reviews

{"productUrls":["https://www.walmart.com/ip/771934678"],"country":"US","maxReviewsPerProduct":100,"sort":"newest","includeReviewMedia":true}

Analyze Walmart Canada product reviews

{"productUrls":["https://www.walmart.ca/ip/6000206618756"],"country":"CA","maxReviewsPerProduct":250,"sort":"relevant","includeReviewMedia":true}

Investigate low-star Walmart feedback

{"productUrls":["https://www.walmart.com/ip/771934678"],"country":"US","maxReviewsPerProduct":100,"sort":"newest","rating":1,"includeReviewMedia":true}

Output data

FieldMeaning
reviewId, productId, productUrl, marketReview identity, product identity and source market.
productName, brandPublic product labels when exposed.
rating, title, text, submittedAtPublic review rating, content and available submission date.
reviewerName, reviewerLabel, isVerifiedPurchase, helpfulCountPublic display and source badge or helpfulness signals, without private reviewer access.
mediaPublic review media URLs when requested and exposed.
productRating, productReviewCount, ratingDistributionAvailable aggregate product context, distinct from this selected review sample.
sourceUrl, scrapedAtObserved source and collection time.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

After input and target validation, a start event applies, subject to your run's charge limit. Each saved public review creates one review event after dataset delivery. Products with no matching reviews, unavailable products and blocked products do not generate fabricated review rows or review-event charges, but the run can retain its start charge. Extraction stops when no further reviews can be charged within your limit.

The review event price depends on your Apify plan: it is lower on Bronze than on Free, lower again on Silver, and lowest on Gold and higher plans. The start event costs the same on every plan.

The per-product cap controls review volume. Platform usage can also apply. See the live Pricing tab for current rates.

Tips for best results

  • Select the matching market. US and Canadian product URLs must agree with country.
  • Start with a small review cap. Inspect source dates and content before expanding the sample.
  • Keep filters with your analysis. A one-star subset is not the overall product review distribution.
  • Distinguish blocked access from no matches. Read RUN_STATS and pagination warnings before interpreting an empty dataset.
  • Keep IDs and source links. Deduplicate and compare repeated exports in your own destination.

Limits and caveats

The Actor uses anonymous public Walmart surfaces. It does not access accounts, orders, private reviewer data or reviewer profiles. Media and optional fields depend on what the public source exposes. A source badge does not independently verify a person's identity or claim.

Walmart may challenge anonymous traffic. Initially blocked products are counted separately, while a later pagination block can leave previously collected reviews available with a partial-result reason in RUN_STATS. Products with no matching reviews emit no fabricated rows. A run can finish with zero rows for blocked or no-matching products, so successful completion alone does not prove review coverage or that a product has no reviews.

Pagination can stop when repeated pages produce no new reviews, and the per-product cap bounds the collected sample. Ordering is applied to returned records and does not guarantee that every newer, higher- or lower-rated review was accessible. Source outages, storage or charge failures can still fail a run after earlier rows are saved. The supported allocation is 256 MiB, matching the current default. Processing has an independent maximum of 570 seconds. Keep the platform timeout at 600 seconds or less. Unlimited or longer timeout overrides are rejected before extraction. Responses are limited to 4 MiB, parsed JSON to 200,000 structural tokens and 64 nesting levels, and collected reviews to 16 MiB per product. Exceeding a safety limit fails the run rather than claiming a complete export. Restarting or resurrecting the same run does not repeat extraction. Start a new run for a new export.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST "https://api.apify.com/v2/acts/fetch_cat~walmart-reviews-scraper/runs?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"productUrls":["https://www.walmart.com/ip/771934678"],"country":"US","maxReviewsPerProduct":5,"sort":"newest","includeReviewMedia":false}'

Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/walmart-reviews-scraper').call({
"productUrls": [
"https://www.walmart.com/ip/771934678"
],
"country": "US",
"maxReviewsPerProduct": 5,
"sort": "newest",
"includeReviewMedia": false
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient
client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/walmart-reviews-scraper').call(run_input={
"productUrls": [
"https://www.walmart.com/ip/771934678"
],
"country": "US",
"maxReviewsPerProduct": 5,
"sort": "newest",
"includeReviewMedia": False
})
print(client.dataset(run['defaultDatasetId']).list_items().items)

MCP and AI agents

You can ask your AI assistant to collect data with Walmart Reviews Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Walmart Reviews Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com?tools=fetch_cat/walmart-reviews-scraper"
}
}
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Walmart Reviews Scraper by Fetch Cat, or give it the identifier fetch_cat/walmart-reviews-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

  • “Use Fetch Cat’s Walmart Reviews Scraper to collect up to 5 newest public reviews for https://www.walmart.com/ip/771934678 in the US market with review media off. Keep source links and review dates without treating the sample as complete.”
  • “Collect up to 5 public reviews for https://www.walmart.ca/ip/6000206618756 in the Canadian market, relevant order and media off. Keep market and available aggregate product context separate from the sample.”
  • “Retrieve up to 5 one-star public reviews for https://www.walmart.com/ip/771934678 in the US market, newest first and media off. Preserve any blocked or empty outcome instead of inventing reviews or calculating overall sentiment.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can I collect reviews from both markets in one request?

Choose one country per run. Every supplied URL must match it. Run separate inputs for US and Canadian products.

Does an empty dataset prove there are no reviews?

No. A product can have no matching exposed reviews, or anonymous access can be blocked. Inspect RUN_STATS and the run log before drawing a conclusion.

Does this perform sentiment analysis?

No. It returns public review records. Grouping themes, comparing sentiment and monitoring changes are your own downstream work.

Does this discover products by keyword?

No. Supply known product URLs or IDs. Use the related Walmart Products Scraper for product discovery first.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥