Alibaba Email Scraper
Pricing
from $2.99 / 1,000 supplier emails
Go to Apify Store
Alibaba Email Scraper
Extract publicly indexed Alibaba seller emails from Google search results and public profile pages.
Alibaba Email Scraper
Pricing
from $2.99 / 1,000 supplier emails
Extract publicly indexed Alibaba seller emails from Google search results and public profile pages.
Supplier keyword used to build a public Google site search when no explicit startUrls or profileUrls are provided.
Optional supplier keywords. Each becomes a public Google site:alibaba.com source; explicit startUrls/profileUrls take precedence over generated searches.
Optional public Alibaba supplier-search, company-profile, supplier-index, or product URLs. These are combined with startUrls and suppress generated Google searches.
Optional Google or Alibaba URLs in request-list form. URLs are deduplicated, paginated per source, and share one global maxResults limit.
Optional lowercase or @-prefixed domains. A contact passes when its domain equals a value or is a subdomain of it.
Optional case-insensitive text match across email, supplier, company, product, country, badges, tags, markets, revenue, and context fields. Missing text does not match.
Optional case-insensitive exact match against the observed Country/Region value, such as China or Vietnam.
Keep only records with an observed supplier tenure at or above this value. Records without a tenure value do not pass.
Keep only records with an observed response rate at or above this percentage. Records without a response rate do not pass.
Keep records whose observed badge list contains every requested value, case-insensitively, such as Gold Supplier or Trade Assurance.
[]Relevance keeps source/page/card order. Other choices sort globally after all permitted pages are fetched; missing numeric values sort last and text ties are stable.
Global maximum number of unique email-bearing contact records emitted across every source and page.
Maximum pages followed for each source URL. Use 0 for automatic pagination up to the hard 100-page safety cap.
Merge repeated public observations globally by normalized email across pages and sources.
Maximum parsed email-bearing rows considered from each response before filters. The global maxResults limit still applies.
Include observed product title/URL pairs and productUrls. The first productUrl remains available as the primary URL when present.
Maximum product title/URL pairs retained per contact. Use 0 to omit product arrays while retaining the observed product count.
Keep the bounded Tags list observed on supplier cards.
Keep a bounded public contextSnippet around each normalized email. When enabled, the snippet contains the exact email.
Minimum delay between starts of public requests. Use respectful pacing for live sources.
Maximum number of source URLs processed concurrently. Pagination within one source stays sequential.
Finite retries for transient network, timeout, 408, 425, 429, and 5xx responses. Challenge and access-denied pages fail closed.
Maximum time allowed for one public response.
Safety cap for one HTML or JSON response.
Optional standard Apify Proxy route for permitted public requests. Proxying never bypasses robots, login, CAPTCHA, or access controls.
Optional transparent single-line HTTP user-agent string.