# Ziprecruiter Email Scraper - Keyword & Location Targeting (`scrapido/ziprecruiter-email-scraper`) Actor

💼 ZipRecruiter Email Scraper extracts employer and hiring contact emails by keyword and location. 🔓 Domain filters, obfuscated-address decoding and duplicate handling. 📤 Export ZipRecruiter leads to CSV, JSON or Excel.

- **URL**: https://apify.com/scrapido/ziprecruiter-email-scraper.md
- **Developed by:** [Scrapido](https://apify.com/scrapido) (community)
- **Categories:** Lead generation, Jobs, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.50 / 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 marketers, recruiters, and sales pros quickly find and extract emails from Ziprecruiter without endless manual searching. It’s an email extraction tool designed for ZipRecruiter lead generation—so you can scrape Ziprecruiter emails faster and scale outreach with less guesswork.

***

### 🌟 Key Features of Ziprecruiter Email Scraper

| Feature | Benefit |
|---|---|
| ✅ **Targeted Keyword Search** | Reach the exact Ziprecruiter audience you need using your chosen keywords |
| ✅ **Location Filtering** | Geo-target results by filtering to a specific location for more relevant Ziprecruiter lead generation |
| ✅ **Custom Domain Filter** | Extract only the email domains you care about (e.g. `@gmail.com`, `@yahoo.com`) |
| ✅ **Bulk Export (Dataset Output)** | Each result is saved as a dataset record for easy downstream use |
| ✅ **Proxy-Ready Scraping** | Designed to work reliably at scale using Apify Proxy support |
| ✅ **Real-Time Saving** | Results are pushed incrementally so long runs don’t risk losing progress |
| ✅ **Controlled Result Volume** | Set `maxEmails` to cap scraping time and manage run costs |

***

### 📥 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 | — | A list of keywords or queries used for email extraction from Ziprecruiter |
| `location` | String | No | `""` | Location to filter results, so your contact data is more region-specific |
| `customDomains` | Array | No | `["@gmail.com","@yahoo.com"]` | Email domain filter (for example, `@gmail.com` or `@yahoo.com`) to focus your ZipRecruiter email extractor output |
| `maxEmails` | Integer | No | `20` | Maximum number of emails to collect in a run (helps control scraping time and cost) |

***

### 📤 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, Logistics & Supply Chain",
  "description": "Experienced operations leader focused on logistics optimization and team execution.",
  "url": "https://www.ziprecruiter.com/candidate/jordan-park-ops-manager",
  "email": "jordan.park@gmail.com"
}
```

| Field | Type | Description |
|---|---|---|
| `keyword` | String | The search term that surfaced this lead during your Ziprecruiter email finder run |
| `title` | String | Ziprecruiter profile name or business title associated with the result |
| `description` | String | Profile bio or summary text captured with the lead |
| `url` | String | Direct link to the Ziprecruiter profile where the email was found |
| `email` | String | The extracted email address for contact outreach |

***

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

1. **Open the Actor** — Find **Ziprecruiter Email Scraper** on [Apify Store](https://apify.com/store).
2. **Enter Keywords** — Add job titles, roles, or names you want to target for ZipRecruiter lead generation.
3. **Set Location** *(optional)* — Use `location` to filter results to a specific city or region.
4. **Filter by Domain** *(optional)* — Set `customDomains` to focus on domains like `@gmail.com` or `@yahoo.com`.
5. **Set Max Emails** — Use `maxEmails` to cap the number of emails scraped per run.
6. **Run the Actor** — Start the run and monitor progress in live logs.
7. **Export Results** — Grab your dataset export (JSON/CSV) from the Apify dataset tab.

***

### 💡 Best Use Cases for Ziprecruiter Email Scraper

- 🎯 **B2B Lead Generation** — Build a Ziprecruiter email list for targeted outreach campaigns
- 📣 **Email Marketing** — Enrich sequences with fresh Ziprecruiter contact data
- 🤝 **Recruitment Prospection** — Find relevant professionals for hiring and networking
- 🔬 **Market Research** — Identify industry roles and contact patterns within Ziprecruiter
- 📊 **CRM Enrichment** — Add scraped Ziprecruiter emails to existing lead records

***

### Disclaimer

Ziprecruiter Email Scraper accesses **publicly available data** on Ziprecruiter. It does not scrape private profiles, authenticated content, or password-protected pages. You are responsible for ensuring your use complies with Ziprecruiter’s Terms of Service and applicable privacy and anti-spam laws (including GDPR/CCPA where relevant). For data-removal requests, contact 📧 <scrapidocontact@gmail.com>.

***

### 🆘 Support & Feedback

Need help with the Ziprecruiter Email Scraper or want to request an improvement?

- 🐞 **Bug Reports:** Open a ticket in the repository’s Issues section
- ✨ **Custom Solutions & Feature Requests:** Reach out to our team
- 📧 **Email:** <scrapidocontact@gmail.com>

We’re happy to help—your feedback directly improves the actor.

### Multiple Email Types

**Email Types** replaces the old single Audience Type choice: select as many
kinds of mailbox as you want and the run chases all of them together.

| Type | What it matches |
| --- | --- |
| Personal / free webmail | Gmail, Outlook, Yahoo, iCloud, AOL, Proton, ... |
| Business / corporate | Company domains - free webmail and institutions excluded |
| Education (.edu / .ac) | `.edu`, `.ac.uk`, `.edu.au`, `.ac.in` and other academic suffixes |
| Government (.gov / .mil) | `.gov`, `.mil`, `.gov.uk`, `.gc.ca`, ... |
| Non-profit (.org) | `.org`, `.ngo`, `.org.uk`, ... |

Each selected type contributes its own Google dork patterns *and* its own domain
test, so a result is only kept if it genuinely belongs to the type that found
it. Every row carries an `emailType` field recording which one that was.

Suffixes are matched as real domain suffixes, so `cs.mit.edu` counts as
Education while `notedu.com` does not.

Setting **Custom Email Domains** still overrides everything: an explicit domain
list is a manual override and replaces the type-driven patterns. The legacy
`audienceType` value is still accepted, so saved inputs keep working.

# Actor input Schema

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

A list of keywords or queries to search for.

## `audienceType` (type: `string`):

Business Emails runs contextual discovery patterns tuned for company contact pages ("email us at", "contact@", careers, bookings, ...) and filters out consumer webmail domains. Consumer Emails instead searches gmail.com, yahoo.com, outlook.com, hotmail.com and icloud.com directly.

## `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.

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

