# LinkedIn Profile Scraper + Email Finder — No Cookies (`korado_labs/linkedin-profile-scraper`) Actor

Scrape LinkedIn profiles without cookies: name, headline, company, past roles, education, followers — plus verified work emails. Export scraped data, run the scraper via API, schedule and monitor runs, or integrate with other tools.

- **URL**: https://apify.com/korado\_labs/linkedin-profile-scraper.md
- **Developed by:** [Korado Labs](https://apify.com/korado_labs) (community)
- **Categories:** Lead generation, Social media, 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 scrapeds

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 Scraper + Email — No Cookies

Scrape **public LinkedIn profiles** with no login and no cookies. Paste profile
URLs (or bare public identifiers) and get structured data back, with an optional
**verified work-email finder**.

### What you get per profile

- Full name, first/last name
- Headline / summary
- Current company + full work history (company names & LinkedIn URLs)
- Education
- Location (country + locality)
- **Follower count**
- Languages, awards, profile photo
- Optional: **verified work email** (name + company → domain → pattern → deliverability)

### Input

Paste any of these (all accepted, so it's a drop-in for other LinkedIn actors):

| Field | What |
|---|---|
| `profileUrls` | LinkedIn profile URLs or bare identifiers |
| `urls`, `queries`, `publicIdentifiers` | Aliases for easy migration |
| `findEmail` | `true` to also find work emails (or set `profileScraperMode` to `email`) |
| `verifierApiUrl` | Optional HTTPS verifier endpoint containing `{email}` for true mailbox checks |
| `maxItems` | Optional cap |
| `proxy` | Residential recommended (datacenter IPs are soft-blocked) |

```json
{
  "profileUrls": [
    "https://www.linkedin.com/in/williamhgates",
    "melindagates"
  ],
  "findEmail": true
}
```

### Pricing (pay per event)

- **Profile scraped** — $0.004 each. Blocked / not-found / demo profiles are free.
- **Work email found** — $0.005, only when an email is actually returned.
- **Actor start** — $0.005 once per run.

### Notes

- Uses **residential proxy** by default — LinkedIn soft-blocks datacenter IPs (HTTP 999).
- Emails are found by generating common corporate patterns and checking
  deliverability. Apify blocks outbound SMTP (port 25), so without a
  `verifierApiUrl` emails come back at MX-level confidence; set an HTTPS verifier
  (e.g. Reoon, MillionVerifier) for mailbox-confirmed results.
- Only **public** profile data is collected.

# Actor input Schema

## `profileUrls` (type: `array`):

LinkedIn profile URLs to scrape, e.g. https://www.linkedin.com/in/williamhgates. You can also paste bare public identifiers (williamhgates).

## `urls` (type: `array`):

Alias of profileUrls for drop-in migration from other LinkedIn actors.

## `publicIdentifiers` (type: `array`):

The last part of a profile URL, e.g. williamhgates. Alias for drop-in migration.

## `queries` (type: `array`):

Alias accepting profile URLs, for drop-in migration from other LinkedIn actors.

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

Also find and verify a work email for each profile (name + company → domain → pattern → deliverability). Charged only when an email is found.

## `profileScraperMode` (type: `string`):

Migration alias: set to 'email' to enable the work-email finder (same as turning on Find work email).

## `verifierApiUrl` (type: `string`):

Optional HTTPS email-verification endpoint containing {email} (e.g. Reoon, MillionVerifier). When set, emails are mailbox-verified over HTTPS. Without it, emails are returned at MX-level confidence (Apify blocks SMTP port 25).

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

Optional cap on the number of profiles to scrape this run.

## `navigationTimeout` (type: `integer`):

Per-request timeout in seconds.

## `proxy` (type: `object`):

Proxy settings. Residential is strongly recommended — datacenter IPs are soft-blocked by LinkedIn (HTTP 999).

## Actor input object example

```json
{
  "profileUrls": [
    "https://www.linkedin.com/in/williamhgates",
    "https://www.linkedin.com/in/melindagates"
  ],
  "findEmail": false,
  "navigationTimeout": 30,
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

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

Scraped LinkedIn profiles with optional verified work emails.

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

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

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

```

## MCP server setup

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