Company Employees Scraper for LinkedIn - No Cookies

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 it is published, seniority, department, location, education, LinkedIn profile URL - and the company's own firmographics on every row, ready for a CRM or an outreach sequence.

What makes this different

• Every row is verified. A web search for a company name returns namesakes (plenty of people are called Gallagher) and people who used to work there. This Actor opens each candidate's public profile and confirms the company is their current employer before the row is emitted - someone whose own profile names a different employer is dropped, even if an old search result still lists them. Each row tells you how it was confirmed (verificationSource, verificationConfidence).
• Decision makers first. Leadership roles (CEO, Founder, VP, Head of, Director, Manager) are searched before anything else, and you can name your own: roleKeywords: ["Head of Marketing", "Account Executive"] finds those roles at every company you list - the "find me the VP of Sales at these 40 accounts" job, in one run.
• Company firmographics on every row, free. Industry, employee headcount, size band, company type, year founded, website, headquarters, street address, LinkedIn follower count, logo, tagline, description and specialties ride along on each person, so the export needs no joining.
• Bring your account list as it is. LinkedIn URLs, slugs or plain company names - typed in, pasted as a list, or linked as a .txt/.csv file or Google Sheet.
• No cookies, no login, no LinkedIn account. Nothing to configure, nothing to get banned.

How to use

1. Add your companies to Companies (or paste a list / link a file in Import companies from a file). A LinkedIn company URL is the most exact input.
2. Optionally add Role keywords to get only the roles you sell to.
3. Set Max employees per company and Max results to the size of list you want.
4. Run it, then export the dataset as CSV, Excel or JSON - or pull it into your CRM through an integration.

Input

Field	Type	What it does
companies	array	Company LinkedIn URLs, slugs, or plain names.
urlsFromFile	string	Paste a list of companies (one per line), or one link to a .txt/.csv file, Google Sheet or Google Drive file. A CSV is read by its first column.
roleKeywords	array	Only find people matching these role phrases. Each is searched across every company.
useRoleBuckets	boolean	When no role keywords are given, lead with CEO / Founder / VP / Head of / Director / Manager. Default on.
locationKeyword	string	Extra search 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 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 on engines that support paging. Default 2.
maxConcurrency	integer	Profiles checked in parallel. Default 6.
proxyConfiguration	object	Fallback proxy for any LinkedIn page the default lane cannot open. Keep the default.

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. Go to supabase.com/careers for…",
  "profileUrl": "https://www.linkedin.com/in/paulcopplestone",
  "publicId": "paulcopplestone",
  "locationName": "United States",
  "country": "United States",
  "profilePhotoUrl": "https://media.licdn.com/dms/image/v2/...",
  "followerCount": 38381,
  "connectionCountText": "500+",
  "education": "Y Combinator",
  "companyName": "Supabase",
  "companyUniversalName": "supabase",
  "companyId": 31546644,
  "companyLinkedinUrl": "https://www.linkedin.com/company/supabase",
  "companyIndustry": "IT Services and IT Consulting",
  "companyHeadcount": 456,
  "companyWebsite": "https://supabase.com",
  "employmentVerified": true,
  "verificationSource": "profile-worksfor-url",
  "verificationConfidence": "high",
  "publicProfileAvailable": true,
  "discoverySource": "web-search",
  "matchedQuery": "site:linkedin.com/in \"Supabase\"",
  "scrapedAt": "2026-10-01T23:02:26.301Z",
  "leadScore": 88,
  "schools": ["Y Combinator"],
  "companySize": "201-500 employees",
  "companyType": "Privately Held",
  "companyFounded": 2020,
  "companyFollowerCount": 118912,
  "companyTagline": "Build in a weekend. Scale to millions.",
  "companyDescription": "Build in a weekend. Scale to millions. Supabase is the Postgres development platform. Start your project with a Postgres Database, Authentication, instant APIs, and realtime subscriptions.",
  "companyLogoUrl": "https://media.licdn.com/dms/image/v2/...",
  "companyCountry": "United States"
}

Output fields

