# Back Market Email Scraper (`email_scraper/back-market-email-scraper`) Actor

Back Market Email Scraper extracts publicly indexed emails using targeted keywords, location filters, custom email domains, and exclusion terms. Build structured Back Market contact datasets for marketplace research, lead discovery, business research, and contact analysis.

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

### Back Market Email Scraper

Back Market Email Scraper is an Apify Actor designed to extract publicly indexed email addresses associated with Back Market pages and profiles based on targeted search keywords. You provide one or more keywords, optionally narrow the search by country, state, or city, select the email domains you want to find, and optionally exclude descriptions containing specific words or phrases.

The Actor returns structured lead records containing the keyword used, result title, description, source URL, and extracted email address. This makes the resulting Back Market contact data suitable for research, lead discovery, business analysis, market research, and dataset creation.

You can process multiple keywords and multiple email-domain suffixes in the same run. The `maxEmails` setting controls the target for each keyword and email-domain combination rather than acting as one shared target across the entire run.

### What Is a Back Market Email Scraper?

A Back Market Email Scraper automates the collection of publicly indexed email addresses that appear in search results associated with Back Market content.

Instead of manually searching different keywords and copying contact information from individual search results, you can provide a structured list of search terms and let the Actor collect matching email records into an Apify dataset.

The Actor supports:

- Multiple search keywords in one run
- Optional geographic filtering
- Custom email-domain suffixes
- Exclusion words and phrases
- Configurable email collection limits
- Structured dataset output
- Duplicate email prevention during a run

The Actor is intended for users who need structured Back Market contact data for legitimate research, prospecting, analysis, and other workflows where publicly indexed information is appropriate to use.

### Key Features

| Feature                      | Description                                              | User Benefit                                         |
| ---------------------------- | -------------------------------------------------------- | ---------------------------------------------------- |
| Keyword-based search         | Search using one or multiple keywords                    | Target specific types of Back Market-related results |
| Location filter              | Optionally add a country, state, or city                 | Narrow searches geographically                       |
| Custom email domains         | Specify domains such as `@gmail.com` or `@outlook.com`   | Focus collection on desired email types              |
| Per-combination email target | Set `maxEmails` for each keyword + domain combination    | Control collection depth for different searches      |
| Exclusion filter             | Skip descriptions containing selected words or phrases   | Reduce unwanted results                              |
| Structured output            | Returns keyword, title, description, URL, and email      | Makes results easier to review and analyze           |
| Duplicate prevention         | Previously collected email addresses are not added again | Helps keep the resulting dataset cleaner             |
| Incremental dataset results  | Records are added as they are collected                  | Makes results available progressively during the run |

### What Data Can You Extract?

The Back Market Email Scraper returns five user-facing fields for each collected email record.

The dataset focuses on contact information together with enough search-result context to understand where an email was found.

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

This structure provides both the contact value and contextual information around the result, which can be useful when reviewing leads or creating a research dataset.

### Why Use the Back Market Email Scraper?

Manual contact research can require repeating similar searches for many terms and email domains. This Actor turns that repetitive search workflow into a configurable Apify run.

You can define several specific keywords instead of relying on one broad query. You can also combine multiple email-domain suffixes with those keywords. For example, a run can search for `MacBook` and `smartphone` while checking for different email domains.

The location field provides another way to narrow the search when geographic targeting matters. Leaving it empty allows the search to run without a geographic filter.

The resulting dataset keeps the search keyword and source context alongside each email, making it easier to understand and review collected records.

### Benefits

Using the Back Market Email Scraper can provide several practical workflow benefits:

- **Automation** — Reduce repetitive manual searching for publicly indexed contact information.
- **Multiple keyword processing** — Run several search terms within one Actor execution.
- **Targeted email collection** — Select the email-domain suffixes relevant to your research.
- **Geographic targeting** — Add a location when you need a more focused search.
- **Structured datasets** — Receive consistent fields for every collected record.
- **Filtering control** — Exclude descriptions containing unwanted words or phrases.
- **Research support** — Create datasets that can be reviewed, analyzed, or used in appropriate business research workflows.
- **Duplicate reduction** — The Actor tracks collected email addresses and avoids adding the same address again.

