Amazon Seller Email Scraper

Find public contact emails for Amazon third-party sellers and retain the page where each address was disclosed. Provide Amazon seller IDs, seller or storefront URLs, or product URLs. The actor opens the Amazon seller profile, extracts public seller and legal-business details, and returns contact emails that appear on the profile. When a seller page does not disclose an email, optional enrichment can inspect the seller’s official website only when Amazon links it or the caller explicitly supplies an official-site mapping for that seller ID.

This is a contact-data discovery tool for supplier research, reseller investigations, brand protection, and B2B lead enrichment. It is deliberately narrow: it does not generate likely addresses from a person or company name, query a people-search database, collect customer data, or claim that an email mailbox is deliverable. Every returned email is syntactically validated and includes provenance.

Returned data

The default dataset contains one stable JSON record per Amazon seller profile inspected. A profile that has no public email still receives an honest record with email: null, emailFound: false, and a warning explaining the limit. That lets a workflow distinguish “not checked” from “checked but no public contact email” without paying the public-email event.

Field	Description
sellerId	Amazon seller or merchant ID.
sellerName	Seller’s public Amazon display name.
businessName	Legal business name Amazon exposes in seller information.
businessAddress	Public Amazon business address when present.
marketplace	Marketplace code such as US, DE, or UK.
sellerUrl	Amazon seller-profile URL used as the primary source.
email and emails	First and all public contact emails found for the seller.
emailSource	amazon_seller_page or official_website.
emailSourceUrl	Exact public page that contained the primary email.
officialWebsiteUrl	Official site linked by Amazon or supplied in the mapping.
warnings	Non-fatal limitations, such as an unavailable website or no disclosed email.

Example:

{
  "sellerId": "A1ODG4ICFE5MU3",
  "sellerName": "Example Seller",
  "businessName": "Example Seller Ltd",
  "marketplace": "DE",
  "sellerUrl": "https://www.amazon.de/sp?seller=A1ODG4ICFE5MU3",
  "email": "sales@seller.example",
  "emails": ["sales@seller.example"],
  "emailSource": "amazon_seller_page",
  "emailSourceUrl": "https://www.amazon.de/sp?seller=A1ODG4ICFE5MU3",
  "officialWebsiteUrl": null,
  "emailFound": true,
  "warnings": []
}

When to use it

Use this actor when you have an Amazon seller ID or a specific Amazon URL and need a traceable public business contact. Typical workflows include identifying a contact point for a reseller, enriching a list of sellers already found by another Amazon actor, researching potential suppliers, or collecting a small and auditable B2B lead list.

Do not use it to broadly search Amazon by a generic keyword, scrape customer information, collect personal contact data, validate email deliverability, or produce email guesses. For seller legal identity, feedback, ratings, and storefront-product details without an email-first workflow, use the related Amazon Seller Scraper.

Inputs

Seller IDs

sellerIds accepts 13–14 uppercase Amazon merchant IDs. Use marketplace to choose the Amazon domain for IDs that do not arrive with a URL. Seller IDs are not ASINs; ASINs have 10 characters and can instead be passed through product URLs.

{
  "sellerIds": ["A1ODG4ICFE5MU3"],
  "marketplace": "DE",
  "maxResults": 1
}

Amazon URLs

startUrls accepts seller-profile URLs, storefront URLs with me=, and product URLs containing /dp/ASIN. For a product URL the actor resolves its third-party seller before opening the seller profile. The Amazon domain in an input URL always wins over the generic marketplace setting.

{
  "startUrls": [{ "url": "https://www.amazon.com/sp?seller=A1ODG4ICFE5MU3" }],
  "discoverWebsiteEmails": true,
  "maxResults": 1
}

Official seller website mappings

Amazon does not always expose a seller’s website. If an existing CRM or research workflow already knows an official company domain, use companyWebsites to map it directly to the merchant ID. The actor checks the supplied homepage and up to maxContactPages same-site contact, support, imprint, legal, or about pages. It does not search the web for a business-name match and does not follow arbitrary unrelated external URLs.

{
  "sellerIds": ["A1ODG4ICFE5MU3"],
  "companyWebsites": [
    { "sellerId": "A1ODG4ICFE5MU3", "url": "https://seller.example" }
  ],
  "discoverWebsiteEmails": true,
  "maxContactPages": 3
}

Pricing

The actor uses Pay per event + platform usage. apify-actor-start costs $0.00005 once per run. The primary value event, public-email-found, costs $0.20 only when a seller record contains at least one syntactically valid email that was publicly disclosed on the Amazon seller page or an eligible official website page. Records with no email do not trigger the primary event. Apify compute and proxy usage are billed separately as platform usage.

maxResults is a hard ceiling on seller profiles. For example, maxResults: 10 caps public-email event charges at $2.00, plus the actor-start event and platform usage. The actor logs the cost ceiling before making requests.

Limits and reliability

Amazon pages can block high-volume access or change their markup. The actor uses a persistent session pool, controlled concurrency, retries, and session retirement after block responses. Residential proxies are recommended for larger jobs. If Amazon blocks every required route before any usable seller record exists, the actor reports an honest UPSTREAM_FAILED result instead of silently completing with an empty dataset.

No email found is not inherently an error: many sellers simply do not disclose one. A valid run with inspected profiles but zero disclosed emails finishes as VALID_EMPTY. A run that preserves some data but encounters blocked profiles or write failures is PARTIAL. Invalid user input gets an actionable INVALID_INPUT message. Every terminal path writes both OUTPUT, a compact machine-readable result, and RUN_SUMMARY, a detailed diagnostics and billing record.

API and AI-agent use

Use the same JSON input through the Apify API, Console, or MCP integration. This actor is appropriate for the job “find public contact emails for these Amazon sellers.” It returns flat, stable field names and every email includes a source page. Do not select it for price tracking, reviews, broad category discovery, or personal-contact lookup.

Responsible use

Use public business contact data in accordance with applicable law, Amazon policies, and your organization’s outreach requirements. An address being public does not establish consent, deliverability, or suitability for unsolicited marketing. Store emailSourceUrl with each CRM entry so a human can review the disclosure and its context before making contact.