# Ziprecruiter Email Scraper - Domain Filter & Deduplication (`insightflow/ziprecruiter-email-scraper-powerful-and-intelligent`) Actor

💼 ZipRecruiter Email Scraper — turn ZipRecruiter searches into a clean employer email list. Filter by keyword, location and domain, merge aliases and decode hidden addresses. 🧑‍💼 For staffing agencies & HR SaaS sales.

- **URL**: https://apify.com/insightflow/ziprecruiter-email-scraper-powerful-and-intelligent.md
- **Developed by:** [InsightFlow](https://apify.com/insightflow) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.99 / 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.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### Ziprecruiter Email Scraper 🔍

**Ziprecruiter Email Scraper** helps you extract emails from Ziprecruiter quickly and at scale, replacing manual contact hunting with a simple workflow built for marketers, recruiters, and sales pros. It’s a practical ZipRecruiter email extractor for lead generation, a ZipRecruiter contact scraper for public web data, and a faster way to build targeted contact lists. 📬

### 🌟 Key Features of Ziprecruiter Email Scraper

| Feature | Benefit |
|---|---|
| ✅ **Targeted Keyword Search** | Use your chosen keywords to find relevant Ziprecruiter results and focus on the contacts that match your audience. |
| ✅ **Location Filtering** | Add a location to narrow results and improve relevance for regional outreach and research. |
| ✅ **Custom Domain Filter** | Filter by email domains such as `@gmail.com` or `@yahoo.com` to shape the results to your needs. |
| ✅ **Max Emails Limit** | Set a cap on how many emails to collect, helping you control run time and scraping costs. |
| ✅ **Real-Time Saving** | Results are saved as they are found, so you don’t lose progress during longer runs. |
| ✅ **Resume Support** | The actor can continue from saved progress, which is useful for larger recruitment data scraping jobs. |
| ✅ **Public Data Extraction** | Collects emails from publicly available sources without requiring manual review. |

### 📥 Input — Ziprecruiter Email Scraper Parameters

```json
{
  "keywords": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20
}
```

| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| `keywords` | Array | ✅ Yes | `["manager","founder"]` | A list of keywords or queries used to find relevant Ziprecruiter results. |
| `location` | String | No | `""` | An optional location filter to narrow the results by area. |
| `customDomains` | Array | No | `["@gmail.com","@yahoo.com"]` | Email domains to include when collecting contacts, such as personal or company domains. |
| `maxEmails` | Integer | No | `20` | The maximum number of emails to collect before the actor stops. |

### 📤 Output — What Ziprecruiter Email Scraper Returns

The actor saves each result as a JSON record in your Apify dataset.

```json
[
  {
    "keyword": "manager",
    "title": "Operations Manager",
    "description": "Experienced operations leader focused on team performance, process improvement, and cross-functional coordination.",
    "url": "https://www.ziprecruiter.com/candidate/jane-smith",
    "email": "jane.smith@gmail.com"
  }
]
```

| Field | Label | Format | Description |
|---|---|---|---|
| `keyword` | Keyword | text | The keyword that produced the result. |
| `title` | Title | text | The result title shown for the Ziprecruiter profile or listing. |
| `description` | Description | text | The extracted description associated with the result. |
| `url` | Url | link | The public URL linked to the result. |
| `email` | Email | text | The email address found in the public content. |

### 💻 How to Use Ziprecruiter Email Scraper — Step-by-Step

1. **Open the actor** — Find **Ziprecruiter Email Scraper** on Apify and open the actor page.
2. **Enter keywords** — Add job titles, roles, or other terms you want to use for ZipRecruiter profile scraper searches.
3. **Set a location** — Optionally narrow the search to a city or region for more relevant recruitment prospecting tool results.
4. **Choose email domains** — Add one or more domains to focus on the contacts you want.
5. **Set the max email limit** — Control how many results are collected in each run.
6. **Run the actor** — Start the task and monitor the live log output.
7. **Export the dataset** — Download your ZipRecruiter lead generation results from the dataset tab.

*No coding required. Results are ready in minutes.* 🚀

### 💡 Best Use Cases for Ziprecruiter Email Scraper

- 🎯 **B2B Lead Generation** — Build contact lists for outreach using relevant job and talent acquisition leads.
- 📣 **Email Marketing** — Create focused email lists for campaigns and follow-ups.
- 🤝 **Recruitment Outreach** — Find public contact details for recruiting prospecting tool workflows.
- 🔬 **Market Research** — Study public employment data scraping signals and role trends.
- 📊 **CRM Enrichment** — Add public contact details to existing lead records for faster action.

### Disclaimer

This actor only accesses **publicly available data** on Ziprecruiter. It does not access private profiles, authenticated content, or password-protected pages. Users are solely responsible for ensuring their use complies with Ziprecruiter’s Terms of Service, GDPR, CCPA, and applicable anti-spam laws. This tool is intended for legitimate purposes only, including lead generation, research, and marketing in compliance with local regulations. For data-removal requests, contact 📧 <insightflowofficial@gmail.com>.

### 🆘 Support & Feedback

Have a question or found an issue with the **Ziprecruiter Email Scraper**? We’re here to help.

- 🐞 **Bug Reports:** Share the issue with our team so we can investigate it.
- ✨ **Custom Solutions & Feature Requests:** Send your ideas for improvements or tailored workflows.
- 📧 **Email:** <insightflowofficial@gmail.com>

Your feedback helps improve the actor for everyone.

### MX Lookup

Every address is checked at the DNS level: the actor resolves the mail domain's
MX records and reports what it found.

| Field | Meaning |
| --- | --- |
| `mxFound` | `true` when the domain publishes at least one mail server |
| `mxHost` | The lowest-preference (primary) mail server |
| `mxRecords` | Every MX record found, in preference order |
| `mxProvider` | Who runs the mail: Google Workspace, Microsoft 365, Zoho, Proton, ... |
| `mxStatus` | `found`, `no_records`, `no_such_domain`, `timeout`, `error`, or `skipped` |

**Inputs**

- **MX Lookup** - turn the check on or off (default: on).
- **Only keep contacts whose domain has an MX record** - drop unreachable domains.
  Only a definite negative (`no_records` / `no_such_domain`) drops a contact; a
  timeout or resolver error is treated as unknown and the lead is kept.
- **MX lookup timeout (seconds)** - per-domain DNS budget, 1-15s.

This is a domain-level check. It confirms the domain can receive mail; it does
not verify that an individual mailbox exists.

# Actor input Schema

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

A list of keywords or queries to search for.

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

Location to filter search results.

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

List of custom email domains

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

Maximum number of emails to collect. The scraper will stop once this limit is reached. Setting a higher limit allows for more potential results but doesn't guarantee reaching that number. This helps save costs by controlling scraping time.

## `minLeadScore` (type: `integer`):

Drop any contact whose Lead Score (0-100) falls below this. Leave at 0 for no filter.

## `mxLookup` (type: `boolean`):

Resolve each address's domain to its mail servers. Adds the resolved MX hosts and the mail provider (Google Workspace, Microsoft 365, ...) to every result, and feeds the Lead Score. DNS-level only - it confirms the domain can receive mail, not that the individual mailbox exists.

## `requireMxRecord` (type: `boolean`):

Drop any contact whose domain provably accepts no mail. A lookup that times out or errors is treated as unknown and kept, so a DNS hiccup never silently deletes good leads.

## `mxTimeoutSecs` (type: `integer`):

How long to wait for each DNS answer. Clamped to 1-15 seconds.

## Actor input object example

```json
{
  "keywords": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "minLeadScore": 0,
  "mxLookup": true,
  "requireMxRecord": false,
  "mxTimeoutSecs": 3
}
```

# 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": [
        "manager",
        "founder"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("insightflow/ziprecruiter-email-scraper-powerful-and-intelligent").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": [
        "manager",
        "founder",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("insightflow/ziprecruiter-email-scraper-powerful-and-intelligent").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": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ]
}' |
apify call insightflow/ziprecruiter-email-scraper-powerful-and-intelligent --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,insightflow/ziprecruiter-email-scraper-powerful-and-intelligent"
        }
    }
}

```

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/X9XkQqTuHyiIdwSaV/builds/KkJrrU9uRmgdrenXp/openapi.json