Amazon Sellers Scraper

Discover and scrape Amazon seller profiles — name, feedback ratings, publicly listed business address, response time, and more — from seller IDs, storefronts, product pages, or category pages across 18 supported Amazon marketplaces. Great for due diligence, brand monitoring, and competitive research.

Why use Amazon Sellers Scraper?

The actor uses an HTTP+Cheerio pipeline with residential proxy rotation, CAPTCHA detection, bounded retries, and marketplace-safe routing. If the first profile attempt returns a blocked or empty response, a resource-blocked browser document can recover the profile; if it fails, one fresh residential identity tries an alternate profile URL before giving up. Product and category discovery stays on the input marketplace, and category product checks use a small bounded worker pool for faster completion without unbounded load. PPE billing charges the result event only for seller rows actually produced.

What does Amazon Sellers Scraper do?

This actor extracts detailed seller profile data from Amazon seller storefronts (/sp?seller=...). It normally reads Amazon's server-rendered HTML using HTTP+Cheerio; a resource-blocked browser document is a fallback for blocked or empty seller-profile responses.

Given seller IDs, storefront URLs, product URLs, or category URLs, the actor discovers unique merchants per marketplace and scrapes:

• Seller name and profile URL
• Positive feedback percentage (lifetime)
• Total feedback count and per-period counts (12mo, 90d, 30d)
• Positive / neutral / negative feedback breakdown
• Business name (from "Detailed Seller Information" section)
• Business address (when publicly listed by Amazon)
• Seller member since date
• Response time (when listed)

Use cases

• B2B lead generation — build lists of Amazon sellers with their business names and addresses for outreach (FBA prep services, Amazon advertising agencies, logistics providers)
• Seller due diligence — verify seller feedback health before wholesale or partnership deals
• Competitor monitoring — track competitor sellers' feedback trends over time
• Brand protection — identify unauthorized resellers by scraping seller storefront info
• Market research — analyze the seller landscape for a product category

How to use Amazon Sellers Scraper

1. Enter seller IDs or URLs

You can provide input in two ways:

Option A — Seller IDs: Enter one or more Amazon seller IDs (e.g. A2L77EE7U53NWQ). Bare IDs use the marketplace selector, which defaults to amazon.com for backward compatibility. You can find a seller's ID on any Amazon product listing under "Sold by" → click the seller name → the URL contains seller=XXXX.

Option B — Storefront URLs: Paste full seller profile URLs on a supported marketplace, such as:

• https://www.amazon.com/sp?seller=A2L77EE7U53NWQ
• https://www.amazon.de/sp?seller=A3JWKAKR8XB7XF

The URL domain is preserved end-to-end; it is never silently redirected to Amazon.com.

Option C — Product URLs: Paste Amazon /dp/ASIN or /gp/product/ASIN URLs. The actor resolves the third-party selling merchant currently exposed in the product buy box, then reuses the seller-profile pipeline. A product sold directly by Amazon, or one where Amazon does not expose a third-party merchant link, honestly produces no seller.

Option D — Category URLs: Paste Amazon category, browse, bestseller, or search-result URLs. The actor traverses up to maxProductsPerCategory visible products per URL (10 by default), discovers their merchants, and stops emitting at maxResults unique sellers.

2. Configure proxy

Amazon requires proxy rotation to avoid rate limiting. The default residential proxy is recommended, and its country automatically follows each URL marketplace. An explicit apifyProxyCountry overrides that routing for all requests. Datacenter groups are cheaper but may be less reliable.

3. Run and export

Results are available as JSON, CSV, or Excel directly from the Apify dataset. You can also integrate via the Apify API or connect to Zapier / Make.

Input

Field	Type	Description
sellerIds	Array of strings	Amazon seller IDs (e.g. A2L77EE7U53NWQ)
marketplace	String	Marketplace for bare seller IDs (default: amazon.com)
startUrls	Array of URL objects	Seller profile/storefront URLs on supported Amazon domains
productUrls	Array of URL objects	Amazon product pages whose current third-party merchant should be discovered
categoryUrls	Array of URL objects	Amazon category, browse, bestseller, or search pages to traverse
maxProductsPerCategory	Integer	Max visible products traversed per category URL (default: 10, max: 100)
categoryConcurrency	Integer	Bounded category product checks running at once (default: 3, max: 5)
maxResults	Integer	Max number of unique seller profiles to scrape across all routes (default: 50)
proxyConfiguration	Object	Apify Proxy settings (default: RESIDENTIAL)
maxRequestRetries	Integer	Retry attempts per failed request (default: 3)