### How to Use the Back Market Email Scraper

The workflow is straightforward:

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

For better targeting, use several specific search terms instead of one overly broad keyword. If a run produces fewer results than expected, consider adding related keywords, expanding the location, or including additional relevant email domains.

### Input

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

| Field           | Type             | Required | Default                     | Description                                                                                 |
| --------------- | ---------------- | -------- | --------------------------- | ------------------------------------------------------------------------------------------- |
| `keywords`      | Array of strings | Yes      | `["MacBook", "smartphone"]` | Keywords or search queries used to find relevant Back Market 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 in searches                                                |
| `maxEmails`     | Integer          | No       | `5`                         | Target number of emails for each keyword + domain combination; minimum `1`, maximum `10000` |
| `excludeWords`  | Array of strings | No       | `[]`                        | Words or phrases that cause a matching description snippet to be skipped                    |

The `keywords` field is an array, so multiple searches can be configured in one run.

The `location` field can contain a manually entered geographic value. Leave it empty when no geographic restriction is required.

The `customDomains` field accepts email suffixes such as `@gmail.com`, `@yahoo.com`, `@outlook.com`, or other domain suffixes relevant to your search.

The `maxEmails` value applies independently to each keyword and domain combination. For example, two keywords and three domains create six combinations, with the configured target applied to each combination.

For free users, the Actor applies a maximum result limit of 100 emails when the requested limit is missing or greater than 100. Paid users are not subject to this Actor-level free-tier restriction.

### Input Example

```json
{
  "keywords": [
    "MacBook",
    "smartphone",
    "iPhone seller"
  ],
  "location": "France",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com",
    "@outlook.com"
  ],
  "maxEmails": 20,
  "excludeWords": [
    "crypto",
    "onlyfans"
  ]
}
```

This example searches multiple targeted terms, narrows results to France, checks three email-domain suffixes, targets up to 20 emails for each keyword-domain combination, and skips descriptions containing the specified exclusions.

### Output

Each collected result is added to the Apify dataset using the following structure:

| Field         | Description                                                             |
| ------------- | ----------------------------------------------------------------------- |
| `keyword`     | The keyword that produced the matching search result                    |
| `title`       | Title of the matching search result                                     |
| `description` | Description or search-result snippet containing the indexed information |
| `url`         | URL associated with the search result                                   |
| `email`       | Extracted email address matching the configured domain suffix           |

The dataset is presented as a table with columns for Keyword, Title, Description, URL, and Email.

The Actor also prevents an email address already collected during the run from being added again, helping reduce duplicate records.

### Output Example

```json
{
  "keyword": "MacBook",
  "title": "MacBook - Back Market",
  "description": "Example publicly indexed result containing contact@example.com",
  "url": "https://www.backmarket.com/example",
  "email": "contact@example.com"
}
```

The example values are illustrative. Actual titles, descriptions, URLs, and email addresses depend on the publicly indexed search results available for the keywords and domains used in the run.

### Use Cases

The Back Market Email Scraper can support several research and data-collection workflows where publicly indexed contact information is relevant.

- **Marketplace research** — Build structured datasets around Back Market-related search terms.
- **Business research** — Investigate publicly indexed business and contact information.
- **Lead research** — Identify publicly indexed email addresses associated with relevant search results.
- **Market analysis** — Organize contact and search-result information around specific product or business terms.
- **Product research** — Search for terms related to devices such as smartphones, laptops, computers, and other relevant categories.
- **Geographic research** — Narrow searches to specific countries, states, or cities.
- **Dataset creation** — Build structured collections of email and search-result data for later analysis.
- **Contact analysis** — Review email addresses alongside their associated titles, descriptions, and URLs.

