Amazon DE Sellers Leads Scraper

Amazon DE Seller Leads Scraper — Business Info, VAT & Ratings

Amazon DE Seller Leads Scraper searches Amazon.de by keyword and category, then follows every product to the seller behind it — pulling business name, VAT number, trade register number, phone, email, and address, alongside the product's price, rating, and review count. Every seller lead ships as structured JSON, ready for a CRM, spreadsheet, or database — no HTML parsing required. Paste search or product URLs directly, or let the Actor build the search for you. Run it on the Apify platform in minutes.

---

What is Amazon DE Seller Leads Scraper?

Amazon DE Seller Leads Scraper is an Apify Actor that turns an Amazon.de keyword search (or a list of search/product URLs) into a deduplicated list of third-party seller leads, each enriched with the product that surfaced them and the seller's public business details. It runs entirely against publicly reachable Amazon.de pages — no Amazon account, Seller Central login, or API key is required. It's built for sourcing and procurement teams, lead-generation and sales teams, market researchers, and developers feeding seller data into internal tools or AI pipelines.

---

What Amazon.de seller data is publicly available to scrape?

Amazon.de shows product, seller-reputation, and legally-required business identity data to any visitor without a login; only the seller's own account console is gated.

Data category	Publicly available	Restricted (Seller Central login only)
Product listing (title, price, image, rating)	✅	—
Seller ID and storefront link	✅	—
Seller ratings (lifetime, 1-year, 3-month)	✅	—
"About seller" description	✅	—
Registered business name, address, country	✅ (EU sellers must publish this)	—
VAT / trade register number	✅ where the seller has entered it	—
Business phone / email	✅ where the seller has entered it	—
Seller account login, order history, buyer messages	—	✅

Amazon DE Seller Leads Scraper only returns publicly visible data — what any visitor to Amazon.de sees. Nothing behind a login wall.

---

What data can I extract with Amazon DE Seller Leads Scraper?

Each row returned is one product–seller pair, carrying product listing fields, seller reputation fields, and the seller's business identity fields.

Product and listing fields

Field name	Description
asin	Product ASIN.
product_name	Product title (sponsored-tile prefixes like "Gesponsert:" stripped).
product_url	Direct link to the product page.
image_url	Main product image URL.
price	Current product price.
currency	Currency code (e.g. EUR).
list_price	Strike-through/original price — only set when genuinely higher than price.
product_rating	Product-level star rating (0–5).
product_review_count	Product-level review count.
category	Breadcrumb category path (e.g. Fashion > Damen > Bekleidung).

Seller identity and reputation fields

Field name	Description
seller_id	Amazon seller ID.
seller_page_url	Link to the seller's storefront page.
rating_lifetime	Lifetime average seller rating.
reviews_lifetime	Lifetime seller review count.
rating_1_year	Average seller rating over the last 12 months.
reviews_1_year	Seller review count over the last 12 months.
rating_3_months	Average seller rating over the last 3 months.
reviews_3_months	Seller review count over the last 3 months.
about_seller	The seller's "About seller" text, when published.

Business and registration fields

Field name	Description
business_name	Registered business name ("Geschäftsname").
business_type	Business type ("Geschäftsart").
registration_number	Trade register number ("Handelsregisternummer").
vat_number	VAT ID ("Umsatzsteuer-Identifikationsnummer").
phone_number	Business phone number.
email	Business email address.
business_address	Full business address.
country_code	Country of the registered address (e.g. DE, US).
scraped_at	ISO 8601 UTC timestamp of when the row was collected.

🤖 Add-on: Need additional Amazon data?

Pair this Actor with Amazon Product Details Scraper for deeper per-ASIN specs, or Amazon Price Tracker to watch price movements on the products these sellers list. Both share the ASIN field with this Actor's output, so joining the datasets is a direct key match.

---

Why not build this yourself?

