Amazon Products Scraper — Prices, ASIN, Ratings | from $2/1K

Scrape Amazon product search results by keyword or category. Returns structured product data including ASIN, title, price, brand, rating, review count, sponsored flag, availability, image, and canonical URL. Ideal for price monitoring, competitor research, catalog enrichment, and market analysis.

Use cases

• Price monitoring — track competitor prices across categories daily
• Product research — find top-ranking ASINs for a niche before launching a listing
• Catalog enrichment — enrich your product database with live Amazon data
• Market analysis — analyse which products dominate search for a keyword
• Sponsored vs. organic — split sponsored placements from organic search results

What you get

Field	Description
asin	Amazon Standard Identification Number (e.g. B0BS1PRC4L)
title	Full product title
brand	Brand name (when available)
url	Canonical product URL (amazon.com/dp/ASIN)
price	Numeric price (USD/GBP/EUR)
price_text	Price as displayed (e.g. $38.00)
price_currency	Currency code
rating	Star rating (1.0–5.0)
review_count	Number of customer reviews
is_sponsored	true for paid/sponsored placements
is_prime_eligible	Prime eligibility (null if session not logged in)
availability	in_stock / Only X left in stock / null
image_url	Product image CDN URL
position	Search result position (1-based)
page_number	Which page of results
parse_confidence	0.0–1.0 structural parse quality score

How to use

1. Enter a search query (e.g. wireless headphones, standing desk).
2. Optionally restrict to a category (e.g. electronics, computers, home-garden).
3. Set maxItems (default 50; Amazon shows ~24–30 per page, up to ~400 total per query).
4. Configure Apify Residential proxy (US) — required for reliable access.

Sample output

{
  "asin": "B0BS1PRC4L",
  "title": "Sony WH-CH520 Wireless Headphones Bluetooth On-Ear Headset with Microphone",
  "brand": null,
  "url": "https://www.amazon.com/dp/B0BS1PRC4L",
  "price": 38.0,
  "price_text": "$38.00",
  "price_currency": "USD",
  "rating": 4.5,
  "review_count": 32667,
  "is_sponsored": false,
  "is_prime_eligible": null,
  "availability": "in_stock",
  "image_url": "https://m.media-amazon.com/images/I/...",
  "position": 3,
  "page_number": 1,
  "parse_confidence": 1.0,
  "scraped_at": "2026-06-08T12:00:00+00:00"
}

Pricing

Pay per product — you are only charged for records actually returned.

Technical notes

• Parsed via structural XPath on data-asin / data-component-type="s-search-result" — no CSS class selectors. Class names rotate with Amazon deployments; structural attributes do not.
• Prime eligibility requires a logged-in Prime session and is not present in anonymous search HTML — returned as null (unknown), not false.
• Uses Apify Residential US proxy for reliable access from cloud.

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Autoscout24 Cars Scraper
• Competitor Price Monitor
• Craigslist Scraper
• Doordash Scraper
• Ebay Scraper
• Etsy Listings

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.