Amazon Product Detail Scraper

Turn ASINs, product URLs, or keywords into clean, structured Amazon product data — the exact fields buyers need for price monitoring, catalog enrichment, market research, and AI pipelines. Data comes straight from Amazon's own product API, so you get consistent JSON (including the full star-by-star rating breakdown) instead of brittle HTML scraping. No Amazon account, no API key.

Who it's for

• E-commerce & retail analysts tracking prices, discounts, and availability.
• Brands & sellers monitoring their own and competitors' listings.
• Catalog / PIM teams enriching product databases from a list of ASINs.
• Data & AI teams feeding structured product data into models and agents.

What you get (output fields)

Field	Description
asin	Amazon product identifier
title	Product title
brand / brand_url	Brand name and its Amazon store URL
price	Current price to pay (numeric)
list_price	Strikethrough / list price (numeric)
savings_amount / savings_percent	Discount amount and percentage
currency	ISO currency code for the marketplace
availability	Stock message (e.g. "In Stock")
rating / rating_display	Average star rating (numeric + display)
ratings_count	Total number of ratings
rating_histogram	% of reviews per star (5→1) — sentiment distribution most scrapers omit
product_type / category_id / sub_category_id	Amazon category taxonomy
images / main_image	Full-resolution product image URLs
overview	Key product attributes (brand, color, material, specs…)
marketplace / url	Marketplace code and canonical product URL

Three ways to input

1. ASINs — the fastest path; enriched directly in batches of 30.
2. Product URLs — paste /dp/… links; the ASIN is extracted automatically.
3. Search keywords — no ASINs yet? Search Amazon and enrich the top matches.

Mix all three in one run. Choose any of 17 marketplaces (US, UK, DE, FR, ES, IT, CA, JP, IN, AU, MX, BR, NL, SE, PL, AE, SG).

Example input

{
  "asins": ["B004YAVF8I", "B0CHX3QBCH"],
  "searchQueries": ["wireless mouse"],
  "maxItemsPerSearch": 20,
  "marketplace": "US",
  "maxItems": 1000
}

Example output (one row)

{
  "asin": "B004YAVF8I",
  "title": "Logitech M185 Compact Ambidextrous 2.4 GHz Wireless Mouse - Swift Grey",
  "brand": "Logitech",
  "price": 14.9,
  "list_price": 17.99,
  "savings_amount": 3.09,
  "savings_percent": "17%",
  "currency": "USD",
  "availability": "In Stock",
  "rating": 4.4,
  "ratings_count": 45106,
  "rating_histogram": { "5": 76, "4": 11, "3": 5, "2": 1, "1": 7 },
  "product_type": "INPUT_MOUSE",
  "images": ["https://m.media-amazon.com/images/I/51WN5aXZWIL.jpg"],
  "overview": { "Brand": "Logitech", "Color": "Swift Grey", "Connectivity Technology": "USB" },
  "marketplace": "US",
  "url": "https://www.amazon.com/dp/B004YAVF8I"
}

Scheduling & webhooks

Run it on a schedule (e.g. daily price checks) from the Apify Console, and wire a webhook to push new datasets straight into your database, Google Sheets, or Slack when a run finishes.

Use it from AI assistants (MCP)

The actor's dataset is standard JSON, so it plugs into AI/agent workflows and the Apify MCP server — hand an agent a list of ASINs and get structured product facts back for RAG, comparison, or monitoring.

FAQ

Do I need an Amazon account or API key? No. The actor calls Amazon's own product API anonymously.

How fresh is the data? Every run fetches live data at request time.

Which marketplaces are supported? 17: US, UK, CA, DE, FR, ES, IT, JP, IN, AU, MX, BR, NL, SE, PL, AE, SG.

Can I get full review text? This actor returns the aggregate rating and the star-by-star histogram, not individual review text (Amazon gates full review listings behind login). The histogram is ideal for sentiment overviews.

Why might a field be null? Some products omit a list price, savings, or specs; those fields are null rather than guessed.

Is scraping this legal? The actor collects publicly available product data. You are responsible for using the data in line with Amazon's terms and applicable law.

How reliable is it? It uses Amazon's structured API rather than HTML parsing, so output is stable across page-layout changes.