# Weibo Email Scraper (`leads-scraper/weibo-email-scraper`) Actor Weibo Email Scraper SD - Weibo Email Scraper is a lead generation tool that extracts leads with public contact emails, account names and profile URLs from Weibo results by keyword, location and email domain - Weibo email extractor. - **URL**: https://apify.com/leads-scraper/weibo-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 ### Weibo Email Scraper ### Weibo Email Scraper for Chinese KOL and Brand Contact Discovery The Weibo Email Scraper is an Apify Actor that collects publicly indexed contact emails from Sina Weibo and returns them as a structured dataset. It exists because finding a 商务合作 (business cooperation) address on Weibo by hand is slow, repetitive work. Rather than logging into the platform, the Weibo Email Scraper builds Google queries with the `site:weibo.com OR site:weibo.cn` operator and parses the result blocks. Everything it extracts is already public in Google's index. Weibo is where Chinese KOLs, MCN agencies, brand accounts and media outlets publish a cooperation mailbox in their bio or pinned post. The Weibo Email Scraper is tuned to surface exactly those patterns. You supply keywords, an optional location and the email domains that matter. You get back account names, profile URLs, bio snippets and normalised, deduplicated email addresses. #### Who this Weibo email extractor is for Brands planning influencer campaigns in mainland China. Agencies building KOL media lists. Cross-border e-commerce teams sourcing partners. Researchers mapping how a vertical presents itself on Chinese social media. ### Key Features of the Weibo Email Scraper | Feature | What it means in practice | |---|---| | Google-based contact discovery | The Weibo Email Scraper reads publicly indexed `weibo.com` and `weibo.cn` results — no login, no cookies, no browser | | Dual-domain targeting | Both the desktop and mobile Weibo domains are searched in one query | | Query expansion | Each keyword runs as a base query, a quoted query, an `intitle:` query and one variant per modifier | | Domain-filtered extraction | Only emails on your `customDomains` list are kept, so you can target `@qq.com` or `@163.com` | | Global deduplication | Every address is deduplicated across all queries and pages in the run | | Email normalisation | Handles `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, zero-width characters and the full-width `＠` common in Chinese text | | 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 | Drops a hit that is only the tail of another address in the same result block | | Concurrency control | An `asyncio` worker pool runs several queries in parallel with a shared stop signal | | Retry logic | Up to 3 attempts per page with exponential backoff and a fresh proxy session per request | | Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried, not treated as empty | | Resumable state | Progress is checkpointed in the key-value store and survives `PERSIST_STATE`, `MIGRATING` and `ABORTING` events | | Fallback parser | If Google's markup changes, the crawler degrades to "emails without account details" rather than "no results" | | Structured output | Fourteen fields per row, exportable to CSV, JSON or Excel | The full-width `＠` handling deserves a note. Chinese-language posts frequently use full-width punctuation, and a naive regex misses those addresses entirely. The Weibo Email Scraper normalises them before matching. ### How the Weibo Email Scraper Works 1. **Read input.** Keywords, location, email domains and limits are validated. 2. **Build queries.** The Weibo Email Scraper composes searches such as `site:weibo.com OR site:weibo.cn 美妆 商务合作 "@qq.com"`. 3. **Fetch search results.** Pages are requested asynchronously through the Apify `GOOGLE_SERP` proxy using `aiohttp`. 4. **Parse structurally.** The parser finds each `

