Alibaba Email Scraper & Company Details

Alibaba Email Scraper — Supplier Profiles, Ratings & Trust Score

Alibaba Email Scraper & Company Details searches Alibaba by keyword and returns two things at once: business email leads pulled from Google's site:alibaba.com results, and the real supplier company record behind each keyword — company name, country, Gold-Supplier years, rating, and a derived trust score. Every response is structured JSON, ready to pass directly to an LLM, index into a vector store, or feed a monitoring pipeline. Instead of a bare list of scraped addresses, you get leads you can actually rank and qualify before outreach.

What is Alibaba Email Scraper & Company Details?

Alibaba Email Scraper & Company Details runs a keyword search against Alibaba and returns two joined result types: a business email lead pulled from Google's site:alibaba.com search results, and the real Alibaba supplier record for that keyword — company name, country, Gold-Supplier tenure, rating, and a derived 0–100 trust score computed from those two signals. This is what separates it from a plain Alibaba email scraper: instead of a bare address, every lead can carry a checkable company profile. No Alibaba account or login is required — both the Google search lane and Alibaba's proTextSearch supplier-offer API are queried logged out.

• Extracts business emails from Google search snippets restricted to alibaba.com
• Joins each keyword to its top-matching Alibaba supplier record: companyName, supplierCountry, goldSupplierYears, supplierRating, supplierUrl
• Computes a derived supplierTrustScore (0–100) from Gold-Supplier years and rating
• Filters leads by minimum Gold-Supplier years and by email domain
• Biases search results toward a specific supplier location or region
• Chooses between two proxy lanes (GOOGLE_SERP vs RESIDENTIAL) for the email-discovery step

What data can you get with Alibaba Email Scraper & Company Details?

Every run returns two joined result types in a single row: a business email lead and, when a match exists, its supplier company profile.

Result Type	Extracted Fields	Primary Use Case
Business email lead	network, keyword, title, description, url, email	Cold outreach and lead list building
Supplier company profile	companyName, supplierCountry, goldSupplierYears, supplierRating, supplierTrustScore, supplierUrl, scrapedAt	Supplier vetting before you contact or place an order

Supplier company profile and trust score

Every lead can carry a real Alibaba supplier record, not a guess. For each keyword, the actor queries Alibaba's own proTextSearch supplier-offer API and reduces the top matching offer to companyName, supplierCountry, goldSupplierYears (Gold-Supplier tenure), and supplierRating (0–5). From those two verified signals it computes supplierTrustScore, a deterministic 0–100 score — rating contributes up to 60 points, Gold-Supplier tenure up to 40 — so you can rank leads without opening 20 supplier pages by hand. When a keyword returns no matching offer, every supplier field is null rather than a faked value, and supplierTrustScore itself is only ever null when both rating and tenure are missing. This join happens at the keyword level, so it reflects Alibaba's top offer for that search term rather than a guaranteed match to the exact company owning the scraped email — see the FAQ below for how that limitation plays out.

{
  "companyName": "Shenzhen Example Lighting Co., Ltd.",
  "supplierCountry": "CN",
  "goldSupplierYears": 6,
  "supplierRating": 4.7,
  "supplierTrustScore": 80.4,
  "supplierUrl": "https://www.alibaba.com/product-detail/example-led-light_123456.html"
}

Business email leads from Google search

The additive lane runs a Google search scoped with site:alibaba.com, extracts the title, description snippet, and URL of each organic result, and pulls a business email out of the snippet text with a regex match. These six fields — network, keyword, title, description, url, email — are the base row shape and are populated even when includeSupplierProfile is off or the supplier API returns nothing for that keyword, which keeps a pure email-only run useful on its own.

Why not build this yourself?

Alibaba doesn't publish a keyword-search API that returns supplier company profiles and business emails together — its Open Platform is built for sellers and approved partners to manage their own listings, orders, and messages, and requires registering for an App key and App secret plus accepting its developer agreement before any call succeeds (Alibaba.com Open Platform Overview). It isn't a public search endpoint you can query for supplier records across the marketplace, and it doesn't return scraped web data like Google snippets or emails at all.

Building this yourself means maintaining two separate scrapers: one against Google's SERP (with block detection and a rotating proxy ladder) and one against Alibaba's internal proTextSearch supplier-offer endpoint (with its own proxy fallback chain), then writing the join and trust-score logic that connects them. Alibaba Email Scraper & Company Details already does both, with retries and a none → datacenter → residential proxy ladder built in, so you send a keyword and get back a joined dataset instead of two half-finished scrapers to maintain.

