🏭 Alibaba Email & Supplier Scraper Plus

Alibaba Email Scraper — Extract Business Emails, Phones and Suppliers

Alibaba Email & Supplier Scraper Plus finds Alibaba supplier pages by keyword or from URLs you paste in, then returns typed JSON rows carrying only genuine, verified contact data — a real local@domain email (never a prose fragment turned into one), a libphonenumber-validated phone in E.164, and, optionally, the actual Alibaba company record behind the listing. Unlike scraping frameworks that hand you raw HTML to parse yourself, this Actor returns structured fields ready for a CRM, a spreadsheet, or an LLM context window with no cleanup step. This guide covers every input and output field plus how procurement, sales, and research teams actually run it in production.

🧭 What Does Alibaba Email Scraper Plus Do?

Alibaba Email & Supplier Scraper Plus is a lead-generation and supplier-research Actor for Alibaba.com. It never logs into Alibaba — every field it returns comes from either a public Google search-result snippet or an unauthenticated fetch of a public Alibaba page, so no Alibaba account or login is required. Every output row represents one supplier result and can carry three kinds of genuine data: a validated business email, a validated phone number, and — when enabled — a real Alibaba company profile (name, country, business type, gold-supplier years, verification flags, response rate, review score).

• 🔍 Discovers Alibaba supplier, company, and product pages via a site:alibaba.com Google search built from your keywords
• 🔗 Accepts direct Alibaba URLs (startUrls) to scrape without any search step
• 📧 Extracts only contiguous, syntactically genuine emails — never a fabricated local@domain stitched from surrounding prose
• ☎️ Extracts only libphonenumber-validated, internationally formatted phone numbers — random digit runs (prices, IDs, counts) are rejected outright
• 🏭 Optionally fetches the real Alibaba supplier minisite (Chrome-impersonated, past Akamai) for structured company data
• 🌐 Optionally follows a supplier's own external website (when the minisite lists one) to harvest a genuine business email or phone there
• 🧹 De-duplicates globally by email/company key, and filters by email domain, free-mail providers, and exclude-keywords

⚡ Features & Capabilities

Every capability below maps to a real code path in the Actor — proxy handling, extraction guards, and enrichment are all covered.

Core features

• Two discovery paths in one Actor — keywords build a site:alibaba.com "<keyword>" Google query (optionally narrowed by location and emailDomains); startUrls skip search entirely and scrape the pasted Alibaba URLs directly. Both paths feed the same extraction and enrichment pipeline.
• Contiguous-email guard — the email regex requires a real local@domain string with no whitespace around the @. The base pattern this Actor fixes allowed \s*@\s*, which turned ordinary prose like "the part before @ gmail.com" into a fabricated address; that bug is closed here.
• Confidence-labeled contacts — emailConfidence is high when the address comes from a mailto: link or sits within 40 characters of a contact-style label (contact, sales, inquiry, enquiry, reach us, etc.), otherwise medium. contactConfidence mirrors this per row, or is high when only a phone was found.
• Validated phone extraction — phone numbers are matched with phonenumbers.PhoneNumberMatcher in international-only mode (region=None) and kept only if is_valid_number() passes, then normalized to E.164. Because the matcher requires an explicit +/country-code form, a bare digit run (a product ID, a price, an order count) can never be misread as a phone number.
• Real Akamai-protected company data — when includeCompanyProfile is on, the Actor fetches the supplier's <slug>.en.alibaba.com minisite with curl_cffi Chrome impersonation (chrome131) over a residential proxy and parses companyName, companyCountry, companyCity, businessType, goldSupplierYears, verifiedSupplier, tradeAssurance, responseRate, and reviewScore straight out of the page's meta tags and embedded JSON. If Akamai blocks the fetch, every one of those fields is left null — never guessed.
• Supplier-website follow-through — with followSupplierWebsite on, if the minisite lists the supplier's own external site (filtered against a block-list of Alibaba/social/CDN hosts so a Facebook page can never be mistaken for it), the Actor fetches that site's homepage plus /contact, /contact-us, and /contact.html and harvests a genuine email/phone from there — this is documented in the code as the channel where real B2B contacts most reliably live, since Alibaba itself renders most contact details behind login.
• Global de-duplication — rows are de-duplicated within a run by an email + companyName/companySlug/url composite key, so the same supplier surfaced from two different keywords is not billed twice.

