Amazon Seller Email Scraper - Contacts, Phone & VAT Leads avatar

Amazon Seller Email Scraper - Contacts, Phone & VAT Leads

Pricing

from $20.00 / 1,000 seller with contact details

Go to Apify Store
Amazon Seller Email Scraper - Contacts, Phone & VAT Leads

Amazon Seller Email Scraper - Contacts, Phone & VAT Leads

Find Amazon seller emails and contact information by keyword or seller ID. Get the business name, email, phone, address, VAT and trade register number of marketplace sellers, with an optional mail-server check. For B2B lead lists, supplier research and seller vetting.

Pricing

from $20.00 / 1,000 seller with contact details

Rating

0.0

(0)

Developer

SR

SR

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

16 hours ago

Last modified

Share

Amazon Seller Email Scraper

Amazon Seller Email Scraper finds the businesses behind Amazon listings and returns their seller contact information: business name, email address, phone number, business address, VAT number and trade register number, as published on the seller profile. Start with product keywords to discover sellers, or provide seller IDs you already know. It is built for B2B lead generation, supplier research and seller vetting.

The actor is useful for identifying marketplace merchants, matching sellers to business records and checking whether a published contact address has a mail server. It returns information from the selected Amazon marketplace. A missing value remains null, and an unavailable seller page does not become a misleading seller record.

Amazon seller email scraper input

Provide keywords, seller_ids, or both. Each field is an array of strings. Keywords identify products to inspect; seller IDs let you look up known sellers directly. When both are present, the supplied seller IDs appear before newly discovered sellers. Duplicate seller IDs are removed while preserving their first position.

This input is from a successful run on the German marketplace:

{
"seller_ids": ["AYSVGQQ89W56K", "A2GYV4E9PQJS54", "A3LMU6BC0XGWOL"],
"marketplace": "de"
}

That run returned three sellers, including DS e-Sales GmbH, MST GmbH and KG Physio LTD. The separate keyword example uses keywords: ["yoga mat"] and the default German marketplace. Its recorded run returned seven sellers with email addresses. Search results can change, so these observations describe the saved runs rather than a guaranteed future count.

marketplace defaults to de. Supported values are de, es, com.be, se, ie, pl, it, nl, fr, co.uk, com, ca, com.mx, com.br, com.au, co.jp, in, sg, ae, sa, eg and com.tr. Contact information varies between marketplaces and sellers. An email is not guaranteed on any marketplace.

products_per_keyword defaults to 10 and accepts integers from 1 to 30. The actor uses at most the first ten nonempty keywords. max_sellers defaults to 50 and accepts integers from 1 to 200. It limits how many unique seller profiles are examined, so the number of returned records can be lower when some profiles are unavailable or the email filter removes sellers.

only_sellers_with_email defaults to true. Set it to false to include successfully retrieved seller profiles without an email address. verify_emails defaults to true. Set it to false to skip the mail-server lookup. Long runs continue automatically; there is no need to manage the optional continuation field during normal actor usage.

Output and dataset fields

The dataset contains one row per returned seller. It includes merchant_id, marketplace, seller_url, business_name, business_type, trade_register_number, vat_number, phone and business_address. The emails array contains discovered addresses. email is its first entry and email_count is the array length. A labelled contact email takes priority over other email addresses on the page.

has_detail_block indicates whether the detailed seller information section appeared. fetch_failed is false on delivered rows: profiles whose page could not be retrieved are counted in the summary instead of being inserted into the dataset. Fields without a published value are null, while the emails array can be empty.

The optional verification object appears only when verification is enabled and the row has an email. Its fields are email, valid_format, domain, has_mx, is_role_account, is_free_provider, is_disposable, is_business_domain and status. A successful MX check reports deliverable_domain; an absent mail-server record reports no_mail_server. A lookup that could not be completed reports unknown with has_mx: null.

Additional fields describe the retrieval time and support matching across data sources: fetched_at, country, source, platform, seller_id, url, name, address and registry_id. These fields supplement the original dataset names. country refers to the selected marketplace, so it can differ from the country in the business address.

Example output row

This is the first row of the seller ID run shown above (German marketplace, 4 October 2026), including the additional matching fields:

{
"merchant_id": "AYSVGQQ89W56K",
"marketplace": "de",
"seller_url": "https://www.amazon.de/sp?seller=AYSVGQQ89W56K",
"business_name": "DS e-Sales GmbH",
"business_type": "Unternehmen in Privatbesitz",
"trade_register_number": "HRB 24435 HL",
"vat_number": "DE815317181",
"phone": "+49 4551 8939200",
"business_address": "Stormarnring, 14, Stapelfeld, 22145, DE",
"emails": [
"kundenservice@dse-sales.de",
"mail@in-trading.com"
],
"email": "kundenservice@dse-sales.de",
"email_count": 2,
"has_detail_block": true,
"fetch_failed": false,
"verification": {
"email": "kundenservice@dse-sales.de",
"valid_format": true,
"domain": "dse-sales.de",
"has_mx": true,
"is_role_account": true,
"is_free_provider": false,
"is_disposable": false,
"is_business_domain": true,
"status": "deliverable_domain"
},
"fetched_at": "2026-10-04T21:52:13.868Z",
"country": "DE",
"source": "amazon-seller-emails",
"platform": "amazon",
"seller_id": "AYSVGQQ89W56K",
"url": "https://www.amazon.de/sp?seller=AYSVGQQ89W56K",
"name": "DS e-Sales GmbH",
"address": "Stormarnring, 14, Stapelfeld, 22145, DE",
"registry_id": "HRB 24435 HL"
}

