# Tokopedia Email Scraper (`email_scraper/tokopedia-email-scraper`) Actor

Tokopedia Email Scraper extracts publicly indexed emails from Tokopedia using targeted keywords, location filters, custom email domains, and exclusion terms. Build structured contact datasets for seller, supplier, business, lead, and market research.

- **URL**: https://apify.com/email\_scraper/tokopedia-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

### Tokopedia Email Scraper

Tokopedia Email Scraper is an Apify Actor designed to extract publicly indexed email addresses associated with Tokopedia search results. It lets you search using one or more keywords, optionally narrow the search by country, state, or city, select the email domains you want to collect, and exclude descriptions containing unwanted words or phrases.

The Actor returns structured contact records containing the search keyword, result title, description, URL, and extracted email address. This makes the resulting dataset useful for business research, supplier discovery, seller research, lead research, contact analysis, and other workflows involving publicly available Tokopedia information.

You can process multiple keywords and multiple email-domain suffixes in the same run. The configured email target applies independently to each keyword and domain combination, allowing different search combinations to contribute results to the dataset.

### What Is a Tokopedia Email Scraper?

Tokopedia Email Scraper is a keyword-based contact extraction tool focused on publicly indexed Tokopedia pages. Instead of manually searching through individual results and copying contact information, you provide search terms and configuration options, then receive matching email records in a structured Apify dataset.

The Actor is particularly useful when your research starts with categories such as `supplier`, `seller`, product-related terms, business roles, or other descriptive keywords. More specific keywords can help narrow the search toward the type of Tokopedia profiles or pages you are researching.

The Actor accepts a required `keywords` array and optional location, email-domain, maximum-email, and exclusion-word settings. The output contains five user-facing fields: `keyword`, `title`, `description`, `url`, and `email`.

### Key Features

| Feature                      | Description                                                                 | User Benefit                                                               |
| ---------------------------- | --------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
| Keyword-based search         | Search Tokopedia using one or more keywords or queries.                     | Target specific businesses, sellers, suppliers, or other relevant results. |
| Multiple keywords            | Submit several search terms in one run.                                     | Expand research coverage across related search intents.                    |
| Location filtering           | Optionally specify a country, state, or city.                               | Narrow research toward a geographic area.                                  |
| Custom email domains         | Choose email suffixes such as `@gmail.com`, `@yahoo.com`, or other domains. | Focus collection on the contact types relevant to your research.           |
| Per-combination email target | Set a maximum number of emails for each keyword + domain combination.       | Control collection depth for individual search combinations.               |
| Exclude words                | Skip descriptions containing specified words or phrases.                    | Reduce unwanted records based on description content.                      |
| Duplicate prevention         | The Actor avoids adding the same email address more than once during a run. | Keep the resulting contact dataset cleaner.                                |
| Structured dataset           | Results are stored with keyword, title, description, URL, and email.        | Make collected information easier to review and analyze.                   |
| Incremental results          | Collected records are added to the dataset during processing.               | Results can become available as the run progresses.                        |

### What Data Can You Extract?

The Tokopedia Email Scraper produces structured contact records rather than only returning a list of email addresses.

Each result can contain:

- **Keyword** — The keyword associated with the search that produced the result.
- **Title** — The title of the matching Tokopedia search result.
- **Description** — The publicly indexed description or snippet associated with the result.
- **URL** — The URL associated with the search result.
- **Email** — The email address extracted from the result description when it matches one of the configured email-domain suffixes.

This structure gives you context around each email address. Instead of receiving an email without a source, the dataset also records the associated search keyword, result title, description, and URL.

### Why Use This Actor?

Manual contact research can involve repeatedly searching for relevant Tokopedia results, checking descriptions, identifying email addresses, and recording source information. The Tokopedia Email Scraper organizes this workflow around configurable search inputs.

It can be useful when your research requires:

- Multiple keyword combinations.
- Geographic targeting.
- Specific email-domain targeting.
- Description-based exclusions.
- Structured contact records.
- A repeatable Apify-based collection workflow.

The Actor is intended for research and data-collection workflows where publicly indexed information is relevant to the user's purpose.

### Benefits

The main practical benefits include:

- **Automated collection** — Reduce repetitive manual searching and copying.
- **Structured data** — Keep email addresses together with their related search context.
- **Flexible targeting** — Combine keywords, locations, and email domains.
- **Multiple search terms** — Research several related categories within one run.
- **Configurable filtering** — Exclude descriptions containing unwanted terms.
- **Controlled collection depth** — Configure the maximum number of emails for each keyword + domain combination.
- **Dataset creation** — Build a structured collection that can be reviewed after the Actor finishes.
- **Research support** — Use the resulting records for business, supplier, seller, and market research.