How to scrape Alibaba with Alibaba Email Scraper & Company Details?

1. Open Alibaba Email Scraper & Company Details on its Apify Store page and go to the Input tab (or call it via the Apify API).
2. Enter one or more product or niche keywords in searchTerms — no field is required by the schema, but an empty list returns zero rows.
3. Set the real query controls you need: supplierLocation to bias by region, emailDomainFilter to restrict email domains, minGoldSupplierYears to filter suppliers by tenure, and emailSearchEngine to pick the Google proxy lane.
4. Start the run.
5. Read results from the Apify dataset as JSON or CSV, or pull them through the API.

{
  "searchTerms": ["led lights", "phone case"],
  "minGoldSupplierYears": 2,
  "supplierLocation": "Guangzhou"
}

How to run multiple keywords in one job

searchTerms is an array — the actor loops over every keyword inside the same run, doing the supplier lookup and (when enabled) the email lane for each term in turn and pushing rows as they're produced. A single run with ["led lights", "phone case", "cosmetics"] returns interleaved leads for all three keywords, no separate jobs needed. maxLeads is applied per keyword, not to the whole run, so three keywords with maxLeads: 20 can return up to roughly three times that many rows across the full dataset.

⬇️ Input

Parameter	Required	Type	Description	Example Value
searchTerms	No	array	Product or niche keywords to search on Alibaba. Each term is queried on Google with a site:alibaba.com filter to find supplier emails, and against Alibaba's supplier API to attach the matching company profile. Also accepts legacy key keywords.	["led lights", "phone case"]
includeSupplierProfile	No	boolean	When enabled, each email lead is joined with the top Alibaba supplier record for its keyword — companyName, supplierCountry, goldSupplierYears, supplierRating and the derived supplierTrustScore. Turn off for a pure email-only run. Default true.	true
minGoldSupplierYears	No	integer	Only keep leads whose joined supplier has at least this many Gold-Supplier years. 0 = no filter. Minimum 0, maximum 30. Default 0.	3
emailDomainFilter	No	array	Only keep emails ending in these domains. Leave empty to collect every domain. Also accepts legacy key emailDomains.	["@gmail.com"]
supplierLocation	No	string	Add a location term to the search query to bias results toward a region. Leave empty for global. Also accepts legacy key location.	"Guangzhou"
maxLeads	No	integer	Maximum number of leads to collect per keyword. Minimum 1, maximum 5000. Prefilled at 20. Also accepts legacy key maxEmails.	20
marketplace	No	string (enum)	B2B marketplace to mine for supplier records and business emails — currently Alibaba only. Also accepts legacy key platform.	"Alibaba"
emailSearchEngine	No	string (enum)	Proxy group for the email-discovery lane: legacy runs the Google search over the GOOGLE_SERP proxy group, residential runs it over the RESIDENTIAL proxy group. Also accepts legacy key engine.	"legacy"
proxyConfiguration	No	object	Proxy for the Alibaba supplier API lookup. Falls back none → datacenter → residential automatically if left unset.	{"useApifyProxy": true}

Every parameter above is optional in the schema — but searchTerms is the one field you actually need to fill in: leave it empty and the run finishes immediately with zero rows and a log warning, no error. minGoldSupplierYears also filters silently — set it too high for a niche keyword and you may see fewer, or zero, supplier-linked rows for that term even though matching offers exist.

{
  "searchTerms": ["led lights", "phone case"],
  "includeSupplierProfile": true,
  "minGoldSupplierYears": 2,
  "emailDomainFilter": [],
  "supplierLocation": "",
  "maxLeads": 20,
  "marketplace": "Alibaba",
  "emailSearchEngine": "legacy",
  "proxyConfiguration": { "useApifyProxy": true }
}

⬆️ Output

Results are written to a structured Apify dataset with the same 13-field schema on every row, whether or not a supplier match was found. Export as JSON, CSV, Excel, or any other format the Apify dataset UI and API support. Each pushed row is billed as one row_result event, including additive email-only rows with null supplier fields, so the row count in your dataset is also the count of billed events.

Scraped results

