Amazon Product Details Scraper

Amazon Product Details Scraper is an Apify Actor for ecommerce teams, analysts, and AI agents that need one flat dataset record per Amazon product. It accepts ASINs, direct Amazon product or listing URLs, or a keyword search, then returns product-level fields such as title, price, list price, discount percent, rating, review count, BSR, seller, Prime and FBA status, bullets, images, variants, breadcrumbs, and scrape timestamp. The output is designed for use in Apify workflows and through Apify MCP.

Best fit and connected workflows

This Actor fits workflows that begin with Amazon product discovery and continue with product-level enrichment.

Use it when you want to:

• enrich known ASINs with product details for catalog checks or competitive tracking,
• turn Amazon search or category pages into a flat product dataset,
• feed Amazon product records into an AI agent that fits the workflow with concise, bounded JSON,
• compare pricing, availability, and merchant signals across 18 Amazon marketplaces.

Focused standalone workflow

This Actor is designed as a focused standalone workflow.

Practical scenario

Maya, an ecommerce analyst, starts with a list of ASINs for a laptop accessory category. She sends the ASINs, chooses the marketplace, and sets a max-results cap for the first pass.

The Actor returns records with fields such as title, price, listPrice, rating, reviewCount, seller, isPrime, and bestSellerRank. Maya uses those fields to flag products for a price review, then sends the same ASINs into a reporting workflow that groups products by marketplace and seller.

Input fields

Provide one primary input path: asins, startUrls, or searchQuery. The other fields refine marketplace scope, page depth, and product detail depth.

Field	Type	Purpose
searchQuery	string	Keyword search on Amazon for the selected marketplace.
asins	array of strings	ASIN list, resolved against the chosen marketplace domain.
startUrls	array	Amazon product, search, or category URLs.
country	string	Marketplace code used with searchQuery or asins.
maxResults	integer	Maximum products to scrape across all inputs combined.
maxSearchPages	integer	Maximum result pages to paginate through per search or category seed.
scrapeProductDetails	boolean	When true, fetches each found product page for fuller product data.
proxyConfiguration	object	Proxy settings, with residential proxies as the default.

Focused JSON input example

{
  "asins": ["B08N5WRWNW", "B09G9HD6PD"],
  "country": "US",
  "maxResults": 10,
  "maxSearchPages": 2,
  "scrapeProductDetails": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}

Output fields

Each record is a flat JSON object in the dataset. The live dataset contract defines these fields.

Field	Type	Purpose
asin	string	Amazon Standard Identification Number.
title	string	Product title.
url	string	Canonical product URL.
marketplace	string	Marketplace code.
brand	string or null	Brand or manufacturer.
price	number or null	Current price.
listPrice	number or null	Original price before discount.
currency	string or null	ISO currency code.
discountPercent	number or null	Discount percentage.
rating	number or null	Star rating.
reviewCount	integer or null	Total review count.
boughtInPastMonth	string or null	Purchase-frequency badge text.
availability	string or null	Stock status text.
inStock	boolean or null	Purchasable status.
isPrime	boolean or null	Prime eligibility.
seller	string or null	Merchant name.
isFBA	boolean or null	Fulfilled by Amazon flag.
bestSellerRank	array or null	suitable Sellers Rank entries.
bullets	array or null	Feature bullet points.
description	string or null	Full product description.
images	array or null	Product image URLs.
thumbnail	string or null	Primary image URL.
variants	array or null	Product variants such as color or size.
breadcrumbs	array or null	Category breadcrumb path.
sourceType	string	Discovery path: search, category, product, or asin.
scrapedAt	string	ISO timestamp of the scrape.

Illustrative output record

{
  "asin": "B08N5WRWNW",
  "title": "Product title",
  "url": "https://www.amazon.com/dp/B08N5WRWNW",
  "marketplace": "US",
  "brand": "Brand name",
  "price": 199.99,
  "listPrice": 249,
  "currency": "USD",
  "discountPercent": 20,
  "rating": 4.7,
  "reviewCount": 85432,
  "boughtInPastMonth": "10K+ bought in past month",
  "availability": "In Stock",
  "inStock": true,
  "isPrime": true,
  "seller": "Amazon.com",
  "isFBA": true,
  "bestSellerRank": [
    {
      "category": "Electronics",
      "rank": 1
    }
  ],
  "bullets": [
    "Feature bullet point one",
    "Feature bullet point two"
  ],
  "description": "Full product description text",
  "images": [
    "https://m.media-amazon.com/images/I/example.jpg"
  ],
  "thumbnail": "https://m.media-amazon.com/images/I/example.jpg",
  "variants": [
    {
      "asin": "B0EXAMPLE01",
      "label": "Black"
    }
  ],
  "breadcrumbs": [
    "Category",
    "Subcategory"
  ],
  "sourceType": "asin",
  "scrapedAt": "2026-06-19T04:20:00.000Z"
}

