# Booking.com Email Scraper (`leads-scraper/booking-com-email-scraper`) Actor

Booking.com Email Scraper SD - Booking.com Email Scraper is a lead generation tool that extracts leads with public contact emails, account names and profile URLs from Booking.com results by keyword, location and email domain - Booking.com email extractor.

- **URL**: https://apify.com/leads-scraper/booking-com-email-scraper.md
- **Developed by:** [Leads Scraper](https://apify.com/leads-scraper) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.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

### Booking.com Email Scraper — public property contact emails from Google

The **Booking.com Email Scraper** builds a deduplicated list of publicly indexed property contact
emails from Booking.com pages, together with the account label, name and snippet that Google prints
alongside them. It is aimed at hospitality-tech vendors, hotel suppliers and OTA supply teams.

One caveat shapes every run, so the Booking.com Email Scraper states it first. Booking.com routes
guest contact through its own messaging and indexes city and search pages heavily, so most rows
carry a property email without a resolvable property handle.

That is a shape, not a failure. In measured live runs, roughly every 10 parsed results returned
about 2 rows with an identity, 1 profile URL and 7 unique emails — plenty of reservation addresses,
few clean handles.

The Booking.com Email Scraper never logs in, never opens the Booking.com website and never touches
a Booking.com API. Every field comes from Google's public index: result titles, snippets and the
site label beside them.

#### Who the Booking.com Email Scraper is for

Property management systems, channel managers and revenue-management vendors use it to find hotels
and guest houses that publish a reservations address. Hotel suppliers — linen, amenities, F\&B,
furniture — use it to reach independent properties in one destination.

OTA supply teams recruiting new properties, destination marketing organisations mapping local
accommodation stock, and travel PR teams pitching to hotels are the other regular users. Properties
publish reservation and group-booking addresses deliberately, so treat outreach as a trade approach.

#### Why a live search beats a static hotel email list

A bought "hotel owner email list" is fixed on the day it is sold. The Booking.com Email Scraper runs
a fresh Google search against the keywords and email domains you choose, so the hotel leads it
returns reflect what is publicly indexed right now.

Re-run it quarterly for a market and new independent properties appear as they publish contact
details. That makes the Booking.com Email Scraper a hospitality prospecting instrument rather than
a one-off purchase.

***

### Key features of the Booking.com Email Scraper

Everything below is code that ships in the Booking.com Email Scraper today, not a roadmap.

| Feature | What it does |
|---|---|
| Google `site:` targeting | Searches `booking.com`, including its heavily localised path structure |
| Query expansion | Base, quoted, `intitle:` and one variant per query modifier; base queries run first |
| Global deduplication | Each email is emitted once across every query and every page |
| Email normalisation | Case-insensitive; handles `name [at] domain [dot] com`, `(at)`, `name @ domain.com`, `domain .com`, zero-width characters and the full-width `＠` |
| Junk filter | Rejects placeholders such as `email@`, `yourname@`, `test@`, `xxx@` and single-character locals |
| Boundary-correct matching | `@gmail.com` does not match inside `@gmail.company` or `@gmail.com.br` |
| Soft-wrap repair | Drops a hit that is only the tail of another email in the same block |
| Structural parsing | Locates the `<h3>` title then the smallest surrounding block, instead of relying on Google CSS class names |
| Whole-page fallback | If Google's markup changes, the run degrades to "emails without account details", not "no emails" |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried, not counted as empty |
| Retries | Up to 3 attempts per page, exponential backoff, fresh proxy session per request |
| Requeue | Blocked or failed queries are re-queued once at the end of the run |
| Concurrency | `asyncio` worker pool with a shared stop signal on `maxEmails` |
| Resumable state | Progress is stored in the key-value store, keyed by a hash of the input, and saved on `PERSIST_STATE`, `MIGRATING` and `ABORTING` |
| Run summary | Logs pages fetched, blocked pages, retries and emails per page |

***

### How the Booking.com Email Scraper works

The pipeline is short and fully inspectable. The Booking.com Email Scraper reads your input, builds
Google queries with the `site:` operator, fetches result pages through the Apify **GOOGLE\_SERP**
proxy using `aiohttp`, and parses each result block structurally.

Emails are extracted from the block text with a domain-filtered regular expression, normalised,
deduplicated globally and pushed to the Apify dataset immediately. There is no browser, no
JavaScript rendering, no authentication and no cookies.

A base query looks like this, with your keyword and one of your email domains:

```
site:booking.com hotel "@gmail.com" "Lisbon"
```

#### Query expansion inside the Booking.com Email Scraper

Google caps a single query at roughly 300 results, so pagination depth alone can never fill a large
list. Coverage in the Booking.com Email Scraper comes from query diversity, which is why
`expandQueries` defaults to `true`.

Each keyword × domain pair runs as a base query, a quoted query, an `intitle:` query, and one extra
query per entry in `queryModifiers`. The Booking.com defaults are `email`, `contact`, `reservations`,
`group bookings` and `owner`.

Base queries always run first, so a short run with a low `maxEmails` finishes on the strongest
phrasings. Because deduplication is global, expansion can only add property leads, never repeat them.

#### Destination-led prospecting with location and countryCode

`location` is a genuine lever. The phrase you supply is quoted and appended to every query, so
`"Amsterdam"` or `"Costa Brava"` narrows the whole Booking.com Email Scraper run to one
accommodation market.

`countryCode` points the search proxy at a two-letter country such as `US`, `GB`, `NL` or `ID`,
which changes which localised Booking.com pages Google surfaces. Pairing a city in `location` with
its country in `countryCode` is the most reliable way to build a market-by-market hotel list.

***

### Input fields of the Booking.com Email Scraper

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["hotel", "guest house"]` | Search terms describing the Booking.com pages you want |
| `location` | string | `""` | Optional location phrase added to every query |
| `customDomains` | array | `["@gmail.com", "@yahoo.com"]` | Only emails on these domains are kept; the `@` is optional |
| `maxEmails` | integer 1–10000 | `20` | Stop after this many unique emails |
| `countryCode` | string | `""` | Two-letter country for the search proxy (US, GB, DE…) |
| `expandQueries` | boolean | `true` | Search each keyword × domain pair in several phrasings |
| `queryModifiers` | array | `["email", "contact", "reservations", "group bookings", "owner"]` | Extra words combined with each keyword when expansion is on |
| `maxPagesPerQuery` | integer 1–50 | `30` | Page cap per query |
| `maxConcurrency` | integer 1–20 | `5` | Parallel queries |

#### Example input for the Booking.com Email Scraper

```json
{
  "keywords": ["hotel", "guest house", "boutique hotel"],
  "location": "Amsterdam",
  "customDomains": ["@gmail.com", "@yahoo.com", "@hotmail.com"],
  "maxEmails": 250,
  "countryCode": "NL",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "reservations", "group bookings", "owner"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

Independent hotels and guest houses very often publish a free-mail reservations address, which is
why the defaults work well here. Add `@hotmail.com` or a country domain to widen the catch.

***

### Output fields of the Booking.com Email Scraper

Every dataset item the Booking.com Email Scraper pushes carries all fourteen fields below — no
optional keys, no schema drift between runs.

| Field | Meaning |
|---|---|
| `network` | Platform name |
| `keyword` | The keyword that produced the lead |
| `query` | The exact Google query used |
| `title` | Raw result title |
| `accountName` | Account label Google prints (handle or property name) |
| `fullName` | Display name parsed from a profile-style title; empty for search and city pages |
| `username` | URL-safe handle when Booking.com exposes one; otherwise `null` |
| `profileUrl` | Canonical property URL when a handle is known; otherwise empty |
| `url` | Direct Booking.com link when exposed, else the profile URL |
| `description` | Snippet text, cleaned of labels and counters |
| `email` | Lower-cased email address |
| `emailDomain` | The matched domain (e.g. `@gmail.com`) |
| `possiblyTruncated` | `true` when Google's snippet ellipsis touched the email |
| `foundAt` | ISO 8601 UTC timestamp |

#### Example output from the Booking.com Email Scraper

```json
[
  {
    "network": "Booking.com",
    "keyword": "hotel",
    "query": "site:booking.com hotel reservations \"@gmail.com\" \"Amsterdam\"",
    "title": "Canal View Hotel, Amsterdam - Booking.com",
    "accountName": "nl/canal-view",
    "fullName": "Canal View Hotel",
    "username": "nl/canal-view",
    "profileUrl": "https://www.booking.com/hotel/nl/canal-view.html",
    "url": "https://www.booking.com/hotel/nl/canal-view.html",
    "description": "Family-run canal hotel. Reservations: canalview.reservations@gmail.com",
    "email": "canalview.reservations@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T10:02:18Z"
  },
  {
    "network": "Booking.com",
    "keyword": "guest house",
    "query": "site:booking.com guest house group bookings \"@yahoo.com\" \"Amsterdam\"",
    "title": "Guest houses in Amsterdam - Booking.com",
    "accountName": "Guest houses in Amsterdam",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "https://www.booking.com/city/nl/amsterdam.html",
    "description": "Group bookings for De Oude Gracht guest house: deoudegracht@yahoo.com",
    "email": "deoudegracht@yahoo.com",
    "emailDomain": "@yahoo.com",
    "possiblyTruncated": true,
    "foundAt": "2026-08-31T10:02:41Z"
  }
]
```

The second row is the common case on this platform. It came from a city page, so `username` is
`null` and `profileUrl` is empty — the email is still usable, but the Booking.com Email Scraper
cannot attach a property handle to it, and `possiblyTruncated` warns the address may be cut short.

***

### Use cases for the Booking.com Email Scraper

| Use case | How the Booking.com Email Scraper helps |
|---|---|
| PMS and channel manager sales | Find independent hotels publishing a reservations address |
| Direct-booking tool outreach | Reach properties that already promote direct enquiries |
| Hotel supplier prospecting | Build a destination list for linen, amenity and F\&B vendors |
| OTA supply recruitment | Source guest houses and small hotels not yet on your marketplace |
| Group and MICE sales | Target properties advertising a group-bookings inbox |
| Destination marketing | Map accommodation stock for a DMO or tourism board campaign |
| Travel PR and media | Contact hotels that publish a press or enquiries address |
| Hospitality market research | Sample how properties in a city present contact information |

#### Worked example: a city-level hotel contact list

Set `keywords` to `["hotel", "guest house", "apartment"]`, `location` to `"Porto"` and `countryCode`
to `PT`. Leave expansion on, raise `maxEmails` to 300 and let the Booking.com Email Scraper clear
the base queries before the modifier variants.

#### Worked example: group-bookings prospecting

Trim `queryModifiers` to `["group bookings", "reservations", "email"]` and keep `keywords` to
`["hotel"]`. The Booking.com Email Scraper then concentrates on the pages where properties advertise
an inbox for group enquiries.

***

### Expected results from the Booking.com Email Scraper

In live measurement, about 10 results parsed by the Booking.com Email Scraper produced roughly
2 identity rows, 1 profile URL and 7 unique emails. Email volume is solid; handle resolution is the
weakest part of this platform.

Plan your workflow around the email as the primary key and treat `profileUrl` as a bonus. Yield
still varies with keywords, email domains and location, and no volume is guaranteed.

***

### Limitations of the Booking.com Email Scraper

- **Booking.com routes guest contact through its own messaging and indexes city and search pages
  heavily**, so most rows carry a property email without a resolvable property handle.
- Only properties whose email is **publicly visible in Google's index** can be found by the
  Booking.com Email Scraper.
- Google caps a single query at roughly 300 results, which is exactly why query expansion exists.
- `possiblyTruncated: true` means Google's snippet ellipsis may have cut the address — verify it.
- `username` and `profileUrl` are populated only when Google's result exposes a handle. Many rows
  carry `accountName` with an empty handle. That is a Google limitation, not a bug.
- The Booking.com Email Scraper requires the Apify **GOOGLE\_SERP** proxy and cannot run without
  Apify proxy credentials.
- Free Apify plans are capped at 100 emails per run; paid plans are uncapped.
- Results vary with keywords, domains and location, and no volume is guaranteed.

#### Responsible use and GDPR

Addresses returned by the Booking.com Email Scraper are business contact points that properties
published for reservations and group enquiries, so treat them as B2B outreach data. Identify
yourself, say why you are writing and honour opt-outs immediately.

Under GDPR and comparable regimes you need a lawful basis — usually legitimate interest — plus a
transparent privacy notice and a working unsubscribe path. Do not repurpose hotel contact data for
unrelated consumer marketing.

***

### FAQ about the Booking.com Email Scraper

#### How many results should I expect from the Booking.com Email Scraper?

In measured live runs, roughly every 10 parsed results gave about 2 identity rows, 1 profile URL and
7 unique emails. Volume is never guaranteed and moves with keywords, domains and location.

#### Why do so few rows have a `username` or `profileUrl`?

Booking.com routes guest contact through its own messaging and Google indexes its city and search
pages heavily, so many results are not individual property pages. Those rows still carry an email,
just no resolvable handle.

#### Does the Booking.com Email Scraper log in or use the Booking.com API?

No. The Booking.com Email Scraper does not log in, does not open the Booking.com website and does
not use any Booking.com API. All data comes from publicly indexed Google search results.

#### Which email domains should I use?

Start with `@gmail.com` and `@yahoo.com`, then add `@hotmail.com`, `@outlook.com` or a country
domain. Every extra domain multiplies the queries the Booking.com Email Scraper runs.

#### Can I limit the Booking.com Email Scraper to one city or country?

Yes. `location` appends a quoted phrase to every query and `countryCode` sets the proxy's two-letter
country, which together give destination-led hotel prospecting.

#### Do I need a proxy to run the Booking.com Email Scraper?

Yes. It runs through the Apify GOOGLE\_SERP proxy and cannot operate without Apify proxy credentials.

#### What does `possiblyTruncated` mean?

It flags a row where Google's snippet ellipsis touched the email, so the address may be incomplete.
Verify those rows before you send anything.

#### How do I get more property emails?

Keep `expandQueries` on, add keywords such as `apartment`, `hostel` or `bed and breakfast`, add more
email domains, raise `maxEmails`, and run several narrow city runs rather than one global run.

#### Is there a free-plan limit on the Booking.com Email Scraper?

Free Apify plans stop at 100 emails per run. Paid plans are uncapped, subject to Google's own
per-query ceiling.

#### Can I resume an interrupted Booking.com Email Scraper run?

Yes. Progress is stored in the key-value store keyed by a hash of your input and saved on Apify's
`PERSIST_STATE`, `MIGRATING` and `ABORTING` events.

#### Are the emails verified?

No. The Booking.com Email Scraper reports what Google's index shows, lower-cased and normalised.
Run your own validation before a campaign, especially on rows flagged `possiblyTruncated`.

#### Is the Booking.com Email Scraper affiliated with Booking.com?

No. It is an independent tool that reads public Google search results and is not endorsed by or
connected to Booking.com.

***

### Related Actors

Every Actor below runs the same engine against a different Travel, Hospitality & Food platform.
For broader accommodation coverage, pair this with the [Tripadvisor Hotels Email
Scraper](https://apify.com/leads-scraper/tripadvisor-hotels-email-scraper) and the [Airbnb
Email Scraper](https://apify.com/leads-scraper/airbnb-email-scraper).

For budget stock add the [Hostelbookers Email Scraper](https://apify.com/leads-scraper/hostelbookers-email-scraper);
in Southeast Asia and the Middle East the [Traveloka Email Scraper](https://apify.com/leads-scraper/traveloka-email-scraper)
and [Wego Email Scraper](https://apify.com/leads-scraper/wego-email-scraper) cover regional inventory.

The [HotelsCombined Email Scraper](https://apify.com/neuro-scraper/hotelscombined-email-scraper) adds a
metasearch angle on top.

| Actor | What it collects |
|---|---|
| [Booking.com Email and Phone Number Scraper](https://apify.com/leads-scraper/booking-com-email-and-phone-number-scraper) | Emails and phone numbers from Booking.com |
| [Booking.com Phone Number Scraper](https://apify.com/leads-scraper/booking-com-phone-number-scraper) | Public phone numbers from Booking.com |
| [Airbnb Email Scraper](https://apify.com/leads-scraper/airbnb-email-scraper) | Public contact emails from Airbnb |
| [Caviar Email Scraper](https://apify.com/neuro-scraper/caviar-email-scraper) | Public contact emails from Caviar |
| [ChowNow Email Scraper](https://apify.com/neuro-scraper/chownow-email-scraper) | Public contact emails from ChowNow |
| [Contiki Email Scraper](https://apify.com/neuro-scraper/contiki-email-scraper) | Public contact emails from Contiki |
| [Craigslist Email Scraper](https://apify.com/leads-scraper/craigslist-email-scraper) | Public contact emails from Craigslist |
| [Delivery.com Email Scraper](https://apify.com/neuro-scraper/delivery-com-email-scraper) | Public contact emails from Delivery.com |
| [DoorDash Email Scraper](https://apify.com/leads-scraper/doordash-email-scraper) | Public contact emails from DoorDash |
| [EatStreet Email Scraper](https://apify.com/neuro-scraper/eatstreet-email-scraper) | Public contact emails from EatStreet |
| [G Adventures Email Scraper](https://apify.com/neuro-scraper/g-adventures-email-scraper) | Public contact emails from G Adventures |
| [GetYourGuide Email Scraper](https://apify.com/leads-scraper/getyourguide-email-scraper) | Public contact emails from GetYourGuide |
| [Grubhub Email Scraper](https://apify.com/leads-scraper/grubhub-email-scraper) | Public contact emails from Grubhub |
| [Hostelbookers Email Scraper](https://apify.com/leads-scraper/hostelbookers-email-scraper) | Public contact emails from Hostelworld |
| [HotelsCombined Email Scraper](https://apify.com/neuro-scraper/hotelscombined-email-scraper) | Public contact emails from HotelsCombined |
| [Intrepid Travel Email Scraper](https://apify.com/neuro-scraper/intrepid-travel-email-scraper) | Public contact emails from Intrepid Travel |
| [Just Eat Email Scraper](https://apify.com/leads-scraper/just-eat-email-scraper) | Public contact emails from Just Eat |
| [Klook Email Scraper](https://apify.com/neuro-scraper/klook-email-scraper) | Public contact emails from Klook |
| [OpenTable Email Scraper](https://apify.com/neuro-scraper/opentable-email-scraper) | Public contact emails from OpenTable |
| [Resy Email Scraper](https://apify.com/leads-scraper/resy-email-scraper) | Public contact emails from Resy |
| [TheFork Email Scraper](https://apify.com/leads-scraper/thefork-email-scraper) | Public contact emails from TheFork |
| [Toast Restaurant Email Scraper](https://apify.com/leads-scraper/toast-restaurant-email-scraper) | Public contact emails from Toast |
| [TourRadar Email Scraper](https://apify.com/leads-scraper/tourradar-email-scraper) | Public contact emails from TourRadar |
| [Traveloka Email Scraper](https://apify.com/leads-scraper/traveloka-email-scraper) | Public contact emails from Traveloka |
| [Tripadvisor Attractions Email Scraper](https://apify.com/leads-scraper/tripadvisor-attractions-email-scraper) | Public contact emails from Tripadvisor |
| [Tripadvisor Hotels Email Scraper](https://apify.com/leads-scraper/tripadvisor-hotels-email-scraper) | Public contact emails from Tripadvisor |
| [Tripadvisor Restaurants Email Scraper](https://apify.com/leads-scraper/tripadvisor-restaurants-email-scraper) | Public contact emails from Tripadvisor |
| [Uber Eats Email Scraper](https://apify.com/leads-scraper/uber-eats-email-scraper) | Public contact emails from Uber Eats |
| [Viator Email Scraper](https://apify.com/leads-scraper/viator-email-scraper) | Public contact emails from Viator |
| [Wanderlog Email Scraper](https://apify.com/leads-scraper/wanderlog-email-scraper) | Public contact emails from Wanderlog |
| [Wego Email Scraper](https://apify.com/leads-scraper/wego-email-scraper) | Public contact emails from Wego |
| [Zomato Email Scraper](https://apify.com/leads-scraper/zomato-email-scraper) | Public contact emails from Zomato |
| [Airbnb Email and Phone Number Scraper](https://apify.com/leads-scraper/airbnb-email-and-phone-number-scraper) | Emails and phone numbers from Airbnb |
| [Caviar Email and Phone Number Scraper](https://apify.com/neuro-scraper/caviar-email-and-phone-number-scraper) | Emails and phone numbers from Caviar |
| [ChowNow Email and Phone Number Scraper](https://apify.com/neuro-scraper/chownow-email-and-phone-number-scraper) | Emails and phone numbers from ChowNow |
| [Contiki Email and Phone Number Scraper](https://apify.com/neuro-scraper/contiki-email-and-phone-number-scraper) | Emails and phone numbers from Contiki |
| [Craigslist Email and Phone Number Scraper](https://apify.com/leads-scraper/craigslist-email-and-phone-number-scraper) | Emails and phone numbers from Craigslist |
| [Delivery.com Email and Phone Number Scraper](https://apify.com/neuro-scraper/delivery-com-email-and-phone-number-scraper) | Emails and phone numbers from Delivery.com |
| [DoorDash Email and Phone Number Scraper](https://apify.com/leads-scraper/doordash-email-and-phone-number-scraper) | Emails and phone numbers from DoorDash |
| [EatStreet Email and Phone Number Scraper](https://apify.com/neuro-scraper/eatstreet-email-and-phone-number-scraper) | Emails and phone numbers from EatStreet |
| [G Adventures Email and Phone Number Scraper](https://apify.com/neuro-scraper/g-adventures-email-and-phone-number-scraper) | Emails and phone numbers from G Adventures |
| [Grubhub Email and Phone Number Scraper](https://apify.com/neuro-scraper/grubhub-email-and-phone-number-scraper) | Emails and phone numbers from Grubhub |

### Leave a review

If the Booking.com Email Scraper saved you time, please leave a star rating and a short review
on the Actor page.

Reviews are how other buyers judge whether a tool works, and they tell us which features to
build next.

If something did not work, email <neurodata.apify@gmail.com>
instead - bugs get fixed faster than they get complained about.

### Support

Questions, a bug, or a custom build of the Booking.com Email Scraper? Email
**neurodata.apify@gmail.com** and we will get back to you.

# Actor input Schema

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

Search terms describing the Booking.com accounts you want (niche, job title, industry).

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

Optional location phrase added to every query (e.g. "New York").

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

Only emails ending with one of these domains are collected. With or without the leading @. Each domain is searched separately, so more domains means more results but a longer run - remove some for a faster, narrower search, or add your own (e.g. @company.com).

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

Stop once this many unique emails have been collected.

## `countryCode` (type: `string`):

Two-letter country code for the search proxy (e.g. US, GB, DE). Empty for any.

## `expandQueries` (type: `boolean`):

Search each keyword x domain pair with several phrasings. Recommended - Google caps a single query at ~300 results.

## `queryModifiers` (type: `array`):

Extra words combined with each keyword when Expand queries is on. Tuned for Booking.com.

## `maxPagesPerQuery` (type: `integer`):

Google rarely returns more than ~30 pages for one query.

## `maxConcurrency` (type: `integer`):

How many queries run in parallel.

## Actor input object example

```json
{
  "keywords": [
    "hotel",
    "guest house"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "reservations",
    "group bookings",
    "owner"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

## `results` (type: `string`):

Records produced by Booking.com Email Scraper, stored in the run's default dataset.

# 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": [
        "hotel",
        "guest house"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "reservations",
        "group bookings",
        "owner"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leads-scraper/booking-com-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": [
        "hotel",
        "guest house",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "reservations",
        "group bookings",
        "owner",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("leads-scraper/booking-com-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": [
    "hotel",
    "guest house"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "reservations",
    "group bookings",
    "owner"
  ]
}' |
apify call leads-scraper/booking-com-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,leads-scraper/booking-com-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/FK6AbbUBHtX5w6drA/builds/6QwzBmi3jlFbCtDa7/openapi.json