LinkedIn People + Email Scraper (no cookies) avatar

LinkedIn People + Email Scraper (no cookies)

Pricing

$8.00 / 1,000 linkedin person scrapeds

Go to Apify Store
LinkedIn People + Email Scraper (no cookies)

LinkedIn People + Email Scraper (no cookies)

Bulk-scrape public LinkedIn profiles and find verified work emails — name, headline, company, location + SMTP-verified email. No login, no cookies, no API key.

Pricing

$8.00 / 1,000 linkedin person scrapeds

Rating

0.0

(0)

Developer

MYM

MYM

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

0

Monthly active users

3 hours ago

Last modified

Share

LinkedIn People Scraper — Scrape LinkedIn Profiles & Verified Work Emails (No API Key, No Login)

Turn a list of public LinkedIn profile URLs into clean, structured people data plus SMTP-verified work emails — full name, headline, company, location, image, and email — in a single run. No login, no cookies, no account, and no API key required. Export scraped data to JSON, CSV, Excel, or XML, schedule runs via API, and integrate with your tools and AI workflows.

Built for AI agents: call this actor straight from Claude, ChatGPT / Codex, and Cursor through the Apify MCP server to enrich leads and build contact lists conversationally.

Try Now Input Schema API Docs

What it does · AI agents (MCP) · How to scrape · Output fields · Limits · Output example · Pricing · Integrations · FAQ · Other actors


