# Shopee Email Scraper (`scraperoka/shopee-email-scraper`) Actor 📧 Shopee Email Scraper extracts seller emails from Shopee listings with precision and speed. Automate lead generation for outreach, B2B sales, and marketing. ✅ Save time, enhance targeting, and boost conversions. - **URL**: https://apify.com/scraperoka/shopee-email-scraper.md - **Developed by:** [Scraperoka](https://apify.com/scraperoka) (community) - **Categories:** Lead generation, E-commerce, Automation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $1.99 / 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. Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are a software tools running on the Apify platform, for all kinds of web data extraction and automation use cases. 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. Actors are written with capital "A". ## 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. The best way to integrate Actors is as follows. In JavaScript/TypeScript projects, use official [JavaScript/TypeScript client](https://docs.apify.com/api/client/js/docs.md): ```bash npm install apify-client ``` In Python projects, use official [Python client library](https://docs.apify.com/api/client/python/docs.md): ```bash pip install apify-client ``` In shell scripts, use [Apify CLI](https://docs.apify.com/cli/docs.md): ````bash # MacOS / Linux curl -fsSL https://apify.com/install-cli.sh | bash # Windows irm https://apify.com/install-cli.ps1 | iex ```bash In AI frameworks, you might use the [Apify MCP server](https://docs.apify.com/integrations/mcp.md). If your project is in a different language, use the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ### Shopee Email Scraper 🚀 Manually visiting hundreds of Shopee profiles to collect emails wastes hours you don’t have. **Shopee Email Scraper** automatically collects contact emails from Shopee bios using your chosen keywords and email-domain filters—perfect for marketers, recruiters, and growth teams. This **Shopee Email Scraper** (Shopee email scraper tool, Shopee email finder) helps you build outreach-ready lists with thousands of records in a single run. --- ### What You Get: Sample Output Here's a sample record from a single run: ```json { "network": "Shopee", "keyword": "founder", "title": "Official Store", "description": "Welcome to our shop! 📩 contact@mycompany.com | Fast response", "url": "https://shopee.co.id/seller/123456", "email": "contact@mycompany.com", "proxyGroups": ["RESIDENTIAL"] } ```` | Field | Type | What It Tells You | |---|---|---| | `network` | string | Confirms the source network used for the record (`Shopee`). | | `keyword` | string | The keyword that triggered this email finding (useful for reporting and segmenting). | | `title` | string | The title text captured alongside the result (helps you quickly understand context). | | `description` | string | The surrounding text where the email was detected (great for verification and notes). | | `url` | string | The source URL associated with the found email. | | `email` | string | The extracted contact email address that you can use for outreach. | | `proxyGroups` | array | The proxy configuration used for the run, shown in the output for traceability. | | `status` | n/a | Not included in the pushed dataset records by this actor code. | | `error_message` | n/a | Not included in the pushed dataset records by this actor code. | | `timestamp` | n/a | Not included in the pushed dataset records by this actor code. | Export your dataset as JSON, CSV, or Excel — straight from the Apify dashboard. *** ### Why Shopee Email Scraper? There are a lot of ways to pull data from Shopee — here’s what sets Shopee Email Scraper apart. #### Email extraction guided by your intent Shopee Email Scraper uses your input **keywords** and your **customDomains** (like `@gmail.com`) to focus on relevant contacts. It’s designed for Shopee email scraping software workflows that need outbound-ready data with fewer irrelevant results. #### Clean, structured, integration-ready results Each found email is pushed as a consistent JSON object with fields like `email`, `url`, `keyword`, and `description`. If you’re building a Shopee seller database email or a Shopee outreach email list, the output is ready to map into your CRM or spreadsheet. #### Deduplication and run resumption The actor keeps track of `seen_emails` and can resume from a saved cursor, so you avoid reprocessing the same contacts across runs. This makes it a practical Shopee bulk email scraper when you need reliability over multiple executions. #### Built-in resilience for long or large runs If runs encounter empty pages or temporary fetch failures, the actor includes fallback and stopping logic to keep processing safely. This helps when you scale Shopee email finder jobs beyond small test batches. *** ### Configuring Your Run Drop this into your `input.json` to get started: ```json { "keywords": ["founder", "marketing"], "location": "Indonesia", "platform": "Shopee", "customDomains": ["@gmail.com", "@company.com"], "maxEmails": 200, "proxyConfiguration": { "useApifyProxy": true } } ``` | Parameter | Required | What It Does | |---|---|---| | `keywords` | ✅ | A list of keywords to search for (for example, terms commonly found in bios). | | `location` | ⬜ | Location text to filter the results. Leave empty if you don’t need location narrowing. | | `platform` | ⬜ | Select platform. The only option in the schema is `Shopee`. | | `customDomains` | ⬜ | Email domains filter used during extraction (for example, `@gmail.com`). | | `maxEmails` | ⬜ | Maximum number of emails to collect. The actor stops once it reaches your limit (it may stop early if fewer matches are found). | | `proxyConfiguration` | ⬜ | Configure proxies for this Actor. | *** ### Core Capabilities #### Keyword-based targeting for Shopee bios Shopee Email Scraper is built to collect emails from Shopee bios and other text related to your keywords. Use focused terms to improve relevance when running a Shopee contact email extractor or Shopee product seller email extractor workflow. #### Domain filtering to reduce noise By supplying `customDomains`, you can constrain results to emails from the domains you care about (like `@gmail.com`). This is especially helpful when you want a targeted Shopee seller contact email scraper output instead of a broad list. #### Resumable processing for long lead-generation runs The actor stores progress (including a cursor and `seen_emails`) and resumes from where it left off. That makes it a strong choice for Shopee lead generation email scraper projects where results may take multiple runs. #### Resilience for sparse or inconsistent public web data If results are sparse, the actor stops pagination after consecutive pages yield no usable results, preventing endless runs. It also includes fallback behavior to help continue finding contacts under different proxy conditions. #### Real-time dataset writing as contacts are found As emails are discovered, they are pushed immediately to the Apify dataset. This means you can monitor progress and export partial results without waiting for the run to finish. Shopee Email Scraper turns publicly available Shopee contact signals into an outreach-ready dataset you can use right away. *** ### Who Gets the Most Out of This Here's how different teams put Shopee Email Scraper to work: **Lead generation and outreach teams** — They set up keywords that match how sellers describe themselves and filter by email domains to build a clean Shopee outreach email list. The outcome is fewer irrelevant contacts and a faster path from prospecting to first email. **Marketplace growth analysts** — They run multiple keyword/domain combinations and use the `keyword` and `email` fields to analyze which seller messaging patterns correlate with accessible contact emails. This supports data-driven decisions for campaigns and seller acquisition. **Sales Development Representatives** — They use Shopee email finder results to quickly compile a target set for cold outreach. With dataset exports, they can move the contacts into a CRM workflow without manual copying and pasting. **Freelance researchers** — They request targeted extracts (for example, specific email domains) to deliver contact datasets for client briefs and audits. The structured JSON output helps keep results consistent across projects. **Automation and data pipeline specialists** — They trigger Shopee Email Scraper via the Apify platform and pipe results into their systems. Because each pushed record includes key context like `url`, `title`, and `description`, they can automate enrichment and verification downstream. *** ### Step-by-Step: How to Use It No coding needed. Here's how to run Shopee Email Scraper from start to finish: 1. **Open the actor on Apify** — go to the Apify console and find **Shopee Email Scraper** at [console.apify.com](https://console.apify.com). 2. **Enter your inputs** — set `keywords` (required), and optionally add `location`, `customDomains`, and `maxEmails` in the input form. 3. **Configure proxy settings** — use the `proxyConfiguration` field if you want proxy support for more reliable scraping runs. 4. **Hit Run and watch the live log** — monitor progress while the actor collects emails and pushes results incrementally. 5. **View results in the dataset tab** — once records start appearing, you can inspect fields like `email`, `url`, and `description`. 6. **Export as JSON, CSV, or Excel** — download directly from the dataset to share with your team or load into your tools. The whole process takes under 5 minutes to set up. *** ### Integrations & Export Options Once your data is collected, Shopee Email Scraper plugs directly into your existing workflow. Export your dataset formats (JSON, CSV, Excel) from the Apify dashboard and import them into your CRM, spreadsheets, or analysis tools. If you’re using automation for Shopee email scraping software operations, you can connect the actor to downstream steps using Apify-native capabilities, Zapier or Make, and other webhook-based workflows. For programmatic access, trigger and retrieve results via the Apify API (see the official Apify API documentation at https://apify.com/docs/api). You can also schedule runs to keep your Shopee seller contact email extractor up to date on a recurring cadence. *** ### Pricing & Free Trial Shopee Email Scraper runs on the Apify platform, which offers a **free tier** — no credit card required to get started. In general, costs are based on Apify platform compute usage, and you can scale up when you move from testing keywords to running larger Shopee bulk email scraper jobs. Start for free at [apify.com](https://apify.com) and scale when you’re ready. *** ### Reliability & Performance | What We Handle | How | |---|---| | Sparse results | Stops when multiple consecutive pages return no usable results. | | Retries and fallback behavior | Includes resilience logic to continue when pages fail or yield no results. | | Proxy support | Built-in proxy support via `proxyConfiguration` to help keep runs reliable. | | Incremental dataset writing | Pushes data as it’s found, so you can export partial outputs. | | Run resumption | Saves progress (`cursor` and `seen_emails`) so reruns can continue from where they stopped. | | Scaling within limits | `maxEmails` lets you cap output size to control runtime and cost. | **Limitations:** This actor targets emails found in publicly available content related to Shopee profiles (such as bios). It can’t access private or login-gated pages, so availability and completeness depend on what sellers publish openly. For enterprise-scale runs, contact us to discuss custom configurations. *** ### Frequently Asked Questions #### Is there a free plan or trial? Yes. Apify provides a free tier so you can test Shopee Email Scraper with a limited budget before scaling up. #### Do I need to log in to Shopee to use this? No. The actor is designed to work with publicly available Shopee profile data, so no Shopee login is required from your side. #### How accurate is the data? Accuracy depends on what sellers publish publicly. Shopee Email Scraper extracts email addresses that appear in the publicly available text it processes and applies your `customDomains` filtering. #### How many results can I get per run? You control the maximum with `maxEmails`. The actor will stop when it reaches that limit, but it may also stop early if fewer matching emails are found in the available data. #### How often is the data updated / how fresh is it? Freshness depends on when you run the actor. Each run collects data at runtime from publicly available content and exports a dataset with the records found during that execution. #### Is this legal? Does it comply with GDPR / CCPA? Use depends on your compliance obligations. The actor works on **publicly available data**, but you are responsible for following GDPR, CCPA, applicable local regulations, and platform terms when using the collected emails for outreach. #### Can I export results to Google Sheets or Excel? Yes. You can download results directly from the Apify dataset in common formats, including JSON and CSV, which can be opened in Excel and imported into Google Sheets. #### Can I run this on a schedule automatically? Yes. You can schedule runs using Apify’s scheduling capabilities so your Shopee email finder jobs run automatically on a recurring basis. #### Can I access this via API? Yes. You can trigger and retrieve results using the Apify API. For details, refer to the official Apify API documentation at https://apify.com/docs/api. #### What happens if the actor hits an error? The actor is designed to write results incrementally as it finds them, and it also saves progress for resuming. If a run encounters persistent issues, you can re-run with adjusted keywords, domains, or run options. *** ### Need Help or Have a Request? Got a question about Shopee Email Scraper or want a new feature added? Reach out at . We’re happy to help with setup and we welcome ideas like batch CSV upload for keywords and webhook notifications on completion. This actor is actively maintained based on user feedback. *** ### Disclaimer & Responsible Use *Shopee Email Scraper is the fastest, most reliable way to extract Shopee seller contact emails from publicly available data — start your free run today.* This actor collects **publicly available data** and does not access private accounts, login-gated content, or password-protected pages. You’re responsible for using the output in compliance with GDPR, CCPA, applicable laws, and platform Terms of Service. For data removal requests, contact . Use responsibly, ethically, and only for lawful purposes. # Actor input Schema ## `keywords` (type: `array`): A list of keywords to search for. ## `location` (type: `string`): Location to filter search results. ## `platform` (type: `string`): Select platform. ## `customDomains` (type: `array`): List of custom email domains ## `maxEmails` (type: `integer`): Maximum number of emails to collect. The scraper will stop once this limit is reached. Setting a higher limit allows for more potential results but doesn't guarantee reaching that number. This helps save costs by controlling scraping time. ## `proxyConfiguration` (type: `object`): Configure proxies for this Actor. ## Actor input object example ```json { "keywords": [ "founder", "marketing" ], "location": "", "platform": "Shopee", "customDomains": [ "@gmail.com" ], "maxEmails": 20 } ``` # 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", "marketing" ], "location": "", "customDomains": [ "@gmail.com" ] }; // Run the Actor and wait for it to finish const run = await client.actor("scraperoka/shopee-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", "marketing", ], "location": "", "customDomains": ["@gmail.com"], } # Run the Actor and wait for it to finish run = client.actor("scraperoka/shopee-email-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).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", "marketing" ], "location": "", "customDomains": [ "@gmail.com" ] }' | apify call scraperoka/shopee-email-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=scraperoka/shopee-email-scraper", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "Shopee Email Scraper", "description": "📧 Shopee Email Scraper extracts seller emails from Shopee listings with precision and speed. Automate lead generation for outreach, B2B sales, and marketing. ✅ Save time, enhance targeting, and boost conversions.", "version": "0.0", "x-build-id": "FJnWywV2IObq9z4va" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/scraperoka~shopee-email-scraper/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-scraperoka-shopee-email-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } }, "/acts/scraperoka~shopee-email-scraper/runs": { "post": { "operationId": "runs-sync-scraperoka-shopee-email-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor and returns information about the initiated run in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/runsResponseSchema" } } } } } } }, "/acts/scraperoka~shopee-email-scraper/run-sync": { "post": { "operationId": "run-sync-scraperoka-shopee-email-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } } }, "components": { "schemas": { "inputSchema": { "type": "object", "required": [ "keywords" ], "properties": { "keywords": { "title": "Keywords", "type": "array", "description": "A list of keywords to search for.", "default": [ "founder", "marketing" ], "items": { "type": "string" } }, "location": { "title": "Location", "type": "string", "description": "Location to filter search results.", "default": "" }, "platform": { "title": "Platform", "enum": [ "Shopee" ], "type": "string", "description": "Select platform.", "default": "Shopee" }, "customDomains": { "title": "Custom Email Domains", "type": "array", "description": "List of custom email domains", "default": [ "@gmail.com" ], "items": { "type": "string" } }, "maxEmails": { "title": "Max Emails", "minimum": 1, "maximum": 10000, "type": "integer", "description": "Maximum number of emails to collect. The scraper will stop once this limit is reached. Setting a higher limit allows for more potential results but doesn't guarantee reaching that number. This helps save costs by controlling scraping time.", "default": 20 }, "proxyConfiguration": { "title": "Proxy Configuration", "type": "object", "description": "Configure proxies for this Actor." } } }, "runsResponseSchema": { "type": "object", "properties": { "data": { "type": "object", "properties": { "id": { "type": "string" }, "actId": { "type": "string" }, "userId": { "type": "string" }, "startedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "finishedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "status": { "type": "string", "example": "READY" }, "meta": { "type": "object", "properties": { "origin": { "type": "string", "example": "API" }, "userAgent": { "type": "string" } } }, "stats": { "type": "object", "properties": { "inputBodyLen": { "type": "integer", "example": 2000 }, "rebootCount": { "type": "integer", "example": 0 }, "restartCount": { "type": "integer", "example": 0 }, "resurrectCount": { "type": "integer", "example": 0 }, "computeUnits": { "type": "integer", "example": 0 } } }, "options": { "type": "object", "properties": { "build": { "type": "string", "example": "latest" }, "timeoutSecs": { "type": "integer", "example": 300 }, "memoryMbytes": { "type": "integer", "example": 1024 }, "diskMbytes": { "type": "integer", "example": 2048 } } }, "buildId": { "type": "string" }, "defaultKeyValueStoreId": { "type": "string" }, "defaultDatasetId": { "type": "string" }, "defaultRequestQueueId": { "type": "string" }, "buildNumber": { "type": "string", "example": "1.0.0" }, "containerUrl": { "type": "string" }, "usage": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "integer", "example": 1 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } }, "usageTotalUsd": { "type": "number", "example": 0.00005 }, "usageUsd": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "number", "example": 0.00005 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } } } } } } } } } ```