Amazon Seller Data Extractor By Keyword Search

Amazon Seller Scraper — Extract Profiles, Reviews & VAT Data as JSON

Amazon Seller Data Extractor By Keyword Search finds third-party Amazon sellers by keyword, ASIN, seller ID, or storefront URL, and returns each seller's profile, feedback/ratings, and — on EU marketplaces — their GDPR business-transparency disclosure (VAT number, trade-register number, business type and address). Every response is typed, normalized JSON, not HTML you have to parse. Results land directly in an Apify dataset ready for Sheets, a BI tool, or a CRM. After reading this page you'll know which input to set for keyword prospecting, direct lookups, or storefront enumeration.

What is Amazon Seller Data Extractor By Keyword Search?

Amazon Seller Data Extractor By Keyword Search is an Apify Actor that discovers and profiles third-party sellers on Amazon. It supports three discovery paths — keyword search (finds and de-duplicates unique sellers behind search results), direct lookup (ASIN or seller ID), and URL enumeration (a seller storefront or search-results URL walks every ASIN that seller lists) — and enriches each seller with rating history, written feedback, and, on EU domains, the seller's mandatory business-disclosure panel. No Amazon account or login is required; it fetches only publicly served seller and product pages.

• Discover sellers by keyword, resolving and de-duplicating by seller ID
• Look up a specific seller directly by ASIN, seller ID, or storefront URL
• Collect seller feedback/reviews with configurable sort order (recent, helpful, rating)
• Pull the EU business-transparency panel (VAT, trade-register number, business type, address) on .de/.fr/.it/.es/.nl/.se/.pl
• Export results as JSON or CSV, with no proxy management required

What data does Amazon Seller Data Extractor By Keyword Search collect?

The Actor returns three distinct kinds of data for every seller it resolves: the seller profile itself, that seller's feedback/reviews, and — on supported EU marketplaces — a business-transparency record.

Data Type	Key Fields	JSON Field Names
Seller Profiles	seller name, seller ID, star rating, positive-feedback %, storefront URL, description	seller_name, seller_id, stars, rating_positive, products_link, description
Seller Feedback / Ratings	individual review text, star rating, date, plus lifetime/12mo/3mo/1mo rating counts	feedbacks[].text, feedbacks[].stars, feedbacks[].date, rating_count_lifetime, rating_count_m12, rating_count_m3, rating_count_m1
EU Business Transparency	VAT number, trade-register number, business type, registered address, disclosed phone/email	vat_number, trade_register_number, business_type, business_address, seller_phone_number, business_email

Need more Amazon data?

If you need product-level data instead of seller data, Amazon Bestsellers Scraper: Product Photo & Spec Details enriches ranked Best Sellers products with images, specs, and variations, and Amazon Search Products & Trending Scraper scores keyword markets for trending badges, Best-Sellers-Rank, and demand. Pair either one with this Actor to go from "which products are winning" to "who is selling them."

How does Amazon Seller Data Extractor By Keyword Search differ from the official Amazon API?

Amazon's Product Advertising API (PA-API) is built for Amazon Associates affiliates to pull product and offer data for their own affiliate content — it requires an active, approved Associates account, ties access to affiliate-linking activity, and does not expose arbitrary seller-profile, feedback, or business-transparency data at all. Amazon Seller Data Extractor By Keyword Search instead reads the same seller and product pages a shopper's browser would, so it can return seller profiles, ratings history, and EU business-disclosure fields that PA-API has no endpoint for.

Feature	Amazon PA-API	Amazon Seller Data Extractor By Keyword Search
Access requirement	Approved Amazon Associates account	Runs on Apify, no Amazon account needed
Seller profile data	Not exposed	Full seller profile per lookup
Seller feedback/reviews	Not exposed	Feedback text, stars, dates, rating windows
EU business-transparency data	Not exposed	VAT, trade-register, business type, address on supported domains
Discovery by keyword	Product search only, tied to affiliate use	Keyword → unique-seller discovery, de-duped by seller ID
Discovery by storefront URL	Not supported	Enumerates every ASIN a seller lists

If you already have an approved Associates account and only need catalog/pricing data for affiliate content, PA-API is the right tool. If you need seller-level profile, feedback, or business-disclosure data — which PA-API simply doesn't return — this Actor is the option that reaches it.

Why do developers and teams scrape Amazon?

For seller and competitor research

Sellers and agencies use keyword discovery to map every third-party merchant active in a niche — "handmade ceramics" or "electronics refurb" — and pull each one's rating_positive, rating_count_lifetime, and recent feedbacks[] to gauge how established a competitor is before entering that category. Because discovery de-dupes by seller_id, a single run produces a clean list of unique competing storefronts instead of duplicate rows from overlapping search-result pages. Sorting with keywordSortOrder set to "Best Sellers" surfaces the strongest incumbents first, so a research team can prioritize which sellers to profile in depth before committing to a category.

For marketplace due diligence and compliance teams

Compliance and legal teams researching EU sellers use businessTransparencyLookup to pull the VAT number, trade-register number, and registered business address Amazon is required to disclose under the Omnibus Directive. This turns a manual per-seller lookup into a batch job across .de, .fr, .it, .es, .nl, .se, and .pl storefronts, producing a structured record of vat_number, trade_register_number, and business_address for audit or vendor-verification purposes. Feeding a list of sellerIdsToLookup gathered from prior research lets a due-diligence team batch-verify a whole vendor panel in one run instead of opening each seller's storefront page individually and copying disclosure fields by hand.

For lead sourcing and outreach teams

Agencies and wholesalers sourcing suppliers or partners paste a seller's storefront URL into discoveryUrls to enumerate every ASIN that seller lists, or run keyword discovery against a product category to surface active merchants worth contacting, using seller_name, products_link, and any disclosed seller_phone_number or business_email as the outreach starting point. Because rating_count_lifetime and rating_positive are returned alongside contact details, an outreach list can be filtered to established, well-rated sellers before anyone on the team sends a single message, cutting down on cold outreach to inactive or low-quality storefronts.

For developers building data products

Developers building seller-monitoring dashboards or pricing-intelligence tools call the Actor's REST API on a schedule, feeding the typed JSON output directly into a database without writing an HTML parser. Because discovery_mode and source_keyword/source_asin are stamped on every row, a single dataset can be joined back to the keyword or ASIN that produced it for downstream analytics. Since the direct-lookup and keyword-discovery tiers run on independent concurrency settings (maxParallelSellerLookups versus maxParallelKeywordSearch/maxParallelProductFetch), a product built on this Actor can run a large background discovery job without slowing down time-sensitive direct-lookup requests from end users.

How to scrape Amazon (step by step)

1. Open Amazon Seller Data Extractor By Keyword Search on its Apify Store page and click Try for free (or Start, if already added to your account).
2. Provide at least one input group: searchKeywords for keyword discovery, productAsinsOrSellerIds / sellerIdsToLookup for direct lookups, or discoveryUrls for storefront/search-URL enumeration — the Actor requires no single field, but needs at least one of these to have anything to process.
3. Set searchCategory and keywordSortOrder to scope a keyword search, or turn on businessTransparencyLookup if you're targeting an EU marketplace via marketplaceToSearch.
4. Click Start and watch the run log — it reports domain, proxy country, and how many direct lookups, keywords, and discovery URLs were queued.
5. When the run finishes, download results as JSON or CSV from the dataset, or open the keywordDiscovery / euBusinessTransparency dataset views for a narrower column set.

What to do when Amazon changes its structure

Amazon's seller and search pages change their markup periodically. The Actor is maintained, and the output schema is designed to stay stable — field names and types don't change on your end even when the underlying parsing logic has to be updated to keep up with a markup change.

⬇️ Input

