.
***
### Support
Issues and feature requests via the actor's Issues tab, or email above.
***
### ⚠️ Disclaimer
This actor returns only what LinkedIn shows logged-out visitors. Use it on data you are entitled to access, and comply with LinkedIn's Terms of Service and applicable data-protection law — including the GDPR and CCPA — when storing or processing results. Personal data carries obligations around lawful basis, retention and subject access. You are the data controller for anything you collect; the actor's author is not. Do not use output for unlawful discrimination, harassment, or unsolicited bulk messaging.
***
### SEO Keywords
linkedin profile scraper no cookies, linkedin scraper no login, linkedin scraper, linkedin profile scraper, linkedin data extraction, scrape linkedin profiles, linkedin profile api, linkedin scraper without login, public linkedin profile data, linkedin lead generation, recruitment data, candidate sourcing, linkedin crawler, linkedin json export, linkedin csv export, professional profile data, linkedin employment history, b2b prospecting, sales navigator alternative, reliable linkedin profile scraper, best linkedin profile scraper, linkedin scraper pay per result, cheap linkedin profile scraper, linkedin profile scraper alternative, linkedin scraper transparent billing, apify linkedin actor
# Actor input Schema
## `scrapeMyConnections` (type: `boolean`):
Not shown in the form. Kept so existing tasks and API calls that export their own connections keep working; it needs your cookies. Turn this on to scrape your own first-degree connections instead of supplying URLs yourself. The actor reads your My Network list, then scrapes the full profile of every connection it finds. Leave Start URLs empty when using this. There is no 1,000-result limit — it walks your whole network. Needs your cookies (see the Cookies section below).
## `maxConnections` (type: `integer`):
Only used when 'Scrape my own connections' is on. Caps how many connections are collected before scraping starts.
## `startUrls` (type: `array`):
LinkedIn profile URLs to scrape, like https://www.linkedin.com/in/williamhgates/. No login and no cookies needed: each profile is read as LinkedIn shows it to logged-out visitors.
## `maxItems` (type: `integer`):
Maximum number of Profiles/Items to scrape per crawl.
## `language` (type: `string`):
Not shown in the form: it only applies to runs with cookies. Ask LinkedIn for profile text (headlines, job titles, school and skill names) in this locale. Members who published a translation come back in that language; everyone else keeps their original wording, so you never lose rows. Leave empty for US English. Needs cookies; public profiles read without cookies come back in their original language.
## `maxSkills` (type: `integer`):
Keep only the first N skills on each profile. LinkedIn returns them ordered by endorsement strength, so the top ones survive. Leave at 0 to keep every skill returned. Profiles read without a cookie carry at most three.
## `maxConcurrency` (type: `integer`):
Maximum number of pages that can be processed at the same time.
## `minConcurrency` (type: `integer`):
Minimum number of pages that will be processed at the same time.
## `maxRequestRetries` (type: `integer`):
Number of times the crawler will retry a failed request before giving up.
## `cookies` (type: `array`):
Not shown in the form: the actor reads public profiles without a login. Kept so existing tasks and API calls that pass their own LinkedIn session keep working.
Optional. Leave this empty to scrape the Start URLs as public profiles without a LinkedIn login. Add your cookies for the fuller logged-in profile (volunteering, languages, certifications, LinkedIn IDs), and for profiles hidden from logged-out visitors. Most runs do not need them.
Cookie used to authorize actor with linkedin.com. Install EditThisCookie chrome extension. Login to your linkedin.com account. Click on the extension and press Export to copy all linkedin.com cookies, then paste them here.
Paste the full exported list of cookie objects — not a single value. Both li_at and JSESSIONID must be present: li_at is the session, and JSESSIONID is used as the CSRF token for LinkedIn's internal API. It should look like this:
[
{"name":"li_at","value":"AQED...","domain":".linkedin.com"},
{"name":"JSESSIONID","value":"ajax:...","domain":".linkedin.com"}
]
## `proxy` (type: `object`):
Leave empty — the actor already routes all traffic through its own built-in residential proxy at no extra cost to you. Only set this if you want to use your own proxies.
## Actor input object example
```json
{
"scrapeMyConnections": false,
"maxConnections": 5000,
"startUrls": [
{
"url": "https://www.linkedin.com/in/harsh-shuddhalwar/"
}
],
"maxItems": 100,
"language": "",
"maxSkills": 0,
"maxConcurrency": 10,
"minConcurrency": 1,
"maxRequestRetries": 10,
"cookies": []
}
```
# Actor output Schema
## `profiles` (type: `string`):
One row per profile with name, headline, location, about, current company, and the workHistory, education and skills arrays.
# 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 '' with your token
const client = new ApifyClient({
token: '',
});
// Prepare Actor input
const input = {
"startUrls": [
{
"url": "https://www.linkedin.com/in/harsh-shuddhalwar/"
}
],
"cookies": []
};
// Run the Actor and wait for it to finish
const run = await client.actor("memo23/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 '' with your token.
client = ApifyClient("")
# Prepare the Actor input
run_input = {
"startUrls": [{ "url": "https://www.linkedin.com/in/harsh-shuddhalwar/" }],
"cookies": [],
}
# Run the Actor and wait for it to finish
run = client.actor("memo23/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 '{
"startUrls": [
{
"url": "https://www.linkedin.com/in/harsh-shuddhalwar/"
}
],
"cookies": []
}' |
apify call memo23/linkedin-profile-scraper --silent --output-dataset
```
## MCP server setup
```json
{
"mcpServers": {
"apify": {
"type": "http",
"url": "https://mcp.apify.com/?tools=fetch-actor-details,memo23/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 ` 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/o6kG0foqWs6cu5Orb/builds/HndZtlkODCxSClBP6/openapi.json
