Amazon Bestsellers Scraper

Export product listings from public Amazon Best Sellers, New Releases, Most Wished For, and Most Gifted pages, with ASINs, page positions, titles, visible prices, ratings, review counts, and product URLs. Download CSV, JSON, or Excel, or use the dataset in API and AI-agent workflows.

Amazon can block access or return pages without usable product cards. Those inputs produce diagnostic rows rather than products. Movers & Shakers is not supported.

Quick start

1. Paste a supported Amazon category/list URL into Start URLs.
2. Set Maximum product rows to 10 for a small first run and leave category expansion off.
3. Start the Actor, inspect status in the dataset, and export the product rows you need.

{
  "startUrls": [{ "url": "https://www.amazon.com/Best-Sellers/zgbs" }],
  "maxItems": 10
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a public example to see its settings before starting a run:

• Export Amazon Beauty Most Wished For
• Export Amazon Books New Releases
• Export Amazon Electronics Best Sellers

What you get

• Primary job: Collect a snapshot of public Amazon category-list product cards.
• Input: Public Amazon list/category URLs such as https://www.amazon.com/Best-Sellers/zgbs.
• Output: One row per ranked product plus explicit diagnostic rows for blocked, invalid, or empty inputs.
• Best for: Ecommerce research, rank monitoring, product discovery, merchandising checks, and BI enrichment.

What data can you extract?

Field	Description
status	OK for product rows or ERROR for diagnostic rows.
listType	Best Sellers, New Releases, Most Wished For, Most Gifted, or movers-and-shakers on unsupported diagnostic rows.
marketplace	Amazon marketplace hostname such as www.amazon.com.
category	Category/list title visible on the page.
categoryUrl	Category/list URL used for the row.
categoryPath	Visible breadcrumb/subcategory path when supplied by Amazon.
position	One-based product-card order on each fetched page. Restarts on subsequent pages, not a global sales rank.
asin	Amazon product ASIN.
title	Product title from the list card.
productUrl	Public Amazon product URL.
imageUrl	Product image URL.
price	Parsed displayed price when visible.
priceText	Raw displayed price text.
currency	Currency code derived from displayed price or marketplace.
rating	Star rating when visible.
reviewCount	Review count when visible.
numberOfOffers	Offer count when visible.
availability	Availability/status text when visible.
inputUrl	Original user-provided URL.
url	Product URL for product rows or source URL for diagnostic rows.
scrapedAt	ISO timestamp when the row was created.
errorCode	Diagnostic code for error rows.
error	Short error label.
errorDescription	Human-readable diagnostic description.

Who is it for?

• Ecommerce sellers checking which products lead public Amazon category rankings.
• Retail analysts and brand teams monitoring rank, price, rating, and review-count movement.
• Affiliate publishers finding popular products for buying guides and category pages.
• Automation teams feeding bestseller snapshots into dashboards, alerts, or AI workflows.

How you can use the data

• Prepare a Best Sellers product sheet. Supply a public Best Sellers category URL and a small product cap. Keep rows with status=OK, then export asin, title, productUrl, priceText and categoryUrl for manual product research.
• Review another supported list type. Collect a public New Releases, Most Wished For or Most Gifted category URL. Keep listType and marketplace with each row instead of treating different lists as interchangeable rankings.
• Compare your own category snapshots. Join exports by ASIN within the same marketplace and category URL, retaining page context and collection time. position is the order of cards on each fetched page, not a global sales rank or a continuous rank across pages.
• Separate unavailable inputs before summarizing. Filter out status=ERROR rows and review their diagnostic descriptions. They explain input or access outcomes rather than representing products.

Input settings

Setting	JSON key	Use it for	Example
Start URLs	startUrls	Public Amazon Best Sellers, New Releases, Most Wished For, or Most Gifted category URLs. Movers & Shakers URLs return an UNSUPPORTED_LIST_TYPE diagnostic row.	https://www.amazon.com/Best-Sellers/zgbs
Maximum product rows	maxItems	Total product-row cap across inputs. Form default 20. Diagnostic rows do not count toward this cap.	10
Subcategory depth	subcategoryDepth	Attempt linked child categories, up to two levels. Default 0. Discovery depends on available links.	0
Include next page	includeNextPage	Attempt available next-page links. Default false. Unique continuation is not guaranteed.	false
Proxy country code	proxyCountryCode	Retained configuration field. The current HTTP fetch does not apply this proxy setting. Do not rely on it to select regional prices.	US

Example input

{
  "startUrls": [{ "url": "https://www.amazon.com/Best-Sellers/zgbs" }],
  "maxItems": 10,
  "subcategoryDepth": 0,
  "includeNextPage": false
}

Output data

Illustrative shape only, not an observed product or a guarantee of field availability:

{
  "status": "OK",
  "listType": "best-sellers",
  "marketplace": "www.amazon.com",
  "category": "Amazon Best Sellers",
  "categoryUrl": "https://www.amazon.com/Best-Sellers/zgbs",
  "categoryPath": ["Any Department"],
  "position": 1,
  "asin": "B0EXAMPLE01",
  "title": "Example ranked product",
  "productUrl": "https://www.amazon.com/dp/B0EXAMPLE01",
  "imageUrl": "https://m.media-amazon.com/images/I/example.jpg",
  "price": 19.99,
  "priceText": "$19.99",
  "currency": "USD",
  "rating": 4.7,
  "reviewCount": 1234,
  "numberOfOffers": null,
  "availability": null,
  "inputUrl": "https://www.amazon.com/Best-Sellers/zgbs",
  "url": "https://www.amazon.com/dp/B0EXAMPLE01",
  "scrapedAt": "2026-08-02T16:45:00.000Z",
  "errorCode": null,
  "error": null,
  "errorDescription": null
}

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

This Actor uses pay-per-event billing: the start (Run started) event is charged once when extraction begins, and item (Item extracted) is charged for each product row saved to the dataset. Diagnostic rows do not incur an item charge. A run with no products can still incur the start charge.

Set maxItems explicitly to bound product results. Additional category or page requests can take longer. For current rates and volume tiers, open the live Apify Pricing tab.

Tips for best results

• Start with 10 products. Check that your selected list and marketplace return useful product rows before increasing the cap.
• Choose the marketplace in the URL. The retained country setting does not control request location or guarantee regional prices.
• Inspect status before using an export. Keep product rows for analysis and review diagnostic descriptions separately.
• Compare the same category and marketplace. Preserve source URLs, page context and collection time when joining repeated exports.
• Check the displayed currency. Leave missing commerce fields unknown rather than assuming values from another marketplace.

Limits and caveats

Amazon page availability, prices, currency and visible card fields vary by marketplace and region. Optional commerce fields can be null. Currency interpretation is limited, so inspect it before comparing marketplaces.

position is page-local card order rather than a guaranteed Amazon sales-rank badge or continuous rank across pages. Repeated pages are skipped, but a product can appear on different categories or pages. Category expansion and next-page discovery depend on available links and do not guarantee exhaustive coverage.

Diagnostic rows are saved for invalid URLs, Robot Check/Sorry responses, request failures and pages where no product cards are detected. Movers & Shakers inputs produce an UNSUPPORTED_LIST_TYPE diagnostic. These rows are separate from products.

Product detail pages, seller profiles, reviews, carts, orders and account-specific recommendations are outside this Actor's scope. Repeated collection and change comparison require your own workflow rather than a built-in continuous monitor.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~amazon-bestsellers-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "startUrls": [
    {
      "url": "https://www.amazon.com/Best-Sellers/zgbs"
    }
  ],
  "maxItems": 10
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/amazon-bestsellers-scraper').call({
  "startUrls": [
    {
      "url": "https://www.amazon.com/Best-Sellers/zgbs"
    }
  ],
  "maxItems": 10
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/amazon-bestsellers-scraper').call(run_input={'startUrls': [{'url': 'https://www.amazon.com/Best-Sellers/zgbs'}], 'maxItems': 10})
print(client.dataset(run['defaultDatasetId']).list_items().items)

