# Europages Email Scraper (`leads-scraper/europages-email-scraper`) Actor

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

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

### Europages Email Scraper - public supplier contact emails from the European B2B marketplace

The Europages Email Scraper collects publicly indexed contact emails that appear in Google search results for the Europages domains. Europages is the best-known pan-European B2B marketplace, where manufacturers, wholesalers and service providers publish a company profile so that buyers across the continent can reach them.

That is the whole basis of this Actor. A Europages company page is an advertisement for being contacted, so sales, export and enquiry addresses appear there on purpose.

The Europages Email Scraper covers four domains rather than one - `europages.co.uk`, `europages.com`, `europages.fr` and `europages.de`. That spread is deliberate, because the same supplier is often indexed differently on the UK, French and German front doors.

It is a sourcing tool, not a browsing tool. Procurement teams, import and export agents, industrial distributors and trade-show organisers are the people who get real value out of a European supplier directory turned into a dataset.

#### A measured live result, stated plainly

A live Google run of the Europages Email Scraper returned **10 result blocks, 10 rows with account identity, 10 resolvable profile URLs and 7 unique emails**. Those are observed figures from a real run, not estimates.

Seven unique emails from ten blocks is a strong ratio for a B2B marketplace on the default webmail filter alone. It reflects the fact that many smaller European exporters genuinely do publish a Gmail or Yahoo address as their trade contact.

Just as importantly, identity resolution was complete. Europages exposes a clean page slug in Google's result, so the Europages Email Scraper produced a usable `username` and `profileUrl` on every row.

### Features of the Europages Email Scraper

Every feature below is genuinely implemented. Nothing here is aspirational.