Field	What it holds
fullName, firstName, lastName	The person's name.
jobTitle, seniorityLevel, department	The current role, and the seniority band and department derived from it. Empty when no published copy of the profile carries a role - never guessed.
headline	The member's own one-line headline, when published.
profileUrl, publicId	The LinkedIn profile.
locationName, city, country	Where the person is based.
education, schools	Main school, and every school listed on the public profile.
profilePhotoUrl, followerCount, connectionCountText, about, externalLinks	Public-profile details.
company*	The company's LinkedIn page: name, id, URL, industry, headcount, size band, type, founded, website, HQ, street address, city, region, postal code, country, follower count, tagline, description, logo, specialties.
employmentVerified, verificationSource, verificationConfidence	How the person was confirmed as a current employee.
publicProfileAvailable	false when the member has switched their public profile off.
discoverySource, matchedQuery	Whether the person came from the company's own LinkedIn page or from a search, and which search found them.
leadScore	0-100, higher for verified, senior, complete rows.

Getting the most complete results

• Name the roles you want. roleKeywords is the biggest lever on data quality: a role search only matches people whose role is published, so far more rows arrive with a job title filled in.
• Leave useRoleBuckets on if you do not name roles - leadership roles are searched first.
• Plain names find the main company page. Many brands share their name with a smaller company that owns the obvious LinkedIn handle, so a plain name, bare slug or website (Notion, gong.io) is matched to the page of that name most people follow - Notion goes to linkedin.com/company/notionhq, not a small consultancy also called Notion. Every row shows the page used in companyLinkedinUrl. To choose a specific page yourself, paste its LinkedIn URL.
• Keep verifyEmployment on. It is what keeps ex-employees and namesakes out of your list.

What LinkedIn does not publish to logged-out visitors

So you know the shape of the data before you run it:

• Job titles are not universal. LinkedIn masks the job title on most logged-out profile pages. This Actor reads the role from the copies of the profile that search engines have indexed; when none of them carries a role, jobTitle (with seniorityLevel and department) stays empty rather than being guessed. It never puts the company name or a location in the title field to pad the column.
• Some members switch their public profile off. Their profile URL cannot be opened by anyone who is logged out. They are still returned when the company's own LinkedIn page or a search entry shows them working there, flagged publicProfileAvailable: false, with location, school and connection count taken from that entry when it has them; photo, follower count, about and the school list stay empty.
• Company details depend on the company. Street address, region, founding year, specialties and tagline appear only when the company published them on its LinkedIn page.
• Depth is a targeted list, not a full org chart. It finds the people publicly indexed for a company, weighted toward decision makers - not all employees of a large enterprise.
• Discovery uses public search engines. People are found through public web search, then confirmed on LinkedIn itself. Search engines rate-limit at times; a run that meets a refusing search engine says so in its status message and returns fewer people - re-run later. Nobody is billed for people who were not found.
• Never returned: private profiles, connection graphs, personal email addresses and phone numbers.

How much does it cost to scrape LinkedIn?

This Actor uses Apify's pay-per-event pricing: you pay for each employee it delivers and, from 19 October 2026, a small fee when each run starts. There is no monthly rental. The events it can charge are:

• Actor start - Apify's standard run-start event, charged once when a run starts (from 19 October 2026).
• Employee found - One person confirmed to work at the requested company, with job title, seniority, department, location, LinkedIn profile URL, company firmographics and a lead score.

The current price of each event is shown on the Pricing tab of this page. Set a maximum total charge on the run if you want a hard cap on spend, and use the input limits to control how much the Actor fetches.

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, with no account and 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 for each employee it delivers and, from 19 October 2026, a small fee when each run starts. There is no monthly rental. The per-event prices are 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 Data & lawful use 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.

Data & lawful use

This Actor reads only what LinkedIn publishes to logged-out visitors: it does not log in, use cookies or session tokens, create accounts, or reach anything behind a sign-in. Names, handles, bios and engagement figures are public, but they relate to identifiable people, so treat the output as personal data. If you are in the EU or UK you are the data controller for what you do with it: have a lawful basis (usually legitimate interest for research, marketing analytics or B2B prospecting), honour access and deletion requests, and do not use the output for spam or unsolicited messaging.

Under Apify's Standard Actor Contract, which governs your use of this Actor, you are the controller of any personal data in your input and output and scrapesage acts only as your processor: that data is processed solely to run your job, written only to your own Apify storage, never used for any other purpose and never shared onward. If you need help with a data-subject request that involves this Actor's output, open an issue on the Issues tab.

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.