LinkedIn Profile API | Scrape Public Profile Data avatar

LinkedIn Profile API | Scrape Public Profile Data

Pricing

from $0.01 / 1,000 profile scrapeds

Go to Apify Store
LinkedIn Profile API | Scrape Public Profile Data

LinkedIn Profile API | Scrape Public Profile Data

Collect public LinkedIn person profiles as clean, structured JSON. Send one or many profile URLs and get name, headline, location, current company, experience, education, and follower counts. Reliable, pay per profile, MCP-ready for Claude and AI agents.

Pricing

from $0.01 / 1,000 profile scrapeds

Rating

5.0

(7)

Developer

John

John

Maintained by Community

Actor stats

3

Bookmarked

121

Total users

87

Monthly active users

14 hours

Issues response

2 days ago

Last modified

Share

👤 LinkedIn Profile API | Scrape LinkedIn Profiles to JSON

The LinkedIn Profile API is a reliable LinkedIn profile scraper that turns any public LinkedIn person profile into clean, structured JSON. Use this actor with Claude, Cursor, or any MCP-compatible AI agent to scrape name, headline, location, current company, experience, education, and follower counts, on reliable infrastructure and billed per profile.

Send one or many profile URLs and get one row per profile, collected in parallel. It works as a straightforward LinkedIn data scraper for lead enrichment, people research, and recruiting, and it is built API-first and MCP-ready so AI agents can call it as a tool.


🧩 Part of the Alpha OSINT LinkedIn suite: no login, no cookies

Eight Actors that read only what LinkedIn shows to a signed-out visitor. None of them asks for your account, your password or an li_at session cookie, so none of them can get your LinkedIn account restricted. Each one takes what the previous one returns, so you can chain them into a full people-and-company workflow:

StepYou want toUse
1Find people by name, job title, company, school or location, no profile URL neededLinkedIn People Search API
2Turn profile URLs into full structured profiles: experience, education, followersLinkedIn Profile API (this Actor)
3Enrich the employer: industry, size, headquarters, specialties, follower countLinkedIn Company API
4List the people who work at a company, each checked against their public profileLinkedIn Company Employees API
5See what a company is hiring for, with salary data where LinkedIn publishes itLinkedIn Jobs API
6Search jobs as a guest with filters, total result counts and autocomplete idsLinkedIn Job Scraper
7Read what a person or company posts, with reactions, comments and sharesLinkedIn Posts API
8Map the skills people list to courses, learner reviews and full syllabiLinkedIn Learning API

A worked map of these chains, with live adoption and success-rate stats for every Actor, is at alphaosint.com/linkedin.

📋 What this API returns

FieldDescription
name, firstName, lastNameThe person's name.
headlineThe profile headline, when LinkedIn shows it to signed-out visitors (absent otherwise).
aboutThe About / summary section.
location, countryCodeWhere the person is based.
currentCompany, currentTitleCurrent company, and the job title when LinkedIn shows it publicly.
experienceCurrent employers (company, link, location). Titles and dates are included when LinkedIn shows them publicly; for most members it hides them from signed-out visitors.
pastCompaniesDistinct company names from the experience history.
educationEducation entries (school, degree, field, dates).
honorsAndAwardsHonors and awards listed on the profile.
followers, connectionsAudience size.
avatarProfile photo URL.
publicUrl, linkedinIdThe public profile URL and handle.
emailAlways null (email is not available from this source).
summaryA plain-language one-line interpretation of the profile.
memberIdLinkedIn's numeric member id.
connectionsTextThe connection count as LinkedIn shows it, e.g. 500+.
languagesLanguages listed on the profile.
positionsEvery position in the experience section, with dates and an isCurrent flag. Present only on profiles whose experience section is public.
fromCache, viaUnblockerWhether the row came from the shared cache, and whether LinkedIn's standard route was blocked so the slower route was used.

Where the data comes from

Every profile is read from LinkedIn's public pages: the profile page a signed-out visitor sees. No login and no cookies. About 1 in 4 profiles is blocked on the standard route and is fetched through a slower fallback route, so those rows can take a minute or more; the price is the same.

Not available: email (the email field is always null), and private profiles. When LinkedIn does not serve a profile's public page you get a free error row for that URL, not a charge. Text LinkedIn hides from signed-out visitors (shown as asterisks) is left out.


🎯 Use cases

  • Sales prospecting. Enrich a list of prospect profile URLs with role, company, and seniority.
  • Recruiting. Pull candidate headlines, experience, and education for sourcing and screening.
  • Lead enrichment. Append firmographic and role data to CRM records from a profile URL.
  • Account-based marketing. Map decision-makers at target accounts by title and tenure.
  • People search and list building. Turn a set of profile URLs into a structured people dataset.
  • Talent-market research. Analyze roles, career moves, and education across a cohort of profiles.
  • AI agent workflows. Drive this API over MCP from Claude to look up and summarize profiles in-conversation.