` title, then the smallest surrounding block — it does not rely on Google's CSS class names. 5. **Extract emails.** A domain-filtered regex pulls addresses from the block text, including obfuscated and full-width forms. 6. **Deduplicate and store.** Each unique lead is pushed to the Apify dataset immediately. Base queries run first, so your strongest matches arrive early. Blocked or failed queries are re-queued once at the end of the run. The Weibo Email Scraper never opens weibo.com itself. There is no browser, no JavaScript rendering, no authentication and no API key. ### What Data Does It Extract? Each dataset row pairs one email with the account metadata Google printed beside it — typically a Weibo nickname, a verified brand name or a media outlet title. `username` and `profileUrl` are filled when Google exposes a handle such as `weibo.com/somebrand`. Where Google shows only a Chinese display name, you still get `accountName`, `fullName`, the snippet and the email. Descriptions are cleaned of interface labels and engagement counters, so the bio text you see is the bio text, not "转发 1.2万 · 评论 3421". In short, the Weibo Email Scraper gives you a contact, an identity and the evidence for both: the email itself, the account it belongs to, and the snippet it was lifted from. ### Input Fields and Configuration | Field | Type | Default | Meaning | |---|---|---|---| | `keywords` | array (required) | `["founder", "brand"]` | Search terms — niche, job title or industry | | `location` | string | `""` | Optional location phrase added 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 after this many unique emails | | `countryCode` | string | `""` | Two-letter country for the search proxy (US, GB, DE...) | | `expandQueries` | boolean | `true` | Search each keyword × domain pair in several phrasings | | `queryModifiers` | array | `["email","contact","business","cooperation"]` | Extra words combined with each keyword when expansion is on | | `maxPagesPerQuery` | integer 1–50 | `30` | Pagination cap per query | | `maxConcurrency` | integer 1–20 | `5` | Parallel queries | #### Using countryCode with the Weibo Email Scraper `countryCode` matters more on Weibo than on almost any other platform in this family. Google's index of Chinese social content varies noticeably by search region. Try `HK`, `TW`, `SG` and `US` in separate runs. Hong Kong and Singapore searches often surface cross-border commerce and overseas Chinese accounts that a US-region search does not return. Run the Weibo Email Scraper across several country codes and merge the exports. Deduplication is per run, so overlap between runs is easy to remove afterwards. #### Choosing the right email domains The defaults are `@gmail.com` and `@yahoo.com`, which are not the Chinese norm. Weibo accounts overwhelmingly publish `@qq.com`, `@163.com`, `@126.com`, `@sina.com`, `@sina.cn` and `@foxmail.com` addresses. Setting `customDomains` to those providers is the single biggest change you can make to the Weibo Email Scraper's yield. Add `@gmail.com` alongside them if you are targeting internationally-facing brands. #### Choosing keywords Keywords go into the Google query verbatim, so Chinese input works exactly as well as English. `美妆`, `母婴`, `健身教练`, `品牌方`, `MCN` and `探店` are all valid. Pair Chinese keywords with the default modifiers, or replace the modifiers with `商务`, `合作`, `邮箱` and `联系` for a fully Chinese-language expansion set. ### Output Schema and Dataset Fields | Field | Meaning | |---|---| | `network` | Platform name | | `keyword` | The keyword that produced the lead | | `query` | The exact Google query used | | `title` | Raw result title | | `accountName` | Account label Google prints (handle or display name) | | `fullName` | Display name parsed from a profile-style title; empty for post captions | | `username` | URL-safe handle when Weibo exposes one; otherwise `null` | | `profileUrl` | Canonical account URL when a handle is known; otherwise empty | | `url` | Direct platform link when exposed, else the profile URL | | `description` | Bio or caption snippet, cleaned of labels and counters | | `email` | Lower-cased email address | | `emailDomain` | The matched domain, e.g. `@qq.com` | | `possiblyTruncated` | `true` when Google's snippet ellipsis touched the email — verify before sending | | `foundAt` | ISO 8601 UTC timestamp | Because `query` and `keyword` are stored on every row, the output is fully auditable. You can see which phrasing found which KOL and tune the next run accordingly. ### How to Use the Weibo Email Scraper 1. Open the Weibo Email Scraper on Apify and click **Try for free**. 2. Enter two or three specific keywords — a niche beats a broad category. 3. Replace `customDomains` with the Chinese mail providers listed above. 4. Set `countryCode` to `HK`, `TW`, `SG` or leave it empty and compare. 5. Set `maxEmails` to the list size you actually need. 6. Run it, then export the dataset as CSV, JSON or Excel. Leave `maxPagesPerQuery` and `maxConcurrency` at their defaults for a first test. You can raise concurrency later if your Apify plan has the memory headroom. The Weibo Email Scraper can also be triggered from the Apify API or SDK clients, which makes recurring KOL discovery runs easy to schedule. ### Use Cases for the Weibo Email Scraper | Use case | How the Weibo Email Scraper helps | |---|---| | KOL and influencer sourcing | Find creators who publish a 商务合作 mailbox in their bio | | MCN and agency prospecting | Build lists of talent agencies representing Weibo creators | | Cross-border e-commerce | Locate Chinese brand accounts open to distribution partnerships | | Media and PR outreach | Collect contacts for verified media and vertical publications | | Competitive research | Map which brands in a category maintain an active Weibo presence | | Event and expo sourcing | Gather exhibitor and speaker contacts from event accounts | | Recruitment | Source Chinese-market marketers, designers and community managers | | CRM enrichment | Add public Weibo contact emails to records you already hold | China-focused campaigns rarely stop at one network. Pair the Weibo Email Scraper with the [Zhihu Email Scraper](https://apify.com/leads-scraper/zhihu-email-scraper) for long-form expert voices and the [WeChat Email Scraper](https://apify.com/leads-scraper/wechat-email-scraper) for official-account publishers. If your campaign also covers Western creators, the [Instagram Email Scraper](https://apify.com/leads-scraper/instagram-email-scraper) uses the identical input schema, so the workflow you build around the Weibo Email Scraper transfers without changes. ### Why Use This Weibo Email Scraper Generic email crawlers point at arbitrary websites and hope. This one is a purpose-built Weibo scraper: the domain list, username pattern, profile URL template and query modifiers are all configured for Sina Weibo. Parsing is structural rather than cosmetic. Because the Weibo Email Scraper locates the `

