# LinkedIn Profile API | Scrape Public Profile Data (`johnvc/linkedin-profile-api`) Actor

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.

- **URL**: https://apify.com/johnvc/linkedin-profile-api.md
- **Developed by:** [John](https://apify.com/johnvc) (community)
- **Categories:** Lead generation, Developer tools, AI
- **Features:** Limited permissions
- **Stats:** 201 total users, 111 monthly users, 100.0% runs succeeded, 3 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $0.01 / 1,000 profile scrapeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 👤 LinkedIn Profile API | Scrape LinkedIn Profiles to JSON

The **LinkedIn Profile API** is a reliable **LinkedIn profile scraper** that turns any public [LinkedIn](https://www.linkedin.com) 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:

| Step | You want to | Use |
|---|---|---|
| 1 | Find people by name, job title, company, school or location, no profile URL needed | [LinkedIn People Search API](https://apify.com/johnvc/linkedin-people-search-api?fpr=9n7kx3) |
| 2 | Turn profile URLs into full structured profiles: experience, education, followers | **LinkedIn Profile API** (this Actor) |
| 3 | Enrich the employer: industry, size, headquarters, specialties, follower count | [LinkedIn Company API](https://apify.com/johnvc/linkedin-company-api?fpr=9n7kx3) |
| 4 | List the people who work at a company, each checked against their public profile | [LinkedIn Company Employees API](https://apify.com/johnvc/linkedin-company-employees-api?fpr=9n7kx3) |
| 5 | See what a company is hiring for, with salary data where LinkedIn publishes it | [LinkedIn Jobs API](https://apify.com/johnvc/linkedin-jobs-api?fpr=9n7kx3) |
| 6 | Search jobs as a guest with filters, total result counts and autocomplete ids | [LinkedIn Job Scraper](https://apify.com/johnvc/linkedin-job-search-scraper?fpr=9n7kx3) |
| 7 | Read what a person or company posts, with reactions, comments and shares | [LinkedIn Posts API](https://apify.com/johnvc/linkedin-posts-api?fpr=9n7kx3) |
| 8 | Map the skills people list to courses, learner reviews and full syllabi | [LinkedIn Learning API](https://apify.com/johnvc/linkedin-learning-api?fpr=9n7kx3) |

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

### 📋 What this API returns

| Field | Description |
|---|---|
| `name`, `firstName`, `lastName` | The person's name. |
| `headline` | The profile headline, when LinkedIn shows it to signed-out visitors (absent otherwise). |
| `about` | The About / summary section. |
| `location`, `countryCode` | Where the person is based. |
| `currentCompany`, `currentTitle` | Current company, and the job title when LinkedIn shows it publicly. |
| `experience` | Current employers (company, link, location). Titles and dates are included when LinkedIn shows them publicly; for most members it hides them from signed-out visitors. |
| `pastCompanies` | Distinct company names from the experience history. |
| `education` | Education entries (school, degree, field, dates). |
| `honorsAndAwards` | Honors and awards listed on the profile. |
| `followers`, `connections` | Audience size. |
| `avatar` | Profile photo URL. |
| `publicUrl`, `linkedinId` | The public profile URL and handle. |
| `email` | Always null (email is not available from this source). |
| `summary` | A plain-language one-line interpretation of the profile. |
| `memberId` | LinkedIn's numeric member id. |
| `connectionsText` | The connection count as LinkedIn shows it, e.g. `500+`. |
| `languages` | Languages listed on the profile. |
| `positions` | Every position in the experience section, with dates and an `isCurrent` flag. Present only on profiles whose experience section is public. |
| `fromCache`, `viaUnblocker` | Whether 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

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

#### Several profiles at once (collected in parallel)

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

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.

A profile fetched in the last 7 days is served from a shared cache and billed like a fresh profile. A cached row has `fromCache: true`, and its `fetched_at` is the original fetch time. Older profiles are fetched fresh.
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:

```json
{
  "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](https://claude.ai/referral/uIlpa7nPLg) (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:

https://www.youtube.com/watch?v=jREWahDGhJM

**New to Claude Code or Claude Cowork?** Start a [free trial](https://claude.ai/referral/uIlpa7nPLg).

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](https://docs.apify.com/platform/integrations/x402).
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](https://mcp.apify.com/?tools=actors,docs,johnvc/linkedin-profile-api) and it can
discover, pay for, and run this Actor autonomously. Read the
[Apify x402 announcement](https://apify.com/change-log/pay-for-apify-actors-with-x402?fpr=9n7kx3) 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.
- **Ready-made n8n template.** [Enrich and score LinkedIn inbound leads](https://n8n.io/workflows/22040-enrich-and-score-linkedin-inbound-leads-with-openai-slack-and-gmail/) is a free template that finds a form lead on LinkedIn, uses this API to confirm where they work now, then has an AI model score fit and send hot leads to Slack and warm leads to a Gmail draft.
- **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.

***

### 🔗 Related Tools

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

- [LinkedIn Company API](https://apify.com/johnvc/linkedin-company-api?fpr=9n7kx3) - firmographics and sales intelligence for the companies your prospects work at.
- [LinkedIn Company Employees API](https://apify.com/johnvc/linkedin-company-employees-api?fpr=9n7kx3) - the other people at a prospect's company, each checked against their public profile.
- [LinkedIn Posts API](https://apify.com/johnvc/linkedin-posts-api?fpr=9n7kx3) - a person's public posts and engagement, for social selling and research.
- [LinkedIn Jobs API](https://apify.com/johnvc/linkedin-jobs-api?fpr=9n7kx3) - open roles by keyword, company, and location.
- [LinkedIn Learning API](https://apify.com/johnvc/linkedin-learning-api?fpr=9n7kx3) - public course, ratings and syllabus data for the skills a person lists.

Comparison point: some LinkedIn profile scrapers on the Store are unmaintained and low-rated (for example [bestscrapers/fresh-linkedin-profile-data](https://apify.com/bestscrapers/fresh-linkedin-profile-data?fpr=9n7kx3), 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](https://apify.com/johnvc/linkedin-profile-api/examples/scrape-linkedin-profiles-to-structured-json?fpr=9n7kx3)

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

#### [Bulk-Scrape LinkedIn Profiles from a URL List](https://apify.com/johnvc/linkedin-profile-api/examples/bulk-scrape-linkedin-profiles-from-a-url-list?fpr=9n7kx3)

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

#### [Extract LinkedIn Profile Data to JSON](https://apify.com/johnvc/linkedin-profile-api/examples/extract-linkedin-profile-data-to-json?fpr=9n7kx3)

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

#### [LinkedIn Profile Data API for Python](https://apify.com/johnvc/linkedin-profile-api/examples/linkedin-profile-data-api-for-python?fpr=9n7kx3)

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

#### [LinkedIn Profile Enrichment API](https://apify.com/johnvc/linkedin-profile-api/examples/linkedin-profile-enrichment-api?fpr=9n7kx3)

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

#### [Scrape LinkedIn Profiles in an n8n Workflow](https://apify.com/johnvc/linkedin-profile-api/examples/scrape-linkedin-profiles-in-an-n8n-workflow?fpr=9n7kx3)

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

#### [Get LinkedIn Profile Data in Claude via MCP](https://apify.com/johnvc/linkedin-profile-api/examples/get-linkedin-profile-data-in-claude-via-mcp?fpr=9n7kx3)

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

#### [Monitor Employee LinkedIn Profiles for Flight Risk](https://apify.com/johnvc/linkedin-profile-api/examples/monitor-employee-linkedin-profiles-for-flight-risk?fpr=9n7kx3)

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](https://apify.com/johnvc/linkedin-profile-api?fpr=9n7kx3)

**Example code:** [Python quick-start + MCP setup on GitHub](https://github.com/johnisanerd/Apify-LinkedIn-Profile-API) - call the API from Python, or install it as a tool in Claude, Cursor, and ChatGPT.

***

### 🧭 Use it for B2B prospecting in Claude

[Alpha OSINT Prospector](https://github.com/johnisanerd/alphaosint-prospector) is a free, open-source Claude Code plugin that pairs with this API: it finds the decision-makers, and this API reads their full profiles. Describe your ideal customer once and it returns a ranked leads file: companies hiring for the roles you sell into, enriched with Indeed, LinkedIn and Crunchbase data, scored 0-100 with a reason for every point, plus decision-makers and email verification. Spend caps are enforced in code, and it sends nothing.

```
/plugin marketplace add johnisanerd/alphaosint-prospector
```

New to Claude Code? [Try it with this referral link](https://claude.ai/referral/uIlpa7nPLg).

### 🤖 Ask an AI assistant about this API

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

- 💬 [ChatGPT](https://chatgpt.com/?q=Using%20the%20LinkedIn%20Profile%20API%20on%20Apify%20%28https://apify.com/johnvc/linkedin-profile-api?fpr=9n7kx3%29%2C%20walk%20me%20through%20this%20use%20case:%20%22Scrape%20LinkedIn%20Profiles%20to%20Structured%20JSON%22.%20Show%20me%20the%20input%20JSON%2C%20the%20output%20fields%2C%20and%20how%20to%20automate%20it%20with%20the%20API%20or%20MCP.)
- 🧠 [Claude](https://claude.ai/new?q=Using%20the%20LinkedIn%20Profile%20API%20on%20Apify%20%28https://apify.com/johnvc/linkedin-profile-api?fpr=9n7kx3%29%2C%20walk%20me%20through%20this%20use%20case:%20%22Scrape%20LinkedIn%20Profiles%20to%20Structured%20JSON%22.%20Show%20me%20the%20input%20JSON%2C%20the%20output%20fields%2C%20and%20how%20to%20automate%20it%20with%20the%20API%20or%20MCP.)
- 🔍 [Perplexity](https://www.perplexity.ai/search?q=Using%20the%20LinkedIn%20Profile%20API%20on%20Apify%20%28https://apify.com/johnvc/linkedin-profile-api?fpr=9n7kx3%29%2C%20walk%20me%20through%20this%20use%20case:%20%22Scrape%20LinkedIn%20Profiles%20to%20Structured%20JSON%22.%20Show%20me%20the%20input%20JSON%2C%20the%20output%20fields%2C%20and%20how%20to%20automate%20it%20with%20the%20API%20or%20MCP.)
- 🅒 [Copilot](https://copilot.microsoft.com/?q=Using%20the%20LinkedIn%20Profile%20API%20on%20Apify%20%28https://apify.com/johnvc/linkedin-profile-api?fpr=9n7kx3%29%2C%20walk%20me%20through%20this%20use%20case:%20%22Scrape%20LinkedIn%20Profiles%20to%20Structured%20JSON%22.%20Show%20me%20the%20input%20JSON%2C%20the%20output%20fields%2C%20and%20how%20to%20automate%20it%20with%20the%20API%20or%20MCP.)

### ❓ FAQ

#### Will this put my LinkedIn or LinkedIn Recruiter account at risk?

No. It reads public LinkedIn pages only, the ones anyone can open while signed out. It never logs in and never asks for your cookies: there is no input for an account, a password or an `li_at` session cookie. Nothing it does is tied to your LinkedIn account, your LinkedIn Recruiter seat or your Sales Navigator license. The requests run on Apify's servers, not in your browser, so nothing connects them to you, and you can keep working in Recruiter while a run is going.

#### 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.

#### Is it legal to scrape public LinkedIn profiles?

This actor collects only public profile data. Public-data scraping has been addressed in court cases such as [hiQ Labs v. LinkedIn](https://en.wikipedia.org/wiki/HiQ_Labs_v._LinkedIn), but you are responsible for your own use, including [GDPR](https://en.wikipedia.org/wiki/General_Data_Protection_Regulation) 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](https://claude.ai/referral/uIlpa7nPLg) (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.

#### Why does a member ID link (`/in/ACwAA...`) come back as an error?

Links exported by Sales Navigator and the LinkedIn API use a member ID instead of a name (`linkedin.com/in/ACwAAD9q...`). LinkedIn has no public page at those addresses, so the API returns a free `UnsupportedUrl` error row at once. Send the profile's vanity URL instead, e.g. `https://www.linkedin.com/in/satyanadella`.

#### What happens if my run timeout is too short?

Most profiles take a few seconds. A profile LinkedIn blocks on the standard route is retried on a slower route and can take one to three minutes. The run watches its own timeout: every profile collected is saved as it arrives, and profiles it could not reach in time come back as free `RunTimeout` error rows, so the run finishes with partial results instead of being killed. If you see those rows, raise the run's timeout (`timeoutSecs`) or send fewer URLs per run.

***

### 🧠 Claude skill: find the hiring manager

This API is one of the data sources in a ready-made Claude skill. Give the skill one job posting and it returns the likely hiring manager, the recruiter, and the best people to ask for a referral, each with evidence and an outreach draft you send yourself.

- Skill repo: [claude-skill-find-hiring-manager](https://github.com/johnisanerd/claude-skill-find-hiring-manager)

```bash
npx skills add johnisanerd/claude-skill-find-hiring-manager
```

### 🌐 About Alpha OSINT

This Actor is part of [Alpha OSINT](https://www.alphaosint.com), toolset of financial and operations data sources and APIs.
See the [LinkedIn Profile API source page](https://www.alphaosint.com/sources/linkedin-profile-api/) for related tools and use cases.
For support or requests for this actor, please start a ticket [directly on our support page](https://apify.com/johnvc/linkedin-profile-api/issues/open?fpr=9n7kx3).

Last Updated: 2026.10.27

# Actor input Schema

## `profileUrls` (type: `array`):

One or more LinkedIn personal profile URLs, e.g. https://www.linkedin.com/in/satyanadella. URLs that are not LinkedIn /in/ profile URLs are skipped. Up to 1000 per run. Need larger batches? Contact us and we can raise this limit for your account.

## Actor input object example

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

# Actor output Schema

## `allResults` (type: `string`):

Every dataset item from this run: collected profiles and any error rows.

## `overview` (type: `string`):

Tabular overview of every dataset item using the dataset schema's default view. Columns: type, name, headline, company, location, followers, URL, summary.

## `cards` (type: `string`):

Profiles with headshot thumbnail, follower and connection counts.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "profileUrls": [
        "https://www.linkedin.com/in/satyanadella"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("johnvc/linkedin-profile-api").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "profileUrls": ["https://www.linkedin.com/in/satyanadella"] }

# Run the Actor and wait for it to finish
run = client.actor("johnvc/linkedin-profile-api").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "profileUrls": [
    "https://www.linkedin.com/in/satyanadella"
  ]
}' |
apify call johnvc/linkedin-profile-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,johnvc/linkedin-profile-api"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/IBDtFcC5lRLf0vXoH/builds/6cM2nl6FTCikyebFS/openapi.json