🔁 Use it as a LinkedIn profile scraper at scale

Paste a batch of URLs and this LinkedIn data scraper collects them in budget-capped chunks, one row per profile, so a large run never overshoots what you set. Every profile comes back with the same flat, predictable fields, which is what makes it easy to load into a sheet, a database, or a CRM. If a URL cannot be collected, you get a clear error row for that URL instead of a failed run, so one bad link never sinks the batch. To scrape a LinkedIn profile once or ten thousand times, the shape of the output stays the same.


⚙️ Input examples

One profile

{
"profileUrls": ["https://www.linkedin.com/in/satyanadella"]
}

Several profiles at once (collected in parallel)

{
"profileUrls": [
"https://www.linkedin.com/in/satyanadella",
"https://www.linkedin.com/in/williamhgates"
]
}

Always fetch fresh (skip the cache)

{
"profileUrls": ["https://www.linkedin.com/in/satyanadella"],
"maxAgeDays": 0
}

URLs that are not LinkedIn /in/ profile URLs are skipped with a warning. The API returns one row per profile. You can pass up to 1000 URLs per run; contact us to raise the limit for your account.

maxAgeDays (optional): serve results fetched within this many days from the shared cache. 0 = always fetch fresh. Empty = the default for each record type (7 days for profiles). A cached row has fromCache: true, and its fetched_at is the original fetch time. To ask for a cached copy of your public profile to be removed, contact us via alphaosint.com.


📤 Example output

Each profile is returned as one JSON row:

{
"result_type": "profile",
"name": "Satya Nadella",
"firstName": "Satya",
"lastName": "Nadella",
"headline": "Chairman and CEO at Microsoft",
"currentCompany": "Microsoft",
"currentTitle": "Chairman and CEO",
"location": "Redmond, Washington, United States",
"countryCode": "US",
"experience": [
{
"title": "Chairman and CEO",
"company": "Microsoft",
"company_id": "microsoft",
"url": "https://www.linkedin.com/company/microsoft",
"location": "Greater Seattle Area",
"start_date": "Feb 2014",
"end_date": "Present"
}
],
"pastCompanies": ["Microsoft", "University of Chicago", "Starbucks", "The Business Council U.S.", "Fred Hutch"],
"education": [
{
"title": "The University of Chicago Booth School of Business",
"url": "https://www.linkedin.com/school/universityofchicagoboothschoolofbusiness/",
"start_year": "1994",
"end_year": "1996"
}
],
"followers": 12196634,
"connections": 500,
"connectionsText": "500+",
"linkedinId": "satyanadella",
"memberId": "19186432",
"email": null,
"publicUrl": "https://www.linkedin.com/in/satyanadella",
"summary": "Chairman and CEO at Microsoft, based in Redmond, Washington, United States, 12,196,634 followers",
"fetched_at": "2026-10-01T18:11:04.512000+00:00",
"fromCache": false,
"viaUnblocker": false
}

(experience and positions are shortened here; a real row lists every role.)

The email field is always null; email is not available from this source.


💰 Pricing (pay-per-event)

You pay per profile returned. There is no per-run setup fee. The current per-event price is shown on the Store card and in the Actor's Monetization details. Because billing is per profile, you only pay for the profiles actually delivered. A profile served from the cache is billed the same as a freshly fetched one; error rows are free.


🔌 Use this API from Claude (MCP)

This Actor is MCP-server-compatible, so Claude Code (free trial), Claude (desktop and web), Cursor, and other MCP clients can call it as a tool through Apify's hosted MCP server.

Add it with this Actor-specific URL:

https://mcp.apify.com/?tools=actors,docs,johnvc/linkedin-profile-api

Apify MCP integration docs: https://docs.apify.com/platform/integrations/mcp

Setup walkthrough:

New to Claude Code or Claude Cowork? Start a free trial.

Then ask Claude:

"Use the LinkedIn Profile API to look up the CEO of Microsoft and summarize their background."


💸 Pay per run with crypto (x402)

The LinkedIn Profile API supports agentic payments via the x402 protocol. AI agents and MCP clients can pay for runs in USDC (on Base) with no Apify account or API token needed: point your agent at the Apify MCP server and it can discover, pay for, and run this Actor autonomously. Read the Apify x402 announcement for details.

🔌 Integrations: run profile enrichment on a schedule