How it works

This Actor runs on Apify and resolves Amazon products across 18 marketplaces: US, UK, DE, FR, CA, ES, IT, JP, AU, IN, MX, BR, NL, SE, PL, TR, AE, and SG.

Implementation facts visible in the live contract:

• It uses residential proxies by default.
• It supports ASINs, direct Amazon URLs, and keyword search.
• It paginates search or category results up to the configured page cap.
• When scrapeProductDetails is enabled, it fetches each discovered product on its own product page for fuller fields such as bullets, BSR, variants, and seller.
• The dataset is flat and MCP-friendly, which keeps each record straightforward for downstream use.

Pricing

This Actor uses Pay per event plus Apify platform usage. The live Pricing tab on the Actor page is the source of truth for current cost details, and Apify platform charges are separate from event-based Actor usage.

The primary billable event is Product scraped. The live contract defines this as one event for each product returned to the dataset.

Example in words: if a run returns twenty-five products, the run is billed for twenty-five product-scraped events, plus the applicable Apify platform usage for the run.

See the live Pricing tab on the Actor page for current pricing.

Use with AI agents (MCP)

This Actor is available as an Apify Actor usable through Apify MCP. The tool returns one dataset record per scraped product, with a flat schema that agents can read directly.

Precise tool description:

• resolve Amazon products by ASIN, product URL, keyword, or category,
• return product-level fields such as price, rating, seller, Prime status, images, bullets, variants, and breadcrumbs,
• support marketplace-specific extraction across 18 Amazon marketplaces,
• provide dataset output that an agent can read back after the execution completes.

Exact Actor identity: khadinakbar/amazon-product-details-scraper

Pull product details for these ASINs in the US marketplace, return up to 10 products, and include full product-page fields when available. I need the output as a flat dataset for a pricing review workflow.

Output interpretation:

• sourceType tells the agent how each record was discovered.
• price, listPrice, and discountPercent support pricing comparison.
• rating, reviewCount, and boughtInPastMonth support demand and reputation context.
• seller, isPrime, and isFBA help route records into merchant and fulfillment workflows.
• bestSellerRank, bullets, description, images, variants, and breadcrumbs provide detail-page context for enrichment or summarization.

Provenance and scope:

• Each dataset item comes from a scraped Amazon product record.
• Marketplace scope comes from country or from the Amazon domain in startUrls.
• The Actor returns one record per scraped product.

Pagination and cost guidance:

• maxSearchPages controls how many search or category pages are explored per seed.
• maxResults caps the total number of products across all inputs.
• Billing is event-based per returned product, so the cap you set directly shapes the run size.

API example

The example below runs the Actor with the Apify API, then reads the resulting dataset items. It uses APIFY_TOKEN from your environment.

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({
  token: process.env.APIFY_TOKEN,
});

const run = await client.actor('khadinakbar/amazon-product-details-scraper').call({
  asins: ['B08N5WRWNW'],
  country: 'US',
  maxResults: 1,
  scrapeProductDetails: true,
});

const dataset = await client.dataset(run.defaultDatasetId).listItems();
console.log(dataset.items);

Best results and outcome guidance

• Use asins when you already know the exact products and want precise product-level enrichment.
• Use startUrls for product pages, search result pages, or category pages you already collected.
• Use searchQuery for keyword-driven discovery on the selected marketplace.
• Keep maxResults aligned with the number of products needed for the next workflow step.
• Use scrapeProductDetails: true when the workflow depends on bullets, BSR, variants, or seller context.
• Use scrapeProductDetails: false when a faster, search-page-level pull is sufficient for an initial scan.

Design note

I found that the live dataset contract is intentionally flat: each output record is a single object with fields like asin, price, seller, and scrapedAt, which keeps the Actor easy to consume in agent workflows and in dataset tables.

FAQ

Which input path should I use for a known product list?
Use asins when you have a set of 10-character ASIN codes and want those products resolved on a chosen marketplace.

When should I use startUrls instead of searchQuery?
Use startUrls when you already have Amazon product, search, or category URLs and want the Actor to work from those exact pages.

What does the marketplace setting control?
country sets the Amazon marketplace for searchQuery and asins. If a startUrls entry points to a different Amazon domain, that domain takes precedence.

How does pagination affect results?
maxSearchPages limits how many search or category pages the Actor explores for each seed URL or search query.

What is returned to MCP clients?
MCP clients receive the same flat dataset records, so the downstream agent can read product data directly from the dataset.

How are seller and fulfillment signals represented?
The dataset includes seller, isPrime, and isFBA fields, along with pricing and product detail fields that support routing into commerce workflows.

Responsible use

Use this Actor in ways that respect Amazon's terms, applicable laws, and the rights of others. Review the data you collect before sharing or automating downstream decisions, and keep your use aligned with your own compliance requirements.