# Shopee Email Scraper (`leads-scraper/shopee-email-scraper`) Actor

Shopee Email Scraper SD - Shopee Email Scraper is a lead generation tool that extracts leads with public contact emails, account names and profile URLs from Shopee results by keyword, location and email domain - Shopee email extractor.

- **URL**: https://apify.com/leads-scraper/shopee-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

### Shopee Email Scraper — seller contacts from six Shopee regional marketplaces

The **Shopee Email Scraper** builds a dataset of publicly indexed contact emails belonging to Shopee sellers and shops across Southeast Asia and Taiwan.
You supply keywords and email domains; it returns emails, shop names, usernames, Shopee profile URLs and the snippet each address came from.

Shopee has no public seller directory and no export button, so a Shopee seller contact list normally has to be assembled by hand.
The Shopee Email Scraper closes that gap using nothing but publicly indexed Google results.

Marketplace addresses of this kind are almost always business mailboxes — customer service, wholesale enquiries, order support — published so that buyers and trade partners can write in.
That is the population this Shopee seller email extractor is designed to surface, and it is the reason the default query modifiers lean commercial.

#### What the Shopee Email Scraper does and does not do

The Shopee Email Scraper composes Google queries with the `site:` operator against six Shopee domains, fetches the result pages, and pulls emails out of the titles and snippets.
Every unique address is deduplicated and pushed straight into an Apify dataset the moment it is found.

The Shopee Email Scraper does **not** log into Shopee, use any Shopee API, or open shopee.sg in a browser.
There is no JavaScript rendering, no authentication and no cookies — only what Google has already indexed publicly.

It is an independent tool. It is not affiliated with, supported by or endorsed by Shopee.

#### Who uses this Shopee seller contact tool

Wholesale buyers and importers run the Shopee Email Scraper to find shops already selling a category they want to supply.
Dropshippers use it in reverse — to reach the shops behind products they intend to resell.

Brand-protection teams collect Shopee seller contacts before sending a takedown or authorisation request.
Marketplace agencies build prospect lists of Shopee sellers who might need account management, advertising or logistics help.

