LinkedIn Company Jobs Scraper avatar

LinkedIn Company Jobs Scraper

Pricing

from $4.00 / 1,000 job scrapeds

Go to Apify Store
LinkedIn Company Jobs Scraper

LinkedIn Company Jobs Scraper

Scrape a LinkedIn company's live job postings: title, location, postedAt, apply URL + optional description, applicants, seniority, plus company metadata. MCP/API-ready.

Pricing

from $4.00 / 1,000 job scrapeds

Rating

0.0

(0)

Developer

Khadin Akbar

Khadin Akbar

Maintained by Community

Actor stats

0

Bookmarked

4

Total users

1

Monthly active users

7 days ago

Last modified

Share

What is LinkedIn Company Jobs Scraper?

Use this Apify Actor to scrape a LinkedIn company's live job postings from a company URL, slug, or numeric company ID. It returns one record per job with fields such as title, location, postedAt, workplaceType, employmentType, seniorityLevel, applicants, job URL, and optional company metadata. When full job details are enabled, the output can also include description text and other detail-page fields. The Actor is API-ready and usable through Apify MCP.

Best fit and connected workflows

This Actor fits workflows that start with one LinkedIn company and need that company's current jobs in structured form.

Common routing patterns:

  • Recruiters and sourcers can track open roles at a target company.
  • Competitive hiring workflows can compare a company's live openings across locations and seniority levels.
  • Market research pipelines can monitor company hiring activity over time.
  • AI agents can use the Actor as a focused tool for one-company job lookup through Apify MCP.

For adjacent job-board workflows, see:

  • Then use APEC Jobs Scraper for APEC-specific job board research when the next workflow needs that Actor's focused input and output contract.
  • Then use Ashby Jobs Scraper for Ashby-hosted roles when the next workflow needs that Actor's focused input and output contract.
  • Then use Bayt Jobs Data Scraper for MENA Listings for Bayt listings in MENA-oriented workflows when the next workflow needs that Actor's focused input and output contract.

Practical scenario

Maya is sourcing engineering talent for a competitor review. She starts with the LinkedIn company URL for Stripe, adds the keyword filter engineer, and keeps enrichJobDetails enabled for deeper review. The Actor returns records with title, location, postedAt, applicants, seniorityLevel, and jobUrl, plus company metadata when requested. Maya uses postedAt and seniorityLevel to narrow the freshest mid-senior openings, then opens the jobUrl list for application review and outreach planning.

Input

The Actor accepts one required input field: company.

Input fields

FieldTypeDescription
companystringLinkedIn company URL, slug, or numeric company ID.
keywordsstringOptional job-title keyword filter within one company.
locationstringOptional location filter such as United States, London, or Remote.
datePostedstringTime window: any, month, week, or day.
jobTypestringEmployment type: any, full-time, part-time, contract, temporary, or internship.
experienceLevelstringSeniority filter: any, internship, entry, associate, mid-senior, director, or executive.
remoteOnlybooleanReturns only roles LinkedIn flags as remote when enabled.
maxResultsintegerMaximum number of jobs to return, up to 1000.
enrichJobDetailsbooleanAdds detail-page fields such as description text and applicants when enabled.
enrichCompanybooleanAttaches company metadata when enabled.
proxyConfigurationobjectProxy settings, with Apify Residential US as the default.

Focused input example

{
"company": "https://www.linkedin.com/company/stripe",
"keywords": "software engineer",
"location": "United States",
"datePosted": "month",
"jobType": "full-time",
"experienceLevel": "mid-senior",
"remoteOnly": false,
"maxResults": 25,
"enrichJobDetails": true,
"enrichCompany": true
}

Output

The Actor stores job records in the default dataset and a run summary in the default key-value store.

Output fields

FieldDescription
titleJob title.
companyNameHiring company name.
companyIdNumeric LinkedIn company ID.
locationJob location.
postedAtDate the job was posted.
jobIdLinkedIn job posting ID.
jobUrlLinkedIn job URL.
applyUrlApply URL when available.
workplaceTypeWorkplace classification such as on-site, hybrid, or remote.
employmentTypeEmployment type when included.
seniorityLevelSeniority when included.
applicantsApplicant count when included.
companyCompany metadata object when enrichment is enabled.
scrapedAtScrape timestamp.

Illustrative output record

{
"jobId": "4427202797",
"title": "Senior Software Engineer",
"companyName": "Stripe",
"companyId": "51737071",
"location": "San Francisco, CA",
"postedAt": "2026-06-25",
"jobUrl": "https://www.linkedin.com/jobs/view/4427202797",
"applyUrl": "https://www.linkedin.com/jobs/view/4427202797",
"workplaceType": "Remote",
"employmentType": "Full-time",
"seniorityLevel": "Mid-Senior level",
"applicants": 83,
"company": {
"industry": "Financial Services",
"size": "1001-5000",
"employeeCount": 3000,
"headquarters": "San Francisco, CA",
"followers": 1000000,
"website": "https://stripe.com",
"logo": "https://example.com/logo.png"
},
"scrapedAt": "2026-06-27T08:00:00.000Z"
}