MCP and AI agents notes

Pass the quick-start JSON as the Actor input. Read the returned default dataset and inspect status before using nullable commerce fields. Never treat a successful run containing only diagnostics as extracted product data.

MCP and AI agents

You can ask your AI assistant to collect data with Amazon Bestsellers Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Amazon Bestsellers Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/amazon-bestsellers-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Amazon Bestsellers Scraper by Fetch Cat, or give it the identifier fetch_cat/amazon-bestsellers-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Amazon Bestsellers Scraper to collect up to 5 products from this public Amazon Best Sellers category URL. Show ASINs, titles, displayed prices and product links, excluding diagnostic rows.”
• “Collect at most 5 products from the public Amazon New Releases category URL I provide. Keep the marketplace, list type and category link with each row, and report any unavailable input separately.”
• “Collect a small snapshot of up to 5 products from this Best Sellers category. Include ASIN, page-local position and collection time so I can compare it with my earlier export without treating card positions as global sales ranks.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can this Actor scrape Amazon product detail pages?

No. It focuses on ranked public list pages. Use a product-detail Actor for deeper product attributes.

Why are price, rating, or review fields sometimes empty?

Amazon does not show every commerce field on every list card. The Actor preserves nulls instead of inventing values.

Does it return diagnostic rows?

Yes. Invalid URLs, Robot Check/Sorry pages, failed requests, and parse-empty pages are saved with status: "ERROR" and an error code.

Does this Actor provide built-in monitoring?

No. Each run produces a snapshot. Compare separate exports for the same category and page. It does not send change alerts or maintain a cross-run history.

Related Actors

More Amazon scrapers

• Amazon Products & Search Scraper — Collect public Amazon search listings or look up ASINs and product URLs with available product metadata.
• Amazon Reviews Scraper — Collect available public written reviews for Amazon.com products, including review text, ratings and dates.
• Amazon Seller Profiles Scraper — Retrieve one public Amazon seller profile with identity, storefront links and available feedback or business details.

• Google Shopping Results Scraper — Collect Google Shopping result cards with displayed prices, merchant snippets and available rating or shipping signals.
• Walmart Products Scraper — Collect public Walmart US search listings with product identifiers, displayed prices and available seller or fulfillment labels.
• AliExpress Products Scraper — Collect public AliExpress listing cards with available prices, ratings and product links, rather than full product details.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