The Actor does not guarantee that every requested target will be reached. Results depend on what relevant information is publicly indexed and available for the selected searches.

### How to Use the Tokopedia Email Scraper

The basic workflow is straightforward:

1. Enter one or more Tokopedia-related keywords in the `keywords` field.
2. Optionally enter a country, state, or city in `location`.
3. Select the email-domain suffixes you want to search for in `customDomains`.
4. Set `maxEmails` according to the desired collection depth.
5. Optionally add unwanted words or phrases to `excludeWords`.
6. Start the Actor.
7. Review the structured records in the resulting dataset.

For initial testing, use a small number of keywords and a modest email target. After reviewing the quality of the results, you can adjust your search terms and configuration.

### Input

The Actor requires the `keywords` field. All other configuration fields are optional.

| Field           | Type             | Required | Default                  | Description                                                                                                  |
| --------------- | ---------------- | -------- | ------------------------ | ------------------------------------------------------------------------------------------------------------ |
| `keywords`      | Array of strings | Yes      | `["supplier", "seller"]` | Keywords or search queries used to find relevant Tokopedia results.                                          |
| `location`      | String           | No       | `""`                     | Optional country, state, or city used to narrow the search.                                                  |
| `customDomains` | Array of strings | No       | `["@gmail.com"]`         | Email-domain suffixes to include when identifying email addresses.                                           |
| `maxEmails`     | Integer          | No       | `5`                      | Maximum number of email addresses targeted for each keyword + domain combination. Allowed range is 1–10,000. |
| `excludeWords`  | Array of strings | No       | `[]`                     | Words or phrases that cause matching descriptions to be skipped.                                             |

#### Keywords

`keywords` is an array of search terms. The default values are:

- `supplier`
- `seller`

Using several specific related terms can provide broader research coverage than relying on a single broad keyword.

For example, instead of only searching for a general category, you can use terms that describe more specific business roles, products, or seller types.

#### Location

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

Leave it empty when you do not want to apply a geographic filter.

#### Custom Email Domains

`customDomains` accepts an array of email suffixes. The default is:

- `@gmail.com`

You can configure other suffixes such as:

- `@yahoo.com`
- `@outlook.com`
- `@hotmail.com`
- A relevant company or organization domain

The Actor uses the configured suffixes when identifying matching email addresses.

#### Maximum Emails

`maxEmails` accepts an integer from `1` through `10000`, with a default of `5`.

The limit applies independently to each keyword + email-domain combination. For example, with two keywords, two domains, and a limit of 10, the Actor can target up to 10 emails for each of the four combinations.

The configured value is a target, not a guarantee. The available indexed results may contain fewer matching email addresses.

#### Exclude Words

`excludeWords` is an optional array of words or phrases.

If a result description contains an excluded term, that description is skipped and its email is not collected.

Matching is case-insensitive. Single words are matched as whole words, while phrases are matched as phrases within the description.

### Input Example

```json
{
  "keywords": [
    "supplier",
    "seller",
    "fashion seller"
  ],
  "location": "Jakarta",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com",
    "@outlook.com"
  ],
  "maxEmails": 10,
  "excludeWords": [
    "crypto",
    "onlyfans"
  ]
}
```

### Output

The Tokopedia Email Scraper stores collected records in the Actor dataset. The user-facing dataset contains five primary fields.

| Field         | Description                                                                                 |
| ------------- | ------------------------------------------------------------------------------------------- |
| `keyword`     | The keyword used for the search that produced the record.                                   |
| `title`       | The title of the matching Tokopedia search result.                                          |
| `description` | The publicly indexed description or result snippet associated with the URL.                 |
| `url`         | The URL associated with the matching search result.                                         |
| `email`       | The email address extracted from the description according to the configured email domains. |

The Actor also prevents duplicate email addresses from being added repeatedly during the same collection process.

### Output Example

```json
{
  "keyword": "supplier",
  "title": "Example Tokopedia Seller",
  "description": "Example supplier profile with contact information at seller@example.com",
  "url": "https://www.tokopedia.com/example-seller",
  "email": "seller@example.com"
}
```

The example above illustrates the structure only. Actual titles, descriptions, URLs, and email addresses depend on the available indexed results for the selected search configuration.

### Use Cases

The Tokopedia Email Scraper can support several practical research workflows.

