# LinkedIn Profile Scraper - Extract Public Profile Data (`datascrapers/linkedin-profile-scraper`) Actor

Scrape public LinkedIn profiles by username or URL. Returns name, headline, about, positions, education, skills, activities, and articles.

- **URL**: https://apify.com/datascrapers/linkedin-profile-scraper.md
- **Developed by:** [Farhan Ali](https://apify.com/datascrapers) (community)
- **Categories:** Lead generation, Social media, News
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 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.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

**LinkedIn Profile Scraper** creates a structured dataset of public LinkedIn profiles. Each dataset item can include the profile URL, name, headline, about summary, location, follower count, profile and background image URLs, work positions, education, certifications, skills, recent activity, and articles. Query the source using a list of profile URLs or usernames, control parallelism with `concurrency`, and retrieve records through the Apify Dataset API or export them as JSON, CSV, Excel, XML, or another supported format.

### Dataset at a glance

| Property | Value |
|---|---|
| Source | LinkedIn public profiles (linkedin.com/in/...) |
| Record unit | One public profile |
| Input methods | `profiles` (list of usernames or URLs) |
| Main identifiers | `profileId`, `url` |
| Delivery | Apify Dataset and API |
| Export formats | JSON, CSV, Excel, XML, HTML |
| Update model | Fresh records per Actor run |
| Pricing | $3.00 per 1,000 profiles |

### Coverage and available records

The Actor scrapes public LinkedIn profiles by username or full URL. Supported behavior:

- **Profile inputs** — `profiles` accepts usernames (`"jeffweiner08"`) or full URLs (`"https://www.linkedin.com/in/jeffweiner08"`).
- **Parallelism** — `concurrency` (1–10, default 3) controls how many profiles are scraped in parallel.
- **Public data only** — the Actor reads the public profile view; it does not authenticate or bypass login walls.

Records include work history (`positions`), education, certifications, skills, recent activities, articles, recommendations, and other public sections. Some sections may be empty for private or lightly-populated profiles.

Not currently collected: full connection lists, private-members-only content, and profiles that require authentication to view.

### Data dictionary

| Field | Type | Nullable | Description | Example |
|---|---:|---|---|---|
| `url` | string | no | Profile URL; unique per profile | `https://www.linkedin.com/in/jeffweiner08` |
| `name` | string | yes | Full display name | `Jeff Weiner` |
| `firstName` | string | yes | First name | `Jeff` |
| `lastName` | string | yes | Last name | `Weiner` |
| `headline` | string | yes | Profile headline | `Founding Partner · Founding LP...` |
| `about` | string | yes | About/summary text (may contain HTML) | `For much of the last three decades...` |
| `location` | string | yes | Display location | `United States` |
| `profileId` | string | yes | LinkedIn profile identifier; recommended deduplication key | `22330283` |
| `profilePicture` | string | yes | Profile photo URL | `https://media.licdn.com/dms/...jpg` |
| `backgroundPicture` | string | yes | Background image URL | `https://media.licdn.com/dms/...jpg` |
| `followerCount` | integer | yes | Follower count | `10370544` |
| `openToWork` | boolean | yes | Open-to-work flag | `true` |
| `openToHiring` | boolean | yes | Open-to-hiring flag | `false` |
| `disambiguatingDescription` | string | yes | Platform subtitle | `Creator, Top Voice` |
| `positions` | array | yes | Work history objects | see below |
| `education` | array | yes | Education entries | `[]` |
| `certifications` | array | yes | Certification entries | `[]` |
| `skills` | array | yes | Skill objects with `name` | `[{"name":"Leadership"}]` |
| `activities` | array | yes | Recent post objects (`postUrl`, `text`, `likes`) | `[{"postUrl":"...","text":"..."}]` |
| `articles` | array | yes | Article objects (`title`, `url`, `datePublished`, `likeCount`) | `[{"title":"...","url":"..."}]` |
| `recommendations` | array | yes | Recommendation objects (`author`, `text`) | `[{"author":"...","text":"..."}]` |
| `volunteer`, `projects`, `languages`, `honors`, `publications`, `courses`, `testScores`, `patents`, `organizations`, `causes` | array | yes | Other public sections | `[]` |

Each `positions` element typically contains `title`, `company`, `companyUrl`, `companyLogo`, `location`, `startDate`, `endDate`, and `duration`.

### Example dataset record

```json
{
  "url": "https://www.linkedin.com/in/jeffweiner08",
  "name": "Jeff Weiner",
  "firstName": "Jeff",
  "lastName": "Weiner",
  "headline": "Founding Partner · Founding LP, Investment Committee · Co-Founder",
  "location": "United States",
  "profileId": "22330283",
  "followerCount": 10370544,
  "openToWork": true,
  "openToHiring": false,
  "positions": [
    {
      "title": "Founding Partner",
      "company": "Next Play Ventures",
      "companyUrl": "https://www.linkedin.com/company/next-play-ventures",
      "location": "San Francisco Bay Area",
      "startDate": "2020-07",
      "duration": "6 years"
    }
  ],
  "education": [],
  "certifications": [],
  "skills": [
    {"name": "Leadership"},
    {"name": "Entrepreneurship"}
  ]
}
```

The record above was produced by a run with `profiles: ["jeffweiner08"]`.

### Query and input reference

| Input | Type | Required | Default | Accepted values | Description |
|---|---:|---|---|---|---|
| `profiles` | array | yes | — | usernames or full URLs | List of profiles to scrape |
| `concurrency` | integer | no | `3` | 1–10 | Number of profiles scraped in parallel |
| `proxyConfiguration` | object | no | residential proxy | proxy settings | Residential proxies are used by default |

Minimal request:

```json
{
  "profiles": ["jeffweiner08"],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}
```

Advanced request (multiple profiles, higher parallelism):

```json
{
  "profiles": [
    "jeffweiner08",
    "https://www.linkedin.com/in/faizanaliii"
  ],
  "concurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}
```

### Retrieve the data through the API

1. Start the Actor with a JSON input (see above).
2. Wait for the run to finish.
3. Retrieve items from the run's default dataset.
4. Paginate or export the dataset.

Python example:

```python
import json
import urllib.request

API_TOKEN = "<your Apify API token>"
ACTOR_ID = "datascrapers/linkedin-profile-scraper"

payload = {
    "profiles": ["jeffweiner08"],
    "concurrency": 3,
    "proxyConfiguration": {"useApifyProxy": True, "apifyProxyGroups": ["RESIDENTIAL"]},
}

req = urllib.request.Request(
    f"https://api.apify.com/v2/acts/{ACTOR_ID}/runs?token={API_TOKEN}",
    data=json.dumps(payload).encode(),
    headers={"Content-Type": "application/json"},
)
with urllib.request.urlopen(req) as resp:
    run = json.loads(resp.read())["data"]

dataset_id = run["defaultDatasetId"]
with urllib.request.urlopen(
    f"https://api.apify.com/v2/datasets/{dataset_id}/items?token={API_TOKEN}"
) as resp:
    items = json.loads(resp.read())
```

For other languages, use the generated API tab on the Actor's page.

### Data quality and record handling

- **Public data only** — the Actor reads the public profile view; authenticated-only or private content is not collected.
- **Nullable/empty sections** — `education`, `certifications`, `skills`, `volunteer`, and other sections are empty arrays when a profile does not expose them.
- **Raw HTML** — `about` may contain `<br>` and other HTML tags; strip them if you need plain text.
- **Deduplication** — `profileId` is the stable, recommended unique key; `url` is also unique.
- **Retries and errors** — profiles that fail to load are retried; a profile that cannot be reached is skipped.
- **Dates** — `startDate`/`endDate` follow LinkedIn's own formatting (`YYYY-MM`, `Mon YYYY`, or `YYYY`), so formats vary.

The Actor reflects the public profile at run time and does not retain historical snapshots.

### Export and pipeline examples

| Destination | Recommended method | Typical use |
|---|---|---|
| PostgreSQL/Supabase | Dataset API or webhook consumer | Contact/profile store keyed by `profileId` |
| Google Sheets | Apify integration | Review a short list of profiles |
| S3/cloud storage | Scheduled export or integration | Periodic profile snapshots |
| CRM | Dataset API or integration | Lead enrichment from public profiles |

### Pricing and cost examples

The Actor uses pay-per-event billing. One charge event applies:

- **`profile-scraped`** — $3.00 per 1,000 profiles returned.

| Records | Estimated base cost |
|---:|---:|
| 1,000 profiles | $3.00 |
| 10,000 profiles | $30.00 |
| 100,000 profiles | $300.00 |

Estimates assume the free-tier rate and no proxy markup; actual cost depends on your Apify plan and selected options.

### Limitations and responsible data use

- The Actor collects publicly accessible profile data only; it does not bypass login or paywalls.
- Results depend on LinkedIn's current page structure; site changes can require Actor updates.
- Some sections are conditional or empty (see Data dictionary).
- The Actor does not retain historical snapshots unless you store them yourself.
- You are responsible for complying with LinkedIn's terms of service and applicable privacy, contractual, and data-protection obligations.

### Dataset questions

#### What does one dataset item represent?

One public LinkedIn profile with its work history, education, skills, and other public sections.

#### Which field should I use as a unique identifier?

`profileId`. `url` is also unique per profile.

#### Are fields nullable or conditional?

Yes. Many sections (education, certifications, skills) are empty arrays when a profile does not expose them; individual fields may be null.

#### Can I retrieve the records as CSV or JSON?

Yes. The default dataset supports JSON, CSV, Excel, and XML exports, and the Dataset API returns JSON.

#### How do I paginate large datasets?

The Actor accepts a list of profiles; split large lists into multiple runs, or paginate the default dataset via the Dataset API.

#### What counts as a billable result?

Each profile successfully returned counts as one `profile-scraped` event.

### Related datasets from Data Scrapers

- **[LinkedIn Company Scraper](https://apify.com/datascrapers/linkedin-company-scraper)** — company-level data that joins with profiles by employer name.
- **[Instagram Post Scraper](https://apify.com/datascrapers/instagram-post-scraper)** — social posts for cross-platform identity and brand analysis.
- **[Instagram Comment Scraper](https://apify.com/datascrapers/my-actor-1)** — engagement data that complements profile-level research.
- **[Clutch.co Company Scraper](https://apify.com/datascrapers/clutch-scraper)** — company ratings and reviews for B2B lead enrichment.

### Data Scrapers support

Need an additional field, record type, or export workflow? Contact Data Scrapers at stardustspotlight@gmail.com. Include a sample source URL, required fields, expected record volume, and preferred delivery format.

# Actor input Schema

## `profiles` (type: `array`):

List of LinkedIn profile usernames or full profile URLs to scrape (e.g. "jeffweiner08" or "https://www.linkedin.com/in/jeffweiner08")

## `concurrency` (type: `integer`):

Number of profiles to scrape in parallel. Lower values are safer, higher values are faster.

## `proxyConfiguration` (type: `object`):

Proxy settings for anti-bot protection. Apify Residential proxies are used by default. Override with custom proxyUrls for local testing.

## Actor input object example

```json
{
  "profiles": [
    "jeffweiner08"
  ],
  "concurrency": 3,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `dataset` (type: `string`):

Link to the default dataset containing all scraped profiles

## `run` (type: `string`):

Link to the run in Apify Console

# 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 = {
    "profiles": [
        "jeffweiner08"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("datascrapers/linkedin-profile-scraper").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 = { "profiles": ["jeffweiner08"] }

# Run the Actor and wait for it to finish
run = client.actor("datascrapers/linkedin-profile-scraper").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 '{
  "profiles": [
    "jeffweiner08"
  ]
}' |
apify call datascrapers/linkedin-profile-scraper --silent --output-dataset

```

## MCP server setup

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

```

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/cr0SYSUSfvWkiiXFM/builds/dabImNVQXxt536gfx/openapi.json