At Accenture Federal Services, ...
" }, "searchQuery": "data engineer | United States" } ``` `postedAt` is the exact date from LinkedIn's listing, not a "1 week ago" estimate. `salary` is filled only when the posting states one (`source` says whether it came from a salary element or the description text). `applicants.count` is null when LinkedIn only says "Be among the first 25 applicants". ### What it costs | You pay for | Price | |---|---| | Each job found by a search, delivered with its full posting | **$1.50 per 1,000 jobs** | | Each job delivered as a listing card only ("Read the full posting" off) | **$0.50 per 1,000 jobs** | | Each keyword-and-location search that delivered something (never more than 250 a run) | **$2.00 per 1,000 searches** | | Each company page delivered (once per company, never per job) | **$4.00 per 1,000 companies** | **Free, always:** a job that has closed, a company, post or article that does not exist, a page LinkedIn only shows to signed-in members, a malformed URL, every error row, the coverage row and the run summary, a job skipped by your title filters or id list, and a posting whose stated seniority or job type does not match the filter you set. A run that reads nothing costs nothing. On a one-off run a search is billed only when it delivered at least one job. With **Monitor** on, every search LinkedIn answered is billed, because that check is the work you scheduled — so a day with no new postings costs $2.00 per 1,000 searches and nothing else. A query LinkedIn cannot match (it returns unrelated "similar" jobs) is detected, delivers nothing and costs nothing. Searches never count against your result cap. Set **Cost ceiling (USD)** to stop any run before it passes a number you choose; the free summary row reports what the run actually spent. ### FAQ #### Do I need a LinkedIn login, cookies or a proxy? No. This Actor reads the pages LinkedIn shows to anyone without an account, and it never signs in, never sends a cookie and never uses a session. Everything is handled for you and there is nothing to buy on top. Measured 2026-09-02: a full default run read 25 pages from an ordinary IP with no proxy traffic at all. #### Do the job filters actually work? The date window, job type, Easy Apply, under-10-applicants and company filters change LinkedIn's results reliably (each was checked on three queries on 2026-09-02). Since LinkedIn's August 2026 search change, its experience-level and workplace filters are applied on some queries and ignored on others. So seniority and job type are re-checked against what the posting itself states, and a posting that does not match is neither delivered nor billed. Workplace (remote / hybrid / on-site) is passed to LinkedIn as its own filter and is not re-checked, because the public posting carries no structured workplace field. #### How many jobs can one search return? LinkedIn's public search stops at about 1,000 results per query. To go deeper, add locations, split keywords, or use a shorter date window — each combination is its own search with its own 1,000. #### Why did I get jobs that do not match my keyword? LinkedIn returns "similar" postings when a query has few exact matches and does not mark them. Use **Title must contain** and **Title must not contain**: they are applied before a posting is opened, and skipped jobs are never billed. #### What happens to a job that closed or a page that does not exist? It costs nothing. You get a free error row that says which (closed, not found, or only visible to members), and the run keeps going. #### Does a run fail if everything I asked for is gone? No. "All of these have closed" is a correct answer, not a failure, so the run succeeds and returns free rows explaining each one. Only LinkedIn actually refusing us fails a run. #### Can I put this on a schedule without paying twice for the same data? Yes. Turn **Monitor** on. Job ids delivered for each search are remembered for 60 days and never billed again; a day with no new postings bills only the search itself. A company, post or article whose numbers have not moved is a free row marked `unchanged`. #### Will I be charged twice if the same thing appears twice in my input? No. A post reached through a share link and again from a company page, or a job returned by two searches, is one row and one charge. ### Limits, stated plainly LinkedIn shows its search results (people, companies, content), employee lists, reaction lists and Sales Navigator only to signed-in members, and serves member profiles to visitors only at its own discretion (measured 2026-09-02 from Apify's own exits: 35 of 50 ordinary profiles, and the refused ones stay refused). This Actor reads public pages only and never signs in, so it sells none of those — and says so here rather than on your invoice. LinkedIn's public job search stops at about 1,000 results per query and applies its experience-level and workplace filters inconsistently; seniority and job type are re-checked on the posting, workplace is not. The external "Apply" link and the hiring team are behind LinkedIn's sign-in and are not sold. Salary is delivered when the posting states it. ### Use it from n8n, MCP, the API or a schedule Built to be called by a workflow, not only from the Store form. The Actor is `vonsensey/linkedin-company-jobs-scraper-api`; every snippet below sends `{}`, which runs the defaults shown on the form — replace it with your own input. #### n8n Install the **Apify** community node (`@apify/n8n-nodes-apify` under *Settings → Community Nodes*, or search "Apify" on n8n Cloud). Add **Apify → Run Actor** with Actor `vonsensey/linkedin-company-jobs-scraper-api` and your input JSON, then **Apify → Get Dataset Items** on the run's `defaultDatasetId` and pipe the rows anywhere. For scheduled runs, the **On new Apify Event** trigger fires when a run of this Actor finishes. #### MCP (Claude, Cursor, VS Code, any MCP client) ```json { "mcpServers": { "apify": { "url": "https://mcp.apify.com?tools=vonsensey/linkedin-company-jobs-scraper-api", "headers": { "Authorization": "Bearer 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
{
"datePosted": "any",
"companies": [
"microsoft",
"nvidia"
],
"companyScope": [
"jobs"
],
"includeComments": false,
"easyApply": false,
"under10Applicants": false,
"maxItemsPerQuery": 25,
"includeJobDetails": true,
"includeCompany": false,
"monitorChangesOnly": false,
"maxItems": 50,
"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 = {
"companies": [
"microsoft",
"nvidia"
]
};
// Run the Actor and wait for it to finish
const run = await client.actor("vonsensey/linkedin-company-jobs-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 = { "companies": [
"microsoft",
"nvidia",
] }
# Run the Actor and wait for it to finish
run = client.actor("vonsensey/linkedin-company-jobs-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 '{
"companies": [
"microsoft",
"nvidia"
]
}' |
apify call vonsensey/linkedin-company-jobs-scraper-api --silent --output-dataset
```
## MCP server setup
```json
{
"mcpServers": {
"apify": {
"type": "http",
"url": "https://mcp.apify.com/?tools=fetch-actor-details,vonsensey/linkedin-company-jobs-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/8hoGyu66j7a1Bt9f5/builds/CjTsGJ0BWbBMaNnmz/openapi.json