# LinkedIn Email Scraper (`leads-scraper/linkedin-email-scraper`) Actor

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

- **URL**: https://apify.com/leads-scraper/linkedin-email-scraper.md
- **Developed by:** [Leads Scraper](https://apify.com/leads-scraper) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 0.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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## LinkedIn Email Scraper

### LinkedIn Email Scraper - Public Contact Emails from Indexed LinkedIn Profiles

The **LinkedIn Email Scraper** is an Apify Actor that collects publicly indexed contact emails belonging to LinkedIn profiles and pages. You supply keywords; it returns a structured dataset of B2B leads.

The LinkedIn Email Scraper works by running `site:linkedin.com` searches through the Apify GOOGLE\_SERP proxy and parsing addresses out of the result blocks. That is the whole mechanism, stated plainly.

The LinkedIn Email Scraper does **not** log into LinkedIn, does **not** use LinkedIn's API and does **not** open linkedin.com. No browser, no JavaScript rendering, no authentication, no cookies, no browser extension.

That matters here more than on any other network. Extension-based LinkedIn email scraper tools run inside your own logged-in session and put your account at risk; the LinkedIn Email Scraper never touches your account at all.

Everything it returns already exists in Google's public index: titles, snippets and site labels. If a consultant wrote `reach me at me@gmail.com` in a headline or summary Google crawled, this **LinkedIn email extractor** can surface it.

***

### Key Features

| Feature | What it does |
|---|---|
| Keyword-driven search | Start the LinkedIn Email Scraper from a job title or industry, not from a list of profile URLs |
| No session required | No login, no cookies, no Chrome extension, no risk to your own LinkedIn account |
| Query expansion | Each keyword x domain pair runs as base, quoted, `intitle:` and one variant per modifier |
| Domain filtering | Only emails on the domains you list (`@gmail.com`, `@yahoo.com`, ...) are kept |
| Obfuscation handling | Understands `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, `domain .com`, zero-width characters and the full-width at sign |
| Junk filter | Rejects placeholders such as `email@`, `yourname@`, `test@`, `xxx@` and single-character locals |
| Boundary-correct matching | `@gmail.com` never matches inside `@gmail.company` or `@gmail.com.br` |
| Global deduplication | One row per unique email across every query and every page |
| Concurrency | An `asyncio` worker pool runs several queries in parallel with a shared stop signal |
| Retry logic | 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, never counted as empty |
| Resumable state | Progress lives in the key-value store, keyed by a hash of your input |
| Fallback parser | If Google's markup changes, a run degrades to "emails without account details", not "no emails" |
| Location targeting | An optional location phrase is appended to every query |

The LinkedIn Email Scraper parser locates each `<h3>` title, then the smallest surrounding block. It does **not** depend on Google's CSS class names, which is why the LinkedIn Email Scraper tolerates most SERP layout changes.

***

### How the LinkedIn Email Scraper Works

The LinkedIn Email Scraper pipeline is short, deterministic and auditable - every row stores the exact query that produced it.

1. **Read input.** Keywords, location, email domains and limits are validated.
2. **Build queries.** The LinkedIn Email Scraper composes `site:linkedin.com` queries, e.g. `site:linkedin.com marketing director "@gmail.com" "London"`.
3. **Expand queries.** Base queries run first, then quoted, `intitle:` and one variant per query modifier.
4. **Fetch search results.** Pages are retrieved asynchronously with `aiohttp` through the Apify GOOGLE\_SERP proxy.
5. **Parse structurally.** Each result block is isolated around its `<h3>` heading.
6. **Extract emails.** A domain-filtered regex pulls addresses from the block text after normalisation.
7. **Deduplicate and push.** Every new lead is written straight to the dataset as structured data.

Pagination per query is capped by `maxPagesPerQuery`. A query stops early once several consecutive pages produce no new email, so the crawler does not spend proxy calls on an exhausted result set.

Blocked or failed queries are re-queued once at the end of the run. The LinkedIn Email Scraper then logs a summary: pages fetched, blocked pages, retries and emails per page.

***

### What Data Does It Extract?

Every LinkedIn Email Scraper dataset item pairs an email with whatever profile metadata Google exposed, plus provenance so you can trace the address back to its query.

Member profiles sit under `linkedin.com/in/`, and the LinkedIn Email Scraper turns that path into a `username` slug plus a canonical `profileUrl` such as `https://www.linkedin.com/in/slug/`. Profile-style titles also yield a parsed `fullName`.

Pulse articles, company pages, job posts and school pages do not map to a member handle. Those rows carry `accountName` with `username: null` and an empty `profileUrl`, while the email and snippet are still returned. That is a Google limitation, not a defect.

***

### Input Schema for the LinkedIn Email Scraper

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["founder", "recruiter"]` | Search terms describing the profiles you want (job title, industry, seniority) |
| `location` | string | `""` | Optional location phrase added to every query |
| `customDomains` | array | `["@gmail.com", "@yahoo.com"]` | Only emails on these domains are kept; the leading `@` 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", "reach me", "hiring", "open to work"]` | 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 |

The default modifiers are tuned for LinkedIn's professional phrasing. `reach me`, `hiring` and `open to work` are the exact strings members put beside an address, which is why the LinkedIn Email Scraper ships with them.

#### JSON input example

```json
{
  "keywords": ["technical recruiter", "marketing director", "supply chain manager"],
  "location": "London",
  "customDomains": ["@gmail.com", "@outlook.com"],
  "maxEmails": 500,
  "countryCode": "GB",
  "expandQueries": true,
  "queryModifiers": ["reach me", "hiring", "contact", "email"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

***

### Output Schema and Structured Data Fields

Every item the LinkedIn Email Scraper writes carries all 14 fields below, so a CSV, XLSX or JSON export always has identical columns.

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

#### JSON output example

```json
[
  {
    "network": "LinkedIn",
    "keyword": "technical recruiter",
    "query": "site:linkedin.com technical recruiter \"reach me\" \"@gmail.com\" \"London\"",
    "title": "Sarah Whitfield - Technical Recruiter - LinkedIn",
    "accountName": "sarah-whitfield-recruiting",
    "fullName": "Sarah Whitfield",
    "username": "sarah-whitfield-recruiting",
    "profileUrl": "https://www.linkedin.com/in/sarah-whitfield-recruiting/",
    "url": "https://www.linkedin.com/in/sarah-whitfield-recruiting/",
    "description": "Technical recruiter hiring backend and platform engineers in London. Reach me at s.whitfield.rec@gmail.com",
    "email": "s.whitfield.rec@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-02-27T10:03:55Z"
  },
  {
    "network": "LinkedIn",
    "keyword": "marketing director",
    "query": "site:linkedin.com marketing director \"contact\" \"@outlook.com\"",
    "title": "What I learned running demand gen for five years | LinkedIn",
    "accountName": "LinkedIn",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "https://www.linkedin.com/pulse/what-i-learned-running-demand-gen-five-years",
    "description": "Contact for consulting work: d.okafor.marketing@outlook.com ...",
    "email": "d.okafor.marketing@outlook.com",
    "emailDomain": "@outlook.com",
    "possiblyTruncated": true,
    "foundAt": "2026-02-27T10:05:12Z"
  }
]
```

The second row is the honest case. Google served a Pulse article rather than a member profile, so there is no `/in/` slug to build a `profileUrl` from, and the snippet ellipsis touched the address.

***

### How to Use the LinkedIn Email Scraper in Five Steps

1. **Open the Actor** and confirm your account has Apify proxy access. The GOOGLE\_SERP proxy is required.
2. **Enter 3-10 keywords.** Use real job titles: `demand generation manager` beats `marketing`.
3. **Choose email domains.** Members who publish a contact address usually use a personal one, so keep `@gmail.com` and add `@outlook.com` and `@hotmail.com`.
4. **Set `maxEmails`.** Start at 20 to confirm the titles match your ICP, then raise it.
5. **Run, then export.** Download the dataset as CSV, JSON or XLSX, or pull it via the Apify API into your CRM.

Use `location` plus `countryCode` together when you are prospecting a specific market. LinkedIn headlines contain city names constantly, so location phrases work unusually well in LinkedIn Email Scraper queries.

***

### LinkedIn Email Scraper Use Cases

| Use case | Who it is for | How the LinkedIn Email Scraper helps |
|---|---|---|
| B2B sales prospecting | SDR and sales teams | Build title-targeted lead lists for cold email campaigns |
| Recruiting outreach | In-house and agency recruiters | Find candidates whose headline says `open to work` with a public address |
| Reverse recruiting | Job seekers | Collect recruiter emails by industry and city |
| Agency lead generation | Marketing and dev agencies | Target decision-maker titles in a chosen vertical |
| Partner and reseller sourcing | Channel teams | Identify consultants and integrators publishing contact details |
| Event speaker sourcing | Conference organisers | Reach practitioners by discipline and seniority |
| Account-based marketing | Demand gen teams | Enrich a named-account list with public contact discovery |
| CRM enrichment | RevOps teams | Feed structured data straight into an existing pipeline |

B2B buyers are rarely on one network only. Pair this Actor with the [X Email Scraper](https://apify.com/leads-scraper/x-email-scraper) for founders and operators, and the [Facebook Email Scraper](https://apify.com/leads-scraper/facebook-email-scraper) when your ICP is small local businesses.

***

### Why Use This Actor for Professional Contact Discovery

Most LinkedIn email finders are Chrome extensions that scrape your logged-in session, or enrichment APIs that guess `first.last@company.com` and hope. The LinkedIn Email Scraper does neither.

It only reports addresses that are genuinely present in Google's indexed text. Nothing is guessed, permuted or inferred, so a row in the LinkedIn Email Scraper dataset is something a person actually published.

Because the LinkedIn Email Scraper never touches linkedin.com, there is no login, no connection limit, no API tier and no account risk. Its only dependency is Apify's search proxy.

Normalisation, obfuscation handling, the junk filter, boundary-correct domain matching and soft-wrap repair strip out most of the noise naive regex email scraping produces.

***

### Limitations

Read this before planning a campaign around the LinkedIn Email Scraper.

- **Public index only.** It finds profiles whose email is publicly visible in Google's index. LinkedIn restricts crawling heavily, so coverage is thinner here than on open networks - expect fewer results per keyword than on Instagram or TikTok.
- **Personal addresses dominate.** Members who publish an email in a public headline or summary usually publish a personal one. This is not a corporate email permutation tool.
- **Google's ~300-result cap.** A single query returns roughly 300 results at most. Query expansion exists to work around that ceiling, so keep `expandQueries` on for volume.
- **`possiblyTruncated`.** When Google's snippet ellipsis touched an address, the row is flagged. Verify those rows before sending.
- **Slug availability.** `username` and `profileUrl` are populated only when Google's result exposes an `/in/` path. Pulse, company, job and school results return `accountName` instead.
- **Apify proxy required.** The LinkedIn Email Scraper cannot run without Apify GOOGLE\_SERP proxy credentials.
- **Free-plan cap.** Free Apify plans are capped at 100 emails per run. Paid plans are uncapped.
- **No volume guarantee.** Results vary with keywords, domains, location and what Google has indexed. Nothing is guaranteed, verified or real-time.

The LinkedIn Email Scraper is not affiliated with, endorsed by or officially supported by LinkedIn or Microsoft. Use the output in line with GDPR, CAN-SPAM and local marketing law.

***

### Related Actors

The LinkedIn Email Scraper shares its engine and output schema with every Actor below, all part of the Social, Creator & Community family.

| Actor | What it collects |
|---|---|
| [LinkedIn Email and Phone Number Scraper](https://apify.com/leads-scraper/linkedin-email-and-phone-number-scraper) | Emails and phone numbers from LinkedIn |
| [LinkedIn Phone Number Scraper](https://apify.com/leads-scraper/linkedin-phone-number-scraper) | Public phone numbers from LinkedIn |
| [Behance Email Scraper](https://apify.com/leads-scraper/behance-email-scraper) | Public contact emails from Behance |
| [Bigo Live Email Scraper](https://apify.com/leads-scraper/bigo-live-email-scraper) | Public contact emails from Bigo Live |
| [Bluesky Email Scraper](https://apify.com/leads-scraper/bluesky-email-scraper) | Public contact emails from Bluesky |
| [Bumble Email Scraper](https://apify.com/leads-scraper/bumble-email-scraper) | Public contact emails from Bumble |
| [Clubhouse Email Scraper](https://apify.com/leads-scraper/clubhouse-email-scraper) | Public contact emails from Clubhouse |
| [Dailymotion Email Scraper](https://apify.com/leads-scraper/dailymotion-email-scraper) | Public contact emails from Dailymotion |
| [DeviantArt Email Scraper](https://apify.com/leads-scraper/deviantart-email-scraper) | Public contact emails from DeviantArt |
| [Discord Email Scraper](https://apify.com/leads-scraper/discord-email-scraper) | Public contact emails from Discord |
| [Dribbble Email Scraper](https://apify.com/leads-scraper/dribbble-email-scraper) | Public contact emails from Dribbble |
| [Facebook Email Scraper](https://apify.com/leads-scraper/facebook-email-scraper) | Public contact emails from Facebook |
| [Goodreads Email Scraper](https://apify.com/leads-scraper/goodreads-email-scraper) | Public contact emails from Goodreads |
| [Hinge Email Scraper](https://apify.com/leads-scraper/hinge-email-scraper) | Public contact emails from Hinge |
| [Instagram Email Scraper](https://apify.com/leads-scraper/instagram-email-scraper) | Public contact emails from Instagram |
| [KakaoTalk Email Scraper](https://apify.com/leads-scraper/kakaotalk-email-scraper) | Public contact emails from KakaoTalk |
| [Kick Email Scraper](https://apify.com/leads-scraper/kick-email-scraper) | Public contact emails from Kick |
| [Lemon8 Email Scraper](https://apify.com/leads-scraper/lemon8-email-scraper) | Public contact emails from Lemon8 |
| [Likee Email Scraper](https://apify.com/leads-scraper/likee-email-scraper) | Public contact emails from Likee |
| [LINE Email Scraper](https://apify.com/leads-scraper/line-email-scraper) | Public contact emails from LINE |
| [Mastodon Email Scraper](https://apify.com/leads-scraper/mastodon-email-scraper) | Public contact emails from Mastodon |
| [Medium Email Scraper](https://apify.com/leads-scraper/medium-email-scraper) | Public contact emails from Medium |
| [Mixcloud Email Scraper](https://apify.com/leads-scraper/mixcloud-email-scraper) | Public contact emails from Mixcloud |
| [Patreon Email Scraper](https://apify.com/leads-scraper/patreon-email-scraper) | Public contact emails from Patreon |
| [Pinterest Email Scraper](https://apify.com/leads-scraper/pinterest-email-scraper) | Public contact emails from Pinterest |
| [Quora Email Scraper](https://apify.com/leads-scraper/quora-email-scraper) | Public contact emails from Quora |
| [Reddit Email Scraper](https://apify.com/leads-scraper/reddit-email-scraper) | Public contact emails from Reddit |
| [Rumble Email Scraper](https://apify.com/leads-scraper/rumble-email-scraper) | Public contact emails from Rumble |
| [Snapchat Email Scraper](https://apify.com/leads-scraper/snapchat-email-scraper) | Public contact emails from Snapchat |
| [SoundCloud Email Scraper](https://apify.com/leads-scraper/soundcloud-email-scraper) | Public contact emails from SoundCloud |
| [Substack Email Scraper](https://apify.com/leads-scraper/substack-email-scraper) | Public contact emails from Substack |
| [Telegram Email Scraper](https://apify.com/leads-scraper/telegram-email-scraper) | Public contact emails from Telegram |
| [Threads Email Scraper](https://apify.com/leads-scraper/threads-email-scraper) | Public contact emails from Threads |
| [TikTok Email Scraper](https://apify.com/leads-scraper/tiktok-email-scraper) | Public contact emails from TikTok |
| [Tinder Email Scraper](https://apify.com/leads-scraper/tinder-email-scraper) | Public contact emails from Tinder |
| [Tumblr Email Scraper](https://apify.com/leads-scraper/tumblr-email-scraper) | Public contact emails from Tumblr |
| [Twitch Email Scraper](https://apify.com/leads-scraper/twitch-email-scraper) | Public contact emails from Twitch |
| [Vimeo Email Scraper](https://apify.com/leads-scraper/vimeo-email-scraper) | Public contact emails from Vimeo |
| [VK Email Scraper](https://apify.com/leads-scraper/vk-email-scraper) | Public contact emails from VK |
| [WeChat Email Scraper](https://apify.com/leads-scraper/wechat-email-scraper) | Public contact emails from WeChat |
| [Weibo Email Scraper](https://apify.com/leads-scraper/weibo-email-scraper) | Public contact emails from Weibo |
| [X Email Scraper](https://apify.com/leads-scraper/x-email-scraper) | Public contact emails from X |

### Example: Building a Recruiter List for a Job Search

Here is a realistic LinkedIn Email Scraper run. You are a backend engineer in the UK and want 150 recruiter contacts who publish an inbox.

Set `keywords` to `["technical recruiter", "talent partner", "engineering recruiter"]`, `location` to `London`, `countryCode` to `GB`, `customDomains` to `["@gmail.com", "@outlook.com"]` and `maxEmails` to `150`.

The LinkedIn Email Scraper builds base, quoted, `intitle:` and modifier variants per keyword - including `hiring` and `reach me` - then paginates the search results with five parallel workers. Rows stream into the dataset live.

Sort the LinkedIn Email Scraper dataset by `possiblyTruncated`, verify the flagged rows manually, then personalise using the `description` snippet, which usually contains the recruiter's stated specialism.

***

### LinkedIn Email Scraper FAQ

**Does the LinkedIn Email Scraper log into LinkedIn?**
No. It never authenticates, never opens linkedin.com and never uses LinkedIn's API. Every field comes from Google's public search results.

**Will using it get my LinkedIn account restricted?**
Your account is never involved. The LinkedIn Email Scraper runs on Apify against Google, not inside your browser session, so there is no extension and no session to flag.

**Where do the LinkedIn Email Scraper emails actually come from?**
From titles, snippets and site labels Google already publishes for indexed LinkedIn pages - typically headlines, summaries and Pulse articles where the member wrote the address themselves.

**Does it guess corporate emails like first.last@company.com?**
No. Nothing is permuted or inferred. The LinkedIn Email Scraper only reports addresses that literally appear in the indexed text.

**Why do some rows have no `username` or `profileUrl`?**
Because Google's result exposed no `/in/` path - usually a Pulse article, company page, job post or school page. Those rows still include `accountName`, the email and the snippet.

**What does `possiblyTruncated: true` mean?**
Google's snippet ellipsis touched the address, so it may be cut short. Treat those as leads to verify rather than send-ready contacts.

**How many emails can one LinkedIn Email Scraper run return?**
Free Apify plans stop at 100 emails per run. Paid plans are uncapped and bounded only by `maxEmails` and what Google has indexed.

**Why do I get fewer results than on other networks?**
LinkedIn restricts crawling, so Google indexes a smaller share of its pages. That is a real ceiling on this platform - widen keywords and domains rather than expecting Instagram-scale volume.

**Do I need a proxy to run the LinkedIn Email Scraper?**
Yes. It requires the Apify GOOGLE\_SERP proxy and will not run without Apify proxy credentials.

**Can I target a country or city?**
Yes. Use `location` for a phrase appended to every query and `countryCode` for the search proxy's country.

**Can I resume an interrupted run?**
Yes. Progress is saved in the key-value store, keyed by a hash of your input, and persists on Apify's `PERSIST_STATE`, `MIGRATING` and `ABORTING` events.

**Is scraping LinkedIn emails legal?**
The Actor collects only publicly indexed information, but how you use it is your responsibility. Follow GDPR, CAN-SPAM and local rules on unsolicited B2B outreach.

**How do I get more leads from one job title?**
Add query modifiers, widen `customDomains`, raise `maxPagesPerQuery` and run title synonyms - `talent partner`, `talent acquisition`, `recruiting lead` - rather than one term.

***

### Support

Questions about the LinkedIn Email Scraper, bug reports or a custom build? Email **neurodata.apify@gmail.com**.

# Actor input Schema

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

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

## `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": [
    "founder",
    "recruiter"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com",
    "@outlook.com",
    "@hotmail.com",
    "@icloud.com",
    "@aol.com",
    "@protonmail.com",
    "@live.com",
    "@gmx.com",
    "@mail.com",
    "@yandex.com",
    "@zoho.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "reach me",
    "hiring",
    "open to work"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

Records produced by LinkedIn 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": [
        "founder",
        "recruiter"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
        "@outlook.com",
        "@hotmail.com",
        "@icloud.com",
        "@aol.com",
        "@protonmail.com",
        "@live.com",
        "@gmx.com",
        "@mail.com",
        "@yandex.com",
        "@zoho.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "reach me",
        "hiring",
        "open to work"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leads-scraper/linkedin-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": [
        "founder",
        "recruiter",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
        "@outlook.com",
        "@hotmail.com",
        "@icloud.com",
        "@aol.com",
        "@protonmail.com",
        "@live.com",
        "@gmx.com",
        "@mail.com",
        "@yandex.com",
        "@zoho.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "reach me",
        "hiring",
        "open to work",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("leads-scraper/linkedin-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": [
    "founder",
    "recruiter"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com",
    "@outlook.com",
    "@hotmail.com",
    "@icloud.com",
    "@aol.com",
    "@protonmail.com",
    "@live.com",
    "@gmx.com",
    "@mail.com",
    "@yandex.com",
    "@zoho.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "reach me",
    "hiring",
    "open to work"
  ]
}' |
apify call leads-scraper/linkedin-email-scraper --silent --output-dataset

```

## MCP server setup

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