# Coupang Email Scraper (`neuro-scraper/coupang-email-scraper`) Actor

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

- **URL**: https://apify.com/neuro-scraper/coupang-email-scraper.md
- **Developed by:** [Neuro Scraper](https://apify.com/neuro-scraper) (community)
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.19 / 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

### Coupang Email Scraper

The Coupang Email Scraper collects publicly indexed contact emails connected to `coupang.com`, South Korea's dominant e-commerce platform.
It builds Google queries with the `site:coupang.com` operator, fetches them through the Apify GOOGLE_SERP proxy, and extracts emails from the result blocks.
No login, no browser, no Coupang API — only what Google has already published in its index.

**Start with the honest part.** Coupang exposes few indexable seller pages, so expect low volume.
Coupang is heavily app-first and first-party, its seller tooling lives behind the Wing seller console, and much of the site is not the kind of open, crawlable seller directory that Google indexes deeply.

That shapes what the Coupang Email Scraper realistically finds: supplier, brand and business contact details that happen to be published on Coupang's own indexable pages.
It does not find marketplace-seller inboxes at scale, because Coupang largely does not expose those publicly.
If you need volume from genuine third-party sellers, the [Allegro Email Scraper](https://apify.com/neuro-scraper/allegro-email-scraper) and [Cdiscount Email Scraper](https://apify.com/neuro-scraper/cdiscount-email-scraper) are structurally far more productive.

#### What one run of the Coupang Email Scraper produces

Each dataset row is one unique email plus whatever account context Google printed around it.
You get the raw title, an account label, a snippet, the exact query used and a truncation flag.
The Coupang Email Scraper pushes rows to the Apify dataset as they are found, so you can export CSV or JSON mid-run.

### Korean keywords and `countryCode` in the Coupang Email Scraper

This is the most important configuration section here, and the main lever you have over your results.
`coupang.com` is indexed overwhelmingly in Korean. The shipped defaults — `keywords` of `seller` and `brand`, with `email`, `contact`, `wholesale`, `customer service` and `inquiries` as modifiers — are English starting points, not the optimal configuration.

To search this platform properly, switch to Korean terms.
English queries against a Korean-language domain match a thin slice of the index and will usually return very little.

#### Korean keyword suggestions for the Coupang Email Scraper

| Korean term | Meaning | Use it for |
|---|---|---|
| `판매자` | seller | The direct equivalent of the default `seller` keyword |
| `브랜드` | brand | Brand and label pages |
| `업체` | company / vendor | Business-facing pages |
| `제조사` | manufacturer | Supplier and sourcing research |
| `도매` | wholesale | The Korean equivalent of the `wholesale` modifier |
| `문의` | inquiry | Contact-intent modifier |
| `고객센터` | customer service centre | Support and contact pages |
| `연락처` | contact details | Strong contact-intent modifier |

Combine a noun with an intent word — `판매자 문의`, `도매 연락처` — rather than searching a bare noun.
Keep one or two English terms in the mix as a control so you can compare which language actually returns rows for your niche.

#### Setting `countryCode` for the Coupang Email Scraper

Set `countryCode` to `KR`. This makes the Apify GOOGLE_SERP proxy search from a South Korean vantage point.
Google personalises heavily by country, and a Korean-country search is what surfaces `coupang.com` pages at all; a default or US search will bury them.

`countryCode: "KR"` plus Korean keywords is the pairing that gives the Coupang Email Scraper its best chance.
One caveat worth knowing: Google is not the dominant search engine in South Korea, so Google's index of Korean commercial pages is thinner than you might expect from other markets. The Coupang Email Scraper reads Google only.

#### Korean free-mail domains for `customDomains`

The default `customDomains` are `@gmail.com` and `@yahoo.com`.
Keep Gmail. Yahoo is effectively absent from the Korean market and should be replaced.

These local providers are worth testing. They are suggestions based on how the Korean market publishes contact details, not guarantees of volume:

| Domain | Why add it for Coupang |
|---|---|
| `@naver.com` | By far the most common personal and small-business mailbox in Korea |
| `@daum.net` | The other long-established Korean portal mail |
| `@hanmail.net` | Daum's legacy address, still in wide circulation |
| `@nate.com` | Another Korean portal provider |
| `@gmail.com` | Keep — widely used by Korean businesses that trade internationally |

Each extra domain multiplies the query count, because the Coupang Email Scraper searches every keyword against every domain.
Given the low expected yield, prefer a tight set — `@naver.com`, `@daum.net`, `@gmail.com` — over a wide sweep.

### Coupang Email Scraper features

Everything listed below is implemented in the Coupang Email Scraper today.

| Feature | What it means in practice |
|---|---|
| Query expansion | Base, quoted, `intitle:` and one variant per modifier; base queries run first |
| Global deduplication | An email found by several queries is stored exactly once |
| Email normalisation | Understands `name [at] domain [dot] com`, `name (at) domain`, `name @ domain`, `domain .com`, zero-width characters and the 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 | Drops a hit that is only the tail of another email in the same block |
| Structural parsing | Finds the `<h3>` and the smallest surrounding block, so it does not depend on Google's CSS class names |
| Whole-page fallback | If Google's markup changes, the run degrades to "emails without account details" rather than "no emails" |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried, not counted as empty |
| Retries | Up to 3 attempts per page with exponential backoff and a fresh proxy session per request |
| Failed-query requeue | Blocked or failed queries are re-queued once at the end of the run |
| Concurrency | An `asyncio` worker pool with a shared stop signal on `maxEmails` |
| Resumable state | Key-value store state keyed by an input hash; saves on `PERSIST_STATE`, `MIGRATING` and `ABORTING` |
| Run summary | Logs pages fetched, blocked pages, retries and emails per page |

### How the Coupang Email Scraper works

The Coupang Email Scraper runs the same six steps on every query it builds.

1. It reads your input: keywords, location, email domains and limits.
2. It builds Google queries with the `site:` operator against `coupang.com`, for example `site:coupang.com 판매자 "@naver.com" 문의`.
3. It fetches result pages through the Apify GOOGLE_SERP proxy using async `aiohttp` requests.
4. It parses each result block structurally rather than by CSS class name.
5. It extracts emails with a domain-filtered regex and normalises obfuscated forms.
6. It deduplicates globally and pushes each lead to the dataset immediately.

There is no browser, no JavaScript rendering, no authentication and no cookies.
The Coupang Email Scraper never signs into Coupang and never requests pages from Coupang's own servers.
Everything it returns was already public in Google's search index.

### Coupang Email Scraper input fields

These are the exact input fields the Coupang Email Scraper accepts, with the defaults it ships with.

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["seller","brand"]` | Search terms describing the accounts you want |
| `location` | string | `""` | Optional location phrase added to every query |
| `customDomains` | array | `["@gmail.com","@yahoo.com"]` | Only emails on these domains are kept; `@` optional |
| `maxEmails` | integer 1-10000 | `20` | Stop after this many unique emails |
| `countryCode` | string | `""` | Two-letter country for the search proxy — set `KR` here |
| `expandQueries` | boolean | `true` | Search each keyword x domain 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` | Parallel queries |

#### Example Coupang Email Scraper input

```json
{
  "keywords": ["판매자", "브랜드", "제조사"],
  "location": "서울",
  "customDomains": ["@naver.com", "@daum.net", "@gmail.com"],
  "maxEmails": 100,
  "countryCode": "KR",
  "expandQueries": true,
  "queryModifiers": ["email", "문의", "도매", "고객센터", "연락처"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

The `location` field simply appends a phrase to every query.
Korean city names work as values — `서울`, `부산`, `인천` — or their romanisations, `Seoul`, `Busan`.
On a low-yield platform this narrows an already narrow result set, so leave it empty unless you specifically need regional segmentation.

### Coupang Email Scraper output fields

Every dataset item the Coupang Email Scraper writes carries all fourteen of these 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 |
| `fullName` | Display name parsed from a profile-style title; empty for post captions |
| `username` | URL-safe handle when the platform 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 snippet text, cleaned of labels and engagement counters |
| `email` | Lower-cased email address |
| `emailDomain` | The matched domain |
| `possiblyTruncated` | `true` when Google's snippet ellipsis touched the email |
| `foundAt` | ISO 8601 UTC timestamp |

#### Example Coupang Email Scraper output

```json
[
  {
    "network": "Coupang",
    "keyword": "판매자",
    "query": "site:coupang.com 판매자 \"@naver.com\" 문의",
    "title": "한빛리빙 - 쿠팡 상품 페이지",
    "accountName": "한빛리빙",
    "fullName": "한빛리빙",
    "username": "1234567890",
    "profileUrl": "https://www.coupang.com/vp/products/1234567890",
    "url": "https://www.coupang.com/vp/products/1234567890",
    "description": "생활용품 판매자. 문의: hanbit.living@naver.com",
    "email": "hanbit.living@naver.com",
    "emailDomain": "@naver.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T13:11:29Z"
  },
  {
    "network": "Coupang",
    "keyword": "도매",
    "query": "site:coupang.com 도매 \"@daum.net\" 연락처",
    "title": "도매 문의 안내 - 쿠팡",
    "accountName": "도매 문의 안내",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "",
    "description": "대량 구매 문의: wholesale.example@daum.net",
    "email": "wholesale.example@daum.net",
    "emailDomain": "@daum.net",
    "possiblyTruncated": true,
    "foundAt": "2026-08-31T13:12:50Z"
  }
]
```

Note the second row: `username` is `null` and `profileUrl` is empty, because Google printed an informational page title with no product or seller identifier to build a URL from.
Note also the shape of the first row's `profileUrl`. On Coupang the canonical link the Coupang Email Scraper can construct is a product URL, `https://www.coupang.com/vp/products/{id}`, not a standalone seller storefront — because Coupang does not generally expose one.

#### What a measured Coupang Email Scraper run looked like

In an internal test run against `coupang.com`, only 3 of 10 rows carried a usable account identity in `accountName` or `fullName`.
That is the weakest identity rate of the five regional marketplace Actors in this family, and it is a direct consequence of Coupang exposing few indexable seller pages.

Most rows will give you an email and a query, with thin account context around it.
Plan your enrichment accordingly: expect to match on the email itself rather than on a seller name.

### Use cases for the Coupang Email Scraper

Here is where the Coupang Email Scraper fits into real prospecting and research workflows.

| Use case | How to configure it |
|---|---|
| Korean supplier sourcing | `keywords: ["제조사","도매"]`, `countryCode: "KR"`, `customDomains: ["@naver.com","@gmail.com"]` |
| Brand contact discovery | `keywords: ["브랜드","업체"]` with the `연락처` and `문의` modifiers |
| Filling gaps in an existing KR list | Match on `email` rather than `accountName`, given the low identity rate |
| Cross-border trade research | Combine `@gmail.com` with Korean keywords to find export-oriented businesses |
| Market research | Analyse `query` and `keyword` to see which Korean phrasings surface public contacts |
| Language A/B testing | Run English defaults and Korean keywords separately and compare row counts |
| Cross-market enrichment | Run beside the Rakuten, Shopee and Lazada Actors for a wider APAC picture |
| Data-quality benchmarking | Compare yield here against a European marketplace to calibrate expectations |

### Practical Coupang Email Scraper recipes

**Korean baseline.** Korean keywords, Korean modifiers, `countryCode: "KR"`, `maxEmails: 50`.
This is the configuration most likely to return anything at all.

**English control run.** Shipped defaults, `countryCode: "KR"`, same `maxEmails`.
Comparing the two runs shows you empirically how much the language switch is worth for your niche.

**Domain sweep.** Run `@naver.com`, `@daum.net` and `@gmail.com` as three separate runs.
On a low-yield platform, per-domain visibility is more useful than one merged number.

**Widen before you deepen.** More Korean keyword variants beat more pages per query here.
Raise `maxPagesPerQuery` last, once you have confirmed a keyword returns Coupang pages at all.

### Responsible use, PIPA and GDPR

South Korea's Personal Information Protection Act (PIPA) is one of the stricter privacy regimes in Asia, and it applies to personal data you collect about Korean individuals.
If you are established in the EU or targeting EU residents as part of the same campaign, the GDPR applies too.

An email that identifies a natural person is personal data even when it was published publicly.
Public availability is not consent to send, and PIPA is notably firm on unsolicited commercial messaging.

Practical steps that keep a Coupang Email Scraper workflow defensible:

- Strongly prefer role addresses (`info@`, `sales@`, `문의` inboxes) over addresses naming an individual.
- Keep provenance for every lead — the `query`, `url` and `foundAt` fields exist for exactly this.
- Give a clear sender identity, a stated purpose and a working opt-out in every message.
- Honour opt-outs immediately and check suppression lists before each follow-up.
- Delete data you are not actively using rather than warehousing scraped lists.
- Take Korean legal advice on PIPA before running commercial outreach into that market at scale.

This is operational guidance, not legal advice.

### Related Actors

The Coupang Email Scraper is part of an E-commerce and Marketplaces family that all share this engine.
For a broader Asian sweep, pair it with the [Rakuten Email Scraper](https://apify.com/neuro-scraper/rakuten-email-scraper) for Japan, the [Shopee Email Scraper](https://apify.com/leads-scraper/shopee-email-scraper) for Southeast Asia and the [Taobao Email Scraper](https://apify.com/leads-scraper/taobao-email-scraper) for China.
For markets where third-party seller pages are genuinely indexed, the [Allegro Email Scraper](https://apify.com/neuro-scraper/allegro-email-scraper) and [Cdiscount Email Scraper](https://apify.com/neuro-scraper/cdiscount-email-scraper) return considerably more.

| Actor | What it collects |
|---|---|
| [Coupang Email and Phone Number Scraper](https://apify.com/neuro-scraper/coupang-email-and-phone-number-scraper) | Emails and phone numbers from Coupang |
| [Coupang Phone Number Scraper](https://apify.com/neuro-scraper/coupang-phone-number-scraper) | Public phone numbers from Coupang |
| [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 |
| [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 |
| [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 |

### Coupang Email Scraper limitations

Read these before planning anything around the output.

- **Coupang exposes few indexable seller pages, so expect low volume.** This is the defining limitation of the Coupang Email Scraper and the reason every recommendation above is conservative.
- **Weak account identity.** In an internal test run only 3 of 10 rows carried a usable `accountName` or `fullName`. Expect emails with thin context.
- **Publicly indexed emails only.** The Coupang Email Scraper finds addresses already visible in Google's index. Anything behind the Wing seller console or an in-app contact flow is unreachable.
- **Google's ~300-result cap.** A single query returns roughly 300 results at most, which is why `expandQueries` defaults to `true`.
- **`possiblyTruncated`.** When `true`, Google's snippet ellipsis touched the email and it may be cut off. Verify before sending.
- **`username` and `profileUrl` are frequently empty.** Where they are populated, the link is a product URL rather than a seller storefront, because Coupang does not generally expose one. That is a Google and platform limitation, not a bug.
- **Apify GOOGLE_SERP proxy required.** The Coupang 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, location and Google's index on the day.
- **Not affiliated with Coupang.** This is an independent tool, not supported, endorsed by or connected to Coupang.

### Coupang Email Scraper FAQ

Common questions about the Coupang Email Scraper, its inputs and its output.

#### How many results should I expect from the Coupang Email Scraper?

Few. Coupang exposes few indexable seller pages, so expect low volume, and in an internal test only 3 of 10 rows carried a usable account identity. Treat it as a supplementary source rather than a primary lead engine.

#### Why is the yield lower than on European marketplaces?

Coupang is app-first and heavily first-party, its seller tools sit behind a login, and Google is not the dominant search engine in South Korea. Fewer public seller pages are indexed, so there is less for the Coupang Email Scraper to read.

#### Does the Coupang Email Scraper log into Coupang?

No. It never logs in, never calls a Coupang API and never opens coupang.com in a browser. It reads Google results through the Apify GOOGLE_SERP proxy.

#### Should I use Korean or English keywords?

Korean. Try `판매자`, `브랜드`, `제조사` and `도매` with `문의` and `연락처` as modifiers. The shipped English defaults are a starting point, not the best configuration for a Korean-language domain.

#### What should I set `countryCode` to?

`KR`. Google personalises results by country, and a Korean vantage point is what surfaces `coupang.com` pages at all.

#### Which email domains work best for Coupang?

Start with `@naver.com`, `@daum.net` and `@gmail.com`. `@hanmail.net` and `@nate.com` are worth testing. These are suggestions based on Korean market habits, not guarantees.

#### Whose emails am I actually finding?

Mostly supplier, brand and business contacts that happen to appear on Coupang's indexable pages — not marketplace-seller inboxes at scale. Set expectations accordingly.

#### Why is `profileUrl` a product link rather than a store link?

Because Coupang does not generally expose a public seller storefront URL. When a handle is available, the canonical link the Coupang Email Scraper can build is `https://www.coupang.com/vp/products/{id}`.

#### Does the Coupang Email Scraper verify deliverability?

No. It extracts and normalises what Google indexed. Check rows flagged `possiblyTruncated` before using them.

#### Can I resume an interrupted run?

Yes. State lives in the key-value store keyed by a hash of your input, with saves on Apify's `PERSIST_STATE`, `MIGRATING` and `ABORTING` events.

#### What happens when Google blocks a request?

Block, CAPTCHA and consent pages are detected rather than treated as empty. Pages get up to three attempts with exponential backoff, and failed queries are re-queued once at the end of the run.

#### Is scraping Coupang contact emails legal?

The Coupang Email Scraper only reads publicly indexed Google results. Whether you may then contact those addresses is a separate PIPA — and possibly GDPR — question. See the responsible use section and take your own legal advice.

### Leave a review

If the Coupang 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, a bug, or you need a custom build of the Coupang Email Scraper? Contact **<neurodata.apify@gmail.com>**.

# Actor input Schema

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

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

## `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",
    "brand"
  ],
  "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 Coupang 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",
        "brand"
    ],
    "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("neuro-scraper/coupang-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",
        "brand",
    ],
    "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("neuro-scraper/coupang-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",
    "brand"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "wholesale",
    "customer service",
    "inquiries"
  ]
}' |
apify call neuro-scraper/coupang-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,neuro-scraper/coupang-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/0xZoufQO73rd7QgGc/builds/NAFb4EP3seF1uYdVk/openapi.json
