Company Employees Scraper for LinkedIn - No Cookies

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 roleKeywords like Head of Marketing, Account Executive or VP Engineering and 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 honest null instead 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.

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.