Supported Amazon marketplaces

The actor explicitly supports amazon.com, amazon.ca, amazon.com.mx, amazon.com.br, amazon.co.uk, amazon.de, amazon.fr, amazon.it, amazon.es, amazon.nl, amazon.se, amazon.pl, amazon.com.be, amazon.in, amazon.co.jp, amazon.com.au, amazon.ae, and amazon.sa.

Seller, product, and category URLs must use one of these exact Amazon domains. Unsupported and lookalike hosts fail before any page request. The same seller ID on two marketplaces is treated as two distinct seller profiles, while duplicate sources within one marketplace merge into one row with deterministic provenance.

Output

Each successfully scraped seller is saved as one record in the dataset. Fields that Amazon does not publicly show remain null rather than being guessed:

{
  "sellerId": "A2L77EE7U53NWQ",
  "name": "Example Seller LLC",
  "url": "https://www.amazon.com/sp?seller=A2L77EE7U53NWQ",
  "positiveRatingPercent": 95,
  "feedbackCount": 1240,
  "recentFeedback12Mo": 312,
  "recentFeedback90Days": 78,
  "recentFeedback30Days": 22,
  "positiveFeedback": 1178,
  "neutralFeedback": 37,
  "negativeFeedback": 25,
  "businessName": "Example Seller LLC",
  "businessAddress": "123 Main St, Seattle, WA 98101, US",
  "memberSince": "January 2018",
  "responseTime": "within 24 hours",
  "marketplace": "amazon.com",
  "scrapedAt": "2026-05-10T08:00:00.000Z",
  "discoveredFrom": [
    {
      "type": "product",
      "sourceUrl": "https://www.amazon.com/dp/B0BJMSH4JX",
      "productAsin": "B0BJMSH4JX"
    }
  ]
}

discoveredFrom is additive provenance. When the same seller appears in direct, product, and category inputs, the actor merges unique deterministic provenance entries, emits one seller row, and charges one result event.

How much does it cost to scrape Amazon sellers?

This actor uses Pay-Per-Event (PPE) billing:

• Run start: $0.005 (one-time per run)
• Per seller scraped: $0.005 (FREE), $0.004 (BRONZE), $0.0035 (SILVER), $0.003 (GOLD), $0.0017 (PLATINUM), $0.0008 (DIAMOND)

Scraping 1,000 sellers costs approximately $0.80–$5.00 depending on your subscription tier, plus proxy costs.

Tips for best results

• Use RESIDENTIAL proxy for higher success rates. Amazon aggressively blocks datacenter IPs; the default country follows each marketplace unless explicitly overridden.
• Category traversal is bounded by maxProductsPerCategory; lower it for a smaller discovery run.
• Products sold by Amazon itself or pages without an exposed third-party merchant produce no seller result.
• Seller pages for large sellers (high feedback count) load more data — expect slightly more detail.
• Business address is only shown when the seller has voluntarily published it (EU-based sellers are required to by law; US sellers may omit it).
• Seller IDs are uppercase alphanumeric strings starting with A (14 characters).

FAQ (Frequently asked questions)

Where do I find a seller ID? On any Amazon product page, click the seller's name under "Sold by". The resulting URL contains seller=XXXXXXXXXXXXXXXX — that's the seller ID.

Does this scrape email addresses? The actor does not claim to return email addresses, phone numbers, or other private contact data. It returns the public business address when Amazon displays one; otherwise the field is null.

What happens if a seller page is blocked? The actor tries a lightweight browser document after a blocked/empty profile response and, if needed, one alternate HTTP profile URL with a fresh residential session. If no recognizable seller profile is available, it logs a warning and skips that seller without charging a result.

Is this actor legal to use? This actor scrapes publicly accessible Amazon seller profile pages, the same data visible to any browser user. Always ensure your use case complies with Amazon's Terms of Service and applicable data protection laws.

Integrations

• Apify API — download results or trigger runs programmatically
• Zapier / Make — automate workflows with new scraped seller data
• Google Sheets — export directly via the Apify Google Sheets integration

Who is it for?

Amazon Sellers Scraper is designed for:

