Amazon Product & Reviews Scraper

Amazon Scraper: product data by ASIN or keyword, on seven marketplaces

Give it ASINs and it returns the full product page as a row: title, price, rating, brand, availability, the feature bullets, the image gallery and the reviews Amazon prints on the page. Give it search terms instead and it walks the result pages and returns what it finds there.

The part worth knowing before you plan around it: the two modes do not return the same row. An ASIN row is the full product page. A search row is what a listing tile carries, so no brand, no bullets, no reviews, and one small thumbnail instead of the gallery. And the reviews on an ASIN row are only the handful Amazon embeds on the page, usually 8 to 13, not the whole review history.

🛒 What Amazon Scraper does

Two modes, and you can run both in the same job. asins fetches product pages one by one. searchQueries pages through Amazon's own search results until it has as many as you asked for or the results run out.

Pick your marketplace in domain: com, co.uk, de, fr, it, es or ca. The run is pinned to that marketplace's own currency and language, so a price is the price a shopper in that country sees and does not drift depending on where the run happens from.

Everything comes back as text exactly as the page prints it. price is "$33.33", not 33.33, and rating is "4.4". Parse them your side, where you know which currency and decimal format you want.

📥 What you give it

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

Fill in at least one of the two. A run with both empty writes a BAD_INPUT row rather than guessing what you meant.

📤 What you get back

A real ASIN row from a real run, with the bullets, gallery and review text cut short so the block stays readable:

{
  "ok": true,
  "type": "product",
  "asin": "B0BS1PRC4L",
  "url": "https://www.amazon.com/dp/B0BS1PRC4L",
  "title": "Sony WH-CH520 Wireless On-Ear Bluetooth Headphones with Microphone, Black",
  "price": "$33.33",
  "currency": "USD",
  "rating": "4.4",
  "reviewCount": "(35,261)",
  "brand": "Sony",
  "availability": "In Stock",
  "featureBullets": [
    "LONG BATTERY LIFE: With up to 50-hour battery life and quick charging, you'll have enough power for multi-day road trips and long festival weekends. (USB Type-C Cable included)",
    "..."
  ],
  "images": [
    "https://m.media-amazon.com/images/I/41lArSiD5hL._AC_SL1200_.jpg",
    "https://m.media-amazon.com/images/I/811UeUfPYdL._AC_SL1500_.jpg",
    "..."
  ],
  "reviews": [
    {
      "id": "R31152UC9BQT1G",
      "author": "jimbo",
      "rating": "5",
      "title": "Battery Life is UNREAL!!! Obsessed!",
      "date": "Reviewed in the United States on August 5, 2026",
      "verifiedPurchase": true,
      "helpfulVotes": "39 people found this helpful",
      "body": "I've been using these every single day for the past four months..."
    }
  ]
}

🧾 Reading the output

Two kinds of row land in the dataset, and only the first kind is billed.

Filter on ok == true, then split on type if you ran both modes.

A search that returned some products and then stopped early writes both: the products it collected, which are charged, and one uncharged diagnostic saying how far it got. The run finishes green either way, so judge it by rows rather than by the run status.

▶️ How to run it

1. Open Amazon Scraper and click Try for free. 2. Paste ASINs into ASINs, or terms into Search queries, or both. 3. Pick your Amazon marketplace. 4. Set Max items for search mode. Start at 20 while you look at the row shape. 5. Click Start, then download the dataset as JSON, CSV or Excel, or read it from the API.

💰 How much does it cost?

$0.75 per 1,000 products, which is $0.00075 each. Flat on every Apify plan, no volume tiers.

You pay per product row. Diagnostic rows are not billed, and a dead ASIN or a query that matches nothing produces no product rows to bill for.

Two things do get billed that people sometimes expect not to be. An out-of-stock product is a complete row apart from the price, so it counts. And the same ASIN listed twice, or matched by two different queries, is fetched twice and counts twice, because nothing is deduplicated between lookups. Clean your input list first.

💡 What people use it for

• Watching the price and availability of a fixed list of ASINs on a schedule.
• Pulling the first few hundred results for a keyword to see who actually ranks for it.
• Building a product feed with images and bullets for a comparison page.
• Checking how the same ASIN is priced across the UK, German and US marketplaces.

🚧 What it does not do

• Search rows are thin. No brand, no bullets, no reviews, and one small thumbnail. Take the

ASINs from search mode and run them through ASIN mode when you need the detail.

• Only the reviews on the page. Roughly 8 to 13 per product. For the full review stream, use the

reviews scraper linked below.

• No Best Sellers Rank, no variations, no seller list. Those are not parsed.
• Seven marketplaces, one per run. Two countries means two runs.
• Numbers arrive as text. price, rating and reviewCount are page strings. Convert them

yourself.

• No deduplication. Repeated ASINs and overlapping queries produce repeated rows.
• A run finishes green even when everything failed. Check the row count, not the status.

🧭 Which Amazon scraper do you need?

❓ Questions people ask

Do I need an Amazon account or an API key? Neither. Nothing to register and nothing that expires.

Why is price empty on some rows? Because Amazon printed no price. That happens on out-of-stock items and on some listings that only show a price in the basket.

Can I get more than 1,000 results for one search? Not from one query. Split it into narrower terms, which also gets you past the point where Amazon's own results stop being relevant.

Are search results the same as what I see? Close, but Amazon personalises and rotates listings, and sponsored tiles move around. Treat a search run as a snapshot.

Is scraping Amazon legal? This reads public product pages, the same ones any shopper sees. Reviews are personal data under GDPR and similar laws, so have a reason for keeping them. Apify's write-up on the legality of web scraping is a good starting point, and we are not lawyers.

🆘 If something breaks

Open the Issues tab on the actor page. Send the ASIN or query and the run ID, and the log usually shows what the page did.