Parameter	Required	Type	Description	Example Value
searchKeywords	no	array	One search phrase per row. Each keyword runs its own Amazon search → product → seller resolution pipeline. Also accepts the legacy keywordInputs key.	["handmade ceramics"]
searchCategory	no	string	Amazon's department/category index for the search (e.g. "aps"=All Departments, "electronics", "kitchen"). Applies to every keyword above.	"aps"
keywordSortOrder	no	string (enum)	How Amazon orders the search results walked to find sellers: Featured, Best Sellers, Price: Low to High, Price: High to Low, Avg. Customer Review, Newest Arrivals, Relevance.	"Featured"
maxSellersPerKeyword	no	integer (1–500)	Stop each keyword's discovery once this many distinct sellers (de-duped by seller ID) have been found.	20
discoveryUrls	no	array	An Amazon search-results URL OR a seller's own storefront-listing URL (https://www.amazon.com/s?me=<sellerId>) to enumerate all of its ASINs. A plain product (/dp/) or seller (/sp?seller=) URL is looked up directly instead.	[]
businessTransparencyLookup	no	boolean	When ON and the marketplace domain is amazon.de/.fr/.it/.es/.nl/.se/.pl, fetches each seller's page a second time to surface VAT/trade-register/business-type/address. No-op on non-EU domains.	true
productAsinsOrSellerIds	no	array	One ASIN (e.g. B00P8XQPY4) or seller ID (e.g. A33W53J5GVPZ8K) per row. Also accepts the legacy asinInputs key.	["B00P8XQPY4"]
sellerIdsToLookup	no	array	Amazon seller IDs like A33W53J5GVPZ8K, when you already know exactly who to research. Also accepts the legacy usernameInputs key.	[]
marketplaceToSearch	no	string	Amazon marketplace domain, e.g. amazon.com, amazon.co.uk, amazon.de, amazon.co.jp. Also accepts the legacy amazonDomain key.	"amazon.com"
pageLocaleHint	no	string	Optional locale string (en-US, de-DE…). Leave blank to let Amazon decide. Also accepts the legacy language key.	""
targetProxyCountry	no	string	ISO-style country for proxy routing, or AUTO. Also accepts the legacy proxyCountry key.	"AUTO"
captchaHelperEnabled	no	boolean	Flip ON if Amazon throws puzzles often — escalates the retry ladder. Also accepts the legacy useCaptchaSolver key.	false
reviewSortPreference	no	string (enum)	How feedback is ordered when collected: recent, helpful, rating. Also accepts the legacy sortOrder key.	"recent"
maxReviewsPerSeller	no	integer (0–1000)	Cap feedback rows per seller (0 = grab everything the page allows). Also accepts the legacy maxComments key.	10
maxParallelSellerLookups	no	integer (1–20)	Concurrency for the direct ASIN/seller-ID/URL lookup tier. Also accepts the legacy maxConcurrency key.	10
maxParallelKeywordSearch	no	integer (1–10)	Its own concurrency lane for keyword/URL discovery search pages, kept separate from the direct-lookup tier.	3
maxParallelProductFetch	no	integer (1–20)	Its own concurrency lane for resolving discovered products into sellers during keyword/URL discovery.	8
proxyConfiguration	no	object	This Actor always runs on residential proxies for both tiers. UI choices here stay for compatibility but may be overridden automatically.	{"useApifyProxy": false}

No single parameter is required — but if you leave searchKeywords, productAsinsOrSellerIds, sellerIdsToLookup, and discoveryUrls all empty, the run has nothing to process and exits with no results.

{
  "searchKeywords": ["handmade ceramics"],
  "searchCategory": "aps",
  "keywordSortOrder": "Featured",
  "maxSellersPerKeyword": 20,
  "discoveryUrls": [],
  "businessTransparencyLookup": true,
  "productAsinsOrSellerIds": ["B00P8XQPY4"],
  "sellerIdsToLookup": [],
  "marketplaceToSearch": "amazon.com",
  "pageLocaleHint": "",
  "targetProxyCountry": "AUTO",
  "captchaHelperEnabled": false,
  "reviewSortPreference": "recent",
  "maxReviewsPerSeller": 10,
  "maxParallelSellerLookups": 10,
  "maxParallelKeywordSearch": 3,
  "maxParallelProductFetch": 8,
  "proxyConfiguration": { "useApifyProxy": false }
}

The most common input mistake is turning on businessTransparencyLookup while marketplaceToSearch is set to a non-EU domain like amazon.com — the Actor logs that it's skipping the panel rather than failing, so check the run log if vat_number and related fields come back empty.

⬆️ Output

Every result is a typed, normalized JSON row pushed to the Actor's Apify dataset, exportable as JSON, CSV, Excel, or via API. Discovery-mode rows (keyword or URL enumeration) and direct-lookup rows share the same seller-profile shape, plus a few discovery-context fields.

Scraped Seller Profile

