# Wego Email Scraper (`leads-scraper/wego-email-scraper`) Actor

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

- **URL**: https://apify.com/leads-scraper/wego-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

### Wego Email Scraper — identity-rich travel leads for the Middle East and Asia

The **Wego Email Scraper** turns publicly indexed Wego pages into a deduplicated lead list of
contact emails, account labels and profile URLs. It is built for hospitality-tech vendors, OTA
supply teams and travel suppliers working across the Middle East, South Asia and Southeast Asia.

The Wego Email Scraper has the cleanest identity resolution in this whole travel family. In
live runs, roughly every 10 parsed results returned about 10 rows with an identity, 10 profile
URLs and 5 unique emails — almost every row arrives with a usable account label and a canonical
URL.

The trade-off is stated plainly. Wego is a metasearch aggregator, so listings rarely publish a
direct property email and volume is low. You get excellent structure on the rows you do get, not a
large harvest.

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

#### Who the Wego Email Scraper is for

Property management systems, channel managers and direct-booking vendors selling into the Gulf,
India and Southeast Asia use it to build a structured prospect list of hotels and travel agencies.
The high profile-URL rate makes rows easy to verify manually.

OTA supply teams recruiting regional inventory, destination marketing organisations, hotel and
amenity suppliers, and travel PR teams round out the Wego Email Scraper's audience. Properties and agencies publish
booking and partnership addresses on purpose, so approach them as trade contacts.

#### Why identity beats raw volume in a travel email list

A generic "hotel email list" gives you addresses with no context. The Wego Email Scraper gives you
fewer emails, but nearly all of them arrive attached to an `accountName`, a `username` and a
`profileUrl` you can open and check before writing.

That makes the Wego Email Scraper a good enrichment and verification pass next to higher-volume
sources. Run the big harvesters first, then use Wego to attach identity to the same markets.

***

### Key features of the Wego Email Scraper

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

| Feature | What it does |
|---|---|
| Google `site:` targeting | Searches `wego.com` with your keyword and email domains |
| Handle resolution | Builds `https://www.wego.com/hotels/{username}` whenever Google exposes a URL-safe handle |
| 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 Wego Email Scraper works

The pipeline is short and fully inspectable. The Wego Email Scraper reads your input, builds Google
queries with the `site:` operator, fetches result pages through the Apify **GOOGLE\_SERP** proxy with
`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:wego.com hotel "@gmail.com" "Dubai"
```

#### Query expansion inside the Wego Email Scraper

Google caps a single query at roughly 300 results, so pagination depth alone can never fill a large
list. Coverage in the Wego 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 Wego defaults are `email`, `contact`, `bookings`,
`group tours` and `partnerships`.

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 leads — and on a low-volume
aggregator that matters more, not less.

#### Middle East and Asia targeting with location and countryCode

`location` is a genuine lever. The phrase you supply is quoted and appended to every query, so
`"Dubai"`, `"Riyadh"` or `"Colombo"` narrows the whole Wego Email Scraper run to one market.

`countryCode` points the search proxy at a two-letter country such as `AE`, `SA`, `EG`, `IN`, `ID`
or `SG`, which changes which regional Wego pages Google surfaces. Country-by-country runs are how
this Actor produces a clean regional pipeline.

***

### Input fields of the Wego Email Scraper

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["hotel", "travel agency"]` | Search terms describing the Wego 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", "bookings", "group tours", "partnerships"]` | 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 Wego Email Scraper

```json
{
  "keywords": ["hotel", "travel agency", "resort"],
  "location": "Dubai",
  "customDomains": ["@gmail.com", "@yahoo.com", "@hotmail.com"],
  "maxEmails": 150,
  "countryCode": "AE",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "bookings", "group tours", "partnerships"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

Because email volume is the constraint here, widen `customDomains` before you raise `maxEmails`.
Each extra domain gives the Wego Email Scraper another full set of queries to work through.

***

### Output fields of the Wego Email Scraper

Every dataset item the Wego 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 listing pages |
| `username` | URL-safe handle when Wego exposes one; otherwise `null` |
| `profileUrl` | Canonical account URL when a handle is known; otherwise empty |
| `url` | Direct Wego 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 |

`profileUrl` takes the shape `https://www.wego.com/hotels/{username}`, and on this platform it is
usually populated — that is the Wego Email Scraper's main advantage.

#### Example output from the Wego Email Scraper

```json
[
  {
    "network": "Wego",
    "keyword": "hotel",
    "query": "site:wego.com hotel bookings \"@gmail.com\" \"Dubai\"",
    "title": "Marina Suites Dubai - Wego",
    "accountName": "marina-suites-dubai",
    "fullName": "Marina Suites Dubai",
    "username": "marina-suites-dubai",
    "profileUrl": "https://www.wego.com/hotels/marina-suites-dubai",
    "url": "https://www.wego.com/hotels/marina-suites-dubai",
    "description": "Marina-side apartments and suites. Bookings: marinasuites.dxb@gmail.com",
    "email": "marinasuites.dxb@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T14:03:29Z"
  },
  {
    "network": "Wego",
    "keyword": "travel agency",
    "query": "site:wego.com travel agency partnerships \"@yahoo.com\" \"Dubai\"",
    "title": "Al Noor Travel - Wego",
    "accountName": "al-noor-travel",
    "fullName": "Al Noor Travel",
    "username": "al-noor-travel",
    "profileUrl": "https://www.wego.com/hotels/al-noor-travel",
    "url": "https://www.wego.com/hotels/al-noor-travel",
    "description": "Group tours and partnerships: alnoor.travel@yahoo.com",
    "email": "alnoor.travel@yahoo.com",
    "emailDomain": "@yahoo.com",
    "possiblyTruncated": true,
    "foundAt": "2026-08-31T14:04:02Z"
  }
]
```