How it works

  1. The Actor resolves the company input to a numeric LinkedIn company ID.
    • Company URLs and slugs are resolved through a primary data provider first, then a fallback provider as fallback.
    • Numeric company IDs can be used directly.
  2. The Actor lists live LinkedIn job postings for that company through LinkedIn's public jobs-guest endpoint.
  3. The Actor paginates until it reaches maxResults.
  4. When enrichJobDetails is enabled, the Actor visits each job detail page and adds detail-page fields.
  5. When enrichCompany is enabled, the Actor attaches company metadata from the primary or fallback data provider.
  6. Results are written to the dataset and a summary is written to the OUTPUT key in the key-value store.

Pricing

LinkedIn Company Jobs Scraper uses Pay per event on the Apify platform with Apify platform usage included charges. The live Pricing tab shows the current pricing details for the Actor.

Charged events include:

  • Actor start
  • Job scraped
  • Company resolved and enriched

Event-count example: if a run starts once, resolves one company URL, and returns fifty job records, the total includes one actor start event, one company-resolved event, and fifty job-scraped events. For current pricing details, open the live Pricing tab.

Use with AI agents (MCP)

This Actor is usable through Apify MCP as a focused tool for one-company LinkedIn jobs retrieval.

Tool description: scrape live job postings for a single LinkedIn company, with optional filters for keywords, location, date posted, employment type, seniority, remote roles, job enrichment, and company metadata.

Exact Actor identity: khadinakbar/linkedin-company-jobs-scraper

Find the live LinkedIn job postings for the company below. Return structured job records with title, location, posted date, job URL, applicants, seniority, and company metadata when available.

Output interpretation:

  • Use the dataset items for the job list.
  • Use title, location, postedAt, workplaceType, employmentType, seniorityLevel, and applicants for filtering and ranking inside your workflow.
  • Use jobUrl and applyUrl to open the live posting.
  • Use the summary record from the OUTPUT key to review the resolved company ID and provider information.

Provenance and scope:

  • The Actor works on public LinkedIn company job postings.
  • It is designed around one company per run.
  • Company URLs and slugs are resolved before the scrape begins.

Pagination and cost guidance:

  • maxResults controls the job count returned.
  • The Actor paginates through LinkedIn results until that limit.
  • Each returned job is a billed event.
  • The live Pricing tab shows the current pricing details for the Actor.

Apify API example

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({
token: process.env.APIFY_TOKEN,
});
const input = {
company: 'https://www.linkedin.com/company/stripe',
keywords: 'engineer',
location: 'United States',
datePosted: 'month',
maxResults: 10,
enrichJobDetails: true,
enrichCompany: true,
};
const run = await client.actor('khadinakbar/linkedin-company-jobs-scraper').call(input);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Set APIFY_TOKEN in your environment before running the script.

Best results and outcome guidance

  • Use a LinkedIn company URL, slug, or numeric company ID that points to the target employer.
  • Add keywords when you want only a subset of that company's roles.
  • Use location for geography-based filtering within the company.
  • Use datePosted to focus on recent openings.
  • Turn on enrichJobDetails when your workflow needs description text, applicants, or other detail-page fields.
  • Keep enrichCompany enabled when you need company metadata alongside jobs.
  • Keep maxResults aligned with the number of roles your workflow needs to process.

Continue the workflow

Design note

I found that the live output contract exposes two storage locations: the dataset for jobs and the key-value store OUTPUT record for the run summary. That makes the run summary a separate, inspectable artifact rather than part of each dataset item.

FAQ

Use this Actor when your starting point is one LinkedIn company and you want that company's live openings. For broad keyword search across LinkedIn, use linkedin-jobs-scraper.

Can I pass a LinkedIn company URL or slug?

Yes. The Actor accepts a company URL, bare slug, or numeric LinkedIn company ID. URLs and slugs are resolved to a numeric ID before scraping.

What does enrichJobDetails add?

When enabled, it visits each job detail page and adds fields such as description text, applicant count, seniority, employment type, job function, and industries.

What does enrichCompany add?

When enabled, it attaches company metadata such as industry, size, employee count, headquarters, followers, website, and logo.

Is this Actor usable through Apify MCP?

Yes. It is an Apify Actor usable through Apify MCP and is designed for single-company job retrieval.

If your source is another job board, these verified related Actors may fit the workflow:

  • Then use APEC Jobs Scraper when the next workflow needs that Actor's focused input and output contract.
  • Then use Ashby Jobs Scraper when the next workflow needs that Actor's focused input and output contract.
  • Then use Bayt Jobs Data Scraper for MENA Listings when the next workflow needs that Actor's focused input and output contract.

Responsible use

Use the output in compliance with applicable law and the terms that apply to your use of LinkedIn data. This Actor works with public job listings and optional public company metadata. Review your downstream storage, sharing, and enrichment practices before operational use.