{
  "section_index": 1,
  "section": "B00P8XQPY4",
  "discovery_mode": "asin",
  "source_keyword": null,
  "source_asin": "B00P8XQPY4",
  "source_product_name": null,
  "source_product_url": "https://www.amazon.com/dp/B00P8XQPY4",
  "url": "https://www.amazon.com/sp?seller=A33W53J5GVPZ8K",
  "seller_id": "A33W53J5GVPZ8K",
  "seller_name": "Stackbear",
  "description": "Stackbear is a family-run seller of handmade home goods.",
  "detailed_info": [
    { "title": "Business Name", "value": "Stackbear LLC" },
    { "title": "Business Address", "value": "1200 Market St, Wilmington, DE, US" }
  ],
  "feedbacks": [
    { "stars": "5.0 out of 5 stars", "text": "Fast shipping, item as described.", "date": "Reviewed in the United States on June 3, 2026" }
  ],
  "stars": "4.7 out of 5 stars",
  "return_policy": ["Items can be returned within 30 days of receipt."],
  "shipping_policies": "Ships within 2 business days.",
  "privacy_security": "This seller adheres to Amazon's privacy and security standards.",
  "privacy_policy": "",
  "help_content": "Contact the seller through Amazon's Buyer-Seller Messaging.",
  "products_link": "https://www.amazon.com/s?ie=UTF8&me=A33W53J5GVPZ8K",
  "rating_positive": "94% positive lifetime",
  "feedbacks_percentages": { "star_5": "82%", "star_4": "9%", "star_3": "3%", "star_2": "2%", "star_1": "4%" },
  "rating_count_m12": 412,
  "rating_count_m3": 98,
  "rating_count_lifetime": 3106,
  "rating_count_m1": 31,
  "country": "US",
  "timestamp": "2026-07-25T09:14:02.000Z",
  "seller_phone_number": null,
  "eu_business": null,
  "business_transparency_available": false,
  "vat_number": null,
  "trade_register_number": null,
  "business_type": null,
  "business_address": null,
  "business_country_code": null,
  "business_email": null
}

Keyword-Discovered Seller

{
  "section_index": 2,
  "section": "keyword: handmade ceramics",
  "discovery_mode": "keyword_search",
  "source_keyword": "handmade ceramics",
  "source_asin": "B0CQRSK1F2",
  "source_product_name": "Handmade Stoneware Mug Set of 4",
  "source_product_url": "https://www.amazon.com/dp/B0CQRSK1F2",
  "url": "https://www.amazon.com/sp?seller=A1PTWQ9XJ7HZ2K",
  "seller_id": "A1PTWQ9XJ7HZ2K",
  "seller_name": "Kiln & Clay Co.",
  "description": "Small-batch stoneware and ceramics studio.",
  "detailed_info": [
    { "title": "Business Name", "value": "Kiln & Clay Co." }
  ],
  "feedbacks": [
    { "stars": "5.0 out of 5 stars", "text": "Beautiful glaze, well packaged.", "date": "Reviewed in the United States on May 21, 2026" }
  ],
  "stars": "4.9 out of 5 stars",
  "rating_positive": "97% positive lifetime",
  "rating_count_lifetime": 512,
  "rating_count_m12": 88,
  "rating_count_m3": 19,
  "rating_count_m1": 6,
  "country": "US",
  "timestamp": "2026-07-25T09:16:47.000Z",
  "seller_phone_number": null,
  "business_transparency_available": false
}

EU Business Transparency Record

{
  "seller_name": "Töpferwerk GmbH",
  "seller_id": "A2K9X7YFQZ1V3M",
  "business_type": "GmbH",
  "vat_number": "DE291837465",
  "trade_register_number": "HRB 84213",
  "business_address": "Musterstraße 12, 10115 Berlin, DE",
  "business_email": "kontakt@topferwerk-example.de",
  "seller_phone_number": "+49 30 1234567",
  "business_transparency_available": true,
  "eu_business": {
    "business_name": "Töpferwerk GmbH",
    "business_type": "GmbH",
    "registration_number": "HRB 84213",
    "vat_number": "DE291837465",
    "phone_number": "+49 30 1234567",
    "email": "kontakt@topferwerk-example.de",
    "business_address": "Musterstraße 12, 10115 Berlin, DE",
    "country_code": "DE"
  }
}

How many results can you scrape with Amazon Seller Data Extractor By Keyword Search?

Each keyword or discovery URL is capped by maxSellersPerKeyword (1–500, default 20 unique sellers), and discovery stops early once that many distinct seller IDs are found or Amazon's search results run out (the Actor caps its own internal search-page walk at 200 pages per keyword). Direct lookups via productAsinsOrSellerIds, sellerIdsToLookup, or a direct product/seller discoveryUrls entry have no built-in cap — the Actor processes exactly as many rows as you supply. There is no overall cap across how many keywords, ASINs, or discovery URLs you submit in one run; total runtime scales with the number of inputs and your concurrency settings.