- **Seller research** — Find publicly indexed contact information associated with Tokopedia seller-related searches.
- **Supplier discovery** — Search for supplier-focused keywords and collect matching contact records.
- **Business research** — Build datasets around business categories or commercial search terms.
- **Market research** — Investigate different product, seller, or supplier categories using multiple search queries.
- **Lead research** — Organize publicly indexed contact information together with source context.
- **Geographic research** — Narrow searches to specific cities, states, or countries.
- **Contact analysis** — Review extracted emails alongside titles, descriptions, and URLs.
- **Dataset creation** — Create structured Tokopedia-related contact datasets for further analysis.
- **Keyword research workflows** — Compare results from several related search terms.
- **Business intelligence research** — Combine structured contact information with broader research processes where appropriate.

Use collected information responsibly and in accordance with applicable laws, regulations, and the terms governing the relevant data sources.

### Advantages

The Actor provides several configurable elements that can make targeted research easier:

- Multiple keywords can be processed within one run.
- Geographic targeting can be added when needed.
- Email-domain suffixes can be customized.
- Collection depth can be configured per keyword + domain combination.
- Description-based exclusions can remove unwanted results.
- Output includes source context instead of only an email address.
- Results are organized in an Apify dataset.
- Duplicate email addresses are avoided during collection.

These capabilities allow users to adapt the Actor to different Tokopedia contact research objectives without changing the documented input structure.

### Limitations

There are several important limitations to keep in mind:

- The Actor depends on publicly indexed Tokopedia-related search results.
- An email address is only collected when it is available in the information being processed and matches the configured email-domain suffix.
- The requested `maxEmails` value is a target rather than a guarantee.
- Narrow keywords can produce fewer relevant results.
- Location filtering can reduce the available result pool.
- Exclusion terms can remove otherwise relevant descriptions.
- Search results and publicly indexed information can change over time.
- A free usage tier applies a maximum collection limit of 100 emails when the requested limit is missing or exceeds that threshold.
- Large or broad searches may take longer to complete.

The Actor should therefore be treated as a configurable research and data-collection tool rather than a guarantee of complete Tokopedia contact coverage.

### Pros and Cons

| Pros                                    | Cons                                           |
| --------------------------------------- | ---------------------------------------------- |
| Supports multiple keywords              | Results depend on publicly indexed information |
| Optional geographic targeting           | Narrow searches may return fewer contacts      |
| Custom email-domain filtering           | Not every result contains an email address     |
| Per-keyword + domain collection targets | Requested targets are not guaranteed           |
| Description-based exclusions            | Exclusion rules can remove matching results    |
| Structured source and contact fields    | Search availability can change over time       |
| Duplicate email prevention              | Large searches may take longer                 |

### Comparison With Alternative Approaches

| Capability               | Tokopedia Email Scraper | Manual / Typical Alternative                    |
| ------------------------ | ----------------------- | ----------------------------------------------- |
| Keyword-based collection | Supported               | Usually requires repeated manual searches       |
| Multiple search terms    | Supported               | Often handled separately                        |
| Location targeting       | Supported               | Requires manual query refinement                |
| Email-domain targeting   | Supported               | Requires manual filtering                       |
| Description exclusions   | Supported               | Requires manual review                          |
| Structured output        | Supported               | Often requires manual copying and formatting    |
| Duplicate prevention     | Supported               | Manual processes may require additional cleanup |
| Apify dataset workflow   | Supported               | Depends on the alternative workflow             |

This comparison describes workflow characteristics rather than claiming that one approach is universally better for every research task.

### Best Practices

For better-targeted research:

- Start with specific keywords instead of relying only on very broad terms.
- Use multiple related keywords when researching several business categories.
- Add a location when geographic targeting is important.
- Leave `location` empty when wider coverage is preferred.
- Configure email domains according to the type of contacts you want to research.
- Start with a modest `maxEmails` value when testing a new search.
- Increase the target after reviewing the quality and quantity of results.
- Use `excludeWords` when certain description categories are not relevant.
- Review the resulting email addresses and source URLs before using the data.
- If results are sparse, broaden the keywords, adjust the location, or add relevant email domains.
- For broad runs, allow sufficient execution time.

### Troubleshooting

**Invalid Input**

Check that `keywords` is an array of strings and that integer values such as `maxEmails` are within the documented range of 1–10,000.

**Empty Results**

Try broader or more specific keywords depending on your research objective. You can also remove the location filter or review whether the configured email-domain suffix is too restrictive.

**Fewer Emails Than Requested**

