Company Employees Scraper for LinkedIn - No Cookies
Pricing
$5.00 / 1,000 employee founds
Company Employees Scraper for LinkedIn - No Cookies
Find the people who work at any company on LinkedIn without a login or cookies. Filter by role keywords to get just the decision makers, and every person is checked against the company before it is returned, so namesakes and ex-staff are dropped. Independent tool, not affiliated with LinkedIn.
Pricing
$5.00 / 1,000 employee founds
Rating
0.0
(0)
Developer
Scrape Sage
Maintained by CommunityActor stats
0
Bookmarked
13
Total users
8
Monthly active users
6 days ago
Last modified
Categories
Share
Disclaimer: This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by LinkedIn Corporation or any of its subsidiaries. All trademarks mentioned are the property of their respective owners. "LinkedIn" is referenced only to describe the publicly available website this Actor collects data from.
Give it companies, get the people who work there. No login, no cookies, no session tokens - and every person is checked against the company before you are charged for them, so namesakes and ex-staff do not end up in your list.
Point it at https://www.linkedin.com/company/stripe, a bare slug (stripe) or just a company name, and get back a verified employee list: name, job title where LinkedIn publishes it, seniority, department, location, profile URL, and the company's own firmographics on every row.
What makes this different
- Every row is verified. A plain web search for a company name returns namesakes (there is a real person called "Alain Vercel") and people who merely mention the company. This actor opens each candidate's public profile and confirms the company is actually their employer before emitting the row. Unverified candidates are dropped by default, and each row tells you exactly how it was confirmed via
verificationSource. - Find the decision makers, not just a headcount dump. Pass
roleKeywordslikeHead of Marketing,Account ExecutiveorVP Engineeringand it searches those roles across every company you gave it - the "find me the VP of Sales at these 40 accounts" job, in one run. - No cookies, no login, no LinkedIn account. Nothing to configure, nothing to get banned.
- Company firmographics included free. Industry, employee headcount, website, HQ and LinkedIn company id ride along on every row, so the output drops straight into a CRM.
Input
| Field | Type | What it does |
|---|---|---|
companies | array | Company LinkedIn URLs, slugs, or plain names. |
roleKeywords | array | Only find people matching these role phrases. Each is searched separately across every company. |
useRoleBuckets | boolean | When no role keywords are given, also search CEO / Founder / VP / Head of / Director / Manager. Default on. |
locationKeyword | string | Extra filter phrase, e.g. London. |
maxEmployeesPerCompany | integer | Cap per company, so one big company cannot eat the run. Default 25. |
maxResults | integer | Total cap for the run. 0 = no limit. Default 100. |
verifyEmployment | boolean | Open each profile and confirm the employer. Default on - turning it off is cheaper but returns unchecked matches. |
includeUnverified | boolean | Also return candidates that could not be confirmed, flagged employmentVerified: false. Default off. |
searchPages | integer | How deep to page each search. Default 2. |
maxConcurrency | integer | Profiles checked in parallel. Default 6. |
Output
One row per person. Company context is flat on every row, so a CSV export needs no joining.
{"type": "employee","fullName": "Paul Copplestone","firstName": "Paul","lastName": "Copplestone","jobTitle": "CEO","seniorityLevel": "Owner/C-Level","department": "Executive","headline": "CEO @ supabase.com","profileUrl": "https://www.linkedin.com/in/paulcopplestone","publicId": "paulcopplestone","locationName": "United States","city": "United States","country": "United States","profilePhotoUrl": "https://media.licdn.com/...","followerCount": 21458,"connectionCountText": "500+","education": "University of Auckland","companyName": "Supabase","companyUniversalName": "supabase","companyId": 68979500,"companyLinkedinUrl": "https://www.linkedin.com/company/supabase","companyIndustry": "Software Development","companyHeadcount": 411,"companyWebsite": "https://supabase.com","companyHqLocation": "San Francisco, California","employmentVerified": true,"verificationSource": "profile-worksfor-url","verificationConfidence": "high","publicProfileAvailable": true,"discoverySource": "web-search","leadScore": 79,"scrapedAt": "2026-08-07T02:31:00.000Z"}
Getting the most complete results
Use roleKeywords. It is the single biggest lever on data quality, and here is exactly why.
LinkedIn only publishes a member's job title to logged-out visitors when that member's headline is public. A role-targeted search finds precisely those people, so the rows come back with titles filled in. Measured on this actor's own runs:
| How you run it | Rows with a job title |
|---|---|
roleKeywords: ["VP", "Head of", "Director"] on Stripe | 20 of 25 (80%) |
| Broad company search, role buckets on (the default) | ~65% |
| Broad company search, role buckets off | ~17% |
So: name the roles you actually want, or leave useRoleBuckets on and it will sweep CEO / Founder / VP / Head of / Director / Manager for you. Every row still arrives verified either way - the difference is how many of them can show you a title.
What LinkedIn does not publish to logged-out visitors
Measured, not assumed - so you know the shape of the data before you buy.
- Job titles are not universal. For members whose headline is private, LinkedIn returns the title as an asterisk mask (
"*** * **********"). This actor emits an honestnullinstead of shipping you asterisks, and it will never put the company name in the title field to pad the column. A crawler user-agent does not unlock it either - that was tested across five (Chrome, Googlebot, Googlebot-mobile, Bingbot, DuckDuckBot). - Some members switch their public profile off entirely. Their profile URL answers HTTP 999 to every logged-out request - permanently, from any country, on any retry. Those people are still returned when the company page or the search index vouches for them, flagged
publicProfileAvailable: false, with location, photo, follower count and education null. That flag is there so you can filter rather than guess. - Depth is a targeted list, not a full org chart. This finds the people publicly indexed for a company, weighted toward decision makers. It does not enumerate all 17,000 employees of a mega-corp. For a specific role across a specific list of accounts, that is exactly what you want.
- Never returned: private profiles, connection graphs, personal email addresses and phone numbers. This actor reads only what LinkedIn serves to a logged-out visitor.
Pricing
Pay-per-event: $0.005 per verified employee. Runs that find nobody charge nothing, and every finished run tells you what to change.
Use with AI assistants (MCP)
This actor works as a tool in any MCP-compatible assistant through the Apify MCP server - ask your agent to "find the heads of marketing at these 20 companies" and it can call this actor directly.
Agent-ready: autonomous payments (x402 & Skyfire)
This actor is agent-ready — AI agents can discover it, run it, and pay for it autonomously, with no Apify account and no human in the loop. It uses pay-per-event pricing and limited permissions, so it qualifies for Apify's agentic-payment standards:
- x402 — an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the Apify MCP server — no account, no API key.
- Skyfire — agent-to-service payments for fully autonomous AI-agent workflows.
Building an AI agent, MCP tool, or autonomous data pipeline? This scraper is ready to plug in and pay as it goes.
Automate & schedule
Run this Actor on autopilot and pull results into your own stack:
- Apify API - start runs, fetch datasets and manage schedules over REST.
- apify-client for JavaScript and apify-client for Python - official SDKs.
- Schedules - run it hourly, daily or weekly and keep your dataset current.
- Webhooks - trigger downstream actions (CRM import, Slack alert, email sequence) the moment a run finishes.
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: 'MY_APIFY_TOKEN' });const run = await client.actor('scrapesage/linkedin-company-employees-scraper').call({"companies": ["https://www.linkedin.com/company/apify","supabase"],"maxEmployeesPerCompany": 25,"maxResults": 100,"verifyEmployment": true,"useRoleBuckets": true,"proxyConfiguration": {"useApifyProxy": true,"apifyProxyGroups": ["RESIDENTIAL"]}});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(`Got ${items.length} records`);
Integrate with any app
Connect the dataset to thousands of apps - no code required:
- Make - multi-step automation scenarios.
- Zapier - push new records straight into your CRM or spreadsheet.
- Slack - get notified when a scheduled run finds something new.
- Google Drive / Sheets - auto-export every run to a spreadsheet.
- Airbyte - pipe results into your data warehouse.
- GitHub - trigger runs from commits or releases.
More scrapers from scrapesage
Related Actors in the same category:
- Twitter (X) Scraper - Tweets, Profiles & Monitor
- Instagram Hashtag Scraper - Filtered Post Search
- LinkedIn Profile Scraper - People, Job Changes & B2B Leads
- LinkedIn Ad Library Scraper - Competitor B2B Ads & Creatives
- YouTube Scraper - Channels, Videos & Creator Leads
FAQ
How is this Actor billed? Pay-per-event: you pay only for the results it delivers, with no monthly rental and no start fee. The per-event price is shown on the Pricing tab.
Can I schedule it and get results automatically? Yes - create a Schedule and add a webhook or an integration (Google Sheets, Slack, Make, Zapier) to push each run's dataset wherever you need it.
Which export formats are available? Every run's dataset can be downloaded as JSON, CSV, Excel (XLSX), XML, HTML or RSS from the Apify Console or the API.
Can I run it from code or an AI agent? Yes - through the Apify API and client libraries, or from Claude, ChatGPT and other assistants via the Apify MCP server.
Is it legal to scrape LinkedIn? This Actor collects publicly available data only. You are responsible for using the output in compliance with applicable laws (including data-protection law where personal data is involved) and the source's terms. See Legal and the Disclaimer below.
Is this an official LinkedIn tool? No. It is an independent, third-party Actor with no affiliation to, endorsement by or sponsorship from LinkedIn Corporation. See the Disclaimer below.
Legal
This actor collects only data that LinkedIn publishes to logged-out visitors. It does not log in, does not use cookies or session tokens, and does not attempt to reach private profiles or connection graphs. Employee names and roles at a company are business contact information, but they still relate to identifiable people - if you are in the EU or UK, you are the data controller for what you do with the output, so make sure you have a lawful basis (usually legitimate interest for B2B prospecting) and honour deletion requests. Do not use this output for spam.
This actor is not affiliated with, endorsed by, or sponsored by LinkedIn Corporation. LinkedIn is a trademark of LinkedIn Corporation.
Disclaimer
This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by LinkedIn Corporation or any of its subsidiaries. All trademarks mentioned are the property of their respective owners.
"LinkedIn" and any related marks are the property of their respective owners and are used here only in a descriptive, nominative sense - to identify the publicly accessible website from which this Actor collects data. This Actor is not an official LinkedIn product, is not authorised or certified by LinkedIn Corporation, and does not distribute LinkedIn software. It collects only publicly available information; you are responsible for ensuring your use of that data complies with applicable laws, regulations and the terms of the source website.
Need help?
Open an issue on the Actor's Issues tab, or visit the Apify help center. Feature requests are welcome - this Actor is actively maintained.