Integrate Amazon Seller Data Extractor By Keyword Search and automate your workflow

Amazon Seller Data Extractor By Keyword Search works with any language or tool that can send an HTTP request.

REST API integration

import requests

run = requests.post(
    "https://api.apify.com/v2/acts/api-empire~amazon-seller-data-extractor-by-keyword-search/run-sync-get-dataset-items",
    params={"token": "YOUR_APIFY_TOKEN"},
    json={
        "searchKeywords": ["handmade ceramics"],
        "maxSellersPerKeyword": 20,
        "marketplaceToSearch": "amazon.com",
    },
)
sellers = run.json()
for seller in sellers:
    print(seller["seller_name"], seller["seller_id"], seller["rating_positive"])

Works in Python, Node.js, Go, Ruby, cURL.

Automation platforms (n8n, Make)

In n8n, use the Apify node's "Run Actor and get dataset items" operation, pointing it at api-empire/amazon-seller-data-extractor-by-keyword-search with your searchKeywords or productAsinsOrSellerIds as JSON input. In Make, the equivalent is the Apify > Run Actor module followed by an Apify > Get Dataset Items module, which you can chain into a Google Sheets or CRM module to push new sellers as they're discovered.

Is it legal to scrape Amazon?

Yes — Amazon Seller Data Extractor By Keyword Search only reads seller, product, and business-disclosure pages that Amazon already serves publicly to any visitor, without logging in or bypassing any access control. The seller and business data returned (store names, ratings, VAT numbers, trade-register numbers) is business data governed primarily by Amazon's Terms of Service and database-rights considerations, not personal-data law. That said, some fields — a disclosed seller_phone_number or business_email tied to an individual sole trader — can constitute personal data under GDPR/CCPA depending on the seller's legal structure. Consult legal counsel for commercial use cases involving bulk personal data.

Frequently asked questions

Does Amazon Seller Data Extractor By Keyword Search work without an Amazon account?

Yes. It fetches publicly served Amazon seller, product, and search pages directly — no Amazon account, login, or API key is required to run it.

How often is the scraped data updated?

Every run performs a live fetch of the current Amazon seller and product pages at the time you start it — nothing is served from a cache, so results reflect Amazon's live page content for that run.

What happens if a seller ID or ASIN no longer resolves to a seller?

If Amazon returns no seller link on a product page, or a direct seller lookup can't find a seller-name element, the Actor logs the failure and skips that row rather than pushing an empty or fabricated record — check the run log for "no data — Amazon blocked or seller not found" entries to identify which inputs didn't resolve.

Can I scrape private or login-gated Amazon content?

No. Only publicly accessible seller and product pages are returned — pages that require a buyer login or are otherwise access-gated are not reachable by this Actor.

Does Amazon Seller Data Extractor By Keyword Search work for AI agent workflows and LLM pipelines?

Yes — it's callable as an HTTP endpoint from any agent framework via the Apify REST API. Every response is typed JSON with stable field names, so there's no HTML-parsing step before passing seller records into an LLM context window or agent tool call.

How does Amazon Seller Data Extractor By Keyword Search handle Amazon's anti-bot system?

It rotates residential proxies on a sticky session per lookup, retries with proxy rotation and a fresh session warm-up when Amazon returns a block/CAPTCHA page, and detects block pages in multiple languages (English, German, French, Italian, Spanish, Dutch, Swedish, Polish). Turning on captchaHelperEnabled escalates the retry ladder to more attempts with longer backoff rather than solving CAPTCHA images.

Does Amazon Seller Data Extractor By Keyword Search return data in a format LLMs can use directly?

Yes. Output is typed, normalized JSON with stable field names — no HTML, no selectors, no parsing required before you index it into a vector store or pass it to an LLM.

Can I use Amazon Seller Data Extractor By Keyword Search without managing proxies?

Yes. The Actor always runs on residential proxies for both the direct-lookup and keyword-discovery tiers; the proxyConfiguration input is kept for compatibility but proxy routing is handled for you.

What happens when Amazon changes its structure or blocks the scraper?

The Actor is maintained, and the output schema is designed to stay stable — field names and types don't change on your end even when the underlying parsing has to be updated to track a markup change.

Your feedback

Found a bug or missing a field? We want to know. Reach out through the Actor's Apify Store page or your Apify Console support channel so we can look into it and keep the schema accurate.