LinkedIn Company Employees Scraper - No Cookies, Pay Per Result
Pricing
from $5.00 / 1,000 results
LinkedIn Company Employees Scraper - No Cookies, Pay Per Result
Build B2B prospect lists from any company on LinkedIn. Two modes: Basic (name, headline, URL) or Full (work history, education, skills, certifications, languages, location). Filter by job title and location. No login or cookies required. Works inside Claude, ChatGPT, and any MCP-compatible agent.
Pricing
from $5.00 / 1,000 results
Rating
5.0
(1)
Developer
Thirdwatch
Maintained by CommunityActor stats
7
Bookmarked
564
Total users
181
Monthly active users
3.7 hours
Issues response
a day ago
Last modified
Categories
Share
LinkedIn Company Employees Scraper
Thirdwatch portfolio: 5K users across 88 public Actors, 2M+ records delivered, and >99% run success. Explore all Thirdwatch Actors.
Build structured employee lists from public LinkedIn results for target accounts, competitors, and hiring markets. Search by company name or LinkedIn company URL, optionally filter by job title and location, and export clean JSON for CRM enrichment, recruiting research, ABM, or market analysis.
No LinkedIn login, cookies, Sales Navigator seat, or browser session is required.
Value proposition
Most sales and recruiting workflows need the same first step: turn a company into a usable list of people. This actor does that from public LinkedIn data, returning employee names, profile URLs, headlines, current roles, and optional full profile enrichment.
Use it when you need:
- Prospect lists for named accounts
- Engineering, sales, product, or leadership maps by company
- Competitor talent research
- CRM refreshes for people tied to specific accounts
- A URL source for deeper enrichment with LinkedIn Profile Scraper
What's new
- Company URL or company-name input: use precise LinkedIn company URLs when you have them, or simple company names when you do not.
- Basic and Full modes: start with fast profile discovery, then enrich selected profiles with deeper public profile fields.
- Title and location filters: narrow searches before results are returned.
- Apify-ready JSON output: export directly to datasets, webhooks, API clients, or MCP-compatible agents.
What data you get
Basic mode
| Field | Description |
|---|---|
fullName | Employee full name |
headline | Public LinkedIn headline |
url | LinkedIn profile URL |
experience | Current visible role or headline-derived position |
sourceCompany | Company searched in the run |
Full mode
Full mode includes the Basic fields plus deeper public profile enrichment when available.
| Field | Description |
|---|---|
publicIdentifier | LinkedIn profile slug |
location | Public profile location |
about | Public profile summary |
profilePhoto | Profile image URL |
followersCount | Public follower count |
experience | Work history with company, role, dates, duration, and location when available |
education | Schools, degrees, fields of study, and dates when available |
skills | Listed skills when available |
certifications | Listed certifications when available |
languages | Listed languages when available |
Quick-start input examples
1. Fast employee discovery by company URL
{"queries": ["https://www.linkedin.com/company/stripe/"],"mode": "basic","maxResults": 50}
2. Find engineering employees at one company
{"queries": ["https://www.linkedin.com/company/anthropic/"],"mode": "basic","jobTitle": "Software Engineer","location": "San Francisco","maxResults": 100}
3. Enrich profiles for multiple target accounts
{"queries": ["Stripe", "Datadog", "https://www.linkedin.com/company/anthropic/"],"mode": "full","jobTitle": "Product Manager","maxResults": 25}
Input parameters
| Parameter | Required | Default | Description |
|---|---|---|---|
queries | Yes | - | Company names, company-style searches, or LinkedIn company URLs. |
mode | No | basic | Use basic for discovery or full for profile enrichment. |
jobTitle | No | - | Optional title filter such as Software Engineer, VP Sales, or Product Manager. |
location | No | - | Optional location filter such as San Francisco, London, or India. |
maxResults | No | 50 | Maximum employees per company, up to the actor limit. |
Sample output snippet
{"fullName": "Jane Smith","headline": "Senior Software Engineer at Anthropic","url": "https://www.linkedin.com/in/janesmith/","publicIdentifier": "janesmith","location": "San Francisco, California, United States","about": "Building applied AI systems.","profilePhoto": "https://media.licdn.com/dms/image/...","followersCount": 2450,"experience": [{"position": "Senior Software Engineer","companyName": "Anthropic","startDate": {"year": 2023},"duration": "3 yrs","location": "San Francisco, CA"}],"education": [{"schoolName": "Stanford University","degreeName": "Master of Science","fieldOfStudy": "Computer Science"}],"skills": ["Python", "Machine Learning", "Distributed Systems"],"certifications": [],"languages": ["English"],"sourceCompany": "anthropic"}
Use cases
- Account-based sales: map decision-makers and functional teams at named accounts before outbound campaigns.
- Recruiting research: find engineers, designers, product managers, or executives at competitor companies.
- Competitive intelligence: monitor how public LinkedIn-visible teams are distributed by role and location.
- CRM enrichment: refresh account contacts with current public LinkedIn profile URLs, headlines, and locations.
- Market mapping: compare talent density across companies, regions, and job functions.
Pricing examples
Pricing is pay per result. The current Store pricing for this actor is designed around $3 per 1,000 results.
| Run size | Approximate result cost |
|---|---|
| 100 employees | $0.30 |
| 1,000 employees | $3.00 |
| 10,000 employees | $30.00 |
Apify platform usage and proxy costs, if applicable to your account, are handled by Apify separately from pay-per-result pricing.
Limitations
- Results come from public search visibility and should not be treated as an exhaustive company org chart.
- Very common company names can produce false positives. Use the LinkedIn company URL for higher precision.
- Title and location filters narrow public search results but are not guaranteed exact-match filters.
- Full mode is slower than Basic mode because it enriches profile pages one by one.
- Profiles with restricted visibility may return fewer fields.
FAQ
Do I need LinkedIn login credentials?
No. The actor works from public LinkedIn-visible data and does not require cookies, a LinkedIn account, or Sales Navigator.
Should I use company names or LinkedIn company URLs?
Use LinkedIn company URLs when possible. They are more precise than names such as Apple, Stripe, or Google, which can have multiple public interpretations.
Which mode should I start with?
Start with basic to validate that your query returns the right people. Use full when you need work history, education, skills, certifications, or languages.
Can I filter by both title and location?
Yes. For example, use jobTitle: "Data Scientist" and location: "New York" to narrow employee discovery before results are returned.
Can I schedule this actor?
Yes. Use Apify schedules to refresh target-company employee lists daily, weekly, or monthly.
Support and custom builds
Need a custom LinkedIn workflow, CRM export, enrichment chain, or private actor for a specific sales or recruiting process? Contact Thirdwatch through Apify or visit thirdwatch.dev for custom builds.
Pairs well with LinkedIn Profile Scraper for profile-level enrichment and LinkedIn Jobs Scraper for hiring-intent data.
Last verified: 2026-05