LinkedIn Email Finder API (No Cookies)

Find anyone's work email from a LinkedIn profile, without cookies, a login, or any setup. Paste profile links, handles, or IDs and get one clean row per person with the email plus their name, headline, company, and location, ready for Excel, CSV, or JSON.

🎯 What it does

Give it the LinkedIn profiles you want to reach. It accepts three input forms, mixed freely:

• Profile links. Full links like https://www.linkedin.com/in/janesmith/, including country links like fr.linkedin.com/in/janesmith.
• Handles. The short name from a link, the part after /in/. Example: janesmith.
• Profile IDs. LinkedIn's internal ID, if you already have it. Enter it as text, never as a number.

You get one row per person: their work email when one is publicly discoverable, plus their name, headline, current company, and location. Turn on optional extras for email validation, the full profile, a phone number, and company details. Export to Excel, CSV, or JSON, or pull through the Apify API.

📋 How to use it

Step 1: Add the people to look up

Paste profile links, handles, or IDs, one per line. You can mix all three. Duplicates are merged, so each person appears once.

• Profile links: linkedin.com/in/janesmith
• Handles: janesmith
• IDs: 123456789

Step 2: Choose the extras you need

Every row comes with the core email result and the person's public identity. Add any of these when you need more. Each fills in only where the data is available:

• Validate email. Checks the address is well formed, its domain can receive mail, and it is not a role inbox, a typo, or a throwaway.
• Full profile. Their complete public history: experience, education, certifications, languages, and more.
• Phone number. A number the person published on their own profile.
• Company details. The current employer's website, size, industry, and head office.

Step 3: Press Start and download

Rows appear as each profile is looked up, so you can watch the list fill up. When it finishes, open the Output tab and download as Excel, CSV, or JSON, or pull it through the Apify API.

Example output

One row per person. This is a basic row with no extras switched on:

{
  "status": "success",
  "email": "jane.smith@acme.com",
  "emailLookupStatus": "found",
  "fullName": "Jane Smith",
  "headline": "Marketing Manager at Acme",
  "currentCompanyName": "Acme",
  "location": "London, United Kingdom",
  "canonicalUrl": "https://www.linkedin.com/in/janesmith"
}

Switch on validation, full profile, phone, or company and those fields join the same row.

💎 Add-ons

Switch these on only when you need them. Each adds data only where it exists, so a miss just leaves the field empty.

• Validate email. A verdict (valid, risky, invalid, or unknown) with a score and the evidence behind it: format, domain and mail server checks, disposable, role based, typo, and placeholder checks, plus a mailbox existence check for common providers.
• Full profile. Experience, education, certifications, languages, projects, recommendations, publications, volunteer work, honors, recent posts, and summary.
• Phone number. A number the person published on their own profile, in standard international format when it is safe to normalize.
• Company details. The current employer's website and domain, industry, employee count, head office, founded year, and logo.

🤖 Use it from AI clients (MCP)

Call this Actor from Claude Code, Claude Desktop, Codex, Cursor, or any client that speaks the Model Context Protocol. Then just ask: "Find the work emails for these 50 LinkedIn profiles."

Every example needs an APIFY_TOKEN from console.apify.com/settings/integrations.

Claude Code

claude mcp add apify -- npx -y @apify/actors-mcp-server \
  --actors lurkapi/linkedin-email-finder-api

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "apify": {
      "command": "npx",
      "args": ["-y", "@apify/actors-mcp-server",
               "--actors", "lurkapi/linkedin-email-finder-api"]
    }
  }
}

Then add your token to that server's env block as APIFY_TOKEN.

Codex CLI

Edit ~/.codex/config.toml:

[mcp_servers.apify]
command = "npx"
args = ["-y", "@apify/actors-mcp-server",
        "--actors", "lurkapi/linkedin-email-finder-api"]

Add your token to the same block as an APIFY_TOKEN environment variable.

Cursor

Edit ~/.cursor/mcp.json using the same shape as the Claude Desktop example.

💰 Pricing

Free. This actor has no per-result or per-event fees. You only pay for the Apify platform usage each run consumes (compute and proxy) on your own Apify plan. Every field and add-on is included at no extra charge during this period.

💡 Good to know

• Not everyone has a public email. Most LinkedIn profiles do not publish one anywhere public. Expect a found email on a minority of rows, and a clean not_found when there is genuinely none.
• Emails are never guessed. The Actor only returns an address it can attribute to the person. When no lookup stage finds one, the row says so instead of inventing one.
• No login, no cookies. It never asks for a LinkedIn account, so there is no risk to your account.
• Each person appears once. Duplicate inputs are merged before any work, so you are never billed twice for the same person.
• Nothing disappears. Every invalid entry gets its own explanatory row.
• Your data stays in your Apify dataset. How long it is kept depends on your Apify plan.

❓ FAQ

Do I need a LinkedIn account or cookies? No. It never asks you to log in and never uses cookies, so there is no risk of your account being banned.

Why do some profiles have no email? Most people do not publish an email anywhere public. When every lookup stage completes without one, the row is marked not_found. The Actor never guesses an address.

What is the difference between not found and unavailable? Not found means the lookup completed and there is genuinely no reachable email. Unavailable means a lookup stage could not finish right now, so try again later.

Do I get work or personal emails? This Actor returns work emails only. It does not return personal addresses.

What does email validation check? It checks the address format, that the domain can receive mail, and whether it is disposable, role based, a common typo, or a placeholder, with a clear verdict and score. Delivery checks that need a direct mail server connection are not supported by the platform and stay blank.

Can I use it from the API, n8n, or Make? Yes. It runs on the standard Apify API, so you can trigger it from n8n, Make, or your own code and pull the results straight into your workflow.

🔗 Other tools you might like

• LinkedIn Profile Scraper API: full profiles, plus the emails and phone numbers people publish.
• LinkedIn Company Employees Scraper API: find the people who work at a company.
• LinkedIn Company Scraper API: company pages with size, industry, and head office.

⚖️ Disclaimer

Use this Actor in line with LinkedIn's Terms of Service and the data protection laws that apply to you (such as GDPR and CCPA). It only collects data that LinkedIn shows publicly. You are responsible for how you use the data, and the developer is not liable for misuse. What is available depends on LinkedIn at the time you run it.

Keywords: linkedin email finder, linkedin email lookup, find email from linkedin, linkedin work email, no cookies linkedin email finder, linkedin lead generation, b2b email finder, recruiter sourcing tool, sales prospecting emails, linkedin contact finder