Amazon Product Details Scraper — ASIN, BSR, Price & Seller avatar

Amazon Product Details Scraper — ASIN, BSR, Price & Seller

Pricing

from $4.00 / 1,000 product scrapeds

Go to Apify Store
Amazon Product Details Scraper — ASIN, BSR, Price & Seller

Amazon Product Details Scraper — ASIN, BSR, Price & Seller

Look up Amazon products by ASIN, product URL, keyword or category in 18 marketplaces. Each row has price, list price, discount, rating, review count, Best Sellers Rank, seller, FBA/Prime status, bullets, images, variants and breadcrumbs as flat JSON.

Pricing

from $4.00 / 1,000 product scrapeds

Rating

0.0

(0)

Developer

Khadin Akbar

Khadin Akbar

Maintained by Community

Actor stats

1

Bookmarked

167

Total users

41

Monthly active users

4 days ago

Last modified

Share

What is Amazon Product Details Scraper?

Amazon Product Details Scraper turns ASINs, Amazon product or listing URLs, or a keyword search into one flat record per product with 27 fields: title, brand, price, list price, discount percent, rating, review count, Best Sellers Rank, bought-in-past-month badge and its numeric value, seller, Prime and FBA status, bullets, description, images, variants, breadcrumbs and scrape timestamp. It covers 18 Amazon marketplaces and works in Apify workflows, through the API and through Apify MCP.

Proxy routing is automatic: each request first tries the lower-cost datacenter pool and only retries on residential proxies when Amazon blocks it, so residential traffic is used only for pages that need it.

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.

Practical scenario

A marketplace seller tracks 40 competitor ASINs in the US store. A weekly scheduled run with the ASIN list returns price, list price, Best Sellers Rank, seller and FBA status for each product. Comparing two weekly datasets shows which competitors cut prices, lost the buy box to a third-party seller or climbed in category rank.

Input fields

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

FieldTypePurpose
searchQuerystringKeyword search on Amazon for the selected marketplace.
asinsarray of stringsASIN list, resolved against the chosen marketplace domain.
startUrlsarrayAmazon product, search, or category URLs.
countrystringMarketplace code used with searchQuery or asins.
maxResultsintegerMaximum products to scrape across all inputs combined.
maxSearchPagesintegerMaximum result pages to paginate through per search or category seed.
scrapeProductDetailsbooleanWhen true, fetches each found product page for fuller product data.
proxyConfigurationobjectOptional. Leave empty for automatic datacenter-first routing with residential retries.

Focused JSON input example

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

Output fields

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

FieldTypePurpose
asinstringAmazon Standard Identification Number.
titlestringProduct title.
urlstringCanonical product URL.
marketplacestringMarketplace code.
brandstring or nullBrand or manufacturer.
pricenumber or nullCurrent price.
listPricenumber or nullOriginal price before discount.
currencystring or nullISO currency code.
discountPercentnumber or nullDiscount percentage.
ratingnumber or nullStar rating.
reviewCountinteger or nullTotal review count.
boughtInPastMonthstring or nullPurchase-frequency badge text.
boughtInPastMonthCountinteger or nullNumeric floor of the badge, e.g. 10000 for "10K+".
availabilitystring or nullStock status text.
inStockboolean or nullPurchasable status.
isPrimeboolean or nullPrime eligibility.
sellerstring or nullMerchant name.
isFBAboolean or nullFulfilled by Amazon flag.
bestSellerRankarray or nullBest Sellers Rank entries (category and rank).
bulletsarray or nullFeature bullet points.
descriptionstring or nullFull product description.
imagesarray or nullProduct image URLs.
thumbnailstring or nullPrimary image URL.
variantsarray or nullProduct variants such as color or size.
breadcrumbsarray or nullCategory breadcrumb path.
sourceTypestringDiscovery path: search, category, product, or asin.
scrapedAtstringISO timestamp of the scrape.

Sample output record

One record from a real run (array fields shortened). Fields the page did not show, such as a buy-box price for a resale-only offer, are returned as null.

{
"asin": "B0FQFB8FMG",
"title": "Apple AirPods Pro 3 Wireless Earbuds with Active Noise Cancellation",
"url": "https://www.amazon.com/dp/B0FQFB8FMG",
"marketplace": "US",
"brand": "Apple",
"price": null,
"listPrice": 249,
"currency": "USD",
"discountPercent": null,
"rating": 4.4,
"reviewCount": 16514,
"boughtInPastMonth": "10K+ bought in past month",
"boughtInPastMonthCount": 10000,
"availability": "In Stock",
"inStock": true,
"isPrime": false,
"seller": "Amazon Resale",
"isFBA": true,
"bestSellerRank": null,
"bullets": [
"WORLD’S BEST IN-EAR ACTIVE NOISE CANCELLATION — Removes up to 2x more unwanted noise than AirPods Pro 2* so you can stay fully immersed in the moment.*",
"BREAKTHROUGH AUDIO PERFORMANCE — Experience breathtaking, three-dimensional audio with AirPods Pro 3. A new acoustic architecture delivers transformed bass, detailed clarity so you can hear every instrument, and stunningly vivid vocals."
],
"description": "",
"images": [
"https://m.media-amazon.com/images/I/218Mmzk0EaL._AC_SR38,50_.jpg"
],
"thumbnail": "https://m.media-amazon.com/images/I/218Mmzk0EaL._AC_SR38,50_.jpg",
"variants": null,
"breadcrumbs": [
"Apple Products",
"iPad",
"Apple Watch"
],
"sourceType": "asin",
"scrapedAt": "2026-10-16T07:22:29.586Z"
}

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:

  • Each request first tries the Apify datacenter pool; blocked requests retry on residential proxies, and a run that keeps getting blocked on datacenter switches to residential for the rest of the run.
  • 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

Startup billing and empty runs

The apify-actor-start event costs $0.00005 per startup unit. Apify charges one startup unit per GB of allocated memory, with a minimum of one unit, so a 2 GB run incurs two units. This startup charge still applies when input is invalid, no results are found, or an upstream request fails. Statements about free, unbilled, or skipped results refer only to the corresponding result event; they do not waive the startup charge. Apify platform usage is charged separately according to the run resources and your plan. Check the live Pricing tab for current events, tiers, and rates. Result limits cap result events, not the entire run cost.

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.

Continue the workflow

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.