The appropriate use of collected information depends on applicable laws, regulations, website terms, and your intended workflow.

### Advantages

The Actor provides a practical configuration model for targeted Back Market email research.

- Multiple keywords can be processed in one run.
- Email domains can be customized rather than limited to one suffix.
- Geographic filtering is optional.
- Exclusion terms provide control over unwanted descriptions.
- Output fields are simple and consistent.
- The email target can be adjusted from small test runs to larger collection targets within the documented limits.
- Collected email addresses are deduplicated during the run.
- Results are added to the Apify dataset incrementally.

### Limitations

There are several important limitations to understand before starting a large collection.

- Results depend on publicly indexed information available for the search terms.
- An email address is only collected when it appears in the indexed result information and matches the configured domain pattern.
- The requested `maxEmails` value is a target, not a guarantee that that number of addresses will exist.
- Narrow keywords may produce fewer relevant results.
- Adding a location can reduce the available result set because the search becomes more specific.
- Restricting the run to a small number of email domains can also reduce the number of matching addresses.
- Exclusion terms can intentionally remove otherwise matching results when their descriptions contain a configured word or phrase.
- Free users are limited to 100 emails by the Actor when the requested limit exceeds that threshold or is not specified.
- Search availability and indexed content can change over time.

A smaller result count does not necessarily indicate an Actor error; it can simply mean that fewer matching publicly indexed records were available for the selected configuration.

### Pros and Cons

| Pros                                   | Cons                                              |
| -------------------------------------- | ------------------------------------------------- |
| Supports multiple keywords             | Results depend on publicly indexed information    |
| Supports multiple email domains        | A requested target is not guaranteed              |
| Optional location targeting            | Narrow searches may return fewer results          |
| Configurable exclusion terms           | Exclusions can remove otherwise matching snippets |
| Structured Apify dataset output        | Available data can change over time               |
| Duplicate email prevention             | Free users have a 100-email Actor limit           |
| Per-keyword + domain collection target | Results may vary by keyword and domain            |

### Comparison With Alternative Approaches

| Capability                     | Back Market Email Scraper                                      | Manual / Typical Alternative                    |
| ------------------------------ | -------------------------------------------------------------- | ----------------------------------------------- |
| Multiple keyword searches      | Supported                                                      | Often requires repeated manual searches         |
| Multiple email domains         | Supported                                                      | Usually checked separately                      |
| Geographic filtering           | Supported through `location`                                   | Requires manual query refinement                |
| Exclusion filtering            | Supported                                                      | Requires manual review                          |
| Structured output              | Dataset fields for keyword, title, description, URL, and email | Often requires manual collection and formatting |
| Duplicate email handling       | Duplicate addresses are skipped during the run                 | Manual deduplication may be required            |
| Configurable collection target | Supported per keyword + domain combination                     | Usually managed manually                        |

This comparison describes workflow characteristics rather than guaranteeing better results than another method.

### Best Practices

For more useful Back Market contact datasets:

- Start with a small `maxEmails` value to validate your keywords.
- Use specific keywords rather than relying on one broad term.
- Combine related search terms when researching a category.
- Add multiple relevant email domains when broader email coverage is required.
- Use `location` when geographic targeting is important.
- Leave `location` empty when you want broader geographic coverage.
- Use `excludeWords` to remove categories of results that are not relevant to your research.
- Review the first results before launching a larger run.
- Increase the run timeout when configuring a particularly broad search, as the Actor input documentation notes a default timeout of 3600 seconds.
- If results are below your target, try broader or additional keywords, more relevant domains, or a less restrictive location.

### Troubleshooting

**Invalid input:** Make sure `keywords` is supplied as an array of strings. Check that `maxEmails` is an integer between 1 and 10000 when provided.

**Empty results:** Try more specific but related keywords, remove an overly restrictive location, or add additional email-domain suffixes.