| Feature | What it means in practice |
|---|---|
| Google SERP parsing | Reads Google result pages through the Apify GOOGLE_SERP proxy. No browser, no JavaScript rendering |
| Multi-domain coverage | Queries `europages.co.uk`, `europages.com`, `europages.fr` and `europages.de` |
| Structural block detection | Locates the `<h3>` title, then the smallest surrounding block. Does not depend on Google's CSS class names |
| Domain filter | Only emails ending in one of your `customDomains` values are kept |
| Query expansion | Base, quoted, `intitle:` and one variant per query modifier. Base queries run first |
| Global deduplication | An email seen once is never pushed twice, across every query and every page |
| Email normalisation | Understands `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, `domain .com`, zero-width characters and the full-width `＠` sign |
| 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 |
| Concurrency | An `asyncio` worker pool with a shared stop signal on `maxEmails` |
| Retries | Up to 3 attempts per page, exponential backoff, a fresh proxy session per request |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried, not counted as empty |
| Re-queueing | Blocked or failed queries are retried once at the end of the run |
| Resumable run | State is stored in the key-value store, keyed by a hash of the input, and saved on `PERSIST_STATE`, `MIGRATING` and `ABORTING` |
| Fallback parser | If Google's markup changes, the run degrades to "emails without account details" rather than "no emails" |
| Run summary | Logs pages fetched, blocked pages, retries and emails per page |
| Dataset output | Rows push immediately and export to CSV, JSON, Excel or XML from the Apify dataset |

Global deduplication earns its keep in the Europages Email Scraper more than almost anywhere else in this family. Four domains means the same supplier can be found several times, and the Actor pushes that email exactly once.

### How the Europages Email Scraper works

The pipeline is six steps and there is nothing hidden inside it.

1. It reads your input: keywords, location, email domains and limits.
2. It builds Google search queries with the `site:` operator against each Europages domain, for example `site:europages.co.uk supplier "@gmail.com" "Barcelona"`.
3. It fetches Google result pages through the Apify GOOGLE_SERP proxy using `aiohttp`, asynchronously.
4. It parses each result block structurally, finding the `<h3>` title and the smallest block around it.
5. It extracts emails from that block's text with a domain-filtered regex.
6. It deduplicates globally and pushes each lead straight into the Apify dataset.

The Europages Email Scraper does **not** log into Europages, does not use any Europages API, and does not open the marketplace in a browser. Every field comes from publicly indexed Google search results - titles, snippets and site labels, with no authentication and no cookies.

### Who the Europages Email Scraper is built for

This is a B2B sourcing Actor, and the people who benefit from it are the ones who buy, move or represent goods rather than the ones who sell to consumers.

Procurement teams use it to assemble a European supplier shortlist before an RFQ round, especially when nearshoring away from a distant supply chain. Import and export agents use it to find companies that already market themselves as export-ready.

Industrial distributors use it to spot manufacturers with no representation in their territory. Trade-show organisers use it to recruit exhibitors from the exact product categories a hall is short of.

If your targets are local consumer-facing businesses rather than industrial suppliers, the Europages Email Scraper is the wrong Actor and [Cybo Email Scraper](https://apify.com/neuro-scraper/cybo-email-scraper) or [Fyple Email Scraper](https://apify.com/neuro-scraper/fyple-email-scraper) will suit you better.

### Input fields for the Europages Email Scraper

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["manufacturer", "supplier"]` | Search terms - niche, job title, industry |
| `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 x domain pair in several phrasings |
| `queryModifiers` | array | `["email", "contact", "export", "wholesale", "sales enquiries"]` | 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 |

#### How the Europages Email Scraper input fields actually behave

`keywords` is the field that decides your industry. The defaults `manufacturer` and `supplier` are intentionally broad, and any serious run should replace them with a product class - `aluminium extrusion`, `organic olive oil`, `corrugated packaging`.

`queryModifiers` only fire when `expandQueries` is `true`. The defaults `export`, `wholesale` and `sales enquiries` are tuned to Europages because those are the phrases that sit beside a published address on a trade profile.

`customDomains` controls how wide the net is. Small European exporters often use free webmail, but adding `@outlook.com`, `@hotmail.com`, `@web.de`, `@free.fr` or `@libero.it` will noticeably increase what the Europages Email Scraper returns.

`maxEmails` is a hard stop shared across the worker pool. Raising it does not invent leads; it just lets the run continue through the expanded query set instead of finishing early.

`maxConcurrency` and `maxPagesPerQuery` trade speed against politeness, and the defaults of 5 and 30 are appropriate for a four-domain target of this size.

### JSON input example for the Europages Email Scraper

```json
{
  "keywords": ["corrugated packaging", "Wellpappe Hersteller", "emballage carton"],
  "location": "Nordrhein-Westfalen",
  "customDomains": ["@gmail.com", "@yahoo.com", "@web.de", "@t-online.de"],
  "maxEmails": 250,
  "countryCode": "DE",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "export", "wholesale", "sales enquiries"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

Notice the German and French keywords sitting alongside the English one. Europages publishes profile text in many European languages, and native-language product terms reach listings that an English term never surfaces.

That is a realistic sourcing configuration for the Europages Email Scraper: one product class expressed in three languages, a manufacturing region, a matching country code and a domain filter widened with national webmail providers.

### Output fields of the Europages Email Scraper

Every dataset item carries all fourteen fields.

| 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 |
| `fullName` | Display name parsed from a profile-style title; empty for non-profile results |
| `username` | URL-safe handle when the platform exposes one; otherwise `null` |
| `profileUrl` | Canonical account URL when a handle is known; otherwise empty |
| `url` | Direct platform link when exposed, else the profile URL |
| `description` | Bio or snippet text, cleaned of labels and counters |
| `email` | Lower-cased email address |
| `emailDomain` | The matched domain, for example `@gmail.com` |
| `possiblyTruncated` | `true` when Google's snippet ellipsis touched the email - verify before sending |
| `foundAt` | ISO 8601 UTC timestamp |

On Europages, `username` and `profileUrl` are populated on most rows because company pages carry a stable slug. The Europages Email Scraper builds the canonical link in the form `https://www.europages.co.uk/{username}.html`.

Always check `possiblyTruncated` before sending. When it is `true`, Google's snippet ellipsis may have clipped the address and you should confirm it on the source page.

### JSON output example from the Europages Email Scraper

```json
[
  {
    "network": "Europages",
    "keyword": "corrugated packaging",
    "query": "site:europages.co.uk corrugated packaging export \"@gmail.com\" \"Nordrhein-Westfalen\"",
    "title": "Wellpappenwerk Rheinbach GmbH - Corrugated packaging - Europages",
    "accountName": "Wellpappenwerk Rheinbach GmbH",
    "fullName": "Wellpappenwerk Rheinbach GmbH",
    "username": "WELLPAPPENWERK-RHEINBACH-GMBH",
    "profileUrl": "https://www.europages.co.uk/WELLPAPPENWERK-RHEINBACH-GMBH.html",
    "url": "https://www.europages.co.uk/WELLPAPPENWERK-RHEINBACH-GMBH.html",
    "description": "Corrugated board boxes and displays for food and industrial packaging. Export across the EU.",
    "email": "rheinbach.export@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-29T10:02:11Z"
  },
  {
    "network": "Europages",
    "keyword": "emballage carton",
    "query": "site:europages.fr emballage carton \"sales enquiries\" \"@yahoo.com\"",
    "title": "Cartonnages du Rhone SARL - Europages",
    "accountName": "Cartonnages du Rhone SARL",
    "fullName": "Cartonnages du Rhone SARL",
    "username": "CARTONNAGES-DU-RHONE-SARL",
    "profileUrl": "https://www.europages.co.uk/CARTONNAGES-DU-RHONE-SARL.html",
    "url": "https://www.europages.co.uk/CARTONNAGES-DU-RHONE-SARL.html",
    "description": "Custom cardboard packaging and printed cases. Wholesale supply for European buyers.",
    "email": "contact.cartonnages@yahoo.com",
    "emailDomain": "@yahoo.com",
    "possiblyTruncated": true,
    "foundAt": "2026-08-29T10:03:47Z"
  }
]
```

### Use cases for the Europages Email Scraper

| Audience | What they do with the data |
|---|---|
| Procurement and category buyers | Build a European supplier shortlist before an RFQ or nearshoring review |
| Import and export agents | Find export-ready manufacturers in a specific EU country and language |
| Industrial distributors | Identify brands without regional representation and pitch distribution |
| Trade-show and expo organisers | Recruit exhibitors from the product categories a hall is short of |
| Contract manufacturers | Reach companies that outsource production in an adjacent category |
| Freight forwarders and customs brokers | Approach exporters shipping the trade lanes they already serve |
| B2B marketing agencies | Assemble an industrial prospect list for an account-based campaign |
| Trade researchers and analysts | Map which European product segments publish contact routes and where |

Every one of those jobs is aimed at a company inbox that a supplier published to attract buyers. That is the honest boundary of what the Europages Email Scraper is for.

### Targeting tips and multilingual keywords for the Europages Email Scraper

`location` and `countryCode` are both genuine levers on this Actor, and Europages rewards using them together.

`location` appends a phrase to every query, so `"Lombardia"`, `"Catalunya"` or `"Nordrhein-Westfalen"` narrows to an industrial cluster instead of a whole country. European manufacturing is regionally concentrated, and this field matches that reality.

`countryCode` changes the country of the search proxy, which changes which Europages front door Google favours. Setting `DE`, `FR`, `IT` or `ES` shifts the Europages Email Scraper onto a different slice of the marketplace.

Because Europages profile text appears in many European languages, native-language keywords are not a nicety here - they are the main way to reach the deeper index. Pair `Hersteller` with `DE`, `fournisseur` with `FR`, `fornitore` with `IT` and `proveedor` with `ES`.

Keep `expandQueries` on so the `export` and `wholesale` modifiers reach the pages where addresses actually sit. For overlapping coverage of the same European supply base, run [Kompass Email Scraper](https://apify.com/leads-scraper/kompass-email-scraper) with the same country settings.

### Limitations of the Europages Email Scraper

Read all of these before your first run.

- The Europages Email Scraper only finds addresses that are **publicly visible in Google's index**. Anything Google has not indexed is invisible to it.
- Google caps a single query at roughly 300 results, which is exactly why query expansion exists and why it defaults to on.
- `possiblyTruncated: true` means Google's snippet ellipsis may have cut the email short. Verify it before sending.
- It 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.
- `username` and `profileUrl` are only populated when Google exposes a handle. Europages usually does, but rows built from category or search pages can still arrive with `username: null` and an empty `profileUrl`. That is a Google limitation, not a bug.
- Results vary with keywords, domains, language and location. No volume is guaranteed by the Europages Email Scraper or by any Actor in this family.

### Responsible use of Europages Email Scraper output

The addresses the Europages Email Scraper surfaces are trade contacts that companies published on a public B2B marketplace so that buyers could reach them. Treat them as exactly that.

Under GDPR, a named person's work address remains personal data even when it is publicly listed. Record your legitimate interest, identify yourself and your company in the first line, and make the relevance of the message obvious.

Honour opt-outs immediately and permanently, keep your list current, and respect the national marketing rules of each EU country you contact. Do not use this output for bulk unsolicited mail.

### FAQ about the Europages Email Scraper

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

A live Google run returned 10 result blocks, 10 identified accounts, 10 profile URLs and 7 unique emails on default settings. Yield scales with the number of keyword and domain combinations you supply, so ten product keywords across five domains will return far more than the default pairing. No specific number is guaranteed, because it all depends on what Google has indexed.

#### Which Europages domains does the Actor search?

Four: `europages.co.uk`, `europages.com`, `europages.fr` and `europages.de`. The Europages Email Scraper deduplicates globally, so a supplier found on more than one of them is still pushed once.

#### Does the Europages Email Scraper log into Europages or use its API?

No. It builds Google `site:` queries against the Europages domains, fetches result pages through the Apify GOOGLE_SERP proxy and parses them. There is no browser, no login, no API and no cookies.

#### Should I use non-English keywords?

Yes, whenever you are targeting a non-English market. Europages carries profile text in many European languages, so `Hersteller`, `fournisseur` or `fornitore` reaches listings that `manufacturer` never surfaces.

#### What is the fastest way to increase Europages Email Scraper yield?

Widen `customDomains` past the two webmail defaults and use narrower product keywords. National providers such as `@web.de`, `@free.fr` and `@libero.it` are common among smaller European exporters.

#### Why do most rows have a usable profile URL?

Because Europages company pages carry a stable slug that Google prints. The Europages Email Scraper derives `username` from it and builds `profileUrl` as `https://www.europages.co.uk/{username}.html`.

#### Why does the Europages Email Scraper turn `expandQueries` on by default?

Google caps one query at roughly 300 results. Expansion runs base, quoted and `intitle:` variants plus one per modifier, reaching pages that a single query cannot. Base queries always run first.

#### Can I run the Europages Email Scraper on a free Apify plan?

Yes. Free plans are capped at 100 emails per run, and paid plans are uncapped.

#### What happens if a Europages Email Scraper run is interrupted?

State is saved in the key-value store, keyed by a hash of your input, and written on Apify's `PERSIST_STATE`, `MIGRATING` and `ABORTING` events. Restarting with the same input resumes rather than starting over.

#### Which export formats are available?

Anything the Apify dataset supports - CSV, JSON, Excel and XML - plus the API for pushing rows straight into a CRM.

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

No. It is an independent Actor that reads publicly indexed Google results, with no relationship to or endorsement from the platform.

#### Which other Actor pairs best with the Europages Email Scraper?

For overlapping European coverage, [Kompass Email Scraper](https://apify.com/leads-scraper/kompass-email-scraper). For North American manufacturing, [Thomasnet Email Scraper](https://apify.com/leads-scraper/thomasnet-email-scraper). For Asian export supply, [EC21 Email Scraper](https://apify.com/neuro-scraper/ec21-email-scraper) and [ExportHub Email Scraper](https://apify.com/neuro-scraper/exporthub-email-scraper).

### Related Actors

More email scrapers from the same Business & Professional Directories family, built on the same Google SERP pipeline.

| Actor | What it collects |
|---|---|
| [Europages Email and Phone Number Scraper](https://apify.com/leads-scraper/europages-email-and-phone-number-scraper) | Emails and phone numbers from Europages |
| [Europages Phone Number Scraper](https://apify.com/leads-scraper/europages-phone-number-scraper) | Public phone numbers from Europages |
| [Angi Email Scraper](https://apify.com/leads-scraper/angi-email-scraper) | Public contact emails from Angi |
| [Bark Email Scraper](https://apify.com/leads-scraper/bark-email-scraper) | Public contact emails from Bark |
| [Better Business Bureau Email Scraper](https://apify.com/leads-scraper/better-business-bureau-email-scraper) | Public contact emails from Better Business Bureau |
| [Bizapedia Email Scraper](https://apify.com/neuro-scraper/bizapedia-email-scraper) | Public contact emails from Bizapedia |
| [Brownbook Email Scraper](https://apify.com/neuro-scraper/brownbook-email-scraper) | Public contact emails from Brownbook |
| [Callupcontact Email Scraper](https://apify.com/neuro-scraper/callupcontact-email-scraper) | Public contact emails from CallUpContact |
| [Capterra Email Scraper](https://apify.com/leads-scraper/capterra-email-scraper) | Public contact emails from Capterra |
| [Clutch Email Scraper](https://apify.com/leads-scraper/clutch-email-scraper) | Public contact emails from Clutch |
| [Crunchbase Email Scraper](https://apify.com/leads-scraper/crunchbase-email-scraper) | Public contact emails from Crunchbase |
| [Cybo Email Scraper](https://apify.com/neuro-scraper/cybo-email-scraper) | Public contact emails from Cybo |
| [Cylex Email Scraper](https://apify.com/neuro-scraper/cylex-email-scraper) | Public contact emails from Cylex |
| [EC21 Email Scraper](https://apify.com/neuro-scraper/ec21-email-scraper) | Public contact emails from EC21 |
| [ExportHub Email Scraper](https://apify.com/neuro-scraper/exporthub-email-scraper) | Public contact emails from ExportHub |
| [FindUsLocal Email Scraper](https://apify.com/neuro-scraper/finduslocal-email-scraper) | Public contact emails from FindUsLocal |
| [Foursquare Email Scraper](https://apify.com/neuro-scraper/foursquare-email-scraper) | Public contact emails from Foursquare |
| [Fyple Email Scraper](https://apify.com/neuro-scraper/fyple-email-scraper) | Public contact emails from Fyple |
| [G2 Email Scraper](https://apify.com/neuro-scraper/g2-email-scraper) | Public contact emails from G2 |
| [Hotfrog Email Scraper](https://apify.com/leads-scraper/hotfrog-email-scraper) | Public contact emails from Hotfrog |
| [Houzz Email Scraper](https://apify.com/leads-scraper/houzz-email-scraper) | Public contact emails from Houzz |
| [Infobel Email Scraper](https://apify.com/neuro-scraper/infobel-email-scraper) | Public contact emails from Infobel |
| [Kompass Email Scraper](https://apify.com/leads-scraper/kompass-email-scraper) | Public contact emails from Kompass |
| [Lacartes Email Scraper](https://apify.com/neuro-scraper/lacartes-email-scraper) | Public contact emails from Lacartes |
| [Manta Email Scraper](https://apify.com/leads-scraper/manta-email-scraper) | Public contact emails from Manta |
| [MapQuest Email Scraper](https://apify.com/neuro-scraper/mapquest-email-scraper) | Public contact emails from MapQuest |
| [N49 Email Scraper](https://apify.com/neuro-scraper/n49-email-scraper) | Public contact emails from N49 |
| [Porch Email Scraper](https://apify.com/neuro-scraper/porch-email-scraper) | Public contact emails from Porch |
| [Scoot Email Scraper](https://apify.com/neuro-scraper/scoot-email-scraper) | Public contact emails from Scoot |
| [Thomasnet Email Scraper](https://apify.com/leads-scraper/thomasnet-email-scraper) | Public contact emails from Thomasnet |
| [Thumbtack Email Scraper](https://apify.com/leads-scraper/thumbtack-email-scraper) | Public contact emails from Thumbtack |
| [Touch Local Email Scraper](https://apify.com/leads-scraper/touch-local-email-scraper) | Public contact emails from Touch Local |
| [TradeIndia Email Scraper](https://apify.com/leads-scraper/tradeindia-email-scraper) | Public contact emails from TradeIndia |
| [Trustpilot Email Scraper](https://apify.com/leads-scraper/trustpilot-email-scraper) | Public contact emails from Trustpilot |
| [Tupalo Email Scraper](https://apify.com/leads-scraper/tupalo-email-scraper) | Public contact emails from Tupalo |
| [Yalwa Email Scraper](https://apify.com/leads-scraper/yalwa-email-scraper) | Public contact emails from Yalwa |
| [Yellow Pages Email Scraper](https://apify.com/leads-scraper/yellow-pages-email-scraper) | Public contact emails from Yellow Pages |
| [Angi Email and Phone Number Scraper](https://apify.com/neuro-scraper/angi-email-and-phone-number-scraper) | Emails and phone numbers from Angi |
| [Bark Email and Phone Number Scraper](https://apify.com/neuro-scraper/bark-email-and-phone-number-scraper) | Emails and phone numbers from Bark |
| [Better Business Bureau Email and Phone Number Scraper](https://apify.com/leads-scraper/better-business-bureau-email-and-phone-number-scraper) | Emails and phone numbers from Better Business Bureau |
| [Bizapedia Email and Phone Number Scraper](https://apify.com/neuro-scraper/bizapedia-email-and-phone-number-scraper) | Emails and phone numbers from Bizapedia |
| [Brownbook Email and Phone Number Scraper](https://apify.com/neuro-scraper/brownbook-email-and-phone-number-scraper) | Emails and phone numbers from Brownbook |

### Leave a review

If the Europages 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.

# Actor input Schema

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

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

## `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": [
    "manufacturer",
    "supplier"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "export",
    "wholesale",
    "sales enquiries"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

Records produced by Europages 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": [
        "manufacturer",
        "supplier"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "export",
        "wholesale",
        "sales enquiries"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leads-scraper/europages-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": [
        "manufacturer",
        "supplier",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "export",
        "wholesale",
        "sales enquiries",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("leads-scraper/europages-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": [
    "manufacturer",
    "supplier"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "export",
    "wholesale",
    "sales enquiries"
  ]
}' |
apify call leads-scraper/europages-email-scraper --silent --output-dataset

```

## MCP server setup

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