# LinkedIn Profile Scraper - No Login Required (`gopalakrishnan/linkedin-profile`) Actor

Extract LinkedIn profile data -  name, headline, about, location, current company, experience, education, and follower count - from a list of profile URLs. Works fully logged out, no cookies, zero risk to your own account. Pay only for profiles successfully scraped.

- **URL**: https://apify.com/gopalakrishnan/linkedin-profile.md
- **Developed by:** [Gopalakrishnan](https://apify.com/gopalakrishnan) (community)
- **Categories:** Lead generation, Jobs, Automation
- **Features:** Limited permissions
- **Stats:** 30 total users, 7 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 profile scrapeds

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
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 Scraper (No Login / No Cookies / Safe)

A production-grade, high-performance Apify Actor for scraping public LinkedIn profiles.

Unlike other LinkedIn scrapers on the market, **this Actor does not require cookies, logins, or active account sessions**. It runs entirely logged-out, eliminating the risk of your personal or business LinkedIn accounts getting flagged or banned.

***

### 🚀 Key Differentiators & Benefits

- **Zero Ban Risk**: No login credentials or cookies are required. Your LinkedIn accounts are 100% safe.
- **No Cookie Expiry**: Since no session cookies are used, your scraping pipelines will never break due to "session expired" errors.
- **Blazing Fast & Lightweight**: Built on top of Crawlee and CheerioCrawler (raw HTML parsing), avoiding heavy browser automation overhead. It is up to 10x faster and uses a fraction of the memory/CPU compared to Puppeteer/Playwright alternatives.
- **Apify Proxy Integration**: Automatically routes requests through high-quality proxy IPs to ensure high success rates and prevent rate limiting.
- **Pay-Per-Event (PPE) Friendly**: You only pay for what you successfully scrape!

***

### 🛠️ How it Works

The Actor requests the public profile page (`https://www.linkedin.com/in/<slug>`) using a randomized desktop User-Agent and routes it through Apify Proxy. Public profiles contain structured schema.org `Person` markup embedded inside an `application/ld+json` script tag. The Actor parses this JSON-LD payload to extract rich, structured profile information without needing to authenticate or execute heavy client-side JavaScript.

***

### 📥 Input Settings

The Actor accepts the following input fields:

| Field                | Type             | Description                                                                                                                      | Required / Default                   |
| -------------------- | ---------------- | -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------ |
| `profiles`           | Array of strings | A list of LinkedIn usernames/slugs (e.g. `satyanadella`) or full profile URLs (e.g. `https://www.linkedin.com/in/satyanadella`). | **Required**                         |
| `proxyConfiguration` | Object           | Connection settings for proxy routing. Apify Proxy is used by default.                                                           | Default: `{ "useApifyProxy": true }` |
| `maxProfiles`        | Integer          | Caps the maximum number of profiles to scrape. Useful for budget control.                                                        | Optional / Null                      |

***

### 📤 Output Fields

The Actor produces clean, flat records in the default dataset. Below are the fields extracted:

| Field            | Type    | Description                                                                       |
| ---------------- | ------- | --------------------------------------------------------------------------------- |
| `fullName`       | String  | The full name of the user.                                                        |
| `headline`       | String  | The profile's headline (often current job title/role).                            |
| `about`          | String  | The user's biography/about summary.                                               |
| `location`       | String  | Geolocation (e.g. "Redmond, Washington, United States").                          |
| `currentCompany` | String  | The company name of their current primary employment.                             |
| `currentTitle`   | String  | Their current job title.                                                          |
| `experience`     | Array   | Full employment history (company, company URL, title, location, start/end dates). |
| `education`      | Array   | Education history (school name, school URL, start/end dates).                     |
| `followers`      | Integer | Total number of followers on their profile.                                       |
| `connections`    | Integer | Total number of connections (if available).                                       |
| `skills`         | Array   | A list of endorsed/listed skills.                                                 |
| `languages`      | Array   | Spoken/written languages.                                                         |
| `profileUrl`     | String  | Canonical URL of the profile (`https://www.linkedin.com/in/<slug>`).              |
| `scrapeStatus`   | String  | Either `success` or `error`.                                                      |
| `scrapedAt`      | String  | ISO timestamp of the scraping event.                                              |

#### Example Output JSON

```json
{
    "fullName": "Satya Nadella",
    "headline": "Chairman and CEO at Microsoft",
    "about": "Satya Nadella is Chairman and CEO of Microsoft...",
    "location": "Redmond, Washington, United States",
    "currentCompany": "Microsoft",
    "currentTitle": "Chairman and CEO",
    "experience": [
        {
            "company": "Microsoft",
            "companyUrl": "https://www.linkedin.com/company/microsoft",
            "location": "Greater Seattle Area",
            "title": "Chairman and CEO",
            "startDate": "2014-02",
            "endDate": null
        }
    ],
    "education": [
        {
            "school": "University of Chicago Booth School of Business",
            "schoolUrl": "https://www.linkedin.com/school/chicago-booth/",
            "startDate": "1995",
            "endDate": "1997"
        }
    ],
    "followers": 10500000,
    "connections": 500,
    "skills": ["Enterprise Software", "Cloud Computing", "SaaS"],
    "languages": ["English", "Hindi"],
    "profileUrl": "https://www.linkedin.com/in/satyanadella",
    "scrapeStatus": "success",
    "scrapedAt": "2026-06-21T18:45:00.000Z"
}
```

***

### 💰 Pay-Per-Event (PPE) Pricing

This Actor is configured with Pay-Per-Event billing:

1. **`actor-start`**: Charged once per Actor run to cover initialization costs.
2. **`profile-scraped`**: Charged per successfully scraped profile. Profiles that fail to scrape (e.g. login-walled, invalid username) are marked with `scrapeStatus: 'error'` and are **not** charged the profile success fee.

***

### 🔗 Sibling Actors

If you are scraping LinkedIn data for lead generation or market analysis, you may also find our other specialized tools helpful:

- **[LinkedIn Jobs Scraper](https://apify.com/gopalakrishnan/linkedin-jobs)**: Extract job listings, descriptions, salary details, and employer info without any session cookies.

# Actor input Schema

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

LinkedIn profile URLs or usernames/slugs to scrape (e.g. 'satyanadella' or 'https://www.linkedin.com/in/satyanadella')

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

Apify Proxy settings (required). Only datacenter/residential proxies should be used.

## `maxProfiles` (type: `integer`):

Maximum number of profiles to scrape. Leave empty for no limit.

## Actor input object example

```json
{
  "profiles": [
    "satyanadella"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `profiles` (type: `string`):

No description

# 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": [
        "satyanadella"
    ]
};

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

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

```

## MCP server setup

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

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/j4qiav7vzrmMLcq5A/builds/7E8tAqTBvFwhsGHlM/openapi.json