The `maxEmails` value represents a target. The Actor cannot create results that are not publicly available in the relevant indexed information. Try additional related keywords or email domains if appropriate.

**Location Produces Few Results**

A geographic filter can narrow the available search results. Try a broader location or leave the field empty when geographic targeting is not essential.

**Unexpectedly Missing Records**

Check the `excludeWords` configuration. A matching word or phrase in a description causes that description to be skipped.

**Duplicate Emails**

The Actor is designed to avoid adding the same email address repeatedly during the run. Different search results can still provide different source context for research.

**Long-Running Search**

Broad configurations involving many keywords and email domains can require more processing. The Actor's input description recommends increasing the Run options timeout when necessary; its documented default is 3600 seconds.

### Frequently Asked Questions

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

It searches for publicly indexed Tokopedia-related results using your configured keywords and extracts matching email addresses from the available result descriptions.

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

Each collected record contains `keyword`, `title`, `description`, `url`, and `email`.

**Can I use multiple keywords?**

Yes. The required `keywords` field accepts an array, allowing you to search multiple terms within the same run.

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

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

**Can I search for specific email domains?**

Yes. The `customDomains` field accepts multiple email-domain suffixes such as `@gmail.com`, `@yahoo.com`, or `@outlook.com`.

**How does `maxEmails` work?**

The configured maximum is applied independently to each keyword + domain combination. It is a collection target, not a guarantee that the requested number will be available.

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

Yes. Add words or phrases to `excludeWords`. If a configured exclusion term appears in a result description, that description is skipped.

**Does the Actor return duplicate emails?**

The Actor tracks collected email addresses and avoids adding the same email address more than once during the collection process.

**Why did I receive fewer emails than my configured target?**

The target can be higher than the number of matching publicly indexed email addresses available for the selected keywords, locations, and domains. Broader search terms or additional relevant domains may increase coverage.

**Is the Tokopedia Email Scraper suitable for automated research workflows?**

Yes. It runs as an Apify Actor and produces structured dataset records, making it suitable for repeatable research and data-collection workflows where the collected information is appropriate for the intended use.

### NLP Keywords

- Tokopedia email scraper
- Tokopedia email extraction
- Tokopedia contact data
- Tokopedia seller emails
- Tokopedia supplier emails
- Tokopedia business contacts
- Tokopedia lead data
- Tokopedia contact extraction
- Tokopedia email finder
- Tokopedia seller research
- Tokopedia supplier research
- Tokopedia business research
- Tokopedia lead research
- Tokopedia keyword search
- Tokopedia contact dataset
- Tokopedia email collection
- Tokopedia public contact information
- Tokopedia search results
- Tokopedia structured data
- Tokopedia contact discovery

### Related Keywords

- Tokopedia email scraper actor
- scrape Tokopedia emails
- extract Tokopedia emails
- Tokopedia seller email scraper
- Tokopedia supplier email scraper
- Tokopedia business email extraction
- Tokopedia contact scraper
- Tokopedia lead scraper
- Tokopedia seller contact finder
- Tokopedia supplier contact finder
- Tokopedia business contact finder
- Tokopedia email lead generation
- Tokopedia contact research
- Tokopedia seller data extraction
- Tokopedia supplier data extraction
- Tokopedia keyword email search
- Tokopedia email domain search
- Tokopedia location email search
- Tokopedia public email extraction
- Tokopedia contact dataset scraper

### Final Overview

Tokopedia Email Scraper provides a configurable way to collect publicly indexed Tokopedia contact information using keywords, optional geographic targeting, custom email domains, and description-based exclusion terms.

The required keyword array gives you control over search intent, while optional location and domain settings help refine the type of results you want to research. The `maxEmails` setting provides a configurable collection target for each keyword + domain combination, and `excludeWords` helps remove descriptions that are not relevant to your workflow.

Results are returned as structured records containing the keyword, title, description, URL, and email address. This makes the dataset useful for seller research, supplier discovery, business research, lead research, contact analysis, and other appropriate data-collection workflows.

For the best results, begin with focused keywords, test a small configuration, review the returned records, and then refine your keywords, locations, email domains, and collection targets according to your research needs.

*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": [
    "supplier",
    "seller"
  ],
  "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": [
        "supplier",
        "seller"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com"
    ],
    "excludeWords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("email_scraper/tokopedia-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": [
        "supplier",
        "seller",
    ],
    "location": "",
    "customDomains": ["@gmail.com"],
    "excludeWords": [],
}

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

```

## MCP server setup

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