**Fewer emails than requested:** `maxEmails` is a target rather than a guarantee. The available indexed results may contain fewer matching email addresses.

**Unexpectedly few results after exclusions:** Review `excludeWords`. A matching word or phrase in a result description causes that entire description to be skipped.

**Location-specific results are sparse:** Try a broader country or city value, or remove the location filter if geographic narrowing is not necessary.

**Duplicate-looking results:** The Actor avoids adding the same email address more than once during the run, even when it can be encountered through multiple searches.

**Partial results:** Search result availability can vary. Review the collected dataset and consider expanding the keyword, domain, or location configuration.

**Run takes longer than expected:** Larger combinations of keywords and domains require more search work. Consider testing a smaller configuration first and increasing the run timeout when appropriate.

### Frequently Asked Questions

**What does the Back Market Email Scraper do?**

It searches for publicly indexed Back Market-related results using your keywords and extracts email addresses that match the email-domain suffixes you configure.

**What data does the Back Market Email Scraper return?**

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

**Can I use multiple keywords?**

Yes. The `keywords` input accepts an array, allowing multiple search terms in the same run.

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

Yes. Use `customDomains` to specify suffixes such as `@gmail.com`, `@yahoo.com`, or `@outlook.com`.

**Can I target a particular location?**

Yes. The optional `location` field accepts a country, state, or city. Leave it blank when geographic filtering is not needed.

**How does `maxEmails` work?**

The configured value applies to each keyword + email-domain combination. For example, three keywords and two domains create six combinations, each with its own collection target.

**Does the Actor guarantee the requested number of emails?**

No. `maxEmails` defines the desired collection target. The Actor can only collect matching addresses that are available in the relevant publicly indexed results.

**Can I exclude unwanted results?**

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

**What happens when the same email appears more than once?**

The Actor tracks collected email addresses and does not add the same address again during the run.

**Why did my run return fewer emails than expected?**

Possible reasons include narrow keywords, restrictive locations, limited email domains, exclusion terms, or a lack of publicly indexed matching results. Try broadening the search configuration and reviewing the results.

**Is this Actor suitable for automated research workflows?**

Yes. It is designed to run as an Apify Actor and produce structured dataset records, making it suitable for repeatable research and data-collection workflows where its output and source information are appropriate for the intended use.

### NLP Keywords

- Back Market email scraper
- Back Market email extraction
- Back Market contact data
- Back Market email finder
- Back Market lead data
- Back Market contact extraction
- Back Market business research
- Back Market profile data
- Back Market search data
- Back Market contact information
- marketplace email scraper
- marketplace contact extraction
- email domain filtering
- keyword-based email extraction
- geographic email search
- structured contact dataset
- public email research
- email lead collection
- search result data extraction
- contact data automation

### Related Keywords

- Back Market email scraper actor
- extract emails from Back Market
- Back Market contact scraper
- Back Market lead scraper
- Back Market business email scraper
- Back Market public email extractor
- Back Market email finder tool
- Back Market contact finder
- Back Market lead generation data
- Back Market business contact research
- Back Market email data extraction
- marketplace lead research
- marketplace business email extraction
- keyword email scraper
- location based email search
- custom domain email scraper
- email research automation
- structured email lead dataset
- public contact data scraper
- Back Market data collection

### Final Overview

Back Market Email Scraper provides a configurable way to collect publicly indexed email addresses associated with Back Market search results. Users can combine multiple keywords, optional geographic targeting, custom email domains, collection targets, and exclusion terms to create structured contact datasets.

The output keeps each email connected to its keyword, title, description, and source URL, providing useful context for research and analysis. Duplicate addresses are avoided during the run, while results are added to the Apify dataset incrementally.

For the most relevant results, begin with a focused set of keywords, test a small collection target, review the returned data, and then expand the configuration with additional terms or domains as needed.

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

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

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

```

## MCP server setup

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