# Taobao Email Scraper (`leads-scraper/taobao-email-scraper`) Actor Taobao Email Scraper SD - Taobao Email Scraper is a lead generation tool that extracts leads with public contact emails, account names and profile URLs from Taobao results by keyword, location and email domain - Taobao email extractor. - **URL**: https://apify.com/leads-scraper/taobao-email-scraper.md - **Developed by:** [Leads Scraper](https://apify.com/leads-scraper) (community) - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $2.49 / 1,000 results This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ### Taobao Email Scraper Read this first: **Taobao is largely excluded from Google's index, so expect very low volume.** That is the single most important fact about this Actor. A live test run of the Taobao Email Scraper returned only **5 result blocks** in total. Not 5 pages, not 5 thousand rows — 5 blocks. We are not going to soften that number. The Taobao Email Scraper reads publicly indexed Google search results for `taobao.com` and pulls contact emails out of the titles and snippets it finds. There is very little there to read. If your actual goal is China wholesale supplier list building, start somewhere else. The [DHgate Email Scraper](https://apify.com/neuro-scraper/dhgate-email-scraper) and the [AliExpress Email Scraper](https://apify.com/neuro-scraper/aliexpress-email-scraper) target sites that Google indexes properly, and they will give you dramatically more Chinese marketplace suppliers per run. That advice is not a sales redirect. If you leave this page for DHgate and never run the Taobao Email Scraper at all, you have been served correctly. So who should run the Taobao Email Scraper? Someone who already runs the rest of this family and wants coverage completeness, or someone doing a narrow, patient, long-tail search for one specific Taobao shop contact. Nobody should treat the Taobao Email Scraper as a volume lead source for Taobao lead generation. Used as a supplement it is useful; used as a pipeline it will disappoint you. ### Why the Taobao Email Scraper returns so little The honest reason is structural: **Baidu, not Google, is the dominant search index for Chinese marketplaces.** Taobao's crawler policies and the Chinese-language web mean Google holds very little `taobao.com` content. The Taobao Email Scraper searches Google only. It does not query Baidu, Sogou, or any Chinese search engine, so whatever Baidu knows about a shop is invisible to this Actor. Put simply: the reachable surface is small. No input tuning changes the size of Google's index — it only changes how thoroughly the Taobao Email Scraper sweeps the small part that exists. Compare that with DHgate and AliExpress, which publish English-language, globally targeted pages that Google crawls enthusiastically. Same code, same method, wildly different search-index coverage. The Taobao Email Scraper is therefore an honest completeness tool. It is the right Actor when you need to say "we also checked Taobao," and the wrong Actor when you need a pipeline. ### How the Taobao Email Scraper works The Taobao Email Scraper builds Google queries with the `site:` operator against `taobao.com`, combining your keywords, your chosen email domains and an optional location phrase. Those queries go out through the **Apify GOOGLE\_SERP proxy** using async HTTP requests. There is no browser, no JavaScript rendering, no login, no cookies and no Taobao API call of any kind. Each returned page is parsed by structural block parsing: the Actor locates every `

` title and takes the smallest surrounding block. It never depends on Google's CSS class names, which change often. Inside each block, a domain-filtered regex pulls out addresses that end in one of your `customDomains`. Snippet parsing also lifts the account label, any display name and the description text. Global deduplication runs across every query and every page, so one Taobao seller contact appears once in your dataset no matter how many results mention it. Rows are pushed to the dataset as they are found. Query expansion multiplies each keyword and domain pair into base, quoted and `intitle:` phrasings plus one variant per query modifier. Base queries always run first so the best results land early. That expansion matters more to the Taobao Email Scraper than to any sibling Actor, because sweeping a thin index thoroughly is the only compensation available. Reliability work happens underneath: proxy sessions are refreshed per request, failed pages get up to three attempts with exponential backoff, and CAPTCHA detection treats consent or "unusual traffic" pages as retryable rather than empty. Resumable state is stored in the key-value store, keyed by a hash of your input, and is saved on Apify's `PERSIST_STATE`, `MIGRATING` and `ABORTING` events. A migrated run picks up where it stopped. If Google changes its markup entirely, a whole-page fallback parser degrades the run to "emails without account details" rather than "no emails at all." ### Taobao Email Scraper features | Feature | What it means for you | |---|---| | Google SERP scraping via `site:` operator | Every query is scoped to `taobao.com`; nothing outside that domain is collected. | | Query expansion | Base, quoted, `intitle:` and one variant per query modifier, widening a thin index. | | Domain-filtered regex | Only addresses on your `customDomains` are kept, so noise stays out of the dataset. | | Email normalisation | Understands `name [at] domain [dot] com`, `(at)`, spaced `@`, zero-width characters and full-width `＠`. | | Junk filter | Rejects placeholders such as `email@`, `yourname@`, `test@`, `xxx@` and single-character locals. | | Boundary-correct matching | `@gmail.com` will not match inside `@gmail.company` or `@gmail.com.br`. | | Soft-wrap repair | Discards a hit that is only the tail of another email in the same block. | | Global deduplication | Each unique address is written once across the whole run. | | Structural block parsing | Parses around the `