Both rows carry a handle and a profile URL, which is the normal shape the Wego Email Scraper
returns. Note the second row's `possiblyTruncated: true` — Google's snippet ellipsis touched
the address, so verify it before you send anything.

***

### Use cases for the Wego Email Scraper

| Use case | How the Wego Email Scraper helps |
|---|---|
| Gulf and South Asia PMS sales | Build a structured list of hotels with verifiable profile URLs |
| Channel manager onboarding | Reach properties visible in regional metasearch |
| Travel agency partnerships | Contact agencies advertising a partnerships inbox |
| Hotel supplier prospecting | Assemble a country list for linen, amenity and F\&B vendors |
| OTA supply recruitment | Source Middle East and Asia inventory for your marketplace |
| Lead enrichment | Attach identity and profile URLs to emails found elsewhere |
| Destination marketing | Map how regional stock appears in metasearch for a DMO |
| Travel PR and media | Contact properties and agencies publishing an enquiries address |

#### Worked example: a Gulf market pipeline

Run the Wego Email Scraper once per market — `"Dubai"` with `AE`, `"Riyadh"` with `SA`, `"Doha"`
with `QA` — keeping `keywords` at `["hotel", "resort", "travel agency"]`. Narrow runs consistently
beat one broad regional run.

#### Worked example: enrichment pass

Run a higher-volume accommodation Actor first, then run the Wego Email Scraper on the same
`location` and `customDomains`. Join the two datasets on `email` to attach `username` and
`profileUrl` where they match.

***

### Expected results from the Wego Email Scraper

In live measurement, about 10 results parsed by the Wego Email Scraper produced roughly 10 identity
rows, 10 profile URLs and 5 unique emails. That is the best identity resolution in this travel
category and a mid-range email count.

Because Wego is a metasearch aggregator, total volume is low: expect a smaller, cleaner dataset
rather than a large one. Yield still varies with keywords, email domains and location, and no volume
is guaranteed.

***

### Limitations of the Wego Email Scraper

- **Wego is a metasearch aggregator**, so listings rarely publish a direct property email and volume
  is low. Identity resolution is strong, but the number of addresses per run is modest.
- Only properties whose email is **publicly visible in Google's index** can be found by the Wego
  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. That happens
  often on Wego, but not always, and an empty handle is a Google limitation, not a bug.
- The Wego 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 Wego Email Scraper are business contact points that properties and
agencies published for bookings and partnerships, so treat them as B2B outreach data. Identify
yourself, explain why you are writing and honour opt-outs immediately.

GDPR applies whenever you contact people in the EU or EEA, and several Gulf and Asian markets have
comparable rules. You need a lawful basis — usually legitimate interest — a transparent privacy
notice and a working unsubscribe path.

***

### FAQ about the Wego Email Scraper

#### How many results should I expect from the Wego Email Scraper?

In measured live runs, roughly every 10 parsed results gave about 10 identity rows, 10 profile URLs
and 5 unique emails. Total volume is low because Wego is an aggregator, and nothing is guaranteed.

#### Why does Wego resolve handles so much better than other travel platforms?

Google tends to print a URL-safe hotel slug in Wego's result titles and links, so the Wego Email
Scraper can build `https://www.wego.com/hotels/{username}` for most rows.

#### If identity is strong, why is the Wego Email Scraper's volume low?

Wego is a metasearch aggregator. It compares prices across booking sites rather than hosting
property-managed pages, so a direct property email is published less often.

#### Does the Wego Email Scraper log in or use the Wego API?

No. It does not log in, does not open the Wego website and does not use any Wego 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. On a low-volume source, extra domains are the most effective single change.

#### Can I limit the Wego 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 prospecting across the Middle East and Asia.

#### Do I need a proxy to run the Wego 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 sending.

#### How do I get more emails out of a run?

Keep `expandQueries` on, add keywords such as `resort`, `apartment hotel` or `tour operator`, add
more email domains, and split one regional run into several country runs.

#### Is there a free-plan limit on the Wego 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 Wego 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.

#### Is the Wego Email Scraper affiliated with Wego?

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

***

### Related Actors

Every Actor below runs the same engine against a different Travel, Hospitality & Food platform.

For the same region pair this with the [Traveloka Email Scraper](https://apify.com/leads-scraper/traveloka-email-scraper)
for Southeast Asian inventory and the [Klook Email Scraper](https://apify.com/neuro-scraper/klook-email-scraper)
for Asia-Pacific activities.

For global accommodation volume add the
[Booking.com Email Scraper](https://apify.com/leads-scraper/booking-com-email-scraper) and the
[Airbnb Email Scraper](https://apify.com/leads-scraper/airbnb-email-scraper).

| Actor | What it collects |
|---|---|
| [Airbnb Email Scraper](https://apify.com/leads-scraper/airbnb-email-scraper) | Public contact emails from Airbnb |
| [Booking.com Email Scraper](https://apify.com/leads-scraper/booking-com-email-scraper) | Public contact emails from Booking.com |
| [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 |
| [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 |
| [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 |
| [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 |
| [Hostelworld Email and Phone Number Scraper](https://apify.com/neuro-scraper/hostelbookers-email-and-phone-number-scraper) | Emails and phone numbers from Hostelworld |

### Leave a review

If the Wego 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 Wego Email Scraper? Email
**neurodata.apify@gmail.com** and we will get back to you.

# Actor input Schema

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

Search terms describing the Wego 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 Wego.

## `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",
    "travel agency"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "bookings",
    "group tours",
    "partnerships"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

Records produced by Wego 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",
        "travel agency"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "bookings",
        "group tours",
        "partnerships"
    ]
};

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

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

```

## MCP server setup

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