Amazon India Reviews Scraper

Scrape public Amazon India customer reviews from amazon.in product or review URLs. The actor uses serialized direct HTTPS requests and source-specific HTML parsing for review cards, product context, ratings, verification badges, helpful votes, reviewer links, dates, and public review images.

The runtime uses direct HTTP first and does not launch a browser, solve CAPTCHAs, or sign in. When a standard Apify Proxy is explicitly configured, a blocked, unavailable, or timed-out direct response gets one session-stable proxy fallback. Remaining HTTP denials, redirects outside Amazon.in, and challenge pages fail closed as explicit diagnostics.

Input

Field	Type	Default	Description
productUrls	array	required	Amazon.in product/review URLs or objects with a url property. ASINs are extracted from dp, gp/product, product-reviews, and ASIN paths.
maxReviewsPerProduct	integer	10	Maximum live reviews per product, clamped to 1–50.
maxPages	integer	5	Maximum public review pages to request per product, clamped to 1–10.
requestDelayMs	integer	0	Delay between review-page requests, clamped to 0–10000.
requestTimeoutMs	integer	60000	Direct request timeout, clamped to 5000–120000.

The legacy headless field is accepted but ignored. proxyConfiguration uses the standard Apify editor and defaults to disabled; records and the run summary report whether the fallback was actually used. An input with no valid Amazon.in product or review URL fails immediately with a clear error. In mixed batches, invalid URLs are emitted as diagnostics while valid URLs continue.

Example:

{
  "productUrls": [
    "https://www.amazon.in/dp/B0DG4WXBCF"
  ],
  "maxReviewsPerProduct": 10,
  "maxPages": 5,
  "requestDelayMs": 0,
  "requestTimeoutMs": 30000
}

Output

Each live review contains source-backed fields such as:

• review ID, rating, title, body, date, reviewer name/profile, verification status, helpful votes, and images;
• product ASIN, title, rating, total review count, rating breakdown, original product URL, and canonical review URL;
• direct request/final URL, HTTP status, extraction method, page number, source metadata, field coverage, and data quality.

When no sufficiently rich review is available, the dataset contains a diagnostic record with pageType: "run_diagnostic", an error code, access/challenge evidence, and no fabricated review fields. The actor writes the run summary to the OUTPUT_SUMMARY key-value record.

Local testing

Place input in storage/key_value_stores/default/INPUT.json and run:

$apify run

The dataset is written under storage/datasets/default/. Validate generated rows with:

$node validate-datasets.js