People Search Scraper for LinkedIn - By Job Title
Pricing
from $7.00 / 1,000 people
People Search Scraper for LinkedIn - By Job Title
Find people on LinkedIn by job title without a company list and without a login. Searches every way a role is written, opens each profile to confirm who they are, then filters by real location, employer and seniority. Independent tool, not affiliated with LinkedIn.
Pricing
from $7.00 / 1,000 people
Rating
0.0
(0)
Developer
Scrape Sage
Maintained by CommunityActor stats
0
Bookmarked
59
Total users
5
Monthly active users
13 days ago
Last modified
Categories
Features
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.
Tell it a job title, get the people who hold it. No company list, no login, no cookies. By default each person is checked on their own public LinkedIn profile before you get them, and the location, employer and seniority filters run on that profile, not on the search text.
How it works
1. One role is written several ways, so it searches all of them. Ask for "Head of Marketing" and it also looks for VP Marketing, Marketing Director and CMO; ask for "CFO" and it also looks for Chief Financial Officer. That is where the volume comes from: one phrasing reaches only the people the search engines list for that exact wording, and the variants overlap very little. Turn expandTitleVariants off if you want one exact wording.
2. Every person is checked on their public profile. Candidates come from free public web search (no per-request search fees). Each candidate's LinkedIn profile is then read on Apify's datacenter proxy, and on residential once if datacenter is refused. Many members hide their profile from logged-out visitors: on 5 November 2026 about 1 candidate in 3 opened (192 of 528 profile reads), so the run gathers several candidates for every person it returns. Hidden members are left out by default; switch includeUnverified on to get them as well, with the fields their search listing shows.
3. Location is checked on the person, not on the page. Give it "London" and it adds London to the web search to find more candidates there, then keeps only the people whose own profile says London. That check is what stops a "Mayor of London" or a company address from counting as a match.
When LinkedIn opens no profile at all. If none of the first 8 profiles a run reads will open and a well-known public profile will not open either, LinkedIn is keeping profiles closed to logged-out visitors for that run (this actor's residential reads met that from about 1 November 2026). When only the people found hide their profiles, checks stay on and the status message says so. The run then builds every person from the search engines' listing of their profile instead, leaves publicProfileAvailable empty, and says so in its status message. Those rows carry the name, profile link and job title, the company for about 6 people in 10 and a location for about 1 in 5, so a location filter returns few people in such a run.
Input
| Field | What it does |
|---|---|
jobTitles | The roles you want. Common titles work best. |
expandTitleVariants | Also search equivalent phrasings of the same role, including the full form of a C-level acronym (default on) |
extraKeywords | Optional context words like "SaaS" or "fintech": more reach, less precision |
locations | Added to the search, then checked on each person's own location |
companies | Keep only people at these employers |
seniorityLevels | Owner/C-Level, VP/Director, Manager, Senior, Individual Contributor, Entry |
verifyProfiles | Open each profile to confirm identity and collect the profile fields (default on) |
includeUnverified | Also return people whose own profile is hidden, with their search-listing fields |
maxPerTitle / maxResults | Cap per title, and the total, shared out between the titles |
Output
A person checked on their profile (5 November 2026):
{"type": "person","fullName": "Cristina Diezhandino","firstName": "Cristina","lastName": "Diezhandino","jobTitle": "Chief Marketing Officer","seniorityLevel": "Owner/C-Level","department": "Executive","currentCompany": "Diageo","currentCompanyUrl": "https://www.linkedin.com/company/diageo","headline": "Chief Marketing Officer at Diageo","profileUrl": "https://www.linkedin.com/in/cristina-diezhandino-87655321","publicId": "cristina-diezhandino-87655321","locationName": "London, England, United Kingdom","city": "London","country": "United Kingdom","profilePhotoUrl": "https://media.licdn.com/dms/image/…","followerCount": 21520,"connectionCountText": "500+","education": "Stanford University Graduate School of Business","about": "Global Business Leader with a demonstrated international trajectory in Consumer Packaged…","searchedTitle": "Head of Marketing","matchedVariant": "Chief Marketing Officer","matchedQuery": "site:linkedin.com/in \"Chief Marketing Officer\"","titleMatchesSearch": true,"publicProfileAvailable": true,"scrapedAt": "2026-11-05T04:24:02.850Z","leadScore": 94,"schools": ["Stanford University Graduate School of Business"],"currentRoleLocation": "Greater London, England, United Kingdom","aboutSnippet": "Global Business Leader with a demonstrated international trajectory in Consumer Packaged and Luxury Goods. Has worked in North America, Africa, Latin America and Europe…","schoolsText": "Stanford University Graduate School of Business"}
Every field, and how often it is there
"Checked on the profile" is 35 people returned by 5 test runs on 5 November 2026. "Search listing only" is 136 listings read on the same day: people whose own profile is hidden (with includeUnverified on), or every person in a run where LinkedIn opened no profile or verifyProfiles is off.
| Field | Checked on the profile | Search listing only | Where it comes from |
|---|---|---|---|
fullName, firstName, lastName, profileUrl, publicId | all | all | search result and profile |
jobTitle, seniorityLevel, department | all | about 90% | the search engine's copy of the profile. LinkedIn masks job titles on the logged-out page for most members, so the title comes from the result title or listing; when neither carries a role the field is an honest null, not a guess |
currentCompany | about 95% | about 55% | the profile (worksFor), else the listing |
currentCompanyUrl | about 95% | none | the profile |
locationName, country | all | about 20% (country about 5%) | the profile, else the listing |
city | about 75% | about 15% | the first part of the location (empty when the location is a country) |
followerCount | all | none | the profile |
connectionCountText | about 95% | about 20% | the profile, else the listing |
headline | about 85% | about 95% | the member's own headline: the profile, else the listing's first line |
about | about 95% | none | the profile's About section |
aboutSnippet | about 90% | about 85% | the search listing's copy of the About section, cut short by the engine |
schools, schoolsText | about 75% | none | the profile (schoolsText is the same list as one line) |
education | about 60% | about 15% | the profile summary, else the listing |
profilePhotoUrl | about 60% | none | the profile (LinkedIn's default avatar is left out) |
currentRoleLocation | about 70% | none | the profile (worksFor[0].location) |
languages, awards, organizations | about 15% to 30% | none | member-filled profile sections, present only when the member filled them in |
jobTitles, currentRoleStartYear, otherCurrentCompanies, pastCompanies | rare (none of the 35) | none | LinkedIn masks past employers and role dates on the logged-out page for most members |
searchedTitle, matchedVariant, matchedQuery, titleMatchesSearch, leadScore, scrapedAt | all | all | provenance and scoring |
publicProfileAvailable | true | false for a hidden profile; empty when LinkedIn opened no profile in the run | the profile check |
matchedVariant tells you which phrasing found the person and titleMatchesSearch says whether their title actually matches what you asked for (the employer's name never counts), so you can keep only the exact hits, or keep the wider net, without guessing. Each person is saved once per run, even when two of your titles find them, and the titles share maxResults so every title gets its part. Empty lists are left out of a row rather than shipped as []; the columns the two table views show are always there, empty when there is no value.
What this actor is NOT
Honesty about depth, because it decides whether this is the right tool:
- It is a targeted search, not a database dump. Expect tens of people per title, not thousands. Each query is read up to 4 result pages deep while a title still needs people, and the title variants supply the rest of the volume.
- If you already know the companies, use the other one. Company Employees Scraper for LinkedIn is the better tool when you have an account list and want everyone inside those companies: it anchors on the company and goes far deeper per company than a title search can.
- Many members hide their public profile. Their profile answers every logged-out request with a refusal, permanently: about 2 candidates in 3 on 5 November 2026. They are left out by default, or returned with
publicProfileAvailable: falseand their search-listing fields if you switchincludeUnverifiedon. - Short titles and narrow filters return fewer people. An acronym such as "CFO" or "CHRO" and a single city in
locationsnarrow the search a lot; a run in which LinkedIn opens no profile can only check a city on the listing, which shows one for about 1 person in 5. - Job titles and past employers are masked on the public page. The title is recovered from the search engine's copy; past employers and role dates usually cannot be, so those columns are filled only for the few profiles LinkedIn leaves unmasked.
- Never returned: private profiles, connection graphs, email addresses or phone numbers.
Pricing
Pay-per-event: $0.007 per person found, no monthly rental. A small run fee is added once per run, and only once the web search has returned candidates to check: a run where the search returns nothing, or refuses to answer, stays free. A run whose candidates are all removed by your filters or by the profile check still pays that run fee, and its status message says so. Every finished run tells you what to change, and the Pricing tab always shows the live figures.
Use with AI assistants (MCP)
Works as a tool in any MCP-compatible assistant through the Apify MCP server: ask your agent to "find heads of marketing in the UK" 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-people-search-scraper').call({"jobTitles": ["Head of Marketing"],"expandTitleVariants": true,"locations": [],"maxPerTitle": 50,"maxResults": 100,"verifyProfiles": 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: a price per person found, with no monthly rental, plus a small run fee once the web search has returned candidates. The exact figures 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 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 reads only what LinkedIn publishes to logged-out visitors. It does not log in, use cookies or session tokens, or reach private profiles. Names, roles and employers are business contact information, but they 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 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.