| LinkedIn Public Data Suite • 11 Actors, one codebase, one row billed once | ||
| LinkedIn Scraper API Jobs, Companies, Posts, Articles | LinkedIn Jobs Search Scraper API Filters That Hold | LinkedIn Job Details Scraper API By URL or Job ID |
| LinkedIn Company Jobs Scraper API Open Jobs by Company | LinkedIn New Jobs Scraper API Last 24 Hours, Change-Only | LinkedIn Company Scraper API Exact Employees, Followers |
| LinkedIn Company Posts Scraper API Newest Posts, Exact Counts | LinkedIn Post Scraper API Text, Exact Counts, Top Comments | LinkedIn Pulse Article Scraper API Full Text, Author |
| LinkedIn Profile Scraper API ➤ You are here | LinkedIn Profile Posts Scraper API A Person's Recent Posts | |
form (the link LinkedIn's Share > Copy link gives you). One post row each, with the comments LinkedIn shows publicly as extra rows when the option below is on.
## `includeComments` (type: `boolean`):
Adds one row per comment LinkedIn renders on the public post page, about ten per post, each with the commenter, their profile URL, the text, the date and the like count. The post row always carries the exact total comment count.
## `jobUrls` (type: `array`):
Job posting links (/jobs/view/...), search links that carry currentJobId=, or bare numeric job ids. One full job row each.
## `articleUrls` (type: `array`):
LinkedIn Pulse article links (/pulse/...). One article row each with the full text.
## `experienceLevel` (type: `array`):
Passed to LinkedIn's search and then checked against the seniority the posting itself states; a posting that does not match is neither delivered nor billed. Needs 'Read the full posting' on.
## `jobType` (type: `array`):
Passed to LinkedIn's search and then checked against the employment type the posting states; a posting that does not match is neither delivered nor billed. Needs 'Read the full posting' on.
## `workplaceType` (type: `array`):
Passed to LinkedIn's search as its remote / hybrid / on-site filter. LinkedIn's public job pages carry no structured workplace field, so this one cannot be re-checked on the posting; treat it as LinkedIn's own filtering.
## `companyFilter` (type: `array`):
Company slugs, URLs or numeric LinkedIn company ids. Slugs are resolved to the id from the public company page.
## `geoId` (type: `string`):
Optional numeric region id from a LinkedIn jobs URL (geoId=...). Used together with the free-text location.
## `easyApply` (type: `boolean`):
Passed to LinkedIn's search as its Easy Apply filter.
## `under10Applicants` (type: `boolean`):
Passed to LinkedIn's search. Verified on 2026-09-02 to change the result set.
## `titleInclude` (type: `array`):
Free filter on the listing title before the posting is opened: keep a job only if its title contains every word of at least one of these phrases (case-insensitive). Skipped jobs are neither read nor billed.
## `titleExclude` (type: `array`):
Free filter: drop a job if its title contains any of these words or phrases. Skipped jobs are neither read nor billed.
## `excludeJobIds` (type: `array`):
Job ids you already have. They are never opened and never billed.
## `maxItemsPerQuery` (type: `integer`):
Cap per keyword-and-location search. LinkedIn's public search stops at about 1,000 results; add locations or a shorter date window to go deeper.
## `includeJobDetails` (type: `boolean`):
On: each job is opened and delivered in full (description, seniority, employment type, function, industries, applicants, salary when stated) as a 'job' row. Off: the listing card only (title, company, location, exact posted date, badges) as a cheaper 'job-card' row, ten per request.
## `includeCompany` (type: `boolean`):
For job searches: also deliver one company row per distinct company in the results. Charged once per company, never per job.
## `monitorChangesOnly` (type: `boolean`):
For scheduled runs. The Actor remembers the job ids it delivered for each search and the counts it saw on each company, post and article. On a re-run, jobs you already received are skipped and a company or post whose numbers have not moved is a free 'unchanged' row. Each executed search is still billed as work done.
## `maxItems` (type: `integer`):
Hard cap on billable rows for the whole run, all types together.
## `maxCostUsd` (type: `integer`):
Stop the run before it spends more than this, computed from the live event prices. Leave empty for no ceiling. The free summary row always reports what the run actually spent.
## `useProxy` (type: `boolean`):
Not normally needed. Jobs, company pages, posts and articles are read without any proxy; the Actor escalates to a residential exit by itself when LinkedIn refuses a request. Turn this on only if you have been asked to.
## Actor input object example
```json
{
"profiles": [
"karinklein",
"theseanatkins",
"adi-gelvan",
"bradgroux",
"amitmiglani",
"dpandey"
],
"profileScope": [
"details"
],
"datePosted": "any",
"companyScope": [
"details"
],
"includeComments": false,
"easyApply": false,
"under10Applicants": false,
"maxItemsPerQuery": 100,
"includeJobDetails": true,
"includeCompany": false,
"monitorChangesOnly": false,
"maxItems": 100,
"useProxy": false
}
```
# Actor output Schema
## `dataset` (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 '' with your token
const client = new ApifyClient({
token: '',
});
// Prepare Actor input
const input = {
"profiles": [
"karinklein",
"theseanatkins",
"adi-gelvan",
"bradgroux",
"amitmiglani",
"dpandey"
]
};
// Run the Actor and wait for it to finish
const run = await client.actor("vonsensey/linkedin-profile-scraper-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 '' with your token.
client = ApifyClient("")
# Prepare the Actor input
run_input = { "profiles": [
"karinklein",
"theseanatkins",
"adi-gelvan",
"bradgroux",
"amitmiglani",
"dpandey",
] }
# Run the Actor and wait for it to finish
run = client.actor("vonsensey/linkedin-profile-scraper-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 '{
"profiles": [
"karinklein",
"theseanatkins",
"adi-gelvan",
"bradgroux",
"amitmiglani",
"dpandey"
]
}' |
apify call vonsensey/linkedin-profile-scraper-api --silent --output-dataset
```
## MCP server setup
```json
{
"mcpServers": {
"apify": {
"type": "http",
"url": "https://mcp.apify.com/?tools=fetch-actor-details,vonsensey/linkedin-profile-scraper-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 ` 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/gZ1IPMhFWCoThRL7j/builds/XmCBy9tushQHWKFsU/openapi.json