The other two rows of that run were MST GmbH and KG Physio LTD. KG Physio LTD sells on amazon.de but has a business address in Great Britain, which is why country (the marketplace) and the country in business_address can differ.

Summary and empty results

The SUMMARY key-value record contains marketplace, sellers_looked_up, sellers_with_email, sellers_without_email, sellers_fetch_failed and hit_rate_pct, plus the retrieval counters fetch.fetch_attempts and fetch.stubbed and an explanatory note. sellers_fetch_failed counts seller profiles whose page could not be retrieved; sellers_without_email counts successfully retrieved profiles without an email. hit_rate_pct is the percentage of looked-up sellers with an email. If no sellers are discovered, the NO_SELLERS record provides an explanation in note and retrieval counters in stats. Neither record is added to the dataset.

A profile that does not publish an email is different from a profile that could not be retrieved. The actor keeps those outcomes separate. It can complete successfully with an empty dataset when no usable results are available. Results from other completed parts of a run remain available if a later part encounters an upstream problem.

Which Amazon marketplaces publish seller emails?

Amazon shows a detailed seller information block, including contact details, mainly on its European marketplaces such as Germany, France, Italy, Spain, the Netherlands, Belgium, Poland, Sweden, Ireland and the United Kingdom. On other marketplaces the profile often lists a business name and address but no email or phone number. A recorded run for a seller on amazon.com with only_sellers_with_email: false returned FANTASIA TRADING LLC with its business address in Ontario, California, and an empty emails array. Choose an EU marketplace when email addresses are the goal.

Use cases for Amazon seller contact information

  • Amazon FBA leads and B2B outreach. Agencies, software vendors, logistics providers and accountants that serve marketplace sellers can build a lead list from the products in their niche, with a business email, phone number and VAT number per seller.
  • Supplier and brand research. Find out which companies sell a product type, where they are registered and how to reach them for wholesale, distribution or private-label talks.
  • Seller vetting and compliance. Check that a merchant publishes a trade register number and VAT number, and that its contact address has a working mail domain, before you buy from it or partner with it.
  • Brand protection. Identify the business behind an unauthorised listing of your product and get the published contact details needed for a formal request.
  • CRM enrichment. Match the seller IDs you already track to company names, registry identifiers and addresses using seller_id, name, address and registry_id.

How this Amazon seller email scraper compares

Copying contact details from seller profiles by hand works for a handful of sellers but becomes slow when a keyword surfaces dozens of merchants. Amazon's own help pages and Seller Central contact forms are for reaching Amazon support, not for collecting the published details of third-party sellers. Static lead databases are sold as one-off lists that age quickly; this actor reads the seller profiles at the moment you run it, so the result reflects what Amazon displays today.

Compared with general Amazon product scrapers, the focus here is the business behind the listing rather than prices or reviews. Each row carries the published business fields, an email chosen with the labelled contact address first, and an optional domain mail-server check. You only pay for rows that reach the dataset, and empty results cost nothing beyond the platform start event.

Pricing and free account limit

The existing pricing is $0.02 for each row added to the default dataset, plus the platform start event of $0.002 per GB of actor memory, with a minimum of one start unit. At the actor's existing 1024 MB setting, a normal start is one unit. No additional verification event or separate no-email event is charged.

A delivered row without an email has the same $0.02 dataset-row price when only_sellers_with_email is false. An empty dataset has zero dataset-row events; the platform start charge still applies. Users without a paid Apify plan receive at most ten dataset rows per run. This result cap does not replace the email filter or impose a separate verification price.

Frequently asked questions

Does verification prove that the mailbox receives messages?

No. It checks the address format and the domain's MX records. It does not send mail, test the individual mailbox or guarantee message delivery. A domain-level positive result means a mail-server record was found.

Why are fewer rows returned than max_sellers?

The limit counts seller profiles to examine. The default email filter excludes sellers without a discovered address. Unavailable pages are also excluded from the dataset. Check SUMMARY to distinguish the outcomes.

Can I use seller IDs without a keyword?

Yes. Provide the IDs in seller_ids and select the marketplace on which those sellers appear. This avoids the product discovery step and preserves the supplied seller order after duplicate removal.

Can an address belong to a role account?

Yes. is_role_account labels addresses such as customer service or sales mailboxes. It is descriptive and does not automatically make an address invalid. Likewise, a free email provider does not by itself mean that the address is unusable.

How do I find an Amazon seller's email?

Open the seller's profile and look for the detailed seller information section, or let this actor do it for a list of keywords or seller IDs. On EU marketplaces the section usually lists the business email; the actor returns it in email and emails.

How do I find an Amazon seller ID?

The seller ID is the value after seller= in a seller profile link, such as AYSVGQQ89W56K in https://www.amazon.de/sp?seller=AYSVGQQ89W56K. A keyword run also returns merchant_id for every discovered seller, so you can reuse those IDs in later runs.