[
  {
    "network": "Alibaba.com",
    "keyword": "led lights",
    "title": "LED Lights Manufacturer - Alibaba.com",
    "description": "Wholesale LED lights ... contact info@example.com",
    "url": "https://www.alibaba.com/showroom/led-lights.html",
    "email": "info@example.com",
    "companyName": "Shenzhen Example Lighting Co., Ltd.",
    "supplierCountry": "CN",
    "goldSupplierYears": 6,
    "supplierRating": 4.7,
    "supplierTrustScore": 80.4,
    "supplierUrl": "https://www.alibaba.com/product-detail/example-led-light_123456.html",
    "scrapedAt": "2026-07-25T10:15:30Z"
  },
  {
    "network": "Alibaba.com",
    "keyword": "led lights",
    "title": "Custom LED Strip Lights - Alibaba.com",
    "description": "OEM LED strip lights, sales@ledstriphub.com",
    "url": "https://www.alibaba.com/showroom/led-strip-hub.html",
    "email": "sales@ledstriphub.com",
    "companyName": null,
    "supplierCountry": null,
    "goldSupplierYears": null,
    "supplierRating": null,
    "supplierTrustScore": null,
    "supplierUrl": null,
    "scrapedAt": "2026-07-25T10:15:31Z"
  },
  {
    "network": "Alibaba.com",
    "keyword": "phone case",
    "title": "Silicone Phone Case Factory - Alibaba.com",
    "description": "Custom silicone phone cases wholesale, export@caseworks.cn",
    "url": "https://www.alibaba.com/showroom/phone-case-factory.html",
    "email": "export@caseworks.cn",
    "companyName": "Caseworks Industrial Co., Ltd.",
    "supplierCountry": "CN",
    "goldSupplierYears": 3,
    "supplierRating": 4.2,
    "supplierTrustScore": 62.4,
    "supplierUrl": "https://www.alibaba.com/product-detail/silicone-phone-case_654321.html",
    "scrapedAt": "2026-07-25T10:15:45Z"
  }
]

The second row shows the additive email-only shape: a lead was found on Google but no matching supplier offer existed for that keyword, so every supplier field is null rather than guessed.

How can I use the data extracted with Alibaba Email Scraper & Company Details?

• Procurement and sourcing teams: turn a niche keyword into a ranked shortlist — sort by supplierTrustScore and goldSupplierYears before you ever open a supplier's storefront.
• Supplier vetting and quality teams: filter with minGoldSupplierYears and check supplierRating and supplierCountry as a first-pass trust screen ahead of a factory audit.
• AI engineers and LLM developers: feed a keyword to the actor, get back structured JSON, and ground a sourcing agent's recommendation in real companyName, supplierTrustScore, and email fields instead of a model guess.
• B2B lead generation teams: build outreach lists straight from email, companyName, and supplierCountry, and use emailDomainFilter to target a specific kind of contact (e.g. corporate domains only).

How do you monitor supplier trust score and Gold-Supplier years over time?

Monitoring here means tracking whether a supplier's public trust signals are improving, stable, or slipping — a one-off run only tells you where a supplier stands today. Because goldSupplierYears increments as Alibaba's own tenure counter advances and supplierRating shifts as buyers leave new reviews, supplierTrustScore is recalculated fresh on every run rather than cached, so two runs of the same keyword weeks apart can return a different score for the same company.

To monitor a keyword set, join repeated runs on companyName and supplierUrl as the identity key, then diff goldSupplierYears, supplierRating, and supplierTrustScore between runs. A rating drop, a trust score that falls below your threshold, or a previously Gold-Supplier company that disappears from the results are the deltas worth alerting on. A practical workflow: run the same searchTerms list on a schedule, store each run's dataset keyed by date, and compare the latest run against the previous one for your target suppliers before you place a repeat order or renew an outreach sequence.

The actor itself does not diff runs — use Apify's Schedule feature to trigger repeated runs on a cron interval, and pull each run's dataset via the API to do the comparison in your own pipeline.

Integrate Alibaba Email Scraper & Company Details and automate your workflow

Alibaba Email Scraper & Company Details works with any language or tool that can send an HTTP request.

REST API with Python

import requests

run = requests.post(
    "https://api.apify.com/v2/acts/<YOUR_USERNAME>~alibaba-email-scraper-company-details/run-sync-get-dataset-items",
    params={"token": "<APIFY_TOKEN>"},
    json={
        "searchTerms": ["led lights", "phone case"],
        "maxLeads": 20,
        "minGoldSupplierYears": 2,
    },
)
leads = run.json()
for lead in leads:
    print(lead["email"], lead.get("companyName"), lead.get("supplierTrustScore"))

MCP for query-grounded AI agents

Any Apify Actor, including this one, can be exposed as a tool through Apify's @apify/actors-mcp-server:

APIFY_TOKEN=<your_token> npx -y @apify/actors-mcp-server --actors <your-username>/alibaba-email-scraper-company-details

