LinkedIn Profile Scraper

Build a clean file of LinkedIn people from profile URLs, public identifiers, or searches. Keep names, roles, employers, locations, audience size, experience, and education together for prospecting and company research.

The record

The dataset schema names every field before the run. The first working set is username, fullName, firstName, lastName, headline, currentTitle, currentCompany, companyWebsite, companyHeadcount, companyIndustry, location, and country. Dataset views keep related fields together without changing the underlying row.

Captured row

{
  "companyHeadcount": 232991,
  "connectionsCount": 500,
  "country": "US"
}

Input

LinkedIn Profile Scraper accepts source URLs, public identifiers, and searches. Run controls stay in the same form.

Field	What it controls	Starting value
startUrls	Paste exact LinkedIn URLs, one per line.	["https://www.linkedin.com/in/satyanadella"]
urls	Paste the LinkedIn URLs to process, one per line.	["https://www.linkedin.com/in/satyanadella","https://www.linkedin.com/in/williamhgates"]
publicIdentifiers	Enter the public identifiers to resolve, one per line.	["williamhgates","satyanadella","jeffweiner08"]
queries	Enter the search phrases to run, one per line.	["Satya Nadella"]
enrich	Choose the enrichment mode applied to returned records.	"off"
maxItems	Stop after this many dataset rows.	10
includeHistory	Keep history in the returned record.	true
maxConcurrency	Set the number of source requests that may run in parallel.	5
findWorkEmail	Add the work-email lookup step to this run.	false
maxSeconds	Stop after this many seconds and keep completed rows.	180

Example input

{
  "startUrls": [
    "https://www.linkedin.com/in/satyanadella"
  ],
  "urls": [
    "https://www.linkedin.com/in/satyanadella",
    "https://www.linkedin.com/in/williamhgates"
  ],
  "publicIdentifiers": [],
  "queries": [],
  "enrich": "off",
  "maxItems": 1,
  "includeHistory": true
}

Price

$0.00001 per dataset item. Other Apify plans use the rates shown in the Pricing tab.

Console, API, schedules, and exports

Runs can begin in Apify Console, from a saved task, or through the Actor API. A schedule can reuse the same input. Completed rows remain in the run dataset for API retrieval and Apify dataset exports.

POST https://api.apify.com/v2/acts/JhXpCI1Re4ltZYSZd/runs
GET  https://api.apify.com/v2/datasets/{datasetId}/items

Saved tasks

Twenty task pages cover distinct research, comparison, operations, automation, and export jobs. The opening set is:

• LinkedIn profile exact lookup: Review one LinkedIn record around username, fullName, headline, and headlineSource. The saved task uses startUrls, urls, and publicIdentifiers and opens the overview view. Configured in LinkedIn Profile Scraper.
• LinkedIn profile account comparison: Compare LinkedIn profiles using companyHeadcount, country, followersCount, and connectionsCount. The stats view keeps the differences close together. Configured in LinkedIn Profile Scraper.
• LinkedIn profile source list: Process a saved LinkedIn input queue with startUrls, urls, and publicIdentifiers. Source and identifier fields remain visible in the identity view. Configured in LinkedIn Profile Scraper.
• LinkedIn profile identity index: Index LinkedIn profiles by username, headlineSource, currentTitleSource, and companyWebsiteSource. The saved input keeps the same matching keys from run to run. Configured in LinkedIn Profile Scraper.
• LinkedIn profile contact coverage: Assemble a LinkedIn register centered on companyWebsite, workEmail, phone, and emailConfidence. The task keeps startUrls, urls, and publicIdentifiers visible for later review. Configured in LinkedIn Profile Scraper.
• LinkedIn profile audience benchmark: Compare numeric and status fields across LinkedIn profiles, led by companyHeadcount, country, followersCount, and connectionsCount. Results open as the contact table. Configured in LinkedIn Profile Scraper.

Related products

• LinkedIn Email Scraper
• LinkedIn Post Scraper
• LinkedIn Search Scraper
• LinkedIn Lead Scraper
• LinkedIn Account Scraper

Support

Include the Actor ID, run ID, saved task name, and affected input when reporting an issue. That is enough to locate the run and its dataset.