People Search Scraper for LinkedIn - By Job Title

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. Every person is looked up on their own public profile before you get them, and the location, employer and seniority filters run on that profile - not on the search text.

The two things that make this work

1. One role is written four different ways, so it searches all of them. Ask for "Head of Marketing" and it also looks for VP Marketing, Marketing Director and CMO. That is where the volume comes from: a single phrasing returns roughly 20 people, and eight variants returned 113 unique people in testing, with almost no overlap between them. Turn expandTitleVariants off if you want one exact wording.

2. 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 opens each profile and keeps only the people whose own profile says London. In testing, 4 of 9 profiles found with the location term really were in London, against 2 of 8 without it - so a filtered run wastes far fewer profile reads - and the profile check is what stops a "Mayor of London" or a company address from counting as a match.

How it finds people: free public web search (no per-request search fees), one paced request at a time, then the public LinkedIn profile of every candidate over residential proxies. A run where the search returns nothing costs nothing.

Input

Field	What it does
jobTitles	The roles you want. Common titles work best.
expandTitleVariants	Also search equivalent phrasings of the same role (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 profile
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 filter fields (default on)
includeUnverified	Also return people whose public profile is switched off
maxPerTitle / maxResults	Cap per title, and the total

Output

{
  "type": "person",
  "fullName": "Cristina Diezhandino",
  "firstName": "Cristina",
  "lastName": "Diezhandino",
  "jobTitle": "Chief Marketing Officer",
  "seniorityLevel": "Owner/C-Level",
  "department": "Executive",
  "currentCompany": "Diageo",
  "currentCompanyUrl": "https://uk.linkedin.com/company/diageo",
  "headline": "Global Business Leader with a demonstrated international trajectory in Consumer Packaged…",
  "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": 21413,
  "connectionCountText": "500+",
  "education": "Stanford University Graduate School of Business",
  "about": "Global Business Leader with a demonstrated international trajectory…",
  "searchedTitle": "Head of Marketing",
  "matchedVariant": "Chief Marketing Officer",
  "matchedQuery": "site:linkedin.com/in \"Chief Marketing Officer\"",
  "titleMatchesSearch": true,
  "publicProfileAvailable": true,
  "scrapedAt": "2026-09-24T17:32:03.780Z",
  "leadScore": 94,
  "schools": ["Stanford University Graduate School of Business"],
  "currentRoleLocation": "Greater London, England, United Kingdom"
}

Every field, and how often it is there

Measured on the actor's own verification runs. "Verified rows" are people whose public profile opened, which is every row unless you switch includeUnverified on.

Field	Populated	Where it comes from
fullName, firstName, lastName, profileUrl, publicId	all rows	search result + profile
headline, about, locationName, city, country, profilePhotoUrl, followerCount	all verified rows	the profile's own structured data
currentCompany	~95%	profile (worksFor), else the search result
currentCompanyUrl, connectionCountText	~90%	profile
jobTitle, seniorityLevel, department	~70-85%	the search engine's indexed copy of the profile. LinkedIn masks job titles on the logged-out page for most members, so the title comes from the result title/snippet; when neither carries a role, the field is an honest null rather than a guess
schools	~85%	profile (alumniOf)
education	~70%	profile meta description
currentRoleLocation	~80%	profile (worksFor[0].location)
languages, awards, organizations	~10-25%	member-filled profile sections - present only when the member filled them in
jobTitles, currentRoleStartYear, otherCurrentCompanies, pastCompanies	rare	LinkedIn masks past employers and role dates on the logged-out page for most members; populated only for the few profiles it leaves unmasked
searchedTitle, matchedVariant, matchedQuery, titleMatchesSearch, publicProfileAvailable, leadScore, scrapedAt	all rows	provenance and scoring

matchedVariant tells you which phrasing found the person and titleMatchesSearch says whether their real title actually matches what you asked for - so you can keep only the exact hits, or keep the wider net, without guessing. Empty arrays are omitted from a row rather than shipped as [].

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. Depth at source is limited: extra result pages return nothing new, which is why title variants rather than pagination supply 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.
• Some members switch their public profile off. Their profile answers 999 to every logged-out request, permanently - about half of the candidates a search surfaces, in testing. They are dropped by default, or returned with publicProfileAvailable: false and the search-indexed fields (name, title, company, headline, sometimes location) if you switch includeUnverified on.
• Job titles and past employers are masked on the public page. The title is recovered from the search engine's indexed copy; past employers and role dates usually cannot be, so those columns are populated 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. From 10 October 2026 a small run fee is added on top, charged 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. 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 — 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-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; from 10 October 2026 a small run fee is added on top. 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.