Optional manual override — provide specific email domains to search for (e.g. @hubspot.com) instead of using Audience Type. Leave empty to use Audience Type.

## `emailTypes` (type: `array`):

Which kinds of mailbox to hunt for. Pick as many as you like - each type contributes its own set of Google search patterns and its own domain filter, and every result records the type it was found as. Personal = free webmail (Gmail, Outlook, Yahoo, iCloud). Business = company domains, excluding free webmail and institutions. Education = .edu / .ac.uk and friends. Government = .gov / .mil. Non-profit = .org.

## Actor input object example

```json
{
  "keywords": [
    "manager",
    "founder"
  ],
  "audienceType": "Consumer Emails",
  "maxEmails": 20,
  "customDomains": [],
  "emailTypes": [
    "Personal",
    "Business"
  ]
}
```

# 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"
    ],
    "customDomains": [],
    "emailTypes": [
        "Personal",
        "Business"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapido/ziprecruiter-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": [
        "manager",
        "founder",
    ],
    "customDomains": [],
    "emailTypes": [
        "Personal",
        "Business",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("scrapido/ziprecruiter-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": [
    "manager",
    "founder"
  ],
  "customDomains": [],
  "emailTypes": [
    "Personal",
    "Business"
  ]
}' |
apify call scrapido/ziprecruiter-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapido/ziprecruiter-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/ajMovKNzVF7puIoxZ/builds/NDEhhITqh9etO8Oqe/openapi.json