` and walks outward, a Google layout change degrades quality instead of breaking the run. Chinese-text handling is deliberate. Full-width at signs, zero-width characters and `[at]` obfuscation are all normalised before matching, which is where most generic extractors lose leads on Chinese content. Runs are resumable and checkpointed, and every row tells you whether the snippet may have truncated the address. Finally, the Weibo Email Scraper is transparent about its method. It reads Google, it says so, and it stores the exact query on every lead so you can reproduce any result yourself. ### Limitations of the Weibo Email Scraper Please read this before buying. These constraints are real. - **Only publicly indexed emails.** The Weibo Email Scraper finds addresses already visible in Google's index. Private data and login-gated content are out of reach. - **Google caps a single query at roughly 300 results.** Query expansion exists to work around that ceiling. - **Google indexes Weibo far less completely than Western networks.** Chinese platforms are thinly crawled, much of the indexed content is in Chinese, and coverage shifts over time. Expect lower volume than an Instagram or Facebook run. - **`username` and `profileUrl` may be empty.** They are only populated when Google exposes a handle. Some rows carry `accountName` and `fullName` only — a Google limitation, not a bug. - **`possiblyTruncated: true` means verify.** Google's snippet ellipsis may have clipped the address. - **Requires the Apify `GOOGLE_SERP` proxy.** The Actor cannot run without Apify proxy credentials. - **Free Apify plans are capped at 100 emails per run.** Paid plans are uncapped. - **No volume guarantee.** Results vary with keywords, domains, country code and location. The Weibo Email Scraper is not affiliated with, endorsed by or connected to Sina Weibo. Use the output in line with PIPL, GDPR and your own outreach policy. ### Related Actors | Actor | What it collects | |---|---| | [Weibo Email and Phone Number Scraper](https://apify.com/leads-scraper/weibo-email-and-phone-number-scraper) | Emails and phone numbers from Weibo | | [Weibo Phone Number Scraper](https://apify.com/leads-scraper/weibo-phone-number-scraper) | Public phone numbers from Weibo | | [Behance Email Scraper](https://apify.com/leads-scraper/behance-email-scraper) | Public contact emails from Behance | | [Bigo Live Email Scraper](https://apify.com/leads-scraper/bigo-live-email-scraper) | Public contact emails from Bigo Live | | [Bluesky Email Scraper](https://apify.com/leads-scraper/bluesky-email-scraper) | Public contact emails from Bluesky | | [Bumble Email Scraper](https://apify.com/leads-scraper/bumble-email-scraper) | Public contact emails from Bumble | | [Clubhouse Email Scraper](https://apify.com/leads-scraper/clubhouse-email-scraper) | Public contact emails from Clubhouse | | [Dailymotion Email Scraper](https://apify.com/leads-scraper/dailymotion-email-scraper) | Public contact emails from Dailymotion | | [DeviantArt Email Scraper](https://apify.com/leads-scraper/deviantart-email-scraper) | Public contact emails from DeviantArt | | [Discord Email Scraper](https://apify.com/leads-scraper/discord-email-scraper) | Public contact emails from Discord | | [Dribbble Email Scraper](https://apify.com/leads-scraper/dribbble-email-scraper) | Public contact emails from Dribbble | | [Facebook Email Scraper](https://apify.com/leads-scraper/facebook-email-scraper) | Public contact emails from Facebook | | [Goodreads Email Scraper](https://apify.com/leads-scraper/goodreads-email-scraper) | Public contact emails from Goodreads | | [Hinge Email Scraper](https://apify.com/leads-scraper/hinge-email-scraper) | Public contact emails from Hinge | | [Instagram Email Scraper](https://apify.com/leads-scraper/instagram-email-scraper) | Public contact emails from Instagram | | [KakaoTalk Email Scraper](https://apify.com/leads-scraper/kakaotalk-email-scraper) | Public contact emails from KakaoTalk | | [Kick Email Scraper](https://apify.com/leads-scraper/kick-email-scraper) | Public contact emails from Kick | | [Lemon8 Email Scraper](https://apify.com/leads-scraper/lemon8-email-scraper) | Public contact emails from Lemon8 | | [Likee Email Scraper](https://apify.com/leads-scraper/likee-email-scraper) | Public contact emails from Likee | | [LINE Email Scraper](https://apify.com/leads-scraper/line-email-scraper) | Public contact emails from LINE | | [LinkedIn Email Scraper](https://apify.com/leads-scraper/linkedin-email-scraper) | Public contact emails from LinkedIn | | [Mastodon Email Scraper](https://apify.com/leads-scraper/mastodon-email-scraper) | Public contact emails from Mastodon | | [Medium Email Scraper](https://apify.com/leads-scraper/medium-email-scraper) | Public contact emails from Medium | | [Mixcloud Email Scraper](https://apify.com/leads-scraper/mixcloud-email-scraper) | Public contact emails from Mixcloud | | [Patreon Email Scraper](https://apify.com/leads-scraper/patreon-email-scraper) | Public contact emails from Patreon | | [Pinterest Email Scraper](https://apify.com/leads-scraper/pinterest-email-scraper) | Public contact emails from Pinterest | | [Quora Email Scraper](https://apify.com/leads-scraper/quora-email-scraper) | Public contact emails from Quora | | [Reddit Email Scraper](https://apify.com/leads-scraper/reddit-email-scraper) | Public contact emails from Reddit | | [Rumble Email Scraper](https://apify.com/leads-scraper/rumble-email-scraper) | Public contact emails from Rumble | | [Snapchat Email Scraper](https://apify.com/leads-scraper/snapchat-email-scraper) | Public contact emails from Snapchat | | [SoundCloud Email Scraper](https://apify.com/leads-scraper/soundcloud-email-scraper) | Public contact emails from SoundCloud | | [Substack Email Scraper](https://apify.com/leads-scraper/substack-email-scraper) | Public contact emails from Substack | | [Telegram Email Scraper](https://apify.com/leads-scraper/telegram-email-scraper) | Public contact emails from Telegram | | [Threads Email Scraper](https://apify.com/leads-scraper/threads-email-scraper) | Public contact emails from Threads | | [TikTok Email Scraper](https://apify.com/leads-scraper/tiktok-email-scraper) | Public contact emails from TikTok | | [Tinder Email Scraper](https://apify.com/leads-scraper/tinder-email-scraper) | Public contact emails from Tinder | | [Tumblr Email Scraper](https://apify.com/leads-scraper/tumblr-email-scraper) | Public contact emails from Tumblr | | [Twitch Email Scraper](https://apify.com/leads-scraper/twitch-email-scraper) | Public contact emails from Twitch | | [Vimeo Email Scraper](https://apify.com/leads-scraper/vimeo-email-scraper) | Public contact emails from Vimeo | | [VK Email Scraper](https://apify.com/leads-scraper/vk-email-scraper) | Public contact emails from VK | | [WeChat Email Scraper](https://apify.com/leads-scraper/wechat-email-scraper) | Public contact emails from WeChat | | [X Email Scraper](https://apify.com/leads-scraper/x-email-scraper) | Public contact emails from X | ### Example Run A realistic Weibo Email Scraper input for beauty-category KOL sourcing: ```json { "keywords": ["美妆博主", "护肤", "brand"], "location": "上海", "customDomains": ["@qq.com", "@163.com", "@sina.com", "@foxmail.com"], "maxEmails": 250, "countryCode": "HK", "expandQueries": true, "queryModifiers": ["email", "contact", "business", "cooperation"], "maxPagesPerQuery": 30, "maxConcurrency": 5 } ``` One dataset item from that run: ```json { "network": "Weibo", "keyword": "美妆博主", "query": "site:weibo.com OR site:weibo.cn 美妆博主 cooperation \"@qq.com\" \"上海\"", "title": "小鹿美妆日记 (@xiaolu_beauty) 的微博_微博", "accountName": "xiaolu_beauty", "fullName": "小鹿美妆日记", "username": "xiaolu_beauty", "profileUrl": "https://weibo.com/xiaolu_beauty", "url": "https://weibo.com/xiaolu_beauty", "description": "上海美妆博主 / 护肤测评。商务合作请联系 xiaolu.pr@qq.com", "email": "xiaolu.pr@qq.com", "emailDomain": "@qq.com", "possiblyTruncated": false, "foundAt": "2025-03-14T09:41:22Z" } ``` Every row the Weibo Email Scraper writes contains all fourteen fields, so the JSON shape is stable and safe to map into a database schema. Leads are pushed as they are found, so you can start reviewing the dataset while the Weibo Email Scraper is still running. ### Weibo Email Scraper FAQ #### What is the Weibo Email Scraper? An Apify Actor that extracts publicly indexed contact emails from Sina Weibo search results and returns them as a structured dataset. #### Does the Weibo Email Scraper log into Weibo? No. It never opens weibo.com, never authenticates and never uses Weibo's API. All data comes from Google search results. #### Can it scrape private Weibo accounts or hidden emails? No. If an address is not publicly visible in Google's index, the Weibo Email Scraper cannot find it. #### Which email domains work best for Weibo? `@qq.com`, `@163.com`, `@126.com`, `@sina.com`, `@sina.cn` and `@foxmail.com` are the highest-yield choices for mainland Chinese accounts. #### Do Chinese-language keywords work? Yes. Keywords are inserted into the Google query as written, so `美妆` and `商务合作` behave exactly like English terms. #### Does it handle the full-width `＠` used in Chinese posts? Yes. Full-width at signs, zero-width characters and `[at]` style obfuscation are all normalised before matching. #### Why do I get fewer results than from a Western platform? Google's index of Weibo is much thinner than its index of Facebook or Instagram. That is the main constraint on volume, and no scraper can add pages Google never crawled. #### What does `possiblyTruncated` mean? Google's snippet ellipsis may have clipped the email. Verify those rows before sending. #### Why are some `username` and `profileUrl` values empty? Google sometimes prints only a Chinese display name with no handle. The Weibo Email Scraper fills those fields when a handle is exposed and leaves them empty otherwise. #### Does the Weibo Email Scraper need a proxy? Yes. It requires the Apify `GOOGLE_SERP` proxy and cannot run without Apify proxy credentials. #### How many emails can I collect per run? Free Apify plans are capped at 100 emails per run. Paid plans are uncapped, up to the `maxEmails` value you set (maximum 10000). #### Can I run the Weibo Email Scraper on a schedule? Yes. Use Apify Schedules or the API. Runs are resumable and state is checkpointed in the key-value store. #### What export formats are supported? The Weibo Email Scraper writes to a standard Apify dataset, which exports to JSON, CSV, Excel, XML and HTML. #### Is the Weibo Email Scraper affiliated with Sina Weibo? No. It is an independent Apify Actor with no affiliation with or endorsement from Weibo. ### Leave a review If the Weibo 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. ### Support Questions, feature requests or need a custom build? Email **neurodata.apify@gmail.com** and we will get back to you. # Actor input Schema ## `keywords` (type: `array`): Search terms describing the Weibo 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 Weibo. ## `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": [ "founder", "brand" ], "location": "", "customDomains": [ "@gmail.com", "@yahoo.com" ], "maxEmails": 20, "countryCode": "", "expandQueries": true, "queryModifiers": [ "email", "contact", "business", "cooperation" ], "maxPagesPerQuery": 30, "maxConcurrency": 5 } ``` # Actor output Schema ## `results` (type: `string`): Records produced by Weibo 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": [ "founder", "brand" ], "location": "", "customDomains": [ "@gmail.com", "@yahoo.com" ], "countryCode": "", "queryModifiers": [ "email", "contact", "business", "cooperation" ] }; // Run the Actor and wait for it to finish const run = await client.actor("leads-scraper/weibo-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": [ "founder", "brand", ], "location": "", "customDomains": [ "@gmail.com", "@yahoo.com", ], "countryCode": "", "queryModifiers": [ "email", "contact", "business", "cooperation", ], } # Run the Actor and wait for it to finish run = client.actor("leads-scraper/weibo-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": [ "founder", "brand" ], "location": "", "customDomains": [ "@gmail.com", "@yahoo.com" ], "countryCode": "", "queryModifiers": [ "email", "contact", "business", "cooperation" ] }' | apify call leads-scraper/weibo-email-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,leads-scraper/weibo-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/1Ui15QcvVFVD299b9/builds/p6MnTXY2JlRsSAR4w/openapi.json