This API is most useful as a recurring step in a pipeline, not a one-off run:

  • Tasks and Schedules. Save a set of profile URLs as a Task, then attach a Schedule to refresh that people dataset daily, weekly, or monthly with no code.
  • n8n, Make, and Zapier. Trigger a run when a new lead lands in your CRM, then push the enriched profile back. Apify has native connectors for each.
  • Supabase, Google Sheets, and databases. Send the dataset straight to storage with a webhook or the Apify API so the rows land where your team already works.
  • MCP. Call the API as a tool from Claude and other AI agents (see the section above) to enrich profiles inside an agent workflow.
  • Webhooks. Fire a webhook on run completion to kick off the next step in your own system.

Build a full picture of a person, their company, and their activity by pairing this with the rest of the LinkedIn suite:

Comparison point: some LinkedIn profile scrapers on the Store are unmaintained and low-rated (for example bestscrapers/fresh-linkedin-profile-data, rated under 2 stars). This API is built for reliability, pay-per-profile billing, and MCP access from AI agents.


📎 Applications

Ready-made task pages for common jobs. Open one, run it, or duplicate it as a starting point:

Scrape LinkedIn Profiles to Structured JSON

Turn public profile URLs into clean JSON with name, role, company, experience, and education.

Bulk-Scrape LinkedIn Profiles from a URL List

Paste up to 1000 profile URLs and get one clean row each, collected in batches.

Extract LinkedIn Profile Data to JSON

Extract role, company, experience, education, location, and followers from a profile.

LinkedIn Profile Data API for Python

Call the API from Python: a profile URL in, structured JSON out.

LinkedIn Profile Enrichment API

Enrich a profile URL into structured fields for CRM and lead records.

Scrape LinkedIn Profiles in an n8n Workflow

Add profile data to an n8n workflow: pass URLs, get structured JSON back.

Get LinkedIn Profile Data in Claude via MCP

Use profiles as a tool in Claude and other AI agents over MCP.

Monitor Employee LinkedIn Profiles for Flight Risk

Check your team's public profiles on a schedule and watch headline, role, and activity for signs someone may be leaving.


🚀 How to get started

  1. Open the Actor and paste one or more LinkedIn profile URLs into profileUrls.
  2. Run it and read the results from the dataset (JSON, CSV, Excel, or API).

View on Apify Store

Example code: Python quick-start + MCP setup on GitHub - call the API from Python, or install it as a tool in Claude, Cursor, and ChatGPT.


🤖 Ask an AI assistant about this API

Open a ready-to-send prompt about the LinkedIn Profile API in the AI of your choice:

❓ FAQ

Do I need to give you my LinkedIn cookies or login?

No, never. This Actor does not ask for, accept or store your LinkedIn cookies, your session cookie (li_at), your password or your account. There is no input field for any of them. It reads LinkedIn's public pages the way a signed-out visitor sees them. Any cookie involved is one LinkedIn's site hands to that anonymous visit, and it is used only inside that single run.

Is this a LinkedIn API or a LinkedIn profile scraper?

Both descriptions fit. You call it like an API (a profile URL in, structured JSON out), and under the hood it is a LinkedIn profile scraper that reads public profile pages. You never touch scraping infrastructure; you get clean fields back.

How do I scrape LinkedIn profiles with this actor?

Paste public LinkedIn /in/ URLs into profileUrls and run it. Each URL returns one row of structured data. This works whether you want to scrape a LinkedIn profile once or run a large batch.

This actor collects only public profile data. Public-data scraping has been addressed in court cases such as hiQ Labs v. LinkedIn, but you are responsible for your own use, including GDPR and platform terms. Consult your own counsel for your use case.

Can I run it from Claude or another AI agent over MCP?

Yes. The Actor is MCP-server-compatible, so Claude Code (free trial) and other MCP clients call it as a tool. See the MCP section above for the setup URL.

Can I schedule it or connect it to my other apps?

Yes. Save your inputs as a Task and attach a Schedule for recurring runs, and connect the output to n8n, Make, Zapier, Supabase, or your own system by webhook. See the Integrations section above.

How do I find a LinkedIn profile URL by name and company?

This actor takes a profile URL as input, so you supply the URL. Once you have it, the API returns the person's role, company, experience, and education as structured data.

Do you return email addresses?

No. The email field is always null; email is not available from this data source.

Can I collect many profiles at once?

Yes. Provide a list in profileUrls; they are collected in parallel and returned one row per profile, up to 1000 per run.

What if a profile cannot be collected?

The API returns a clear error row for that URL explaining why, so a single bad URL does not fail the whole run. Error rows are not charged. A private profile, or one LinkedIn will not show to signed-out visitors, comes back as an error row saying LinkedIn did not serve its public page.


🌐 About Alpha OSINT

This Actor is part of Alpha OSINT, toolset of financial and operations data sources and APIs. See the LinkedIn Profile API source page for related tools and use cases. For support or requests for this actor, please start a ticket directly on our support page.

Last Updated: 2026.10.04