Cross-border sourcing teams often pair regional marketplaces: the [Lazada Email Scraper](https://apify.com/neuro-scraper/lazada-email-scraper) covers much of the same Southeast Asian merchant base from a second angle.

### Key features of the Shopee Email Scraper

Everything in this table is behaviour the Shopee Email Scraper genuinely implements.

| Feature | What it means in practice |
|---|---|
| Six-domain `site:` scoping | Queries are locked to `shopee.com`, `shopee.sg`, `shopee.ph`, `shopee.co.id`, `shopee.com.my` and `shopee.tw` |
| Query expansion | Each keyword × domain pair runs as a base query, a quoted query, an `intitle:` query, plus one variant per query modifier |
| Domain-filtered extraction | Only emails on the domains you list are kept, so you control the shape of the output |
| Global deduplication | An address appears once per run no matter how many queries or pages surfaced it |
| Obfuscation handling | Reads `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, `domain .com`, zero-width characters and the full-width `＠` |
| Junk filter | Discards placeholders such as `email@`, `yourname@`, `test@`, `xxx@` and single-character locals |
| Boundary-correct matching | `@gmail.com` does not match inside `@gmail.company` or `@gmail.com.br` |
| Soft-wrap repair | Drops a hit that is only the tail of another email in the same result block |
| Structural parsing | Locates the `<h3>` title and the smallest surrounding block instead of trusting Google's CSS class names |
| Whole-page fallback | A Google layout change degrades to "emails without account details", not "no emails" |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried rather than counted as empty |
| Retries with backoff | Up to 3 attempts per page, exponential backoff, a fresh proxy session per request |
| End-of-run requeue | Blocked or failed queries get one more pass before the run finishes |
| Resumable state | Progress lives in the key-value store keyed by an input hash, saved on `PERSIST_STATE`, `MIGRATING` and `ABORTING` |
| Async concurrency | An `asyncio` worker pool with a shared stop signal once `maxEmails` is reached |
| Run summary | Pages fetched, blocked pages, retries and emails per page are all logged |

### How the Shopee Email Scraper works

Six steps, start to finish.

1. The Shopee Email Scraper reads your input: keywords, location, email domains and limits.
2. It composes Google queries with the `site:` operator, for example `site:shopee.sg seller wholesale "@gmail.com"`.
3. It fetches the result pages through the Apify **GOOGLE\_SERP** proxy using async `aiohttp`.
4. It parses each result block structurally, finding the `<h3>` title and the tightest block around it.
5. It extracts emails from that block text with a domain-filtered regex.
6. It deduplicates globally and pushes each lead into the dataset immediately.

#### Regional coverage: why `countryCode` is a real lever here

Shopee is not one marketplace but a family of national storefronts, and the Shopee Email Scraper searches all six indexed domains.
Singapore, the Philippines, Indonesia, Malaysia and Taiwan each have their own seller population, their own shop-naming habits and their own trade vocabulary.

Set `countryCode` to `SG`, `PH`, `ID`, `MY` or `TW` and the search proxy resolves Google's index from that country.
The same keyword can return a visibly different Shopee seller list depending on which country you point it at.

Non-English keywords matter just as much. `penjual` and `toko grosir` reach Indonesian shops that `seller` never touches, and `pembekal` or `borong` do the same for Malaysia.
Adding a `location` phrase such as `Jakarta` or `Cebu` narrows a Shopee shop email search further still.

#### Beating Google's per-query ceiling

Google returns roughly 300 results for any single query, however many Shopee shops actually match.
Shopee's seller base is far larger than that, so one query can never see the whole marketplace.

Query expansion is the answer.
The Shopee Email Scraper turns each keyword into several phrasings and pairs it with each modifier, so a swarm of narrow queries covers ground a single broad query cannot.

### Input settings for the Shopee Email Scraper

Nine fields drive the Shopee Email Scraper. Only `keywords` is required; every other field ships with a working default.

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["seller", "shop"]` | Search terms describing the Shopee accounts you want (niche, job title, industry) |
| `location` | string | `""` | Optional location phrase added to every query |
| `customDomains` | array | `["@gmail.com","@yahoo.com"]` | Only emails on these domains are collected; the leading `@` is optional |
| `maxEmails` | integer 1–10000 | `20` | Stop once this many unique emails have been collected |
| `countryCode` | string | `""` | Two-letter country code for the search proxy (US, GB, DE...) |
| `expandQueries` | boolean | `true` | Search each keyword × domain pair in several phrasings |
| `queryModifiers` | array | `["email","contact","wholesale","customer service","inquiries"]` | 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 |

#### Example input for a Shopee seller email run

```json
{
  "keywords": ["seller", "shop", "toko grosir", "penjual"],
  "location": "Jakarta",
  "customDomains": ["@gmail.com", "@yahoo.com"],
  "maxEmails": 300,
  "countryCode": "ID",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "wholesale", "customer service", "inquiries"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

Start a new keyword set at `maxEmails` of 20–50.
A short Shopee Email Scraper probe tells you whether the niche is well indexed before you spend compute on a long run.

### Output fields from the Shopee Email Scraper

Every dataset item the Shopee Email Scraper writes carries all fourteen fields. The keys are always present; some values are conditional.

| 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 (shop handle or display name) |
| `fullName` | Display name parsed from a profile-style title; empty for listing-style results |
| `username` | URL-safe handle when the platform exposes one; otherwise `null` |
| `profileUrl` | Canonical shop URL when a handle is known; otherwise empty |
| `url` | Direct platform link when exposed, else the profile URL |
| `description` | Bio or snippet text, cleaned of labels and engagement 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 |

#### Example output rows

```json
[
  {
    "network": "Shopee",
    "keyword": "shop",
    "query": "site:shopee.sg shop wholesale \"@gmail.com\"",
    "title": "brighthome.sg | Shopee Singapore",
    "accountName": "brighthome.sg",
    "fullName": "Bright Home Living",
    "username": "brighthome.sg",
    "profileUrl": "https://shopee.sg/brighthome.sg",
    "url": "https://shopee.sg/brighthome.sg",
    "description": "Home and living essentials shipped from Singapore. Wholesale enquiries: brighthome.sg@gmail.com",
    "email": "brighthome.sg@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2025-06-12T08:41:07Z"
  },
  {
    "network": "Shopee",
    "keyword": "penjual",
    "query": "site:shopee.co.id penjual contact \"@gmail.com\"",
    "title": "tokosarana.id | Shopee Indonesia",
    "accountName": "tokosarana.id",
    "fullName": "Toko Sarana Grosir",
    "username": "tokosarana.id",
    "profileUrl": "https://shopee.co.id/tokosarana.id",
    "url": "https://shopee.co.id/tokosarana.id",
    "description": "Grosir peralatan rumah tangga. Kontak: tokosarana.grosir@gmail.com",
    "email": "tokosarana.grosir@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2025-06-12T08:44:22Z"
  }
]
```

Export what the Shopee Email Scraper collects as CSV, JSON, Excel or XML, or read it through the Apify API straight into your CRM.

### Use cases for the Shopee Email Scraper

Shopee is a seller marketplace, so these use cases sit in sourcing, trade and marketplace operations rather than consumer prospecting.

| Use case | How the Shopee Email Scraper helps |
|---|---|
| Wholesale supplier sourcing | Find Shopee shops already trading in your category and reach the address they publish for wholesale enquiries |
| Dropshipping supplier outreach | Build a Shopee seller contact list for products you want to resell |
| Brand protection | Collect Shopee seller emails before an authorisation, takedown or grey-market enquiry |
| Marketplace agency prospecting | Prospect Shopee sellers who may need ads, listings or account management |
| Logistics and fulfilment sales | Reach cross-border shops that ship between SEA markets |
| Category and competitor research | Sample a Shopee niche by keyword to see how crowded it is and who is in it |
| Regional market entry | Compare seller density across Singapore, Malaysia, the Philippines, Indonesia and Taiwan |
| CRM enrichment | Match scraped Shopee shop emails against merchants you already track |

#### Worked example: sourcing home and living suppliers across SG and MY

Set `keywords` to `["shop", "seller", "borong", "pembekal"]` and run the Shopee Email Scraper once with `countryCode: "SG"`.
Then repeat the identical input with `countryCode: "MY"` and compare the two datasets.

Leave `expandQueries` on so each keyword also runs with `email`, `contact`, `wholesale`, `customer service` and `inquiries`.
Keep `customDomains` at the free-mail defaults for owner-operated shops, or add a branded domain when you want larger merchants.

Probe at `maxEmails: 30` first.
The second Shopee Email Scraper run reuses the same expansion plan, so the cost of the probe is small.

### Tips for getting more from the Shopee Email Scraper

Category keywords beat generic ones.
"kitchen storage" or "hijab" is worth far more to the Shopee Email Scraper than "shop".

Write keywords in the local language of the market you are targeting.
Bahasa Indonesia, Malay, Filipino and Traditional Chinese terms reach shops that English keywords will never match.

Treat `customDomains` as a segmentation lever.
Free-mail domains skew towards small and owner-run Shopee shops; branded domains skew towards established merchants.

Do not raise `maxConcurrency` for its own sake.
More parallel queries will not make the Shopee Email Scraper find emails that are absent from the index — it only spends proxy budget faster.

Schedule the Shopee Email Scraper monthly on a stable input.
New shops get indexed continuously, so repeat runs keep a Shopee seller email list current.

If you sell into more than one region, run the [Flipkart Email Scraper](https://apify.com/leads-scraper/flipkart-email-scraper) and the [Coupang Email Scraper](https://apify.com/neuro-scraper/coupang-email-scraper) with equivalent keywords to extend the same sourcing motion into India and Korea.

#### Responsible use, GDPR and marketplace terms

The Shopee Email Scraper only collects addresses that are already public in Google's index, and most of them are business or customer-service mailboxes published for trade enquiries.
That does not make every use lawful by default.

GDPR, PDPA, CAN-SPAM and equivalent local rules still apply to how you store, contact and profile the people behind those addresses.
Shopee's own terms of service govern how you may interact with sellers on the platform.

Keep outreach relevant and commercial, honour opt-outs immediately, and do not use marketplace contact data for consumer spam.
Compliance is your responsibility, not the Actor's.

### Limitations of the Shopee Email Scraper

Stated plainly, because they affect what you should expect.

- **Publicly indexed emails only.** If a shop's address is not in Google's index, the Shopee Email Scraper cannot find it. Contact forms, in-app chat and images are invisible to it.
- **Google's ~300-result cap.** A single query tops out at roughly 300 results, which is exactly why query expansion exists.
- **`possiblyTruncated`.** When Google's snippet ellipsis touched the email, this flag is `true` and the address may be incomplete. Verify before sending.
- **`username` and `profileUrl` are conditional.** They are only populated when Google's result exposes a usable handle. Some rows will carry `accountName` and `fullName` with an empty `username` and `profileUrl`. That is a Google limitation, not a bug.
- **Apify GOOGLE\_SERP proxy required.** The Shopee Email Scraper cannot run without Apify proxy credentials.
- **Free-plan cap.** Free Apify plans stop at 100 emails per run; paid plans are uncapped.
- **No guaranteed volume.** Results vary with keywords, domains, country and location, and no volume is guaranteed.

In our own measured testing, a Shopee Email Scraper run resolved 10 of 10 targeted results into usable rows, all 10 carrying a shop handle and a working profile URL.
That is the strongest identity resolution in this marketplace family, but it describes that test, not your keywords.

### Related Actors

The Shopee Email Scraper shares its engine with the rest of this E-commerce & Marketplaces family; only the platform configuration differs.

| Actor | What it collects |
|---|---|
| [Shopee Email and Phone Number Scraper](https://apify.com/neuro-scraper/shopee-email-and-phone-number-scraper) | Emails and phone numbers from Shopee |
| [Shopee Phone Number Scraper](https://apify.com/neuro-scraper/shopee-phone-number-scraper) | Public phone numbers from Shopee |
| [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 |
| [Shopify Store Email Scraper](https://apify.com/leads-scraper/shopify-store-email-scraper) | Public contact emails from Shopify Store |
| [Taobao Email Scraper](https://apify.com/leads-scraper/taobao-email-scraper) | Public contact emails from Taobao |
| [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 |

### FAQ about the Shopee Email Scraper

#### Does the Shopee Email Scraper use the Shopee API?

No. It does not use any Shopee API, does not log in, and does not open the Shopee website. Every field comes from publicly indexed Google search results.

#### Is this Actor affiliated with or endorsed by Shopee?

No. It is an independent tool built on public Google results, and it is not officially supported by, affiliated with or endorsed by Shopee.

#### Which domains does the Shopee Email Scraper search?

Six: `shopee.com`, `shopee.sg`, `shopee.ph`, `shopee.co.id`, `shopee.com.my` and `shopee.tw`. Every query is scoped with Google's `site:` operator.

#### Can I restrict a run to one Shopee country?

You cannot switch off individual domains, but `countryCode` changes which country the search proxy resolves Google from, and local-language keywords plus a `location` phrase pull results strongly towards one market.

#### Whose emails does the Shopee Email Scraper actually find?

Mostly business mailboxes — customer service, wholesale enquiries and order support — that shops publish so buyers and trade partners can reach them.

#### Why does the Shopee Email Scraper leave `username` and `profileUrl` empty on some rows?

Those fields fill only when Google's result exposes a usable handle. When Google prints only a display name you still get `accountName` and `fullName`. This is a Google limitation, not a bug.

#### What does `possiblyTruncated: true` mean?

Google's snippet ellipsis touched the email, so the address may be cut off. Treat those rows as leads to verify rather than addresses to mail.

#### How many emails can one Shopee Email Scraper run return?

Free Apify plans stop at 100 emails per run. Paid plans are uncapped and bounded by `maxEmails`, which accepts 1 to 10000.

#### Do I need a proxy?

Yes. The Shopee Email Scraper requires the Apify GOOGLE\_SERP proxy and cannot run without Apify proxy credentials.

#### Why did I get fewer emails than `maxEmails`?

Google caps a single query at roughly 300 results, and only some shops publish an email that Google indexes. Widening `keywords` and `customDomains` usually helps more than raising `maxPagesPerQuery`.

#### Can a run be resumed after a migration?

Yes. Progress is stored in the key-value store keyed by a hash of your input, and saved on Apify's `PERSIST_STATE`, `MIGRATING` and `ABORTING` events.

#### Is this data compliant to use?

The Shopee Email Scraper only collects addresses already public in Google's index. How you store and use them — GDPR, PDPA, CAN-SPAM, local marketing rules and Shopee's own terms — remains your responsibility.

### Leave a review

If the Shopee 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 <neurodata.apify@gmail.com>
instead - bugs get fixed faster than they get complained about.

### Support

Questions, feature requests or a custom build? Email **neurodata.apify@gmail.com**.

# Actor input Schema

## `keywords` (type: `array`):

Search terms describing the Shopee 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 Shopee.

## `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": [
    "seller",
    "shop"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "wholesale",
    "customer service",
    "inquiries"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

## `results` (type: `string`):

Records produced by Shopee 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "seller",
        "shop"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "wholesale",
        "customer service",
        "inquiries"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leads-scraper/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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keywords": [
        "seller",
        "shop",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "wholesale",
        "customer service",
        "inquiries",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("leads-scraper/shopee-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": [
    "seller",
    "shop"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "wholesale",
    "customer service",
    "inquiries"
  ]
}' |
apify call leads-scraper/shopee-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,leads-scraper/shopee-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 <APIFY_API_TOKEN>` 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/Ls4qOMvafjruaJzhd/builds/JsT59aOqXMIajo5YY/openapi.json