Amazon.de has no public API for this: Amazon's Product Advertising API (PA-API) covers product listings for approved Associates accounts with qualifying referral sales, is being retired (Amazon stopped onboarding new PA-API customers and is migrating remaining users to the Creators API, effective mid-2026), and never exposed a seller's registered business name, VAT number, or contact details even when active. The Selling Partner API only lets a seller manage their own account — it cannot be used to look up other sellers' business information. Building this yourself means maintaining HTML selectors against Amazon's frequent DOM and layout changes, detecting captcha/block pages that Amazon can serve with a plain HTTP 200 status, rotating and paying for proxy infrastructure, and re-implementing a multi-layer fallback just to locate the seller ID on a product page. Amazon DE Seller Leads Scraper already does all of that.

---

How to use Amazon DE Seller Leads Scraper

Run it from the Apify Console — no separate signup or API key needed beyond your Apify account.

1. Open Amazon DE Seller Leads Scraper on the Apify Store and click Try for free.
2. Provide the required input: either keyword + amazon_category, or one or more URLs in startUrls.
3. Optionally set sort_by to control which products are scanned first, and maxResults to cap how many unique seller leads to collect.
4. Click Start and watch progress in the Log tab.
5. Open the Storage → Dataset tab and export results as JSON, CSV, Excel, or another supported format.

How to scale to bulk seller lead extraction

startUrls accepts an array, so a single run can process multiple Amazon.de search URLs and product URLs together — each search URL is paginated automatically and each product URL is resolved straight to its seller. There's no separate "multi-keyword" field: to cover several unrelated keywords or categories in parallel, either list their search URLs together in startUrls, or launch one run per keyword (directly, via the Apify API, or on a schedule) and let each run push to its own dataset.

---

What can you do with Amazon.de seller lead data?

• 🏢 Sourcing and procurement teams use business_name, vat_number, and business_address to vet and shortlist Amazon.de sellers before requesting a quote.
• 📞 Sales and lead-gen teams use email and phone_number to build an outbound contact list for a specific product category.
• 📊 Market researchers use seller_id, price, and product_rating to map how many distinct sellers compete for a given keyword and how they're priced against each other.
• ⚖️ Compliance and trust teams use registration_number and country_code to check a seller's declared legal identity against public trade-register records.
• 🤖 AI engineers feed about_seller, business_name, and the rating fields into a RAG pipeline or agent tool that answers "who sells this product on Amazon.de, and are they established" questions.

---

How does Amazon DE Seller Leads Scraper handle rate limits and blocking?

Every request runs through Apify Proxy, residential and pinned to Germany by default. A session warm-up visit to the Amazon.de homepage sets cookies before any product or seller page is requested, headers rotate across five real desktop/mobile user agents, and requests are spaced with a randomized 0.8–1.5 second delay. Amazon can return a captcha or "confirm you're not a robot" page with a plain HTTP 200 status; the Actor detects this by content, not status code, and treats it as a block. On a block, timeout, or 403/503 response, the connection escalates through connection tiers (default residential → an alternate route, retried up to 3 times per tier) before giving up on that one page, up to 8 attempts total. If a product or seller page still can't be loaded after retries, that product is simply skipped — no partial or error row is pushed to the dataset for it.

---

⬇️ Input

Parameter	Required	Type	Description	Example value
keyword	Yes	String	Enter what you want to search (e.g. shirt, shoes, phone case). Used to discover relevant products and their sellers on Amazon.de. Default: "shirt".	"sneakers"
amazon_category	Yes	String	Category to narrow results. Enum: fashion-womens, fashion-mens, fashion-kids, electronics, grocery, toys, sports, books, beauty, home-garden, automotive, pet-supplies, tools-garden, baby, health. Default: "fashion-womens".	"electronics"
sort_by	No	String	Order search results before seller extraction. Enum: Featured, Best Sellers, Price: Low to High, Price: High to Low, Avg. Customer Review, Newest Arrivals, Relevance, Select.... Default: "Featured".	"Best Sellers"
maxResults	No	Integer	Maximum number of unique seller leads to collect in this run (1–50,000). Higher values may increase run time. Default: 10. Minimum: 1. Maximum: 50000.	500
startUrls	No	Array	Amazon.de search or product URLs to guide scraping directly, with or without keyword/category search. Default: [].	[{"url": "https://www.amazon.de/s?k=sneakers"}]
proxyConfiguration	No	Object	Apify Proxy settings. Uses residential proxy pinned to Germany (DE) by default for reliable Amazon.de access.	{"useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"], "apifyProxyCountry": "DE"}

Example input

{
  "keyword": "sneakers",
  "amazon_category": "fashion-womens",
  "sort_by": "Best Sellers",
  "maxResults": 500,
  "startUrls": [],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "DE"
  }
}

---

⬆️ Output

Results are typed, normalized JSON with a consistent schema across runs — one item per unique product–seller pair, pushed to the dataset the instant it's collected. Download as JSON, CSV, Excel, or another format Apify supports directly from the run's dataset.

Example output

{
  "asin": "B0FCS9LBVN",
  "product_name": "Ficerd 3er Pack Langarm Shirts für Damen",
  "product_url": "https://www.amazon.de/dp/B0FCS9LBVN",
  "seller_id": "A3OJWAJQNSBARP",
  "seller_page_url": "https://www.amazon.de/sp?ie=UTF8&seller=A3OJWAJQNSBARP",
  "category": "Fashion > Damen > Bekleidung > Tops, T-Shirts & Blusen",
  "price": 24.99,
  "currency": "EUR",
  "list_price": 29.99,
  "product_rating": 4.3,
  "product_review_count": 512,
  "image_url": "https://m.media-amazon.com/images/I/71abcXYZ.jpg",
  "rating_lifetime": 4.6,
  "reviews_lifetime": 18420,
  "rating_1_year": 4.7,
  "reviews_1_year": 3210,
  "rating_3_months": 4.8,
  "reviews_3_months": 512,
  "about_seller": "Amazon Export Sales, LLC is a third-party seller on Amazon.de...",
  "business_name": "Amazon Export Sales LLC",
  "business_type": null,
  "registration_number": "82-0544687",
  "vat_number": null,
  "phone_number": "+1206-266-1000",
  "email": "ags-prodm-us-de@amazon.com",
  "business_address": "410 TERRY AVE N, Seattle, WA, 98109-5210, US",
  "country_code": "US",
  "scraped_at": "2026-08-15T10:00:00+00:00"
}

Fields that Amazon doesn't display for a given seller or product (not every seller publishes VAT number, business type, or a list price) come back as null — they are never guessed or interpolated.

---

How does it work?

Requests route through Apify Proxy, residential and pinned to Germany, and a warm-up visit to the Amazon.de homepage sets session cookies before any product or seller page is fetched. Search-result pages are parsed for product ASINs, skipping tiles explicitly tagged as sponsored so an unrelated advertiser isn't reported as an organic result. Each product page is opened and run through a five-layer fallback chain to locate the embedded seller ID — from a direct profile-trigger link down to a raw pattern match in the page HTML — then the seller's storefront and business-info pages are fetched to pull ratings and registration details. Only publicly visible Amazon.de pages are requested; the output schema stays the same field-for-field regardless of how Amazon's page layout changes.

---

Integrations

Amazon DE Seller Leads Scraper runs on the Apify platform, so it works with anything that can call the Apify API or an Apify-built integration.

Calling Amazon DE Seller Leads Scraper programmatically

from apify_client import ApifyClient

client = ApifyClient("<APIFY_API_TOKEN>")

run_input = {
    "keyword": "sneakers",
    "amazon_category": "fashion-womens",
    "maxResults": 500,
}

run = client.actor("amazon-de-sellers-leads-scraper").call(run_input=run_input)

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

Works in Go, Ruby, Node.js, cURL — any language that can make an HTTP request.

MCP integration for AI agents

Amazon DE Seller Leads Scraper is reachable through Apify's official MCP server. Connect a hosted MCP client (e.g. Claude.ai, VS Code) directly to https://mcp.apify.com, or run it locally with npx @apify/actors-mcp-server and an APIFY_TOKEN environment variable, then select this Actor as a callable tool. (Verified against Apify's MCP documentation, 2026-08-15.)

No-code tools (n8n, Make, LangChain)