• B2B sales teams looking to build targeted outreach lists of Amazon sellers in specific categories
• Amazon aggregators (Thrasio-style buyers) researching acquisition targets based on feedback health
• Brand protection managers identifying unauthorized resellers listing a brand's products
• SaaS companies offering tools to Amazon sellers (advertising, logistics, bookkeeping) who need prospect lists
• Market researchers analyzing seller density and quality across Amazon categories

API Usage

You can trigger and retrieve results from Amazon Sellers Scraper programmatically.

Node.js (Apify Client)

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });

const run = await client.actor('automation-lab/amazon-sellers-scraper').call({
    sellerIds: ['A2L77EE7U53NWQ', 'ATVPDKIKX0DER'],
    maxResults: 10,
    proxyConfiguration: { useApifyProxy: true, apifyProxyGroups: ['RESIDENTIAL'] },
});

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

Python (ApifyClient)

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")

run = client.actor("automation-lab/amazon-sellers-scraper").call(run_input={
    "sellerIds": ["A2L77EE7U53NWQ", "ATVPDKIKX0DER"],
    "maxResults": 10,
    "proxyConfiguration": {"useApifyProxy": True, "apifyProxyGroups": ["RESIDENTIAL"]},
})

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

cURL

# Start a run
curl -X POST "https://api.apify.com/v2/acts/automation-lab~amazon-sellers-scraper/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"sellerIds":["A2L77EE7U53NWQ"],"maxResults":5}'

# Get results (replace DATASET_ID with the ID from the run response)
curl "https://api.apify.com/v2/datasets/DATASET_ID/items?token=YOUR_TOKEN"

Legality — Is Amazon Sellers Scraper legal?

This actor only accesses publicly accessible Amazon seller profile pages — the same pages visible to any person browsing Amazon without logging in. No login credentials are used and no private data is accessed.

The data extracted (seller names, business addresses, feedback ratings) is publicly displayed by Amazon on seller profile pages. In many jurisdictions, scraping publicly available web data is lawful. However, you remain responsible for:

• Complying with Amazon's Terms of Service for your use case
• Ensuring your use of the data complies with applicable data protection laws (GDPR, CCPA, etc.)
• Not using the data for spam, harassment, or other unlawful purposes

This actor is an independent data-extraction tool and is not affiliated with, endorsed by, or sponsored by Amazon.

Data handling, AI, and support

The actor does not call an AI model or send input or scraped records to an AI provider. It sends only the requested public Amazon URLs through the configured network route. Seller rows are written to the run's default Apify dataset; up to two diagnostic seller-page HTML snapshots may be written to the run's key-value store. The actor creates no external database or cache. Datasets, key-value store records, and logs follow your Apify account retention settings and can be deleted with the corresponding run or storage controls.

Inputs and outputs can contain public business names and addresses. Use them only when you have a lawful purpose, and avoid placing secrets in URLs. Operational logs contain request labels, status, retry information, and seller IDs but do not intentionally log proxy credentials or full seller-page HTML.

For problems or feature requests, use the Actor's Issues tab and include a sanitized input and run ID. Do not post credentials or private data.

MCP (Model Context Protocol)

Amazon Sellers Scraper is available as an MCP server, allowing you to query Amazon seller data directly from AI assistants like Claude.

Claude Desktop

$claude mcp add --transport http https://mcp.apify.com?tools=automation-lab/amazon-sellers-scraper

Cursor

Add this remote server in Settings → Cursor Settings → MCP:

{
  "mcpServers": {
    "amazon-sellers-scraper": {
      "url": "https://mcp.apify.com?tools=automation-lab/amazon-sellers-scraper"
    }
  }
}

VS Code

Add the same server to .vscode/mcp.json:

{
  "servers": {
    "amazon-sellers-scraper": {
      "type": "http",
      "url": "https://mcp.apify.com?tools=automation-lab/amazon-sellers-scraper"
    }
  }
}

Example prompts you can ask your AI assistant:

• "Look up the feedback rating and business address for Amazon seller A2L77EE7U53NWQ"
• "Scrape profile data for these 5 seller IDs and give me a summary table"
• "Find the business name and address for the seller on this product listing URL"

Related actors

• Amazon Scraper — scrape product listings, prices, and ASINs from Amazon
• Amazon Reviews Scraper — collect product reviews in bulk
• Amazon Bestsellers Scraper — extract bestseller rankings by category