How Alibaba Email Scraper Plus compares to other Alibaba scrapers

Feature	Alibaba Email Scraper Plus	scrape-alibaba-suppliers	Alibaba Supplier Scraper (devcake)
Output format	Typed JSON dataset	Typed JSON dataset	Typed JSON dataset
Genuine business email/phone field	✅ email, phone (confidence-labeled, validated)	Not documented in its output field list, as observed on the Apify Store on 2026-07-26	Not documented in its output field list, as observed on the Apify Store on 2026-07-26
Company verification data	verifiedSupplier, tradeAssurance, goldSupplierYears, responseRate, reviewScore	isAssessedSupplier, goldYears, reviewScore, reviewCount	is_assessed_supplier, is_verified_supplier_pro, years_as_gold_supplier, response_rate — plus factory metrics (total_employees, factory_size, annual_revenue), as observed on the Apify Store on 2026-07-26
Discovery input	Keywords (Google SERP) or direct URLs	Keyword or a custom Alibaba searchUrl	Not documented beyond supplier keyword input, as observed on the Apify Store on 2026-07-26
Anti-bot handling	GOOGLE_SERP/RESIDENTIAL proxy rotation + Chrome impersonation for Akamai-protected pages	Not documented, as observed on the Apify Store on 2026-07-26	Not documented, as observed on the Apify Store on 2026-07-26
Pricing model	Pay-per-event (row_result)	Flat monthly price, as observed on the Apify Store on 2026-07-26	Pay-per-event, as observed on the Apify Store on 2026-07-26

If your use case is feeding structured data to an LLM or a CRM import job, the "genuine email/phone field" row is the decision-maker — none of the three competitor listings document a validated contact-extraction field as of the date checked, which is what this Actor exists to fill. The other two lean toward deeper factory/verification metadata (devcake) or a simpler keyword-to-listing lookup (shareze001).

When another tool might suit you better

If your priority is factory-floor intelligence — employee counts, factory square footage, estimated annual revenue — devcake/alibaba-supplier-scraper documents fields for exactly that (total_employees, factory_size, annual_revenue), as observed on the Apify Store on 2026-07-26; this Actor does not attempt to extract those because Alibaba does not expose them reliably outside login, and it will not guess at a factory size it cannot verify. Likewise, if you need to search Alibaba by product photo rather than keyword, toolsnmoreapi/Alibaba-Product-and-Vender-Finder documents an image and reverse-image search mode this Actor does not have, as observed on the Apify Store on 2026-07-26.

Alibaba Email Scraper Plus within the Scrapio data stack

Alibaba Email & Supplier Scraper Plus covers Alibaba supplier contact discovery specifically. For general-purpose contact harvesting on any domain — not just Alibaba — Scrapio's Website Contact & Email Crawler crawls a site's contact/about/team pages directly rather than going through a search engine. For lead generation on a different marketplace, Scrapio's Airbnb Host Contact & Lead Scraper Plus applies the same confidence-tagged, never-fabricated contact model to Airbnb listings and hosts.

Why do developers and data teams scrape Alibaba?

🏢 Procurement and sourcing teams

A sourcing team feeds in product keywords (stainless steel water bottle, silicone kitchenware) and gets back rows with companyName, companyCountry, verifiedSupplier, tradeAssurance, goldSupplierYears, and — when a genuine one exists — an email or phone. That combination lets a buyer triage suppliers before ever opening a message thread: filter to verifiedSupplier: true and goldSupplierYears above a threshold, then reach out directly using the extracted contact instead of routing everything through Alibaba's in-platform messaging queue.