In n8n, use the official Apify node (or the HTTP Request node) pointed at this Actor's run endpoint to trigger a run and pull the dataset into your workflow. In Make, the Apify app's "Run an Actor" module does the same. In LangChain or similar agent frameworks, wrap the apify_client call above as a tool function.

---

Is it legal to scrape Amazon.de seller leads?

Scraping publicly available business data is generally lawful; Amazon DE Seller Leads Scraper only returns data any visitor to Amazon.de can already see without logging in. The data here — registered business names, VAT and trade-register numbers, business addresses and contact details — is business/company record data, not consumer personal data, so it falls under Amazon's Conditions of Use and general database-rights considerations rather than a GDPR/CCPA personal-data regime. If a seller trades as a private individual rather than a registered company, their contact details could still count as personal data in some jurisdictions. Consult legal counsel if your use case involves bulk storage of personal data.

---

Frequently asked questions

What Amazon.de seller fields does Amazon DE Seller Leads Scraper return?

business_name, vat_number, registration_number, email, and phone_number are the core lead fields, alongside seller_id and the product that surfaced the seller. See What data can I extract above for the full list.

Does Amazon DE Seller Leads Scraper require an Amazon account or login?

No. The Actor makes plain HTTP requests through Apify Proxy against public Amazon.de pages — no Amazon account, Seller Central login, or API key is needed.

How many seller leads can I extract in one run?

Set maxResults from 1 up to 50,000 unique seller leads per run; the default is 10. Higher values increase run time since each lead requires a product-page fetch plus two seller-page fetches.

What happens if a product has no identifiable third-party seller?

If the five-layer seller-ID fallback can't find a seller on a product page — for example a product sold and shipped only by Amazon itself — that product is skipped and no row is pushed for it, so you never get a lead with a missing seller_id.

Can I scrape multiple Amazon.de searches or products at once?

Yes. Paste multiple search and/or product URLs into startUrls in a single run; each is processed and deduplicated by (asin, seller_id) pair.

Does Amazon DE Seller Leads Scraper work with Claude, ChatGPT, and other AI agent tools?

Yes. It's reachable through Apify's MCP server at https://mcp.apify.com for MCP-compatible clients, and callable as a standard HTTP endpoint by any agent framework via apify_client.

What makes Amazon DE Seller Leads Scraper's seller data reliable?

It combines a five-layer fallback chain for locating the seller ID with content-based block-page detection (Amazon can serve a captcha page with a normal HTTP 200 status), so leads aren't silently generated from a page that never actually loaded.

Does Amazon DE Seller Leads Scraper return data in a format LLMs can use directly?

Yes. Typed, normalized JSON with consistent field names across runs — no HTML parsing or selectors needed. Pass it directly to an LLM, index it into a vector store, or feed it to an agent tool.

What happens when Amazon changes its layout or anti-bot system?

The Actor is maintained and the output schema stays stable across Amazon.de layout changes; no specific update turnaround is promised.

Can I use Amazon DE Seller Leads Scraper without managing proxies or browser infrastructure?

Yes. Apify Proxy (residential, pinned to Germany) is preconfigured by default, along with user-agent rotation, session warm-up, and retry/escalation logic — you don't need to run or maintain any of it yourself.

Which fields work best for AI training data and RAG indexing?

For RAG, index about_seller, business_name, and product_name — the free-text fields carrying the most descriptive information. For structured training data, asin, seller_id, business_name, price, and the rating fields return as consistent typed primitives (strings, numbers, or null) across every record.

---

Related scrapers

Scraper name	What it extracts
Amazon Search Scraper	Product listings from an Amazon keyword or search URL.
Amazon Product Details Scraper	Full per-ASIN product specs from Amazon ASINs or product URLs.
Amazon Price Tracker	Price history and changes for Amazon products over time.
eBay Product Listing Scraper	Product listing data from eBay search and listing URLs.

---

Your feedback

Found a bug, or need a field this Actor doesn't return yet? Message the developer through the Issues tab on this Actor's Apify Store page, or use the Contact developer button in the Console. Reports get read and the Actor is actively maintained.