Amazon Product & Reviews Scraper

Amazon Product & Reviews Scraper

Scrape Amazon product details, search-result listings, and on-page top customer reviews from server-rendered HTML. No login and no API key required. Give the actor a list of ASINs for full product details + reviews, or a list of search queries for paginated result listings. Supports 7 marketplaces (com, co.uk, de, fr, it, es, ca), and forces each marketplace's native currency/language via an i18n cookie so prices come back consistently.

What it does

• ASIN / product mode — for each ASIN, returns title, price, currency,

rating, review count, brand, availability, feature bullets, hi-res images, and the top reviews embedded in the product page.

• Search mode — for each query, paginates through Amazon's result pages

(up to maxItems) and returns asin, title, price, currency, rating, reviewCount, a thumbnail image (~200px), sponsored flag, and url.

Input

{
  "asins": ["B0BS1PRC4L"],
  "searchQueries": ["wireless earbuds"],
  "domain": "com",
  "maxItems": 50,
  "proxyConfiguration": { "useApifyProxy": true }
}

Provide asins, searchQueries, or both. At least one is required — an empty input returns an uncharged BAD_INPUT diagnostic row (it does not crash the run).

You do not need to configure a proxy. The actor routes every request through its own pool of static US addresses and takes a fresh exit address on each retry. proxyConfiguration is only there if you would rather the requests came from addresses you control — set your own proxy servers under *Custom proxies* and they are used exactly as given.

Sample output

Product row (ASIN mode):

{
  "ok": true,
  "type": "product",
  "asin": "B0BS1PRC4L",
  "url": "https://www.amazon.com/dp/B0BS1PRC4L",
  "title": "Example Wireless Earbuds",
  "price": "$49.99",
  "currency": "USD",
  "rating": "4.5",
  "reviewCount": "1,234 ratings",
  "brand": "ExampleBrand",
  "availability": "In Stock",
  "featureBullets": ["40h battery life", "IPX5 water resistant"],
  "images": ["https://m.media-amazon.com/images/I/hi-res-1.jpg"],
  "reviews": [
    { "id": "R1", "author": "Jane", "rating": "5.0", "title": "Great", "date": "...", "verifiedPurchase": true, "helpfulVotes": "3 people found this helpful", "body": "..." }
  ],
  "reviewsParsed": 1
}

Search row (search mode):

{
  "ok": true,
  "type": "search",
  "query": "wireless earbuds",
  "asin": "B0XXXXXXXX",
  "title": "Example Wireless Earbuds",
  "price": "$49.99",
  "currency": "USD",
  "rating": "4.5",
  "reviewCount": "1,234",
  "images": ["https://m.media-amazon.com/images/I/thumb-200px.jpg"],
  "sponsored": false,
  "url": "https://www.amazon.com/dp/B0XXXXXXXX"
}

Both modes expose images as an images array so the output schema is uniform downstream. The difference is content: product mode yields hi-res image URLs, search mode yields a single ~200px thumbnail URL.

Nullable fields

These fields can be null/empty when Amazon does not render them for a given product or listing: price, rating, reviewCount, brand, availability, images (empty array), and reviews (empty array). Plan downstream pipelines to tolerate nulls.

Pricing

$0.75 per 1,000 products ($0.00075 each), with no run-start fee. Flat rate — no volume tiers, no plan gates — and you are charged only for products actually returned.

You are charged once per successfully parsed product/search row (ok: true). Blocked, failed, truncated, or empty results are never charged — those come back as ok: false diagnostic rows with an errorCode (BLOCKED, RATE_LIMITED, SERVER_ERROR, NETWORK, NO_RESULTS, BAD_INPUT). Embedded reviews ride along inside the product row at no extra charge: a product with ten on-page reviews still costs one row.

> Price change on 19 August 2026: the per-product price stays at $0.00075, > and a $0.001 run-start fee is added to each run from that date.

Troubleshooting

• BLOCKED / robot check — Amazon served a captcha/robot-check page on every

attempt. The actor already retries on a fresh exit address; if it persists, retry later or supply your own proxy servers in proxyConfiguration.

• Truncated search results — if a later page (page 2+) is blocked mid-run,

the actor returns the rows it already collected and adds a diagnostic row explaining the truncation. Retry, or supply your own proxy servers in proxyConfiguration, for the full set.

• NO_RESULTS — the page loaded but nothing matched your input; check the

ASIN/query and the selected domain.

• BAD_INPUT — you provided neither ASINs nor search queries.