# LinkedIn Profile Scraper + Email Finder ✅ No Cookies (`crustapi/linkedin-profile-scraper-email-finder`) Actor

Extract full LinkedIn profile data in bulk: work experience, education, certifications, followers, and numeric company ids, plus a verified work email with real email verification. Built for lead generation, recruiting and prospecting. No login, no cookies, no fake accounts.

- **URL**: https://apify.com/crustapi/linkedin-profile-scraper-email-finder.md
- **Developed by:** [CrustAPI](https://apify.com/crustapi) (community)
- **Categories:** Lead generation, Social media, AI
- **Features:** Limited permissions
- **Stats:** 599 total users, 184 monthly users, 99.0% runs succeeded, 2 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.50 / 1,000 profile details

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What is LinkedIn Profile Scraper + Email Finder?

Extract full LinkedIn profile data in bulk, without a LinkedIn account, and get a verified work email for each person. Paste public profile URLs, get clean JSON or CSV back: work experience, education, followers, numeric company IDs, and a real email checked live against the mail server. Built for lead generation, recruiting, and sales prospecting.

- 🔑 No login, no cookies, no browser extension, no fake accounts
- 👁️ Reads only what a logged-out visitor can see (public pages)
- 📧 Every email carries an `emailStatus`: `verified` (mailbox confirmed live on the mail server), `pattern-likely` (an unconfirmed best guess from a common name format) or `unknown` (none found)
- 💸 You are charged the email fee on `verified` only, so unconfirmed guesses come free. Filter on `emailStatus == "verified"` to keep just the confirmed ones
- 🆓 A profile that is not public costs nothing, and failed rows are never charged

### What data do I get?

Every accessible profile returns the fields LinkedIn shows publicly:

- **Identity**: name, first and last name, headline, photo, location (city, state, country)
- **Work**: current company, numeric company LinkedIn ID, company domain, industry, size, headquarters
- **History**: experience (company, company LinkedIn URL, location, start and end dates), education (school, school LinkedIn URL, degree, field of study), certifications, courses, languages, honors and awards, volunteering, organizations, projects, publications, recommendations
- **Reach**: follower count, connections count, influencer and creator flags
- **IDs**: public identifier, member ID, numeric LinkedIn identifiers
- **Email**: `workEmail` (also mirrored as `email`), `emailStatus` (`verified`, `pattern-likely` or `unknown`) and `emailConfidence`, a score filled in on verified addresses only

Job titles are the one real gap. LinkedIn no longer shows them to logged-out visitors, so `currentTitle` and `experience[].position` are null on most profiles. We fill a title in only when the headline states it unambiguously (roughly a third of profiles) and never guess at the rest. Other fields the person or their company has not published stay null too.

### Pricing

**$3.50 per 1,000 profiles** ($0.0035 each), plus **$9.00 per 1,000 verified emails** ($0.009 each) and only when the address comes back `verified`. Rows where the email is `pattern-likely` or `unknown` are delivered at no extra cost. Profiles that are not public, and rows that fail, cost nothing. There is no charge to start a run.

| Run | Actor cost |
|---|---|
| 1,000 profiles, no email lookup | $3.50 |
| 1,000 profiles, 300 verified emails | $6.20 |
| 10,000 profiles, 3,000 verified emails | $62 |

### How it works

1. Paste one or more profile URLs (or bare usernames), one per line
2. Leave "Find a verified work email" on, or switch it off for profile data only
3. Run. Each profile lands in the dataset as one row
4. Export JSON or CSV from the Storage tab, or pull results over the Apify API

Profiles are fetched several at a time, so a long list moves quickly. Measured on a real run: 8 profiles with the email lookup on in 14 seconds, about 1.7 seconds per profile. Switching the email lookup off is faster again.

### Output sample

Real output for one public profile, trimmed:

```json
{
  "name": "Dharmesh Shah",
  "headline": "Founder and CTO at HubSpot. Helping millions grow better.",
  "currentCompany": "HubSpot",
  "currentCompanyId": 68529,
  "companyDomain": "hubspot.com",
  "workEmail": "dharmesh.shah@hubspot.com",
  "email": "dharmesh.shah@hubspot.com",
  "emailStatus": "verified",
  "location": {
    "linkedinText": "Cambridge, Massachusetts, United States",
    "countryCode": "US",
    "parsed": { "city": "Cambridge", "state": "Massachusetts", "country": "United States" }
  },
  "followerCount": 1190598,
  "connectionsCount": 4285,
  "experience": [
    {
      "companyName": "HubSpot",
      "companyLinkedinUrl": "https://www.linkedin.com/company/hubspot",
      "endDate": { "text": "Present" }
    }
  ],
  "education": [
    {
      "schoolName": "Massachusetts Institute of Technology",
      "schoolLinkedinUrl": "https://www.linkedin.com/school/mit/"
    }
  ],
  "publicIdentifier": "dharmesh",
  "linkedinUrl": "https://www.linkedin.com/in/dharmesh"
}
```

Sales teams use it for lead generation and prospecting. Recruiters use it to source and enrich candidates. RevOps teams use it to keep a CRM current, one verified email at a time.

### LinkedIn Profile API

Everything here runs programmatically: pass a list of profiles and read enriched rows through the Apify API, or through any Apify integration (Zapier, Make, n8n, Google Sheets, webhooks). For a direct LinkedIn profile API with the same data outside Apify, the same engine powers [crustapi.com](https://crustapi.com/linkedin-api).

### FAQ

**Do I need a LinkedIn account or cookies?** No. The actor reads public pages the way a signed-out visitor sees them. There is no account to get restricted.

**What happens on private or deleted profiles?** You get a row saying the profile is not publicly accessible, and you are not charged for it.

**Where do the emails come from?** The company domain on the person's public profile plus common name patterns, checked live against the mail server. `verified` means the mailbox was confirmed. `pattern-likely` means nothing could be confirmed and the address is a best guess, so treat it as a lead, not a deliverable address. Filter to `verified` for the lowest bounce rate. It is also the only status you pay the email fee on.

**Can I run big lists?** Yes. Paste as many URLs as you like, or set Max profiles to cap a test run.

### More from CrustAPI

| Actor | What it does |
| --- | --- |
| [LinkedIn Jobs Scraper](https://apify.com/crustapi/linkedin-jobs-scraper) | Search jobs by title and city, full descriptions included |
| [LinkedIn Company Scraper](https://apify.com/crustapi/linkedin-company-scraper) | Company size, industry, IDs, and followers |
| [LinkedIn Company Posts Scraper](https://apify.com/crustapi/linkedin-company-posts-scraper) | Latest company posts with engagement |
| [LinkedIn Profile Posts Scraper](https://apify.com/crustapi/linkedin-profile-posts-scraper) | Latest posts from any public profile |

Need millions of profiles a month, or a custom feed? See [crustapi.com/wholesale](https://crustapi.com/wholesale).

### Support and feedback

Found a bug or missing a field? Open an issue on the Issues tab and it gets a same-day look, or email support@crustapi.com.

*This actor is not affiliated with, endorsed by, or sponsored by LinkedIn Corporation. It collects only publicly available data.*

# Actor input Schema

## `profiles` (type: `array`):

Public LinkedIn profile URLs (https://www.linkedin.com/in/...) or bare usernames, one per line.

## `findEmail` (type: `boolean`):

Also look up the person's work email. Every address carries an emailStatus: verified (confirmed live on the mail server), pattern-likely (an unconfirmed best guess) or unknown. You are charged the email fee on verified only.

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

Stop after this many profiles. 0 means process the whole list.

## Actor input object example

```json
{
  "profiles": [
    "https://www.linkedin.com/in/dharmesh",
    "https://www.linkedin.com/in/satyanadella",
    "https://www.linkedin.com/in/williamhgates"
  ],
  "findEmail": true,
  "maxItems": 0
}
```

# Actor output Schema

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

One row per profile: identity, company, education, reach and ids, plus a work email with its verification status when one is found.

# 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 = {
    "profiles": [
        "https://www.linkedin.com/in/dharmesh",
        "https://www.linkedin.com/in/satyanadella",
        "https://www.linkedin.com/in/williamhgates"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("crustapi/linkedin-profile-scraper-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 = { "profiles": [
        "https://www.linkedin.com/in/dharmesh",
        "https://www.linkedin.com/in/satyanadella",
        "https://www.linkedin.com/in/williamhgates",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("crustapi/linkedin-profile-scraper-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 '{
  "profiles": [
    "https://www.linkedin.com/in/dharmesh",
    "https://www.linkedin.com/in/satyanadella",
    "https://www.linkedin.com/in/williamhgates"
  ]
}' |
apify call crustapi/linkedin-profile-scraper-email-finder --silent --output-dataset

```

## MCP server setup

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