# Kayak Email Scraper - Keyword Search & Domain Filter (`parse-point/kayak-email-scraper-lightning-fast-and-accurate`) Actor

🧭 Kayak Email Scraper extracts travel supplier and agency emails using keyword and location filters. 🎯 Domain restriction, decoding and duplicate skipping. ✈️ Fast Kayak lead generation for travel tech sales.

- **URL**: https://apify.com/parse-point/kayak-email-scraper-lightning-fast-and-accurate.md
- **Developed by:** [Parse Point](https://apify.com/parse-point) (community)
- **Categories:** Lead generation, Travel, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.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/platform/actors/running/actors-in-store#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

### Kayak Email Scraper 🔍

**Kayak Email Scraper** helps you extract emails from Kayak using targeted keywords, making manual email hunting much faster for marketers, recruiters, and sales pros. It’s built for Kayak lead generation, contact discovery automation, and scalable travel lead generation when you need public web data at speed. 🚀

### 🌟 Key Features of Kayak Email Scraper

| Feature | Benefit |
|---|---|
| ✅ **Targeted Keyword Search** | Uses your keywords to focus on relevant Kayak listings data extraction and prospect email finder workflows. |
| ✅ **Custom Email Domain Filtering** | Lets you narrow results to specific domains like `@gmail.com` or `@yahoo.com` for more precise email harvesting. |
| ✅ **Location Filtering** | Add a location to refine travel website scraper results for more relevant travel agency prospects. |
| ✅ **Max Email Limit** | Caps the total number of emails collected so you can control cost and run time. |
| ✅ **Real-Time Saving** | Saves results incrementally, helping prevent data loss during longer travel website scraper runs. |
| ✅ **Public Web Data Extraction** | Collects emails from publicly available sources only, supporting ethical travel leads database building. |
| ✅ **Built-In Proxy Support** | Includes built-in proxy support for more reliable scraping and fewer interruptions. |

### 📥 Input — Kayak 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 to search for. These help the actor find relevant results for kayak email extraction. |
| `location` | String | No | `""` | Location to filter search results. Leave it empty if you want broader coverage. |
| `customDomains` | Array | No | `["@gmail.com", "@yahoo.com"]` | List of custom email domains to focus your email extraction on specific address types. |
| `maxEmails` | Integer | No | `20` | Maximum number of emails to collect. The actor stops once this limit is reached. |

### 📤 Output — What Kayak Email Scraper Returns

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

```json
{
  "keyword": "founder",
  "title": "Founder & CEO",
  "description": "Contact the team for partnership opportunities and travel solutions. Email: hello@alpinetravelco.com",
  "url": "https://www.kayak.com/travel/partners/alpine-travel-co",
  "email": "hello@alpinetravelco.com"
}
```

| Field | Label | Format | Description |
|---|---|---|---|
| `keyword` | Keyword | text | The keyword that produced the record. |
| `title` | Title | text | The result title associated with the public listing or page. |
| `description` | Description | text | The visible description text from the result. |
| `url` | Url | link | The URL of the public page where the result was found. |
| `email` | Email | text | The extracted email address. |

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

1. **Open the Actor** — Find Kayak Email Scraper in the Apify Store and open its input form.
2. **Enter Keywords** — Add the terms you want to use for finding relevant public travel contacts.
3. **Set Location** — Optionally add a location to narrow your travel website scraper results.
4. **Filter by Domain** — Add one or more email domains to improve kayak email extraction quality.
5. **Set Max Emails** — Choose how many emails you want to collect in this run.
6. **Run the Actor** — Start the actor and monitor the live logs as results are collected.
7. **Export Results** — Download the dataset when the run finishes and use it in your CRM or research workflow.

*No coding required. Results ready in minutes.*

### 💡 Best Use Cases for Kayak Email Scraper

- 🎯 **B2B Lead Generation** — Build targeted travel leads database lists for outreach campaigns.
- 📣 **Email Marketing** — Gather public contacts for newsletters, promotions, and follow-ups.
- 🤝 **Travel Agency Prospects** — Find public contact information for travel-related outreach and partnerships.
- 🔬 **Market Research** — Study publicly available travel website scraper results for trend analysis.
- 📊 **CRM Enrichment** — Add public email contacts to existing records for better prospect email finder workflows.

### Disclaimer

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

### 🆘 Support & Feedback

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

- 🐞 **Bug Reports:** Let us know what happened so we can investigate.
- ✨ **Custom Solutions & Feature Requests:** Reach out with ideas for travel lead generation and contact discovery automation.
- 📧 **Email:** <helloparsepoint@gmail.com>

Your feedback shapes the roadmap — we read every message.

### Run Memory

**Skip keywords already scraped in a previous run** - the actor keeps a
persistent record of every keyword it finishes, in a named key-value store that
survives between runs. Turn this on and a repeat run silently drops the keywords
it has already covered, so a scheduled job over a fixed list only pays for new
ground.

A keyword is identified by the keyword *plus* the set of email domains it was
searched against, so re-running `fitness` against a new domain list is correctly
treated as new work rather than a duplicate.

**Reset keyword history** - wipe that record before the run starts, so
everything counts as new again.

**Max emails per keyword** - cap how many results any single keyword may
produce before the actor moves on to the next one. Stops one broad term from
consuming the entire run budget. `0` means no per-keyword limit.

These sit alongside the existing address-level deduplication: *Skip previous
runs* prevents re-pushing an individual mailbox, while *Skip duplicate keywords*
prevents re-running the search at all.

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

## `decodeProtectedEmails` (type: `boolean`):

Read addresses the page hides behind Cloudflare protection or HTML entities. These are invisible to a plain text scan.

## `decodeWrittenEmails` (type: `boolean`):

Read addresses written to defeat scrapers, such as 'name \[at] example \[dot] com'.

## `decodeEncodedEmails` (type: `boolean`):

Read addresses stored base64-encoded in the page markup.

## `mergeAliasDuplicates` (type: `boolean`):

Collapse different spellings that reach the same inbox (e.g. j.o.h.n+news@gmail.com and john@gmail.com) into a single result, so you are not billed twice for one lead.

## `skipPreviousRuns` (type: `boolean`):

Do not return leads that an earlier run of this Actor already returned. Skipped leads are never charged.

## `duplicateHandling` (type: `string`):

What to do when several spellings reach the same inbox: merge them into one result, keep them apart but flag them, or keep everything as found.

## `skipDuplicateKeywords` (type: `boolean`):

Remember every keyword this actor completes and skip it next time. Ideal for a scheduled run over a fixed keyword list - you only pay for ground you have not covered. A keyword searched against a different set of email domains counts as new work, not a duplicate.

## `resetKeywordHistory` (type: `boolean`):

Clear the remembered keywords before this run starts, so everything is treated as new again. Use after changing your target list.

## `maxEmailsPerKeyword` (type: `integer`):

Stop collecting for a keyword once it has produced this many results, then move on to the next one. Keeps one broad term from consuming the whole run. Leave at 0 for no per-keyword limit.

## Actor input object example

```json
{
  "keywords": [
    "business",
    "travel agent"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "decodeProtectedEmails": true,
  "decodeWrittenEmails": true,
  "decodeEncodedEmails": true,
  "mergeAliasDuplicates": true,
  "skipPreviousRuns": false,
  "duplicateHandling": "merge",
  "skipDuplicateKeywords": false,
  "resetKeywordHistory": false,
  "maxEmailsPerKeyword": 0
}
```

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

// Run the Actor and wait for it to finish
const run = await client.actor("parse-point/kayak-email-scraper-lightning-fast-and-accurate").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": [
        "business",
        "travel agent",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("parse-point/kayak-email-scraper-lightning-fast-and-accurate").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": [
    "business",
    "travel agent"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ]
}' |
apify call parse-point/kayak-email-scraper-lightning-fast-and-accurate --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,parse-point/kayak-email-scraper-lightning-fast-and-accurate"
        }
    }
}

```

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/Ax5d13pQKrdYcWiWh/builds/JTMyLW83LLehSPoN7/openapi.json