📊 AI training data and RAG indexing

The title, description, and businessType fields carry the free-text supplier and listing copy that makes good RAG chunks for a sourcing-assistant index — they describe what the supplier actually makes, in their own listing language. For structured training data, companyCountry, goldSupplierYears, verifiedSupplier, tradeAssurance, and reviewScore are typed primitives with consistent shape across every row, useful for models that need to reason about supplier trust signals rather than free text.

📱 Competitive and market intelligence

Running the same keyword set on a schedule and diffing on verifiedSupplier, tradeAssurance, goldSupplierYears, and reviewScore surfaces real movement — a competitor's supplier gaining trade-assurance status, or a new entrant appearing on page one of the same site:alibaba.com search you're tracking. serpRank and pageNumber tell you exactly where in the search results each supplier landed on that run.

🔬 Research and academic use

Because every input path relies on public Google snippets and unauthenticated page fetches, the dataset is limited to what Alibaba already exposes publicly — no login-gated data is ever accessed. That makes it usable for research into B2B marketplace structure, trust-signal prevalence by product category, or supplier geography by keyword, without touching any account-gated information.

🎥 Product and SaaS development

row_result rows are typed enough to back a supplier-directory product or a sourcing-lead enrichment API directly: pass in a client's product keywords, get back a de-duplicated, confidence-labeled contact list, and store it against companyDomain as the join key for later enrichment passes.

🍚 Input Parameters

All ten input parameters, read directly from .actor/actor.json, in schema order.

Parameter	Required	Type	Description	Example Value
keywords	Yes (unless startUrls is supplied)	array	Keywords/niches to search on Alibaba via Google. Each becomes a site:alibaba.com "keyword" search.	["stainless steel water bottle"]
startUrls	No	array	Alibaba supplier/company/product URLs to scrape directly instead of, or in addition to, keyword search. Non-Alibaba URLs are silently ignored.	["https://example.en.alibaba.com/"]
location	No	string	Optional term appended to the search query to bias results to a place. Default "" (global).	"Guangdong"
emailDomains	No	array	Keep only emails ending with these domains. The Actor matches by suffix after stripping a leading @, so "company.com" also matches mycompany.com — use a fuller domain string if you need an exact match. Leave empty to keep all genuine emails.	["@163.com"]
excludeKeywords	No	array	Case-insensitive words that drop a result if found anywhere in its title, description, or URL.	["wholesale", "used"]
excludeFreeMail	No	boolean	When true, drops emails on free consumer providers (Gmail, Yahoo, Hotmail, 163, QQ, and 16 other domains on the Actor's block list) and keeps only business-domain emails. Default false.	true
includeCompanyProfile	No	boolean	When true, visits each genuine Alibaba supplier minisite (Chrome-impersonated, residential proxy) and extracts the real company record plus any genuine contact the page exposes server-side. Default false.	true
followSupplierWebsite	No	boolean	When true (and includeCompanyProfile is also true), if a supplier's minisite lists their own external website, that site's homepage and contact pages are fetched too for a genuine email/phone. Default true.	true
maxResults	No	integer (min 1, max 5000)	Maximum billable rows to collect. Default 20. During keyword search this cap applies per keyword — each keyword gets its own budget. During the startUrls pass it is applied as a running total across all pasted URLs, consumed before the keyword loop even starts.	50
proxyConfiguration	No	object	Proxy used for requests. If you leave it unset or pick Apify Proxy without a group, the Actor adds GOOGLE_SERP automatically for search requests — Google blocks datacenter IPs without it. When includeCompanyProfile is on, the company-page and supplier-website fetches switch to the RESIDENTIAL group instead (unless you supplied custom proxyUrls, which are honored for both paths).	{"useApifyProxy": true, "apifyProxyGroups": ["GOOGLE_SERP"]}

Complete JSON input example

{
  "keywords": ["stainless steel water bottle", "silicone kitchenware"],
  "startUrls": [],
  "location": "Guangdong",
  "emailDomains": [],
  "excludeKeywords": ["wholesale"],
  "excludeFreeMail": true,
  "includeCompanyProfile": true,
  "followSupplierWebsite": true,
  "maxResults": 50,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["GOOGLE_SERP"]
  }
}

