# LinkedIn Profile Email Finder (`thenetaji/linkedin-profile-email-finder`) Actor

Turn a list of LinkedIn profiles into work email addresses. Each person's current employer is read off their profile, that company's address format is derived from addresses it already publishes, and the name is rendered under it — with the real addresses behind the format on every row.

- **URL**: https://apify.com/thenetaji/linkedin-profile-email-finder.md
- **Developed by:** [The Netaji](https://apify.com/thenetaji) (community)
- **Categories:** Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 profile with an addresses

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
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 Profile Email Finder

Give it a list of LinkedIn profiles and it returns each person's work email address. No company list, no domain, no email format to supply — the current employer is read off the profile, the company's address format is derived from addresses that company already publishes, and the person's name is rendered under it.

### Accepted input

| Field | Type | Default | Description |
|---|---|---|---|
| `username` | array of strings | — | Required. One line per person — a `/in/` profile URL or a username. |
| `verify_emails` | boolean | `false` | Confirm each address against the company's mail server before returning it. |
| `max_candidates` | integer | `3` | Ranked alternates to return per person, 1–5. |
| `maxItems` | integer | `100` | Maximum profiles to resolve. `0` removes the limit. |

```json
{
  "username": [
    "https://www.linkedin.com/in/yanbingli",
    "https://www.linkedin.com/in/sean-walters"
  ],
  "verify_emails": true
}
```

### What comes back

| Field | Description |
|---|---|
| `name`, `headline`, `location`, `profile_url` | Who the row is about |
| `target_company` | The employer read off the profile |
| `company_domain` | The mail domain used to build the address |
| `email` | Best-match work email |
| `email_confidence` | How much to trust it, `0`–`1`, per name rather than per company |
| `email_status` | `best_match` when a format was derived, `guess` when only ranking was possible |
| `email_candidates` | Ranked alternates worth trying if the first bounces |
| `email_verified` | True only when a mailbox was confirmed to exist |
| `email_pattern`, `email_pattern_rule` | The company's format and the full rule behind it |
| `email_pattern_evidence` | Real addresses at that company the format was derived from |

### Why the addresses come with evidence

Most tools assume `first.last` because it is the most common layout. It is wrong often enough to matter: some companies use first names alone, some join every surname token, some keep particles like `de` and `van`, and some truncate a hyphenated family name while collapsing a hyphenated given one. Two people at the same company can render very differently, which is why confidence is reported per person.

Every row carries the real published addresses its format came from, so the format can be checked rather than believed.

### Cost of a long list

A company's format is worked out once. The first person at an employer pays for that; everyone else on the same payroll is rendered under the format already in hand. A list of 200 people across 20 companies does 20 derivations, not 200.

### What it cannot do

Only the employer LinkedIn shows publicly is used. A signed-out view of a profile names the current employer in the clear and masks every earlier one, and an address built from a job somebody left will bounce — so a masked employer is refused rather than guessed at, and a profile with nothing readable is skipped and not charged for.

Around 40% of company domains accept every address (catch-all). No mailbox can be confirmed on those by anyone, so they are reported as unverifiable rather than guessed at, and verification is never charged for them.

Free sources of published addresses are uneven. They are rich for companies that publish code and for firms with public staff directories, and can be absent entirely. A profile whose employer yields no format is not returned and not charged for.

### Pricing

Charged per profile that comes back with an address. Verified addresses cost extra, and only when a mailbox is actually confirmed.

# Actor input Schema

## `username` (type: `array`):

One line per person — a /in/ profile URL or a username. Their current employer is read off the profile, so no company list is needed.

## `verify_emails` (type: `boolean`):

Confirm each address against the company's mail server before returning it. Around 40% of company domains accept every address (catch-all), where no mailbox can be confirmed by anyone — those are reported as unverifiable rather than guessed at, and are never charged for.

## `alternate_emails` (type: `boolean`):

Return the runner-up addresses alongside the best one, each with the format rule and confidence behind it. Off by default: one address per person is the answer, and a column of near-identical alternates next to it reads as uncertainty rather than as options. Turn it on when you intend to try the alternates after a bounce.

## `maxItems` (type: `integer`):

Maximum profiles to resolve. Set 0 for no limit.

## Actor input object example

```json
{
  "username": [
    "satyanadella"
  ],
  "verify_emails": false,
  "alternate_emails": false,
  "maxItems": 20
}
```

# Actor output Schema

## `dataset` (type: `string`):

All records scraped by this run

# 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 = {
    "username": [
        "satyanadella"
    ],
    "maxItems": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("thenetaji/linkedin-profile-email-finder").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 = {
    "username": ["satyanadella"],
    "maxItems": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("thenetaji/linkedin-profile-email-finder").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 '{
  "username": [
    "satyanadella"
  ],
  "maxItems": 20
}' |
apify call thenetaji/linkedin-profile-email-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,thenetaji/linkedin-profile-email-finder"
        }
    }
}

```

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/ERqc6POiNAHYjuNWU/builds/1wt1rao7305PPlLSb/openapi.json