What can LinkedIn People Scraper do? {#what-can-linkedin-people-scraper-do}

LinkedIn People Scraper takes a list of public LinkedIn profile URLs and returns structured people records — and, optionally, a verified work email for each person. It is built for sales, recruiting, and research teams who need to scrape LinkedIn people and enrich contacts at scale without touching a browser, a login, or a cookie.

Feed it profile URLs like https://www.linkedin.com/in/williamhgates, and it gives you back a clean JSON row per person: full name, headline, current company, location, profile image, and a work-email block with the best candidate, an SMTP verification status, and a ranked list of fallbacks. It only collects publicly available data, runs entirely in the cloud, and needs no API key and no loginno cookies or account required. Get your first results free in under 2 minutes.

  • Scrape LinkedIn people in bulk — paste a handful of URLs or up to 500 per run.
  • Find & verify work emails — SMTP-checked, with a confidence score.
  • 🗂️ Clean, structured records — flat JSON ready for a CRM or spreadsheet.
  • 💬 Ranked email candidates — fallbacks ready when the first send bounces.
  • Zero setup — no proxies, no session cookies, no external keys.
  • 🚀 Fast, fresh data — parallel fetching finishes large lists in seconds.

✅ Verified work-email discovery

For every profile, the LinkedIn People Scraper can derive the person's likely work email using company-domain pattern matching, then confirm it over SMTP. Each result carries an emailStatus of verified, catch-all, or unverified, plus an emailConfidence score, so you know exactly how much to trust each address before you send.

🗂️ Clean, structured people records

No parsing HTML yourself. Each person comes back as a flat, predictable object — fullName, firstName, lastName, headline, company, location, image, and profileUrl — ready to drop straight into a CRM, spreadsheet, or database.

💬 Ranked email candidates

Beyond the single best email, the actor returns an emailCandidates array of every plausible address pattern for the person and domain (for example first.last@, firstlast@, flast@). If your first send bounces, the fallbacks are already there.

📊 Bulk mode — scrape LinkedIn people at scale

Point it at a handful of URLs or up to 500 profiles per run in parallel "mass mode." Tune throughput with a single concurrency field. There are no limitations on requests — it is designed for enriching entire prospect lists in a single pass.

🔄 Domain override for accuracy

Know the target company's email domain already? Pass companyDomain (e.g. microsoft.com) to force it for the whole run instead of auto-detecting per profile — perfect for enriching one company's org chart.

⚡ Zero setup — no login, no cookies, no API key

There is nothing to configure. No LinkedIn account, no session cookies, no proxy setup, and no external API keys. The actor handles connectivity, rotation, and retries for you, so you can go beyond the limitations of the official LinkedIn API. Paste URLs, hit run.


Use LinkedIn People Scraper with AI agents — Claude, ChatGPT & Cursor (MCP) {#use-linkedin-people-scraper-with-ai-agents-mcp}

This actor is fully compatible with the Apify MCP server, so AI agents and assistants can call it as a tool and scrape LinkedIn people on demand.

  • Claude (Desktop, Code, or the API) — add the Apify MCP server and ask Claude to "enrich these 40 LinkedIn URLs and find verified emails."
  • ChatGPT / Codex — expose the actor as a tool and let the model build contact lists for you.
  • Cursor — call the scraper from inside your editor while you build outreach automations.

Once the data lands in an Apify dataset, you can pipe it onward through MCP connectors and no-code tools — Slack, Notion, Airtable, Google Sheets, Zapier, Make, and n8n — to update your CRM, notify a channel, or trigger a sequence automatically.


How to scrape LinkedIn people and emails {#how-to-scrape-linkedin-people-and-emails}

Scraping LinkedIn people takes a few clicks — no login and no API key:

  1. Open the LinkedIn People Scraper on Apify (or add it to your account for free).
  2. Paste one or more public LinkedIn profile URLs into the profileUrls field.
  3. Leave findEmail on (default) to also derive and SMTP-verify a work email for each person.
  4. (Optional) Set companyDomain if you already know the company's email domain.
  5. (Optional) Adjust maxItems (up to 500) and concurrency (up to 12) for large lists.
  6. Click ▶ Start / Save & Run.
  7. When the run finishes, export the scraped data as JSON, CSV, Excel, or XML, or pull it via the API.

No account, no cookies, and no API key required — the actor takes care of everything.


What data can you scrape from LinkedIn people? {#what-data-can-you-scrape-from-linkedin-people}

Each profile produces one dataset item with the following fields:

FieldTypeDescription
okbooleanWhether the profile was processed successfully.
fullNamestringPerson's full display name.
firstNamestringParsed first name.
lastNamestringParsed last name.
headlinestringLinkedIn headline / current role text.
companystringCurrent company name.
companyLinkedInstring / nullCompany's LinkedIn URL, when available.
locationstringPerson's location.
imagestring / nullProfile image URL, when available.
profileUrlstringCanonical LinkedIn profile URL.
inputUrlstringThe URL you supplied (for matching back to your list).
foundbooleanWhether a work email was found.
emailstringBest / recommended work email.
emailStatusstringverified, catch-all, or unverified.
emailConfidencestringConfidence in the chosen email (high / medium / low).
emailDomainstringDomain used for email derivation.
emailSourcestringHow the email was derived (e.g. smtp-pattern).
emailCandidatesarrayRanked list of all plausible email addresses.

Use cases for scraping LinkedIn people

  • B2B lead enrichment — turn a list of prospect profile URLs into contactable records with verified emails.
  • Outbound sales prospecting — build targeted contact lists for cold email and multichannel outreach.
  • Recruiting & sourcing — enrich candidate shortlists with current role, company, location, and email.
  • CRM hygiene — refresh stale contacts and fill in missing email addresses.
  • Account-based marketing — enrich an entire target company's people using the companyDomain override.
  • Market & talent research — collect structured people data across an industry or region.
  • Competitor analysis — map the teams and hires behind competing companies.
  • Data appending — append verified emails to existing spreadsheets of LinkedIn URLs.

Input examples

All examples use the real input field names from the actor's schema.

Scrape a few LinkedIn people with email discovery (default)

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

Scrape LinkedIn people data only (skip email finding)

{
"profileUrls": [
"https://www.linkedin.com/in/williamhgates"
],
"findEmail": false
}

Force a specific company email domain

Use this when you are enriching people who all work at the same company:

{
"profileUrls": [
"https://www.linkedin.com/in/satyanadella"
],
"findEmail": true,
"companyDomain": "microsoft.com"
}

Bulk mode — scrape a large list of LinkedIn people at once

{
"profileUrls": [
"https://www.linkedin.com/in/williamhgates",
"https://www.linkedin.com/in/satyanadella",
"https://www.linkedin.com/in/jeffweiner08",
"https://www.linkedin.com/in/reidhoffman"
],
"findEmail": true,
"maxItems": 500,
"concurrency": 12
}

Balanced throughput for medium lists

{
"profileUrls": [
"https://www.linkedin.com/in/williamhgates",
"https://www.linkedin.com/in/satyanadella"
],
"findEmail": true,
"maxItems": 100,
"concurrency": 8
}

Input parameters reference

FieldTypeDefaultDescription
profileUrlsarray (required)Public LinkedIn profile URLs to scrape.
findEmailbooleantrueDerive and SMTP-verify a work email for each person.
companyDomainstring(auto)Force a specific company email domain for all profiles in the run.
maxItemsinteger100Max profiles per run — up to 500 (mass mode, parallel).
concurrencyinteger8How many profiles to fetch in parallel (1–12; higher = faster).

Limiting results {#limits}

  • maxItems — caps how many profiles a single run will process. Default is 100; you can raise it up to 500 for mass enrichment, or lower it to control cost on small tests.
  • concurrency — controls how many profiles are fetched in parallel (1–12, default 8). Higher values finish large lists faster.

To run a quick, cheap test, set maxItems to a small number and pass just one or two URLs.


Output example {#output-example}

A single dataset item looks like this (real sample):

{
"ok": true,
"email": "bill.gates@gatesfoundation.org",
"found": true,
"image": null,
"company": "Gates Foundation",
"fullName": "Bill Gates",
"headline": "Chair, Gates Foundation and Founder, Breakthrough Energy",
"inputUrl": "https://www.linkedin.com/in/williamhgates",
"lastName": "Gates",
"location": "Seattle",
"firstName": "Bill",
"profileUrl": "https://www.linkedin.com/in/williamhgates",
"emailDomain": "gatesfoundation.org",
"emailSource": "smtp-pattern",
"emailStatus": "catch-all",
"companyLinkedIn": null,
"emailCandidates": [
"bill.gates@gatesfoundation.org",
"billgates@gatesfoundation.org",
"bgates@gatesfoundation.org",
"bill_gates@gatesfoundation.org",
"b.gates@gatesfoundation.org",
"gatesb@gatesfoundation.org",
"bill@gatesfoundation.org"
],
"emailConfidence": "low"
}

How much does it cost to scrape LinkedIn people? {#how-much-does-it-cost-to-scrape-linkedin-people}

This actor uses a simple, pay-per-result model — you are billed for the profiles you enrich, not for idle compute time. Because it fetches profiles in parallel and returns compact structured records, runs are fast and cost-efficient even for large lists. Get your first results free in under 2 minutes on Apify's free plan.

To keep costs predictable:

  • Start with a small maxItems value to validate your URLs.
  • Turn off findEmail if you only need people data (email verification is the heavier step).
  • Batch your list into a single run rather than many one-off runs.

See the live per-result price on the actor's Apify page.


Integrate LinkedIn people data with n8n, Zapier, and Make {#integrations}

Run the actor and get results directly from the Apify API. Use the actor path myagizm~linkedin-people-scraper.

Synchronous — run and get dataset items in one call

curl -X POST "https://api.apify.com/v2/acts/myagizm~linkedin-people-scraper/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"profileUrls": [
"https://www.linkedin.com/in/williamhgates"
],
"findEmail": true
}'

Asynchronous — start a run, then fetch results

# 1) Start a run
curl -X POST "https://api.apify.com/v2/acts/myagizm~linkedin-people-scraper/runs?token=YOUR_APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"profileUrls": [
"https://www.linkedin.com/in/williamhgates",
"https://www.linkedin.com/in/satyanadella"
],
"findEmail": true,
"maxItems": 100
}'
# 2) Fetch the run's dataset items when it finishes
curl "https://api.apify.com/v2/datasets/DATASET_ID/items?token=YOUR_APIFY_TOKEN&clean=true&format=json"

You can wire these calls into Make, Zapier, n8n, Slack, Airbyte, Gumloop, CrewAI, IFTTT, Lindy, GitHub, Google Sheets, and Google Drive to enrich leads and push contacts automatically. AI agents can do the same through the Apify MCP server.


Support {#support}

Questions, edge cases, or a field you'd like added? Open an Issue on the actor's Apify page and we'll respond. We actively maintain the scraper and welcome feedback on new fields and improvements.


FAQ — scraping LinkedIn people {#faq}

The actor only accesses publicly available profile information. You are responsible for using the data in compliance with applicable laws (such as GDPR/CCPA) and LinkedIn's terms. Use it for legitimate business purposes like sales, recruiting, and research.

Do I need a LinkedIn account, login, or cookies to scrape LinkedIn people?

No. There is no login, no session cookie, and no API key. Paste public profile URLs and run — no cookies or account required.

Can I use LinkedIn People Scraper with the Apify API?

Yes. Start runs and fetch datasets through the Apify API using the actor path myagizm~linkedin-people-scraper. Sync and async examples are shown above.

Can I scrape LinkedIn people through an MCP server (AI agents)?

Yes. The actor works with the Apify MCP server, so Claude, ChatGPT, and Cursor can call it as a tool to scrape and enrich people on demand.

Do I need proxies to scrape LinkedIn people?

No. The actor handles connectivity, rotation, and retries for you — nothing to configure and no proxies to bring.

Can I integrate LinkedIn people data with other apps?

Yes. Push results into Make, Zapier, n8n, Slack, Google Sheets, Airtable, Notion, and more via the API, webhooks, or MCP connectors.

Can I export scraped LinkedIn people to CSV, Excel, or JSON?

Yes. Results are stored in an Apify dataset and can be exported to JSON, CSV, Excel, or XML, or pulled via the API.

Can I scrape multiple LinkedIn people at once?

Yes — up to 500 profiles per run via the maxItems field, processed in parallel. Set concurrency (up to 12) to control speed. There are no limitations on the number of runs.

Can I schedule the LinkedIn People Scraper?

Yes. Use Apify Schedules to run enrichment daily, weekly, or on any cron you like.

Can I scrape data from private LinkedIn accounts?

No. The actor only works with public LinkedIn /in/ profiles. Private or restricted profiles may return limited or no data.

How accurate are the emails?

Each email carries an emailStatus (verified, catch-all, or unverified) and an emailConfidence score. Verified means the address was confirmed over SMTP. Catch-all means the domain accepts all addresses, so treat it as probable, not guaranteed. Always check these fields before sending.

What is the emailCandidates list for?

It's a ranked set of every plausible email pattern for the person and domain. If the primary email bounces, use the next candidate as a fallback.

Can I skip email finding and just get profile data?

Yes — set findEmail to false. This is faster and cheaper when you only need name, headline, company, and location.

Can I force a specific email domain?

Yes. Set companyDomain (e.g. microsoft.com) and it applies to every profile in the run, overriding auto-detection.

Can I match results back to my input list?

Yes — every item includes inputUrl, the exact URL you supplied, so you can join results back to your source rows.

How fast is it?

It fetches profiles in parallel, so large lists finish quickly. Increase concurrency for more throughput; lower it if you want gentler runs. Fast, fresh data every run — no caching.


Want other LinkedIn data? {#want-other-linkedin-data}

Scrape more of LinkedIn with the rest of the myagizm LinkedIn family — same no-login, no-API-key approach:


Disclaimer

This is an independent tool and is not affiliated with, endorsed by, or sponsored by LinkedIn. All product names, logos, and brands are property of their respective owners. Use this actor only to collect publicly available data and in compliance with applicable laws and platform terms.


Resources {#resources}