` title instead of trusting Google's class names. | | Proxy sessions and exponential backoff | Fresh session per request, up to three attempts per page. | | CAPTCHA detection | Consent and "unusual traffic" pages are retried, not counted as empty. | | Requeue of blocked queries | Blocked or failed queries run once more at the end of the run. | | Resumable state | Progress survives migrations and aborts, keyed by an input hash. | | Whole-page fallback parser | A layout change degrades output instead of breaking it. | | Dataset export | CSV/JSON and other Apify dataset formats, ready for your CRM. | | Run summary logs | Pages fetched, blocked pages, retries and emails per page. | ### Taobao Email Scraper input fields Every field below is taken verbatim from the Taobao Email Scraper input schema. Only `keywords` is required. | Field | Type | Default | Meaning | |---|---|---|---| | `keywords` | array (required) | `["supplier","wholesale"]` | Search terms describing the Taobao shops you want. | | `location` | string | `""` | Optional location phrase appended to every query. | | `customDomains` | array | `["@gmail.com","@yahoo.com"]` | Only emails on these domains are kept; the `@` is optional. | | `maxEmails` | integer 1-10000 | `20` | Stop once this many unique emails are collected. | | `countryCode` | string | `""` | Two-letter country for the search proxy (US, GB, DE, CN, HK). | | `expandQueries` | boolean | `true` | Search each keyword x domain pair in several phrasings. | | `queryModifiers` | array | `["email","contact","wholesale","cooperation","business"]` | Extra words combined with each keyword when expansion is on. | | `maxPagesPerQuery` | integer 1-50 | `30` | Page cap per query. | | `maxConcurrency` | integer 1-20 | `5` | How many queries run in parallel. | Two levers matter more here than on any other Actor in the family: `countryCode` and Chinese-language querying. Both are real, and both are worth using. Setting `countryCode` to `"CN"` or `"HK"` routes the search proxy through that region, which changes which of Google's regional result sets you see. It is a genuine difference, not a placebo. Chinese keywords matter because most `taobao.com` text is Chinese. Try `供应商` (supplier), `批发` (wholesale), `厂家` (factory or manufacturer) and `代理` (agent) alongside the English defaults. Widening `customDomains` is the third lever. Chinese sellers commonly use `@163.com`, `@qq.com` and `@126.com`, and the default Gmail/Yahoo pair will simply miss them. Be clear-eyed, though: all three levers together still will not produce large volume from the Taobao Email Scraper. They move you from almost nothing to slightly more than almost nothing. ### Taobao Email Scraper input examples A standard run of the Taobao Email Scraper using the shipped defaults: ```json { "keywords": ["supplier", "wholesale"], "location": "", "customDomains": ["@gmail.com", "@yahoo.com"], "maxEmails": 20, "countryCode": "", "expandQueries": true, "queryModifiers": ["email", "contact", "wholesale", "cooperation", "business"], "maxPagesPerQuery": 30, "maxConcurrency": 5 } ``` A Chinese-language run with country targeting and widened domains. This is the configuration we would actually recommend for the Taobao Email Scraper: ```json { "keywords": ["供应商", "批发", "厂家", "代理"], "location": "", "customDomains": ["@gmail.com", "@163.com", "@qq.com", "@126.com"], "maxEmails": 200, "countryCode": "CN", "expandQueries": true, "queryModifiers": ["email", "contact", "wholesale", "cooperation", "business"], "maxPagesPerQuery": 30, "maxConcurrency": 5 } ``` Raising `maxEmails` costs nothing when the index is thin — the run simply ends when the queries are exhausted, well below the ceiling you set. ### Taobao Email Scraper output fields Every dataset item written by the Taobao Email Scraper has exactly these fourteen fields. | Field | Meaning | |---|---| | `network` | Platform name. | | `keyword` | The keyword that produced the lead. | | `query` | The exact Google query used. | | `title` | Raw result title. | | `accountName` | The account label Google prints. | | `fullName` | Display name parsed from a profile-style title; empty for listing captions. | | `username` | URL-safe handle when Taobao exposes one in the result; otherwise `null`. | | `profileUrl` | `https://shop{username}.taobao.com/` when a handle is known; otherwise empty. | | `url` | Direct link when exposed, else the profile URL. | | `description` | Snippet text, cleaned of labels and counters. | | `email` | Lower-cased email address. | | `emailDomain` | The matched domain, e.g. `@gmail.com`. | | `possiblyTruncated` | `true` when Google's snippet ellipsis touched the email — verify before sending. | | `foundAt` | ISO 8601 UTC timestamp. | A realistic sample. Three rows is a plausible whole run for the Taobao Email Scraper, which is exactly why we show three: ```json [ { "network": "Taobao", "keyword": "supplier", "query": "site:taobao.com supplier \"@gmail.com\"", "title": "厂家直销批发 - 淘宝网", "accountName": "厂家直销批发", "fullName": "", "username": null, "profileUrl": "", "url": "https://taobao.com/", "description": "批发供应, 长期合作. Contact: sourcing.hz***@gmail.com", "email": "sourcing.hz88@gmail.com", "emailDomain": "@gmail.com", "possiblyTruncated": true, "foundAt": "2026-08-29T09:14:22Z" }, { "network": "Taobao", "keyword": "批发", "query": "site:taobao.com 批发 \"@163.com\"", "title": "义乌小商品批发店铺", "accountName": "义乌小商品批发", "fullName": "", "username": "123456789", "profileUrl": "https://shop123456789.taobao.com/", "url": "https://shop123456789.taobao.com/", "description": "小商品批发, 支持代发. 商务合作邮箱 yiwu.trade@163.com", "email": "yiwu.trade@163.com", "emailDomain": "@163.com", "possiblyTruncated": false, "foundAt": "2026-08-29T09:15:03Z" }, { "network": "Taobao", "keyword": "wholesale", "query": "site:taobao.com wholesale cooperation \"@qq.com\"", "title": "Wholesale cooperation - Taobao store", "accountName": "Wholesale cooperation", "fullName": "", "username": null, "profileUrl": "", "url": "https://taobao.com/", "description": "Business cooperation and bulk orders welcome. 2286xxxxx@qq.com", "email": "22861234567@qq.com", "emailDomain": "@qq.com", "possiblyTruncated": false, "foundAt": "2026-08-29T09:16:41Z" } ] ``` Note that two of the three rows carry `"username": null` and an empty `profileUrl`. That ratio is typical of the Taobao Email Scraper, and the reason is explained in Limitations. ### Who uses the Taobao Email Scraper | Audience | How they use it | |---|---| | Sourcing agents | Add a handful of Taobao shop contact rows to a supplier discovery sheet already built from better-indexed sites. | | Importers | Chase one specific factory or shop found earlier by name, using a long-tail keyword. | | Private-label brands | Cross-check whether a candidate manufacturer has any public Taobao presence at all. | | Dropshippers | Dropshipping supplier research where Taobao is one of eight or ten marketplaces being swept. | | Market researchers | Measure search-index coverage of Chinese marketplaces rather than harvest leads. | | Agencies | Run the Taobao Email Scraper as the completeness pass in a wider Taobao lead generation workflow. | In every one of those cases the Taobao Email Scraper is a supplement. The volume comes from elsewhere in the family. For serious import sourcing across Chinese marketplace suppliers, pair it with the [Tmall Email Scraper](https://apify.com/leads-scraper/tmall-email-scraper) and the [JD.com Email Scraper](https://apify.com/leads-scraper/jd-com-email-scraper) for domestic Chinese platforms. For export-facing suppliers who actively court Western buyers, the [Temu Email Scraper](https://apify.com/leads-scraper/temu-email-scraper) and the [Shopee Email Scraper](https://apify.com/leads-scraper/shopee-email-scraper) both reach far more sourcing agent leads than Taobao can. ### Limitations **Taobao is largely excluded from Google's index, so expect very low volume.** A live test run returned only 5 result blocks. Baidu is the dominant index for Chinese marketplaces, and the Taobao Email Scraper does not search Baidu. The Taobao Email Scraper only finds accounts whose email is publicly visible in Google's index. If a shop never published an address on an indexed page, no configuration will surface it. Google caps a single query at roughly 300 results. That cap is why query expansion exists, though on a thin index it is rarely the binding constraint. `possiblyTruncated: true` means Google's snippet ellipsis touched the address and it may be cut off. Verify those before sending anything. The Actor requires the Apify GOOGLE\_SERP proxy and cannot run without Apify proxy credentials. This is not optional. Free Apify plans are capped at 100 emails per run; paid plans are uncapped. On this Actor the cap is unlikely to be the thing that stops you. `username` and `profileUrl` are populated only when Google's result exposes a Taobao handle. Many results show only a Chinese display name, so those rows have `accountName` but an empty `profileUrl`. That is a Google limitation, not a bug in the Taobao Email Scraper. Results vary with keywords, domains, country and timing. No volume is guaranteed on any run. ### Responsible use You are the data controller for anything you collect. GDPR, CCPA and equivalent local rules apply to the output of the Taobao Email Scraper just as they would to any other list. B2B outreach usually rests on a legitimate-interest lawful basis, but that basis has conditions: relevance, proportionality and a clear identity in every message. Honour opt-outs immediately and permanently, respect Taobao's marketplace terms, and do not spam. Contacting a supplier about a genuine order is welcome; blasting a list is not. Because the Taobao Email Scraper produces so few rows, careful individual outreach is both the ethical option and the practical one. ### Taobao Email Scraper FAQ #### How many results should I expect? Very low. A live test run of the Taobao Email Scraper returned only 5 result blocks in total. Taobao is largely excluded from Google's index because Baidu dominates Chinese search. Widening `customDomains`, using Chinese keywords and raising `maxEmails` help only marginally. For real volume, use the [DHgate Email Scraper](https://apify.com/neuro-scraper/dhgate-email-scraper) or the [AliExpress Email Scraper](https://apify.com/neuro-scraper/aliexpress-email-scraper). #### Why is volume so low? Because Google holds very little `taobao.com` content. Taobao's crawler policies and the Chinese-language web keep it out of the index Google serves, so the surface the Taobao Email Scraper can reach is genuinely small. #### Does it search Baidu? No. Google only, through the Apify GOOGLE\_SERP proxy. There is no Baidu, Sogou or Shenma support, and that is the main reason for the low yield. #### Does the Taobao Email Scraper log into Taobao? No. It never logs in, never uses a Taobao API and never opens taobao.com in a browser. It reads publicly indexed Google results only — no cookies, no JavaScript rendering, no authentication. #### Why is `profileUrl` usually empty? Google frequently prints a Chinese display name instead of a shop handle. Without a handle the Actor cannot build the `https://shop{username}.taobao.com/` URL, so it leaves `username` as `null` and `profileUrl` empty rather than guessing. #### Do I need the Apify proxy? Yes. The Taobao Email Scraper requires the Apify GOOGLE\_SERP proxy and will not run without Apify proxy credentials. #### Is this legal? It reads publicly indexed search results, which is generally permissible. What you do next is regulated: you are the data controller, GDPR and CCPA apply, and you must honour opt-outs and respect Taobao's terms. #### Should I use Chinese keywords? Yes. Most Taobao text is Chinese, so `供应商`, `批发`, `厂家` and `代理` reach snippets that English terms cannot. Combine them with `countryCode: "CN"` or `"HK"`. Expect a modest improvement, not a transformation. #### Which email domains should I add? Add `@163.com`, `@qq.com` and `@126.com`. These are mainstream Chinese providers and the default `@gmail.com` / `@yahoo.com` pair misses most Chinese sellers entirely. #### Can I export to CSV? Yes. Every row the Taobao Email Scraper writes lands in an Apify dataset, exportable as CSV, JSON, Excel and the other standard formats for cold outreach tooling or your CRM. #### What if my run gets blocked? CAPTCHA and consent pages are detected and retried with exponential backoff on a fresh proxy session, and blocked queries are re-queued once at the end. Genuine hard blocks are rare with the Taobao Email Scraper; empty results usually mean the index is simply thin. #### What is the honest best use of this Actor? Completeness. Run the Taobao Email Scraper when you want Taobao covered in a multi-marketplace sweep, or when you are hunting one specific Taobao seller contact. Do not build a funnel on it. ### Related Actors | Actor | What it collects | |---|---| | [Taobao Email and Phone Number Scraper](https://apify.com/leads-scraper/taobao-email-and-phone-number-scraper) | Emails and phone numbers from Taobao | | [Taobao Phone Number Scraper](https://apify.com/leads-scraper/taobao-phone-number-scraper) | Public phone numbers from Taobao | | [AliExpress Email Scraper](https://apify.com/neuro-scraper/aliexpress-email-scraper) | Public contact emails from AliExpress | | [Allegro Email Scraper](https://apify.com/neuro-scraper/allegro-email-scraper) | Public contact emails from Allegro | | [Amazon Email Scraper](https://apify.com/leads-scraper/amazon-email-scraper) | Public contact emails from Amazon | | [Best Buy Seller Email Scraper](https://apify.com/leads-scraper/best-buy-seller-email-scraper) | Public contact emails from Best Buy | | [BigCommerce Store Email Scraper](https://apify.com/neuro-scraper/bigcommerce-store-email-scraper) | Public contact emails from BigCommerce Store | | [Cdiscount Email Scraper](https://apify.com/neuro-scraper/cdiscount-email-scraper) | Public contact emails from Cdiscount | | [Coupang Email Scraper](https://apify.com/neuro-scraper/coupang-email-scraper) | Public contact emails from Coupang | | [Depop Email Scraper](https://apify.com/leads-scraper/depop-email-scraper) | Public contact emails from Depop | | [DHgate Email Scraper](https://apify.com/neuro-scraper/dhgate-email-scraper) | Public contact emails from DHgate | | [eBay Email Scraper](https://apify.com/leads-scraper/ebay-email-scraper) | Public contact emails from eBay | | [Ecwid Store Email Scraper](https://apify.com/neuro-scraper/ecwid-store-email-scraper) | Public contact emails from Ecwid Store | | [Etsy Email Scraper](https://apify.com/leads-scraper/etsy-email-scraper) | Public contact emails from Etsy | | [Faire Email Scraper](https://apify.com/leads-scraper/faire-email-scraper) | Public contact emails from Faire | | [Flipkart Email Scraper](https://apify.com/leads-scraper/flipkart-email-scraper) | Public contact emails from Flipkart | | [Home Depot Seller Email Scraper](https://apify.com/leads-scraper/home-depot-seller-email-scraper) | Public contact emails from Home Depot | | [JD.com Email Scraper](https://apify.com/leads-scraper/jd-com-email-scraper) | Public contact emails from JD.com | | [Lazada Email Scraper](https://apify.com/neuro-scraper/lazada-email-scraper) | Public contact emails from Lazada | | [Lowe's Seller Email Scraper](https://apify.com/leads-scraper/lowes-seller-email-scraper) | Public contact emails from Lowe's | | [MercadoLibre Email Scraper](https://apify.com/neuro-scraper/mercadolibre-email-scraper) | Public contact emails from MercadoLibre | | [Mercari Email Scraper](https://apify.com/neuro-scraper/mercari-email-scraper) | Public contact emails from Mercari | | [Newegg Email Scraper](https://apify.com/leads-scraper/newegg-email-scraper) | Public contact emails from Newegg | | [Otto Email Scraper](https://apify.com/leads-scraper/otto-email-scraper) | Public contact emails from Otto | | [Overstock Email Scraper](https://apify.com/leads-scraper/overstock-email-scraper) | Public contact emails from Overstock | | [Poshmark Email Scraper](https://apify.com/leads-scraper/poshmark-email-scraper) | Public contact emails from Poshmark | | [Rakuten Email Scraper](https://apify.com/neuro-scraper/rakuten-email-scraper) | Public contact emails from Rakuten | | [Shopee Email Scraper](https://apify.com/leads-scraper/shopee-email-scraper) | Public contact emails from Shopee | | [Shopify Store Email Scraper](https://apify.com/leads-scraper/shopify-store-email-scraper) | Public contact emails from Shopify Store | | [Target Seller Email Scraper](https://apify.com/neuro-scraper/target-seller-email-scraper) | Public contact emails from Target | | [Temu Email Scraper](https://apify.com/leads-scraper/temu-email-scraper) | Public contact emails from Temu | | [Tmall Email Scraper](https://apify.com/leads-scraper/tmall-email-scraper) | Public contact emails from Tmall | | [Vinted Email Scraper](https://apify.com/leads-scraper/vinted-email-scraper) | Public contact emails from Vinted | | [Walmart Email Scraper](https://apify.com/leads-scraper/walmart-email-scraper) | Public contact emails from Walmart | | [Wayfair Email Scraper](https://apify.com/neuro-scraper/wayfair-email-scraper) | Public contact emails from Wayfair | | [Wish Email Scraper](https://apify.com/leads-scraper/wish-email-scraper) | Public contact emails from Wish | | [Wix Stores Email Scraper](https://apify.com/leads-scraper/wix-stores-email-scraper) | Public contact emails from Wix Stores | | [WooCommerce Email Scraper](https://apify.com/neuro-scraper/woocommerce-email-scraper) | Public contact emails from WooCommerce | | [Zalando Email Scraper](https://apify.com/leads-scraper/zalando-email-scraper) | Public contact emails from Zalando | | [AliExpress Email and Phone Number Scraper](https://apify.com/neuro-scraper/aliexpress-email-and-phone-number-scraper) | Emails and phone numbers from AliExpress | | [Allegro Email and Phone Number Scraper](https://apify.com/neuro-scraper/allegro-email-and-phone-number-scraper) | Emails and phone numbers from Allegro | | [Amazon Email and Phone Number Scraper](https://apify.com/leads-scraper/amazon-email-and-phone-number-scraper) | Emails and phone numbers from Amazon | ### Leave a review If the Taobao Email Scraper saved you time, please leave a star rating and a short review on the Actor page. Reviews are how other buyers judge whether a tool works, and they tell us which features to build next. If something did not work, email instead - bugs get fixed faster than they get complained about. # Actor input Schema ## `keywords` (type: `array`): Search terms describing the Taobao accounts you want (niche, job title, industry). ## `location` (type: `string`): Optional location phrase added to every query (e.g. "New York"). ## `customDomains` (type: `array`): Only emails ending with one of these domains are collected. With or without the leading @. Each domain is searched separately, so more domains means more results but a longer run - remove some for a faster, narrower search, or add your own (e.g. @company.com). ## `maxEmails` (type: `integer`): Stop once this many unique emails have been collected. ## `countryCode` (type: `string`): Two-letter country code for the search proxy (e.g. US, GB, DE). Empty for any. ## `expandQueries` (type: `boolean`): Search each keyword x domain pair with several phrasings. Recommended - Google caps a single query at ~300 results. ## `queryModifiers` (type: `array`): Extra words combined with each keyword when Expand queries is on. Tuned for Taobao. ## `maxPagesPerQuery` (type: `integer`): Google rarely returns more than ~30 pages for one query. ## `maxConcurrency` (type: `integer`): How many queries run in parallel. ## Actor input object example ```json { "keywords": [ "supplier", "wholesale" ], "location": "", "customDomains": [ "@gmail.com", "@yahoo.com" ], "maxEmails": 20, "countryCode": "", "expandQueries": true, "queryModifiers": [ "email", "contact", "wholesale", "cooperation", "business" ], "maxPagesPerQuery": 30, "maxConcurrency": 5 } ``` # Actor output Schema ## `results` (type: `string`): Records produced by Taobao Email Scraper, stored in the run's default dataset. # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "keywords": [ "supplier", "wholesale" ], "location": "", "customDomains": [ "@gmail.com", "@yahoo.com" ], "countryCode": "", "queryModifiers": [ "email", "contact", "wholesale", "cooperation", "business" ] }; // Run the Actor and wait for it to finish const run = await client.actor("leads-scraper/taobao-email-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "keywords": [ "supplier", "wholesale", ], "location": "", "customDomains": [ "@gmail.com", "@yahoo.com", ], "countryCode": "", "queryModifiers": [ "email", "contact", "wholesale", "cooperation", "business", ], } # Run the Actor and wait for it to finish run = client.actor("leads-scraper/taobao-email-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "keywords": [ "supplier", "wholesale" ], "location": "", "customDomains": [ "@gmail.com", "@yahoo.com" ], "countryCode": "", "queryModifiers": [ "email", "contact", "wholesale", "cooperation", "business" ] }' | apify call leads-scraper/taobao-email-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,leads-scraper/taobao-email-scraper" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/aOA9ypmCXiP5mydO8/builds/2SUh1YbbXWkxqyBPi/openapi.json