# ECPlaza Email Scraper (`neuro-scraper/ecplaza-email-scraper`) Actor

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

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

### ECPlaza Email Scraper: read this before you run it

The ECPlaza Email Scraper searches Google's public index of `ecplaza.net` for the contact emails that Korean and international suppliers publish on their pages.

Here is the honest headline. ECPlaza blocks most of its supplier pages from search engines, so this Actor often returns nothing; the Global Sources, TradeKey and Tradewheel Actors cover the same ground far better.

A measured live run of the ECPlaza Email Scraper returned zero results. Not a low yield, not a thin yield: zero blocks, zero identities, zero URLs, zero emails.

If you want working Asian supplier leads today, go straight to the [Global Sources Email Scraper](https://apify.com/leads-scraper/global-sources-email-scraper), the [TradeKey Email Scraper](https://apify.com/neuro-scraper/tradekey-email-scraper) or the [Tradewheel Email Scraper](https://apify.com/leads-scraper/tradewheel-email-scraper).

### Why the ECPlaza Email Scraper is still published

Search-engine indexing changes. A platform that blocks crawlers this quarter may open up next quarter, and the ECPlaza Email Scraper is ready for that day.

It also costs little to test. Run it with a small `maxEmails`, see whether anything comes back, and move on if not.

Some niches are indexed even when the bulk of the marketplace is not. Occasional pockets of ecplaza supplier contacts do surface for narrow product terms.

Treat the ECPlaza Email Scraper as a low-cost probe in a wider sourcing sweep, never as the backbone of a lead programme.

### What the ECPlaza Email Scraper actually does

The ECPlaza Email Scraper builds Google queries with the `site:` operator scoped to `ecplaza.net`, fetches result pages through the Apify GOOGLE_SERP proxy, and reads emails out of titles and snippets.

The ECPlaza Email Scraper does not log into ECPlaza, use its API, or open the website. No browser, no JavaScript rendering, no authentication, no cookies.

Because it depends entirely on Google's index, a platform that keeps its pages out of that index leaves the ECPlaza Email Scraper with nothing to read. That is precisely the situation here.

ECPlaza gives each supplier its own subdomain, in the form `suppliername.en.ecplaza.net`. When a page is indexed, that subdomain is the handle, so the ECPlaza Email Scraper can rebuild a canonical profile URL.

### ECPlaza Email Scraper features at a glance

| Feature | What it means when pages are indexed |
|---|---|
| Google `site:` search | Every query is scoped to `ecplaza.net`, so results stay on-platform |
| Query expansion | Base, quoted and `intitle:` variants plus one per query modifier; base queries run first |
| Global deduplication | Each email is pushed once across every query and every page of the run |
| Email normalisation | Handles `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, `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` never matches 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 block parsing | Locates the `<h3>` title then the smallest surrounding block, not Google CSS class names |
| Whole-page fallback parser | A Google markup change degrades to "emails without account details", not "no emails" |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried, never counted as empty |
| Retries and re-queue | Up to 3 attempts per page with exponential backoff and a fresh proxy session; failed queries re-queued once |
| Resumable state | Kept in the key-value store keyed by an input hash; saved on `PERSIST_STATE`, `MIGRATING` and `ABORTING` |
| Concurrency | An `asyncio` worker pool with a shared stop signal on `maxEmails` |
| Run summary | Logs pages fetched, blocked pages, retries and emails per page |

Note the block-detection row. It matters here because it lets you distinguish "Google blocked us" from "the platform is not indexed" in the ECPlaza Email Scraper run log.

### How the ECPlaza Email Scraper works, step by step

1. The ECPlaza Email Scraper reads your keywords, location, email domains and limits.
2. It composes Google queries such as `site:ecplaza.net supplier "@gmail.com" "Seoul"`.
3. It fetches result pages asynchronously through the Apify GOOGLE_SERP proxy using `aiohttp`.
4. It parses each result block structurally to isolate title, snippet and site label.
5. It extracts emails with a domain-filtered regex, normalises them and drops junk.
6. It deduplicates globally and pushes each lead to the Apify dataset immediately.

When the marketplace's pages are absent from the index, steps 4 to 6 have nothing to work on and the ECPlaza Email Scraper finishes with an empty dataset.

### ECPlaza Email Scraper input fields

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["exporter", "supplier"]` | Search terms: niche, product vertical, job title, industry |
| `location` | string | `""` | Optional location phrase added to every query |
| `customDomains` | array | `["@gmail.com", "@yahoo.com"]` | Only emails on these domains are kept; the leading `@` is optional |
| `maxEmails` | integer 1-10000 | `20` | Stop once this many unique emails have been collected |
| `countryCode` | string | `""` | Two-letter country for the search proxy (US, GB, DE...) |
| `expandQueries` | boolean | `true` | Search each keyword x domain pair in several phrasings |
| `queryModifiers` | array | `["email", "contact", "export", "wholesale", "sales enquiries"]` | 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 the ECPlaza Email Scraper

```json
{
  "keywords": [
    "cosmetics OEM exporter",
    "food packaging machinery supplier",
    "auto parts trading company"
  ],
  "location": "Seoul",
  "customDomains": ["@gmail.com", "@naver.com", "@daum.net", "@hanmail.net", "@hotmail.com"],
  "maxEmails": 50,
  "countryCode": "KR",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "export", "wholesale", "sales enquiries"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

Keep `maxEmails` low the first time you run the ECPlaza Email Scraper. There is no point paying for depth on a platform that may return an empty dataset.

Korean mailbox domains such as `@naver.com`, `@daum.net` and `@hanmail.net` are worth adding to the ECPlaza Email Scraper domain list. If anything is indexed at all, those are the addresses Korean sales staff publish.

### ECPlaza Email Scraper output fields

When the ECPlaza Email Scraper does return rows, every dataset item carries all fourteen fields below.

| 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 listing 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` | Company or listing snippet, cleaned of labels and counters |
| `email` | Lower-cased email address |
| `emailDomain` | The matched domain, for example `@naver.com` |
| `possiblyTruncated` | `true` when Google's snippet ellipsis touched the email |
| `foundAt` | ISO 8601 UTC timestamp |

#### Example output from the ECPlaza Email Scraper

```json
[
  {
    "network": "ECPlaza",
    "keyword": "cosmetics OEM exporter",
    "query": "site:ecplaza.net cosmetics OEM exporter \"@gmail.com\" \"Seoul\"",
    "title": "Hanbit Cosmetic Co., Ltd. - ECPlaza",
    "accountName": "Hanbit Cosmetic Co., Ltd.",
    "fullName": "Hanbit Cosmetic Co., Ltd.",
    "username": "hanbitcos",
    "profileUrl": "https://hanbitcos.en.ecplaza.net/",
    "url": "https://hanbitcos.en.ecplaza.net/",
    "description": "Skincare and mask sheet OEM/ODM. Export: hanbit.export@gmail.com",
    "email": "hanbit.export@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T16:22:10Z"
  },
  {
    "network": "ECPlaza",
    "keyword": "food packaging machinery supplier",
    "query": "site:ecplaza.net food packaging machinery supplier \"@naver.com\"",
    "title": "Vacuum Packaging Machine - Buy Food Packaging Machinery",
    "accountName": "Vacuum Packaging Machine",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "https://www.ecplaza.net/products/vacuum-packaging-machine",
    "description": "Vacuum packers for food lines. Contact: sales.vacpack@naver.com",
    "email": "sales.vacpack@naver.com",
    "emailDomain": "@naver.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T16:22:41Z"
  }
]
```

The second row shows the honest case: a listing page with an address but no company handle, so the ECPlaza Email Scraper leaves `username` as `null` and `profileUrl` empty.

### Who might use the ECPlaza Email Scraper

Given the yield, the realistic audience is people already running the other Actors in this family who want ECPlaza checked off as well.

| Buyer type | How the ECPlaza Email Scraper fits their workflow |
|---|---|
| Importers and wholesale buyers | A cheap extra probe when sweeping a category across every Asian marketplace |
| Procurement and sourcing agents | Coverage completeness in a supplier-discovery audit |
| Private-label and dropship brands | Occasional Korean cosmetics or food OEM contacts when a niche happens to be indexed |
| Freight forwarders and customs brokers | Marginal additional leads on Korea lanes already covered elsewhere |
| Trade-show organisers | A supplementary source when building an exhibitor prospect list |
| Quality-inspection firms | A completeness check alongside better-indexed directories |
| Sales teams selling to manufacturers | Only worth running as part of a broader multi-platform sweep |

### Tuning the ECPlaza Email Scraper

Realistically, tuning cannot overcome an absent index. These settings help only in the pockets that are indexed.

Use very narrow product keywords in the ECPlaza Email Scraper. Broad terms such as `supplier` return nothing here, and narrow ones occasionally hit a page that escaped the block.

Set `countryCode` to `KR`, then try `US` and `GB`. Different Google locales occasionally retain pages that others have dropped.

Add `@naver.com`, `@daum.net` and `@hanmail.net` to `customDomains` before you widen keywords.

Keep `maxEmails` small and `maxPagesPerQuery` at the default. Spending a large budget on the ECPlaza Email Scraper is rarely justified.

Check the run summary. If it logs pages fetched with zero blocked pages and still no emails, the platform is not indexed rather than blocking you.

### What results to expect from the ECPlaza Email Scraper

Expect nothing, and treat anything you get as a bonus. A measured live run of the ECPlaza Email Scraper returned zero results across every metric.

That is not a defect in the Actor. The same engine returns 10 emails out of 10 blocks on HKTDC Sourcing and DIYTrade, which tells you the difference is the platform's indexing policy.

If your sourcing needs Korean suppliers specifically, combine the better-indexed marketplaces with your own trade-fair and association lists.

Results vary with keywords, domains and location, and no volume is guaranteed. On this platform that caveat is the main event.

### ECPlaza Email Scraper limitations

- **Yield.** ECPlaza blocks most of its supplier pages from search engines, so the ECPlaza Email Scraper often returns nothing; the Global Sources, TradeKey and Tradewheel Actors cover the same ground far better.
- The ECPlaza Email Scraper only finds accounts whose email is **publicly visible in Google's index**.
- Google caps a single query at roughly 300 results, which is exactly why query expansion exists.
- `possiblyTruncated: true` means Google's snippet ellipsis touched the address; verify before sending.
- The Actor requires the Apify GOOGLE_SERP proxy and cannot run without Apify proxy credentials.
- Free Apify plans are capped at 100 emails per run; paid plans are uncapped.
- `username` and `profileUrl` are populated only when Google exposes a handle. Listing pages without a supplier subdomain leave both empty. That is a Google limitation, not a bug.
- Results vary with keywords, domains and location; no volume is guaranteed.

### Responsible use, GDPR and trade compliance

Business contact data is still personal data in many jurisdictions. Under GDPR and comparable regimes you need a lawful basis, a stated purpose and a working opt-out before using anything the ECPlaza Email Scraper returns.

Keep outreach relevant to the supplier's own trade, identify your company clearly, and honour unsubscribe requests immediately.

Screen counterparties against your own sanctions and denied-party obligations before transacting. The ECPlaza Email Scraper performs no screening of its own.

None of this is legal advice. Take proper counsel if your programme touches restricted jurisdictions or controlled goods.

### Related Actors

| Actor | What it collects |
|---|---|
| [ECPlaza Email and Phone Number Scraper](https://apify.com/neuro-scraper/ecplaza-email-and-phone-number-scraper) | Emails and phone numbers from ECPlaza |
| [ECPlaza Phone Number Scraper](https://apify.com/neuro-scraper/ecplaza-phone-number-scraper) | Public phone numbers from ECPlaza |
| [Alibaba Email Scraper](https://apify.com/leads-scraper/alibaba-email-scraper) | Public contact emails from Alibaba |
| [DirectIndustry Email Scraper](https://apify.com/neuro-scraper/directindustry-email-scraper) | Public contact emails from DirectIndustry |
| [DIYTrade Email Scraper](https://apify.com/neuro-scraper/diytrade-email-scraper) | Public contact emails from DIYTrade |
| [Fibre2Fashion Email Scraper](https://apify.com/neuro-scraper/fibre2fashion-email-scraper) | Public contact emails from Fibre2Fashion |
| [Global Sources Email Scraper](https://apify.com/leads-scraper/global-sources-email-scraper) | Public contact emails from Global Sources |
| [GlobalSpec Email Scraper](https://apify.com/leads-scraper/globalspec-email-scraper) | Public contact emails from GlobalSpec |
| [HKTDC Sourcing Email Scraper](https://apify.com/neuro-scraper/hktdc-sourcing-email-scraper) | Public contact emails from HKTDC Sourcing |
| [IndiaMART Email Scraper](https://apify.com/leads-scraper/indiamart-email-scraper) | Public contact emails from IndiaMART |
| [IndustryStock Email Scraper](https://apify.com/neuro-scraper/industrystock-email-scraper) | Public contact emails from IndustryStock |
| [IQS Directory Email Scraper](https://apify.com/neuro-scraper/iqs-directory-email-scraper) | Public contact emails from IQS Directory |
| [Made-in-China Email Scraper](https://apify.com/leads-scraper/made-in-china-email-scraper) | Public contact emails from Made-in-China |
| [Taiwantrade Email Scraper](https://apify.com/leads-scraper/taiwantrade-email-scraper) | Public contact emails from Taiwantrade |
| [Textile Infomedia Email Scraper](https://apify.com/leads-scraper/textile-infomedia-email-scraper) | Public contact emails from Textile Infomedia |
| [Textile World Email Scraper](https://apify.com/leads-scraper/textile-world-email-scraper) | Public contact emails from Textile World |
| [Thomas Scientific Email Scraper](https://apify.com/leads-scraper/thomas-scientific-email-scraper) | Public contact emails from Thomas Scientific |
| [TradeKey Email Scraper](https://apify.com/neuro-scraper/tradekey-email-scraper) | Public contact emails from TradeKey |
| [Tradewheel Email Scraper](https://apify.com/leads-scraper/tradewheel-email-scraper) | Public contact emails from Tradewheel |
| [Wer Liefert Was Email Scraper](https://apify.com/leads-scraper/wer-liefert-was-email-scraper) | Public contact emails from wlw |
| [DirectIndustry Email and Phone Number Scraper](https://apify.com/neuro-scraper/directindustry-email-and-phone-number-scraper) | Emails and phone numbers from DirectIndustry |
| [DIYTrade Email and Phone Number Scraper](https://apify.com/neuro-scraper/diytrade-email-and-phone-number-scraper) | Emails and phone numbers from DIYTrade |
| [Fibre2Fashion Email and Phone Number Scraper](https://apify.com/neuro-scraper/fibre2fashion-email-and-phone-number-scraper) | Emails and phone numbers from Fibre2Fashion |
| [Global Sources Email and Phone Number Scraper](https://apify.com/leads-scraper/global-sources-email-and-phone-number-scraper) | Emails and phone numbers from Global Sources |
| [GlobalSpec Email and Phone Number Scraper](https://apify.com/neuro-scraper/globalspec-email-and-phone-number-scraper) | Emails and phone numbers from GlobalSpec |
| [HKTDC Sourcing Email and Phone Number Scraper](https://apify.com/neuro-scraper/hktdc-sourcing-email-and-phone-number-scraper) | Emails and phone numbers from HKTDC Sourcing |
| [IndiaMART Email and Phone Number Scraper](https://apify.com/leads-scraper/indiamart-email-and-phone-number-scraper) | Emails and phone numbers from IndiaMART |
| [IndustryStock Email and Phone Number Scraper](https://apify.com/neuro-scraper/industrystock-email-and-phone-number-scraper) | Emails and phone numbers from IndustryStock |
| [IQS Directory Email and Phone Number Scraper](https://apify.com/neuro-scraper/iqs-directory-email-and-phone-number-scraper) | Emails and phone numbers from IQS Directory |
| [Made-in-China Email and Phone Number Scraper](https://apify.com/leads-scraper/made-in-china-email-and-phone-number-scraper) | Emails and phone numbers from Made-in-China |
| [TradeKey Email and Phone Number Scraper](https://apify.com/neuro-scraper/tradekey-email-and-phone-number-scraper) | Emails and phone numbers from TradeKey |
| [wlw Email and Phone Number Scraper](https://apify.com/leads-scraper/wer-liefert-was-email-and-phone-number-scraper) | Emails and phone numbers from wlw |
| [DirectIndustry Phone Number Scraper](https://apify.com/neuro-scraper/directindustry-phone-number-scraper) | Public phone numbers from DirectIndustry |
| [DIYTrade Phone Number Scraper](https://apify.com/neuro-scraper/diytrade-phone-number-scraper) | Public phone numbers from DIYTrade |
| [Fibre2Fashion Phone Number Scraper](https://apify.com/neuro-scraper/fibre2fashion-phone-number-scraper) | Public phone numbers from Fibre2Fashion |
| [Global Sources Phone Number Scraper](https://apify.com/leads-scraper/global-sources-phone-number-scraper) | Public phone numbers from Global Sources |
| [GlobalSpec Phone Number Scraper](https://apify.com/neuro-scraper/globalspec-phone-number-scraper) | Public phone numbers from GlobalSpec |
| [HKTDC Sourcing Phone Number Scraper](https://apify.com/neuro-scraper/hktdc-sourcing-phone-number-scraper) | Public phone numbers from HKTDC Sourcing |
| [IndiaMART Phone Number Scraper](https://apify.com/leads-scraper/indiamart-phone-number-scraper) | Public phone numbers from IndiaMART |
| [IndustryStock Phone Number Scraper](https://apify.com/neuro-scraper/industrystock-phone-number-scraper) | Public phone numbers from IndustryStock |
| [IQS Directory Phone Number Scraper](https://apify.com/neuro-scraper/iqs-directory-phone-number-scraper) | Public phone numbers from IQS Directory |
| [Made-in-China Phone Number Scraper](https://apify.com/leads-scraper/made-in-china-phone-number-scraper) | Public phone numbers from Made-in-China |

### ECPlaza Email Scraper FAQ

#### How many results should I expect?

Realistically, none. A measured live run of the ECPlaza Email Scraper returned zero blocks, zero identities, zero profile URLs and zero emails.

#### Why does it return nothing?

ECPlaza blocks most of its supplier pages from search engines. The Actor reads Google's index, so pages kept out of that index are invisible to it.

#### Is the Actor broken?

No. The same engine returns full records on HKTDC Sourcing and DIYTrade. The difference is the platform's indexing policy, not the code.

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

No. It reads Google search results through the Apify GOOGLE_SERP proxy. No login, no API key, no browser, no cookies.

#### Does it access contact details ECPlaza keeps behind its messaging system?

No. The ECPlaza Email Scraper cannot see anything behind the platform's enquiry or contact-supplier flow. It only reads addresses already public in Google's index.

#### What should I run instead?

Global Sources, TradeKey and Tradewheel cover the same ground far better. HKTDC Sourcing and DIYTrade scored highest of all in testing.

#### Why do some rows resolve a profile URL when others do not?

ECPlaza gives suppliers their own subdomain in the form `suppliername.en.ecplaza.net`. Where Google prints that subdomain the ECPlaza Email Scraper rebuilds a profile URL; on plain listing pages it leaves `username` as `null`.

#### Which email domains should I add?

`@naver.com`, `@daum.net` and `@hanmail.net` alongside the defaults, since those dominate Korean business mail.

#### Does `countryCode` help?

Marginally. Try `KR` first, then `US` and `GB`. Different locales occasionally retain pages that others have dropped.

#### Is it worth spending credits on?

Only a small amount. Run the ECPlaza Email Scraper with a low `maxEmails` as a probe inside a wider sweep.

#### Could the yield improve later?

Possibly. Indexing policies change, and the Actor is ready if this platform becomes crawlable again.

#### Is this affiliated with ECPlaza?

No. The ECPlaza Email Scraper is an independent Actor, not supported, endorsed or affiliated with ECPlaza.

### Leave a review

If the ECPlaza 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 a custom build? Email **neurodata.apify@gmail.com**.

# Actor input Schema

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

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

## `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": [
    "exporter",
    "supplier"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "export",
    "wholesale",
    "sales enquiries"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

Records produced by ECPlaza 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": [
        "exporter",
        "supplier"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "export",
        "wholesale",
        "sales enquiries"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("neuro-scraper/ecplaza-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": [
        "exporter",
        "supplier",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "export",
        "wholesale",
        "sales enquiries",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("neuro-scraper/ecplaza-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": [
    "exporter",
    "supplier"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "export",
    "wholesale",
    "sales enquiries"
  ]
}' |
apify call neuro-scraper/ecplaza-email-scraper --silent --output-dataset

```

## MCP server setup

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