Supported URL types and input formats

• Keyword search — any free-text product keyword or niche term. ["led lighting"] becomes the Google query site:alibaba.com "led lighting", optionally with location and emailDomains folded in as additional quoted terms.
• Direct supplier minisite URLs — the pattern https://<slug>.en.alibaba.com/ (a two-letter language segment is mandatory) is recognized as a genuine supplier minisite and gets companySlug populated and, when enabled, full company enrichment. Category or language sub-domains such as electronics.alibaba.com or portuguese.alibaba.com are explicitly excluded from this pattern so they are never mistaken for a real supplier.
• Mixed mode — supplying both keywords and startUrls in the same run processes the direct URLs first (against the shared maxResults total), then runs the keyword searches afterward with their own per-keyword budgets.
• Non-Alibaba URLs in startUrls — filtered out before the run starts; only URLs whose hostname contains alibaba.com are kept.

📦 Output Format

Every result is a typed, normalized JSON row with a stable field set — no field is ever omitted from a row, only set to null when the underlying data genuinely was not found. The dataset is downloadable through the Apify platform's standard export options (JSON, CSV, Excel, XML) or read directly via the Apify API/dataset client. The default dataset view in the Apify Console surfaces 28 of the fields the Actor actually pushes; description and allPhones are present in every raw row but are not shown in the table view by default — open the row as JSON to see them.

Output for a row with a genuine email

{
  "type": "supplier",
  "isChild": false,
  "keyword": "stainless steel water bottle",
  "title": "Stainless Steel Water Bottle Manufacturer",
  "description": "Guangdong-based manufacturer of vacuum-insulated stainless steel bottles, OEM/ODM available.",
  "url": "https://example.en.alibaba.com/",
  "companySlug": "example",
  "serpRank": 2,
  "pageNumber": 1,
  "companyName": "Example Stainless Products Co., Ltd.",
  "companyCountry": "China",
  "companyCity": "Shenzhen",
  "businessType": "Manufacturer",
  "goldSupplierYears": 8,
  "verifiedSupplier": true,
  "tradeAssurance": true,
  "responseRate": "92%",
  "reviewScore": 4.8,
  "supplierWebsite": "https://example-stainless.com",
  "email": "sales@example.com",
  "emailConfidence": "high",
  "emailDomain": "example.com",
  "isBusinessEmail": true,
  "isRoleEmail": true,
  "companyDomain": "example.com",
  "phone": "+8613800138000",
  "allPhones": ["+8613800138000"],
  "contactSource": "minisite",
  "contactConfidence": "high",
  "scrapedAt": "2026-07-26T10:00:00Z"
}

isChild is present on every row but always false in the current version — there is no nested child-row mode yet, so the field is reserved rather than active.

Output for a company-only row (no genuine email found)

When includeCompanyProfile is on but no genuine email surfaced from the snippet, the minisite, or the supplier's own website, the Actor still emits (and charges) a row keyed on a validated phone or the fetched company record itself — it never fabricates an email to fill the gap:

