# TradeKey Email Scraper (`email_scraper/tradekey-email-scraper`) Actor

TradeKey Email Scraper extracts publicly indexed email addresses from TradeKey using targeted keywords, location filters, custom email domains, and exclusion terms. Build structured TradeKey contact datasets for supplier research, B2B lead research, business intelligence, and contact analysis.

- **URL**: https://apify.com/email\_scraper/tradekey-email-scraper.md
- **Developed by:** [Email Scraper](https://apify.com/email_scraper) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.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

### TradeKey Email Scraper

TradeKey Email Scraper is an Apify Actor designed to extract publicly indexed email addresses associated with TradeKey pages and profiles using targeted search keywords. It helps turn focused TradeKey searches into a structured dataset containing keywords, result titles, descriptions, URLs, and matching email addresses.

You can provide multiple keywords, optionally narrow searches by country, state, or city, select the email domains you want to collect, and exclude results containing specific words or phrases. The Actor processes each keyword and email-domain combination independently and adds discovered results to the Apify dataset.

The resulting TradeKey contact data can support business research, supplier research, market research, lead discovery, company research, and other workflows where structured contact information from publicly indexed TradeKey content is useful.

### What Is a TradeKey Email Scraper?

A TradeKey Email Scraper automates the process of finding email addresses that appear in publicly indexed TradeKey search results.

Instead of manually searching TradeKey pages for contact information, you can define the terms that represent the businesses, suppliers, exporters, or other profiles you are researching. The Actor then searches for matching TradeKey results and extracts email addresses that match your selected domain suffixes.

For example, instead of using only a broad keyword such as `exporter`, you can create more targeted searches such as `electronics exporter`, `garment exporter`, `textile supplier`, or `machinery supplier`.

The Actor returns structured records containing the search keyword, result title, description, URL, and extracted email address.

### Key Features

| Feature                | Description                                                      | User Benefit                                    |
| ---------------------- | ---------------------------------------------------------------- | ----------------------------------------------- |
| Multiple keywords      | Search using a list of keywords or queries                       | Target several business categories in one run   |
| Location filtering     | Optionally add a country, state, or city                         | Narrow research to a geographic area            |
| Custom email domains   | Specify domains such as `@gmail.com` or `@yahoo.com`             | Focus collection on selected email types        |
| Per-combination limits | Set a maximum email target for each keyword + domain combination | Control the amount of data collected            |
| Exclude words          | Skip descriptions containing specified words or phrases          | Reduce unwanted or irrelevant results           |
| Structured dataset     | Results contain consistent fields for each discovered email      | Simplify review and analysis                    |
| Duplicate prevention   | Previously discovered email addresses are not added again        | Keep the collected email list cleaner           |
| Incremental results    | Matching records are added to the dataset during processing      | Make discovered results available progressively |

### What Data Can You Extract?

The TradeKey Email Scraper produces structured contact records based on publicly indexed TradeKey search results.

Each result can contain:

- **Keyword** — The keyword that produced the search result.
- **Title** — The title associated with the indexed TradeKey result.
- **Description** — The available search-result description or snippet.
- **URL** — The URL associated with the result.
- **Email** — An email address matching one of the configured email-domain suffixes.

This structure makes the resulting dataset useful for reviewing which search terms produced each contact and where the corresponding public information was found.

The Actor focuses on email addresses found within the available indexed result descriptions. It does not claim that every TradeKey profile contains a publicly indexed email address.

### Why Use This Actor?

Manual contact research can require repeatedly searching different business categories, locations, and email domains. The TradeKey Email Scraper provides a configurable workflow for performing this type of research through an Apify Actor.

It is particularly useful when your research requires multiple combinations of:

- Business keywords
- Supplier or exporter terms
- Geographic locations
- Email-domain filters
- Exclusion terms

Because the Actor works with keyword and domain combinations, you can create targeted searches rather than relying on one broad query.

For example, a supplier-research workflow could combine terms such as `textile supplier`, `garment exporter`, and `fabric manufacturer` with selected email domains.

### Benefits

The Actor provides several practical benefits for TradeKey contact research:

- **Automation** — Reduce repetitive manual searching and email collection.
- **Structured data** — Receive consistent fields for keyword, title, description, URL, and email.
- **Targeted research** — Use specific keywords instead of relying only on broad searches.
- **Geographic targeting** — Add a location when regional research is required.
- **Domain targeting** — Select the email-domain suffixes relevant to your workflow.
- **Filtering** — Exclude descriptions containing unwanted words or phrases.
- **Dataset creation** — Build an organized collection of TradeKey contact records.
- **Research flexibility** — Combine multiple keywords and domains within one run.

Results depend on what is publicly indexed and available for the configured searches.

### How to Use the TradeKey Email Scraper

A typical workflow is:

1. Add one or more keywords to the `keywords` field.
2. Optionally enter a country, state, or city in `location`.
3. Add the email domains you want to target in `customDomains`.
4. Set `maxEmails` according to the desired collection size.
5. Optionally add unwanted words or phrases to `excludeWords`.
6. Start the Actor.
7. Review the resulting dataset containing the discovered contact records.

For better targeting, use several specific search terms rather than one very broad keyword.

### Input

The Actor requires the `keywords` field. The other fields are optional and provide additional control over the search.

| Field           | Type             | Required | Default                    | Description                                                                      |
| --------------- | ---------------- | -------- | -------------------------- | -------------------------------------------------------------------------------- |
| `keywords`      | Array of strings | Yes      | `["exporter", "supplier"]` | Keywords or search queries used to find relevant TradeKey results                |
| `location`      | String           | No       | `""`                       | Optional country, state, or city used to narrow searches                         |
| `customDomains` | Array of strings | No       | `["@gmail.com"]`           | Email-domain suffixes to search for                                              |
| `maxEmails`     | Integer          | No       | `5`                        | Maximum target for each keyword + domain combination; accepted range is 1–10,000 |
| `excludeWords`  | Array of strings | No       | `[]`                       | Words or phrases that cause matching result descriptions to be skipped           |

#### Keywords

`keywords` accepts multiple search terms. More specific terms can help distinguish different business categories.

Examples include:

- `exporter`
- `supplier`
- `electronics exporter`
- `textile supplier`
- `machinery manufacturer`

The Actor also accepts a single string internally, but the documented Actor input schema expects an array of strings.

#### Location

`location` is optional. Enter a country, state, or city when you want to narrow the search geographically.

Leave it empty when no geographic filter is required.

#### Custom Email Domains

`customDomains` controls which email-domain suffixes are targeted.

Examples include:

- `@gmail.com`
- `@yahoo.com`
- `@outlook.com`
- A relevant company-domain suffix

The default is `@gmail.com`.

#### Maximum Emails

`maxEmails` must be an integer from `1` to `10000`.

The limit applies independently to each keyword + domain combination. For example, with three keywords, two domains, and a limit of 20, the Actor can target up to 20 addresses for each of the six combinations.

The configured value is a target rather than a guarantee. Fewer emails may be returned when matching publicly indexed results are unavailable.

#### Exclude Words

`excludeWords` lets you skip result descriptions containing unwanted terms.

Matching is case-insensitive. A single word is matched as a whole word, while a phrase is matched as a phrase.

For example:

- `crypto`
- `onlyfans`
- `adult products`

If an exclusion term matches the result description, that result is skipped for email extraction.

### Input Example

```json
{
  "keywords": [
    "textile exporter",
    "garment supplier",
    "fabric manufacturer"
  ],
  "location": "Bangladesh",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com",
    "@outlook.com"
  ],
  "maxEmails": 20,
  "excludeWords": [
    "crypto",
    "onlyfans"
  ]
}
```

### Output

The TradeKey Email Scraper produces structured dataset records with five documented output fields.

| Field         | Description                                                     |
| ------------- | --------------------------------------------------------------- |
| `keyword`     | The keyword associated with the search that produced the record |
| `title`       | The title of the indexed result                                 |
| `description` | The available description or snippet for the result             |
| `url`         | The URL associated with the result                              |
| `email`       | The extracted email address matching a configured domain        |

The dataset is designed to make contact records easy to review alongside their originating search information.

Email addresses are de-duplicated during the run, so the same email is not intentionally added multiple times when it is encountered again.

### Output Example

```json
{
  "keyword": "textile exporter",
  "title": "Textile Exporter - TradeKey",
  "description": "Example textile exporter profile with public contact information including sales@example.com.",
  "url": "https://www.tradekey.com/example-textile-exporter.html",
  "email": "sales@example.com"
}
```

The example above illustrates the output structure. Actual titles, descriptions, URLs, and email addresses depend on the publicly indexed TradeKey results available for the selected searches.

### Use Cases

TradeKey Email Scraper can support several research and data-collection workflows.

- **Supplier research** — Find publicly indexed contact information associated with supplier-related searches.
- **Exporter research** — Research exporters by product category or market.
- **Import-export research** — Organize contacts around specific trade-related keywords.
- **B2B lead research** — Build structured contact datasets from relevant TradeKey results.
- **Market research** — Investigate businesses associated with specific products or industries.
- **Company research** — Collect result information connected to targeted business terms.
- **Geographic research** — Narrow searches to a particular country, state, or city.
- **Business intelligence** — Combine search keywords and structured contact records for analysis.
- **Dataset creation** — Build reusable datasets of publicly indexed TradeKey contact information.

The Actor should be used for lawful and appropriate data-collection purposes, with applicable privacy, data-protection, and website terms considered for your particular workflow.

### Competitive Advantages

The Actor's practical strengths come from its configurable search inputs and structured output.

- Multiple keywords can be processed in one run.
- Email domains can be selected according to the research requirement.
- Geographic filtering is available when location-specific research is needed.
- Exclusion terms provide a way to remove descriptions containing unwanted content.
- Results contain both contact information and the associated search-result context.
- The output is organized into a consistent Apify dataset structure.
- Email addresses are de-duplicated during collection.

These capabilities allow users to adapt the Actor to different TradeKey research objectives without changing the output structure.

### Advantages

- **Flexible keyword targeting** — Useful for product, supplier, exporter, manufacturer, and other business terms.
- **Geographic control** — Location can be supplied when regional targeting matters.
- **Domain selection** — Users can focus collection on selected email suffixes.
- **Configurable volume** — The email target can be adjusted from 1 through 10,000 per keyword + domain combination.
- **Result context** — Email records retain title, description, keyword, and URL information.
- **Filtering support** — Exclusion words can help remove unwanted result descriptions.

### Limitations

- Results depend on publicly indexed TradeKey information available to the configured searches.
- Not every TradeKey result contains an email address.
- The configured `maxEmails` value is a target, not a guarantee that the target will be reached.
- A narrow keyword, location, or email-domain selection can reduce the number of matching results.
- Search-result descriptions may contain limited information.
- The Actor does not document private or non-public contact information as an output.
- Free Apify usage can impose a 100-email maximum at the Actor level when the detected account is subject to the free-tier restriction.
- Very broad runs may require more execution time; the Actor input documentation notes a default run timeout of 3600 seconds.

### Pros and Cons

| Pros                          | Cons                                                      |
| ----------------------------- | --------------------------------------------------------- |
| Multiple targeted keywords    | Results depend on publicly indexed information            |
| Optional geographic filtering | Some searches may return few or no matching emails        |
| Custom email-domain targeting | Email availability varies by result                       |
| Exclusion-word filtering      | A configured target does not guarantee that many results  |
| Structured dataset output     | Search-result descriptions may be limited                 |
| Duplicate email prevention    | Free-tier Actor usage can be subject to a 100-email limit |

### Comparison With Alternative Approaches

| Capability             | TradeKey Email Scraper                | Manual / Typical Alternative                        |
| ---------------------- | ------------------------------------- | --------------------------------------------------- |
| Keyword-based research | Supported                             | Usually performed manually                          |
| Multiple search terms  | Supported                             | Requires repeated searches                          |
| Location targeting     | Supported                             | Depends on the research workflow                    |
| Email-domain filtering | Supported                             | Often requires manual checking                      |
| Exclusion filtering    | Supported                             | Usually manual                                      |
| Structured output      | Dataset fields for each result        | May require manual organization                     |
| Duplicate handling     | Duplicate email addresses are skipped | Often requires manual cleanup                       |
| Dataset creation       | Supported through Actor output        | Usually requires separate collection and formatting |

This comparison describes workflow characteristics rather than claiming that one approach is universally better.

### Best Practices

For more focused TradeKey contact research:

- Start with a small test using two or three relevant keywords.
- Use specific business terms instead of relying only on broad categories.
- Add a location when geographic targeting is important.
- Include multiple relevant email domains when broader domain coverage is needed.
- Keep `maxEmails` reasonable during initial testing.
- Use `excludeWords` when certain categories of descriptions are not relevant to your research.
- Review a small result set before expanding the run.
- If results are sparse, broaden the keywords or remove an overly restrictive location filter.
- If the target is not reached, remember that the requested number is a target and depends on available matching indexed results.

### Troubleshooting

**Invalid Input**

Check that `keywords` is an array of strings and that `maxEmails` is an integer between 1 and 10,000. Email-domain entries should be supplied as domain suffixes such as `@gmail.com`.

**Empty Results**

Try broader or more specific keywords depending on the research objective. If a location is configured, test the same keywords without the location filter. You can also review whether the selected email domains are too restrictive.

**Partial Results**

A partial result set does not necessarily indicate an input problem. The requested target can only be reached when sufficient matching, publicly indexed information is available.

**Missing Emails**

A result may have a title, URL, and description without containing an email address matching the selected domain suffixes. Consider adding other relevant domains if appropriate.

**Too Many Irrelevant Results**

Use more specific keywords or add a location. You can also add terms to `excludeWords` when descriptions containing those terms should be skipped.

**Results Below the Requested Target**

Consider adding related keywords, expanding the location, or including additional email domains. The Actor cannot guarantee a particular number of results when matching public information is unavailable.

### Frequently Asked Questions

**What does the TradeKey Email Scraper do?**

It searches for publicly indexed TradeKey results based on your configured keywords and extracts email addresses matching your selected email-domain suffixes.

**What data does the TradeKey Email Scraper return?**

Each documented result contains `keyword`, `title`, `description`, `url`, and `email`.

**Can I use multiple keywords?**

Yes. The `keywords` input is an array, so you can provide multiple search terms in the same Actor run.

**Can I search a specific country or city?**

Yes. The optional `location` field accepts a country, state, or city and can be used to narrow the search.

**Can I choose which email domains to find?**

Yes. Use `customDomains` to provide the email-domain suffixes you want to target, such as `@gmail.com`, `@yahoo.com`, or `@outlook.com`.

**How does `maxEmails` work?**

The configured maximum applies independently to each keyword + domain combination. It accepts values from 1 through 10,000, subject to the applicable Actor usage limitation.

**Can I exclude certain types of results?**

Yes. Add words or phrases to `excludeWords`. If a configured exclusion term matches a result description, that result is skipped for email extraction.

**Why did the Actor return fewer emails than requested?**

The requested number is a target, not a guarantee. There may not be enough publicly indexed TradeKey results containing matching email addresses for the selected keyword, location, and domain filters.

**Does the Actor remove duplicate emails?**

Yes. The Actor tracks discovered email addresses and avoids intentionally adding the same email address more than once during collection.

**Can I use the results for business research?**

Yes. The structured output can support supplier research, exporter research, market research, company research, lead research, and related data-analysis workflows. Users should ensure their use complies with applicable laws and data-use requirements.

### NLP Keywords

- TradeKey email scraper
- TradeKey email extractor
- TradeKey contact scraper
- TradeKey contact data
- TradeKey business contacts
- TradeKey supplier emails
- TradeKey exporter emails
- TradeKey email addresses
- TradeKey lead generation
- TradeKey lead research
- TradeKey business research
- TradeKey supplier research
- TradeKey exporter research
- TradeKey contact extraction
- TradeKey data extraction
- TradeKey structured data
- TradeKey company contacts
- TradeKey B2B leads
- TradeKey public emails
- TradeKey contact dataset

### Related Keywords

- TradeKey email scraper
- scrape TradeKey emails
- extract emails from TradeKey
- TradeKey contact extractor
- TradeKey business email finder
- TradeKey supplier email finder
- TradeKey exporter contact finder
- TradeKey B2B email scraper
- TradeKey lead scraper
- TradeKey contact data scraper
- TradeKey email data extraction
- TradeKey supplier contact scraper
- TradeKey exporter email scraper
- TradeKey company email extraction
- TradeKey public contact scraper
- TradeKey business lead research
- TradeKey supplier lead generation
- TradeKey exporter lead research
- TradeKey contact dataset
- TradeKey email collection

### Final Overview

TradeKey Email Scraper provides a structured way to research publicly indexed TradeKey contact information using configurable keywords, optional locations, selected email domains, and exclusion terms.

The Actor accepts multiple search terms and produces dataset records containing the keyword, result title, description, URL, and matching email address. Per-keyword and per-domain targeting, duplicate prevention, geographic filtering, and exclusion controls give users practical ways to shape their research workflow.

For best results, begin with focused keywords, test a small run, review the returned records, and then expand the keyword, location, or email-domain configuration when broader coverage is appropriate.

*Contact me:* <Alphascraper69@gmail.com>

# Actor input Schema

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

A list of keywords or queries to search for.

## `location` (type: `string`):

Optional country, state or city used to narrow the search. Leave it empty to search without a geographic filter.

## `customDomains` (type: `array`):

List of custom email domains

## `maxEmails` (type: `integer`):

How many addresses each search keyword + domain suffix combination may collect before the finder moves on to the next one. This is a per-combination target, not a run-wide total: with 3 keyword and 2 Domains and a limit of 20, the run works through all 6 combinations and aims for up to 20 addresses in each, so up to 120 overall. Lower values finish sooner and cost less; higher values dig deeper but never guarantee a fuller result, since the run can only find what is publicly listed.

## `excludeWords` (type: `array`):

Words or phrases you do not want to see.

## Actor input object example

```json
{
  "keywords": [
    "exporter",
    "supplier"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com"
  ],
  "maxEmails": 5,
  "excludeWords": []
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

# 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"
    ],
    "excludeWords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("email_scraper/tradekey-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"],
    "excludeWords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("email_scraper/tradekey-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"
  ],
  "excludeWords": []
}' |
apify call email_scraper/tradekey-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,email_scraper/tradekey-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/jcTtl6SUh3EsLN8AG/builds/1DeGKTvbhAufZyOx4/openapi.json