# LinkedIn Public Profile Scraper (No Login) (`usestring/linkedin-profiles`) Actor

Scrape public LinkedIn profiles by slug or /in/ URL, with no login and no cookies. Each row carries the full name, headline, About text, dated work history and education with start and end years, location, current company, languages, profile photo and an exact follower count.

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

## Pricing

from $1.25 / 1,000 results

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/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 — work history and education, no login

This Actor collects public LinkedIn profiles by slug or `/in/` URL. It returns the headline, about
text, **dated work history and education**, location, exact follower count and languages.

No LinkedIn account, login or cookies are used — this reads what a logged-out visitor sees on the
public profile.

### What it returns

| Field | Type | Notes |
| --- | --- | --- |
| `fullName` | string | |
| `headline` | string | The short line under the name |
| `about` | string | The About section |
| `jobTitles` | string\[] | Every title held, e.g. `["Co-chair", "Founder"]` |
| `location`, `country` | string | |
| `currentCompany` | string | Most recent employer |
| `positions` | object\[] | `{ company, url, startYear, endYear }` — dated work history |
| `education` | object\[] | `{ school, url, startYear, endYear }` |
| `followerCount` | number | Exact, e.g. `40560540` |
| `languages` | string\[] | |
| `imageUrl` | string | Profile photo |
| `handle`, `sourceUrl`, `collectedAt` | string | Provenance for every row |

### Input

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

| Field | Description |
| --- | --- |
| `profiles` | Public profile slugs or `/in/` URLs. Required, 1–500. |
| `maxItems` | Cap on dataset items. Default 1000. Free plans stop at 250 requests and 250 results — see below. |
| `concurrency` | Profiles fetched in parallel. Default 5. |

Slugs and full URLs for the same person collapse to one fetch, so a mixed list is never billed twice.

### How it reads a profile without logging in

LinkedIn publishes each public profile as schema.org JSON-LD in the page itself, and this Actor reads
that structured data directly rather than handing rendered markup to a model. That is what makes the
work history dated and the follower count exact: `positions` and `education` carry `startYear` and
`endYear` per entry, and `followerCount` arrives as `40560540` rather than "40M".

Because the JSON-LD is part of the logged-out page, no LinkedIn account, session cookie or `li_at`
token is involved at any point.

### Use cases

- Enriching CRM records with role, employer and tenure
- Recruiting research — who worked where, and for how long
- Mapping an account's org structure before outbound
- Tracking executive moves across a watchlist
- Building alumni or cohort lists from education history

### Reliability

Measured across 30 profile slugs in one run: **every profile that exists was collected** — 19/19,
with the other 11 being slugs that do not resolve on LinkedIn and are reported as failures rather
than emitted as empty rows.

Fields come from the profile's own structured data, so a value is either present and correct or
absent — it does not change between runs for the same profile.

### Frequently asked questions

**How do I scrape LinkedIn profiles without logging in?** Put the public profile slugs or `/in/` URLs
in the `profiles` input and run this Actor. It reads the schema.org JSON-LD that LinkedIn publishes
on the logged-out public profile, so no LinkedIn account, cookie or session token is required.

**Do I need a LinkedIn account, cookies or a session?** No. Only the public, logged-out profile is
read, and no credentials of any kind are supplied.

**Does it return email addresses or phone numbers?** No. Contact details are not on the public
LinkedIn profile and are deliberately out of scope for this Actor.

**Does it include work history with dates?** Yes. `positions` carries company, URL, `startYear` and
`endYear` per role, and `education` does the same for schools.

**Is the follower count exact or rounded?** Exact — `followerCount` comes back as `40560540` rather
than "40M".

**How many profiles can one run collect?** Up to 500 per run, which is the ceiling on the `profiles`
input, and this Actor returns one row per profile.

**What happens with a profile that does not exist?** It is recorded under `failures` in the run's
`SUMMARY` and the rest of the batch still returns. A run in which every profile failed exits with an
error.

**Can I search LinkedIn for profiles?** No. You supply the profiles — the LinkedIn Profile Scraper
does not do discovery or keyword search.

### Limitations

Public profile fields only: no contact details, no connections, no posts or activity, no skills or
endorsements, and no search. Profiles set to fully private return nothing to read and are reported as
failures. Only `linkedin.com` URLs are accepted.

### Free plan limit

Runs started from an Apify **free plan** stop at **250 requests and 250 results**, and the run
reports that it reached the limit. Any paid plan runs the full input and `maxItems` you set.

The limit exists because this Actor fetches through our own infrastructure, which Apify does not
cover for free-plan runs. It binds on requests as well as results so that a large input list cannot
spend those fetches for rows the run will not return.

# Actor input Schema

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

LinkedIn public profile slugs or /in/ URLs.

## `maxItems` (type: `integer`):

Global cap on dataset items. Runs started from an Apify free plan stop at 250 requests and 250 results; any paid plan runs the full amount.

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

Targets fetched in parallel.

## Actor input object example

```json
{
  "profiles": [
    "williamhgates"
  ],
  "maxItems": 1000,
  "concurrency": 5
}
```

# Actor output Schema

## `results` (type: `string`):

Collect public LinkedIn profiles by slug or URL - dated work history, education, headline, location and exact follower count.

## `summary` (type: `string`):

Item count, failure count and every target that failed, with its error.

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

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

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

```

## MCP server setup

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

```

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/JaJHdggfjeUm3fLYf/builds/xklCKro8vDE0XeJth/openapi.json