{
  "type": "supplier",
  "isChild": false,
  "keyword": "silicone kitchenware",
  "title": "Silicone Kitchenware Factory",
  "description": "",
  "url": "https://sample-supplier.en.alibaba.com/",
  "companySlug": "sample-supplier",
  "serpRank": 5,
  "pageNumber": 1,
  "companyName": "Sample Supplier Co., Ltd.",
  "companyCountry": "China",
  "companyCity": null,
  "businessType": "Manufacturer, Trading Company",
  "goldSupplierYears": 3,
  "verifiedSupplier": false,
  "tradeAssurance": true,
  "responseRate": null,
  "reviewScore": null,
  "supplierWebsite": null,
  "email": null,
  "emailConfidence": null,
  "emailDomain": null,
  "isBusinessEmail": null,
  "isRoleEmail": null,
  "companyDomain": null,
  "phone": null,
  "allPhones": [],
  "contactSource": null,
  "contactConfidence": null,
  "scrapedAt": "2026-07-26T10:05:00Z"
}

Schema stability and export options

The field set is fixed by the Actor's row-assembly code, not scraped from Alibaba's markup at runtime, so field names stay stable across runs even when Alibaba's front end changes — a page-layout change affects whether a value is null, never which keys are present. Results are available through Apify's standard dataset export formats (JSON, CSV, Excel, XML) from the Console or via the API, and through the apify_client dataset iterator for programmatic pipelines.

💡 Alibaba Email Scraper Plus Strategy Guide

🎯 Strategy 1: Real-time enrichment pipeline

Trigger a run from your CRM or lead-intake system whenever a new sourcing request comes in, passing the product need as keywords. When the run finishes, read back email, phone, companyName, verifiedSupplier, and tradeAssurance for each row and write them onto the matching lead record, keyed on companyDomain for de-duplication against contacts you already hold. Turning on includeCompanyProfile at trigger time adds the trust-signal fields in the same pass, so the enrichment step never needs a second run.

🎯 Strategy 2: Scheduled monitoring and alerting

Use an Apify Schedule to re-run the same keywords on a recurring cadence. Diff each new run's dataset against the previous one on companySlug plus verifiedSupplier, tradeAssurance, goldSupplierYears, and reviewScore — alert your team only when one of those fields changes for a supplier you already track, rather than re-reviewing the full result set every time.

🎯 Strategy 3: Bulk dataset build

For a research or sourcing dataset spanning many product categories, queue a long keywords list (or a large startUrls batch) in one run and set maxResults up to its documented maximum of 5000 to cap per-keyword volume. Export the finished dataset straight to CSV from the Apify Console, or pull it with the dataset API into a database for downstream analysis.

Strategy comparison at a glance

Strategy	Best for	Run pattern	Output format
Real-time enrichment	Inbound sourcing requests	Triggered single run per lead	JSON row(s) written back to CRM
Scheduled monitoring	Tracking known suppliers over time	Apify Schedule, recurring run	Dataset diffed run-over-run
Bulk dataset build	Research or multi-category datasets	One large run, many keywords/URLs	CSV or database export

🌴 Related Alibaba Scrapers & Tools

Scraper	What it extracts
Website Contact & Email Crawler (Scrapio)	Crawls any domain's contact/about/team pages for emails, phones, and social profiles — not limited to Alibaba
Airbnb Host Contact & Lead Scraper Plus (Scrapio)	The same confidence-tagged, never-fabricated contact model applied to Airbnb listings and hosts
scrape-alibaba-suppliers	Alibaba supplier lookup by keyword or custom search URL, with company/product metadata (no documented email/phone field), as observed on the Apify Store on 2026-07-26
Alibaba Supplier Scraper (devcake)	Alibaba supplier verification and factory intelligence — employee counts, factory size, revenue estimates, as observed on the Apify Store on 2026-07-26
Alibaba Product & Vender Finder (toolsnmoreapi)	Alibaba product/supplier discovery by keyword or reverse image search, as observed on the Apify Store on 2026-07-26

How to integrate Alibaba Email Scraper Plus with your stack

Alibaba Email & Supplier Scraper Plus works with any language or tool that can make an HTTP request to the Apify API.

Python

from apify_client import ApifyClient
import csv