An MCP client — Claude Desktop, Claude Code, or any other MCP-compatible agent framework — registers this command, then an agent can call the actor as a tool with a searchTerms argument, receive the joined JSON dataset back, and ground its sourcing recommendation in real supplier data instead of an unverified guess.

Scheduled monitoring and delivery

Apify's Schedule feature can trigger a run on a cron interval without any code, and Apify's webhook feature can notify your endpoint when a run finishes so you can pull the fresh dataset through the API rather than polling for it manually.

Is it legal to scrape Alibaba supplier emails?

Yes — scraping publicly listed Alibaba supplier pages and Google's public search results for business contact information is generally lawful; Alibaba Email Scraper & Company Details only extracts what any visitor to a public search-results page or a public product listing can already see, logged out. The data returned here — a company email address, company name, country, and public reputation signals — is business contact and company information rather than personal data about an individual, which is a lower-risk category under GDPR/CCPA than scraping personal profiles; if a scraped email happens to embed a person's name, treat that row with the same care you would any personal data under those regimes. Respect Alibaba's and Google's Terms of Service for your jurisdiction and use case, and note that one-off research carries a different risk profile than bulk storage or resale. Consult your legal team for commercial use cases involving bulk data storage.

Frequently asked questions

How many results does Alibaba Email Scraper & Company Details return per query?

Up to maxLeads per keyword, which accepts any value from 1 to 5000 and is prefilled at 20. Because supplier-linked rows and additive email-only rows are both capped near this figure independently, a single keyword can return somewhat more than maxLeads rows in total when the email lane finds more leads than there are matching supplier offers.

Does Alibaba Email Scraper & Company Details extract supplier company details, not just emails?

Yes — when includeSupplierProfile is on (the default), every keyword is queried against Alibaba's proTextSearch supplier-offer API and the top matching offer is joined onto the lead as companyName, supplierCountry, goldSupplierYears, supplierRating, supplierTrustScore, and supplierUrl.

What company details are actually included?

Company name, supplier country, Gold-Supplier tenure in years, a 0–5 supplier rating, a link to the sourcing product/offer page, and a derived 0–100 trust score computed from tenure and rating. There is no address, phone number, or registration-ID data — those fields are not present in the source Alibaba API response, so they are never included.

Does the supplier profile match the exact company that owns the scraped email?

Not guaranteed — the supplier record is joined at the keyword level, meaning the actor attaches Alibaba's top offer for that search term, which is not necessarily the same company whose email was scraped from a Google snippet for the same keyword. Treat the two as correlated by keyword, not confirmed to be the same business.

How does Alibaba Email Scraper & Company Details handle anti-bot measures?

The Google email lane uses a size-gated block detector (only a small response body carrying a hard block phrase counts as blocked, so a normal results page is never a false positive), rotates user agents and Accept-Language headers, retries with a fresh proxy on a block, and adds randomized delays between requests. The supplier lookup falls back automatically through a none → datacenter → residential proxy chain if an attempt fails.

Can I filter results by supplier tenure, location, or email domain?

Yes — minGoldSupplierYears keeps only suppliers with at least that many Gold-Supplier years, supplierLocation biases the search query toward a region, and emailDomainFilter keeps only emails ending in the domains you list.

How do I monitor a supplier's trust score over time?

Run the same searchTerms list on an Apify Schedule, store each run's dataset, and diff goldSupplierYears, supplierRating, and supplierTrustScore between runs for the same companyName/supplierUrl. Alert on a falling trust score or a supplier that drops out of the results entirely.

Does Alibaba Email Scraper & Company Details work with Claude, ChatGPT, and AI agent frameworks?

Yes — it is callable as an HTTP endpoint through the Apify API by any agent framework, and it can also be registered as a tool through Apify's @apify/actors-mcp-server for MCP-compatible clients like Claude Desktop or Claude Code, letting an agent retrieve live supplier and email data before answering.

Can I use it without managing proxies or Alibaba credentials?

Yes — no Alibaba account or login is needed for either lane, and proxy handling is built in: the email lane runs over Apify's GOOGLE_SERP or RESIDENTIAL proxy groups depending on emailSearchEngine, and the supplier lookup falls back through its own proxy chain automatically. You can optionally supply your own proxyConfiguration for the supplier lookup, but it isn't required to get a run working.

Does this only work for Alibaba, or other B2B marketplaces too?

Currently Alibaba only — the marketplace parameter's schema lists a single enum value, Alibaba, which drives both the site: search filter and the network label on every row.

Your feedback

Found a bug or a field that doesn't match this document? Open an issue on this Actor's Apify Store page or reach out to Scrapier through your Apify Console — reports like this are how the join logic and field coverage get improved.