client = ApifyClient("YOUR_APIFY_TOKEN")
run_input = {
    "keywords": ["stainless steel water bottle", "silicone kitchenware"],
    "excludeFreeMail": True,
    "includeCompanyProfile": True,
    "followSupplierWebsite": True,
    "maxResults": 50,
}

run = client.actor("your-username/alibaba-email-supplier-scraper-plus").call(run_input=run_input)

rows = list(client.dataset(run["defaultDatasetId"]).iterate_items())

with open("alibaba_suppliers.csv", "w", newline="", encoding="utf-8") as f:
    writer = csv.DictWriter(f, fieldnames=[
        "companyName", "companyCountry", "email", "phone",
        "verifiedSupplier", "goldSupplierYears", "url",
    ])
    writer.writeheader()
    for row in rows:
        writer.writerow({k: row.get(k) for k in writer.fieldnames})

print(f"Collected {len(rows)} rows")

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });

const run = await client.actor('your-username/alibaba-email-supplier-scraper-plus').call({
  keywords: ['stainless steel water bottle'],
  includeCompanyProfile: true,
  maxResults: 50,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();

const leads = items
  .filter((row) => row.email || row.phone)
  .map((row) => ({ company: row.companyName, email: row.email, phone: row.phone }));

console.log(`Extracted ${leads.length} contactable suppliers`);

Async and scheduled pipelines

Runs started through the Apify API return immediately with a run ID; poll the run's status endpoint or configure an Apify webhook on ACTOR.RUN.SUCCEEDED to be notified when the dataset is ready, instead of holding a connection open for a long keyword batch. For recurring collection, an Apify Schedule re-runs the same input on a cron-style cadence without any code on your side to maintain.

🎯 Who Needs Alibaba Email Scraper Plus? (Use Cases & Industries)

🏢 Procurement and sourcing teams

A sourcing manager evaluating five candidate suppliers for a new SKU runs the Actor with the product keyword and includeCompanyProfile on, then filters the results to verifiedSupplier: true and tradeAssurance: true before ever opening Alibaba's own messaging interface — cutting the initial screening step down to a spreadsheet review.

📊 Outbound sales and lead-generation teams

An agency building supplier outreach lists for a client runs keyword batches across a client's target categories, keeps only rows with a genuine email (excludeFreeMail: true to skip personal Gmail/Yahoo addresses), and loads the result directly into an outreach tool keyed on companyDomain.

📱 Competitive and market intelligence analysts

An analyst tracking a specific product category schedules the same keyword set weekly and watches goldSupplierYears, verifiedSupplier, and reviewScore for movement — a rising reviewScore or a new tradeAssurance: true flag signals a supplier worth re-evaluating.

🔬 Researchers

Academic and market researchers studying B2B marketplace structure — trust-signal prevalence by category, supplier geography, verification-rate patterns — can build a dataset entirely from Alibaba's publicly exposed listing and minisite data, with no login-gated information ever touched.

🎥 Product and SaaS builders

Teams building a supplier-directory product or a sourcing-lead enrichment API can use row_result rows as the seed data for their own database, joining on companyDomain or companySlug as later enrichment passes add more sources.

Is it legal to scrape Alibaba?

Scraping publicly accessible web data is generally lawful in the United States: in hiQ Labs, Inc. v. LinkedIn Corp. (9th Cir. 2019), the court held that scraping data not gated behind a login does not violate the Computer Fraud and Abuse Act. This Actor never authenticates to Alibaba — every field comes from a public Google snippet or an unauthenticated page fetch — which keeps it inside that same public-data pattern.

Separately, scraping in a way that breaches a site's Terms of Service can expose you to civil breach-of-contract claims from the platform, independent of whether the scraping itself was lawful; that risk sits with how you use the tool, not with the Actor.

Because this Actor's headline output includes business contact details (emails, phone numbers), some jurisdictions' data protection laws (GDPR, CCPA, and similar) may apply to how you store and use that contact data, even when it was collected from a public listing. Alibaba Email & Supplier Scraper Plus returns only publicly accessible data. What you do with that data is your responsibility — consult legal counsel for commercial applications involving personal or business contact data.

❓ Frequently asked questions

Does Alibaba Email Scraper Plus work without an Alibaba account?

Yes. No Alibaba login or account is used anywhere in the pipeline — keyword discovery goes through Google, and page fetches (minisite, supplier website) are unauthenticated. That is also why contact fields are null on any page that renders its contact details only behind an Alibaba login: the Actor does not attempt to authenticate to get past that wall.

How does Alibaba Email Scraper Plus handle Alibaba's anti-scraping measures?

Google SERP requests rotate through the Apify GOOGLE_SERP proxy group and retry up to 3 times with a fresh proxy URL and a jittered delay between attempts if a block pattern (CAPTCHA text, "unusual traffic" messaging) is detected. Company-page and supplier-website fetches use curl_cffi with Chrome-131 TLS/HTTP fingerprint impersonation over the RESIDENTIAL proxy group specifically to get past Alibaba's Akamai bot protection; a page is marked blocked (never guessed at) when Akamai's own block markers appear in the response.

Can I run Alibaba Email Scraper Plus at scale without getting blocked?

The Actor scales by raising maxResults (documented up to 5000) and by queuing more keywords or startUrls in a single run. Each keyword search gives up after 5 consecutive empty result pages, and each SERP fetch gives up after 3 failed attempts with proxy rotation between them — these are the Actor's own documented retry limits, not a platform-wide guarantee against blocking.

How fresh is the data Alibaba Email Scraper Plus returns?

Every field is fetched live during the run — there is no caching layer. Each row carries scrapedAt, an ISO-8601 UTC timestamp generated at the moment that row was assembled, so you can always tell exactly when a given contact or company record was captured.

Which Alibaba Email Scraper Plus fields work best for AI training and RAG indexing?

For RAG, description and title carry the free-text listing copy that best captures what a supplier actually offers, in their own words. For structured training data, companyCountry, businessType, goldSupplierYears, verifiedSupplier, tradeAssurance, and reviewScore are typed primitives with a consistent shape across every row — no string parsing or normalization needed before they go into a feature set or a model context window.

Does Alibaba Email & Supplier Scraper Plus collect personal data, and who is responsible for compliant use?

The Actor extracts publicly available business contact information — supplier emails and phone numbers as they appear on public listings and pages. It performs no identity verification and applies no consent check, so the lawful basis for storing and using that contact data under GDPR, CCPA, or similar regimes sits with the person or organization running the Actor, not with the Actor itself.

Does Alibaba Email Scraper Plus work with Claude, ChatGPT, and other AI agent tools?

It is callable as an HTTP endpoint by any agent framework through the Apify API's run and dataset-items endpoints — every response is typed JSON, so an agent can consume it directly without an HTML-parsing step in the loop.

How does Alibaba Email Scraper Plus compare to other Alibaba scrapers?

Against scrape-alibaba-suppliers and devcake/alibaba-supplier-scraper, this Actor is the only one of the three whose documented output includes a validated, confidence-labeled business email and phone field, as observed on the Apify Store on 2026-07-26. Where it is honestly behind: devcake's listing documents deeper factory-floor metrics (employee counts, factory size, revenue estimates) that this Actor does not attempt to extract, and toolsnmoreapi's listing documents a reverse-image search mode this Actor has no equivalent of, both as observed on the Apify Store on 2026-07-26.

ℹ️ Disclaimer

Alibaba Email & Supplier Scraper Plus extracts only publicly available data from Alibaba.com. This tool is intended for lawful use cases only. Users are responsible for complying with Alibaba's Terms of Service and applicable data protection laws in their jurisdiction.