Blog/Sales and GTM
5 min read

LinkedIn Scraper API: Get Company, People and Job Data

Use a LinkedIn scraper API to pull company profiles, employee lists, job postings and posts without handing over your account, billed per call.

LinkedIn Scraper API: Get Company, People and Job Data

Pull a company profile, the people who work there and its open jobs from LinkedIn, in one prompt. Paste this into your agent:

Set up https://monid.ai/SKILL.md, and then use Monid to get the LinkedIn company profile of linkedin.com/company/anthropicresearch, list 25 people who work there with their title and location, and find the latest data engineer jobs in Berlin, as one table per job.

One prompt runs all three lookups. 1 min setup · 24-48 hrs saved.

You want LinkedIn data in a table: the companies on your account list, the people who work at them, the jobs they are hiring for. A LinkedIn scraper API returns that as JSON without you running a browser or lending out a login. This guide shows the quick route from an agent, what each endpoint returned when we ran it on 2026-10-16, and the traps in the output. It runs through Monid, the OpenRouter for agent tools: one key, one balance, every tool priced per call.

What is the easiest way to use a LinkedIn scraper API?

Monid. Install it once, add a key, and your agent calls LinkedIn endpoints with a company URL, a job title or a post and gets typed JSON back, with no vendor account to open for each source and no session of yours involved.

  • Pay per call. Each lookup is billed on its own: a company profile is $0.008 and a job result is $0.001 (Verified 2026-10-16 on the LinkedIn tools page). Buy calls as you need them: no monthly plan and no minimum top-up. Discovery and inspection are free; only a run bills.
  • One install, every API. The same key and the same balance call the LinkedIn endpoints and every other tool on Monid. A company profile, a people search and a job search are three endpoints on one balance, not three vendors.
  • Lives inside your agent. Install the CLI, add your key, run the prompt above, and the tools are there whenever your agent needs them, on demand, with nothing to keep running. Your agent reads SKILL.md and learns the rest, so setup is about a minute.

How do you scrape LinkedIn data for a list of companies?

Run one lookup per company and loop it over your list, then widen to people and jobs. There are three jobs, and each has its own endpoint: a company profile from a company URL, employee profiles from a company URL, and job postings from a title and a location.

RouteWhat you getCost shapeFits
Buy a lead database seatPre-collected records for millions of peopleAnnual contractBroad prospecting across a whole market
Build your own scraperWhatever your parser coversYour hours and proxiesOne fixed page type you will maintain
Marketplace scraper actorOne scraper, one vendor accountPer vendor planA single source
Monid LinkedIn endpointsLive company, people, job and post data as typed JSONPay per call, buy flexiblyAccount lists, hiring signals, agents and n8n flows

Monid fits a list because the work is the same call repeated, and you pay for the companies you look up and nothing between runs. The people search is the same Apify actor pair we used to build a LinkedIn contact list from one integration, so that post shows the email step end to end.

For agents

Grab an API key at app.monid.ai, then paste this to your agent and hand it the key:

set up https://monid.ai/SKILL.md

It learns the whole discover, inspect, run workflow itself. More in the agent quickstart.

For humans

npm install -g @monid-ai/cli
monid keys add -k <your-key> -l main

Look up one company

monid discover -q "linkedin company"
monid inspect -p tikhub -e /api/v1/linkedin/web_v2/get_company_profile
monid run -p tikhub -e /api/v1/linkedin/web_v2/get_company_profile \
  --query '{"url":"https://www.linkedin.com/company/anthropicresearch/"}'

Swap the url for each company on your list and the same call returns one record per company.

Find the people at those companies

monid inspect -p apify -e /harvestapi/linkedin-company-employees
monid run -p apify -e /harvestapi/linkedin-company-employees \
  -i '{"companies":["https://www.linkedin.com/company/anthropicresearch"],
       "profileScraperMode":"Full ($8 per 1k)",
       "maxItems":50}'

profileScraperMode takes one of three values in the schema (Verified 2026-10-16): Short ($4 per 1k), Full ($8 per 1k) and Full + email search ($12 per 1k). maxItems is the maximum number of profiles, and the endpoint bills for the results it returns.

Watch jobs over time

monid run -p apify -e /harvestapi/linkedin-job-search \
  -i '{"jobTitles":["data engineer"],
       "locations":["Berlin"],
       "maxItems":100}'

Or hand the whole job to an agent

Give this to your agent

$Set up https://monid.ai/SKILL.md, and then use Monid to for each company on this list, get its LinkedIn profile, pull 25 people with a sales or marketing title, and list its open data engineer jobs in one table.

Can you build a LinkedIn scraper yourself with Python?

Yes, for one public page it is an afternoon, and it stays that way only until you need a second page type. You fetch the page, parse the HTML, and keep the result. A search on Google for a Python LinkedIn scraper returns GitHub projects for exactly this, and the free ones all share the same shape of problem.

The cost is everything around the parser. Scraping LinkedIn without getting banned goes through the account side in more detail. You need a fetch layer that survives blocking, a different parser for a company page, a profile, a job and a post, and a repair every time the markup changes. Then comes the login question. A tool that uses your session cookie acts as your account, so any limit it trips lands on that account, which is why a profile you have built over years is the thing at risk. A cookie-free endpoint reads public pages from its own infrastructure, so no session of yours exists to restrict.

The Monid route is the choice for anything you will run more than once. The fetch layer and the parsers are maintained for you, the output is typed JSON instead of HTML you parse, and the job-search input even carries an optional cookie field you can leave empty. A company profile is $0.008 (Verified 2026-10-16). Browser extensions and free online scrapers are quicker for one page, but they are made for a person at a screen, not for a list or an agent.

What does LinkedIn data look like, and what can you build with it?

LinkedIn data comes back in layers: a company record, a people list, jobs and posts. We ran each endpoint on 2026-10-16, so the fields below are what came back.

The company record

One call to get_company_profile for linkedin.com/company/anthropicresearch/ returned the name, about text, slogan, website, industries ("Research Services"), organization_type ("Privately Held"), company_id, followers (5,236,351) and employees_in_linkedin (6,244). It also returned a company_size band ("501-1,000 employees"), a similar array of 10 companies, an affiliated array of 2 pages, a short employees sample of 4 people and an updates array of 10 recent posts with likes_count and comments_count. The call took about four seconds and billed $0.008 (Verified 2026-10-16).

The similar array is the underrated field. It is LinkedIn's own list of comparable companies, here OpenAI, Perplexity, NVIDIA, Google and Stripe among them, and it arrives inside a call you were making anyway.

The people list

linkedin-company-employees returned three profiles for the same company in Short mode: firstName, lastName, linkedinUrl, currentPositions (title, company, tenure, start month and year, industry), location, pictureUrl, and the flags openProfile and premium. One of the three also carried a summary. The run reported totalElements 5,576 for the company, in pages of 25.

The jobs

linkedin-job-search for "data engineer" in Berlin returned the job title, postedDate, descriptionText, a parsed location, employmentType, workplaceType, applyMethod with the company's own application URL, an applicants count, expireAt and a nested company record with employeeCount, specialities and locations.

The posts and comments

linkedin-profile-posts returned two company posts with content, postedAt, the linked article and an engagement object that splits reactions by type: for the Singapore office post, 3,128 likes, 190 praise, 93 empathy and four smaller types. get_post_comments returned a page of 10 comments for that post, each with the commenter's name, headline and profile URL, the text and any replies.

What you can build with it

  • An account research table. Loop the company call over your list and keep website, industry, headcount and the similar companies. Automating the company data pulls keeps the table current without anyone re-running it.
  • A prospect list. Filter the employees call by title, seniority, location or function, then contact the ones that match the account.
  • A hiring-signal feed. Run the job search on a schedule and flag companies that post the role you sell into.
  • A content monitor. Pull a company's posts each week and track which topics draw reactions and comments, using the fields described in what a LinkedIn post scraper returns.

What goes wrong when you pull LinkedIn data at scale?

Six things show up when you read the output of more than one call. All six are from the 2026-10-16 runs.

Why do two headcounts disagree for the same company?

Because each field answers a different question. company_size said "501-1,000 employees" while employees_in_linkedin said 6,244, and the people search reported 5,576 profiles for the same company on the same day. The band is what a company picked and rarely updates; the counts are measured. If you segment accounts by company_size you segment on a label, so use employees_in_linkedin and note which field a number came from.

Why is locations empty for a company with offices?

Because the field returned [] for Anthropic, a company with offices in several countries, and its own posts name a Singapore office. Read the locations from the people list or the job location instead, and treat an empty array as no data, not as no offices.

Why does a job search return titles you did not ask for?

Because LinkedIn's search matches loosely. We asked for "data engineer" in Berlin and two of the three results were an "Analytics Engineer", one of them at Octopus Energy, and a "Lead Analytics Engineer" with a remote workplace type. Filter the returned title against your own list before you count the results.

Why are the salary and view fields empty?

Because the posting did not carry them. In all three jobs salary was {text, min, max} with every value null, views was 0 and experienceLevel was null, while applicants was 25, 25 and 53. Do not build a salary report on this endpoint's output without checking how many rows have a value.

Why did the profile scraper return nothing?

On 2026-10-16 /dev_fusion/linkedin-profile-scraper returned an empty output array for two public profile URLs, williamhgates and satyanadella, and billed $0 for both (Verified 2026-10-16). An empty result is a normal response, not an error, so a loop must count rows, not calls. For enrichment of a known URL, run the people search instead or call the endpoint on a small batch first.

Why does the bill follow the result count, not the call count?

Because the people, job and post endpoints bill per result plus a small flat fee per run. The three employee profiles billed $0.039, the three jobs billed $0.004 and the two posts billed $0.00905 (Verified 2026-10-16). The job search runs once per title in jobTitles, so two titles at a limit of 100 can return 200 rows. Pass one title first and set maxItems on purpose. Comments are different (prices Verified 2026-10-16): each page of get_post_comments is one call at $0.05 (Verified 2026-10-16), and the Singapore post has 197 comments at 10 per page, so reading all of them is about 20 calls.

📖 See also LinkedIn job data: which API stays fresh, for how current the postings stay.

Which endpoint should I use for which job?

EndpointWhat it doesInputBillingPrice (Verified 2026-10-16)
tikhub/api/v1/linkedin/web_v2/get_company_profileOne company recordCompany URLPer call$0.008
apify/harvestapi/linkedin-company-employeesPeople at a company, with filtersCompany URLs, titles, locationsPer result plus flat fee$0.008
apify/dev_fusion/linkedin-profile-scraperEnrich known profile URLsProfile URLsPer result$0.01
apify/harvestapi/linkedin-job-searchJob postings by title and placeTitles, locationsPer result plus flat fee$0.001
apify/harvestapi/linkedin-profile-postsPosts from a profile or companyProfile or company URLPer result plus flat fee$0.0045
tikhub/api/v1/linkedin/web_v2/get_post_commentsComments on a postPost activity urnPer call$0.05

Prices Verified 2026-10-16 with monid inspect. The people search is the one to cap with maxItems, and the company profile is the one to loop over a list. Inspect any of them for free, then spend one small run before you commit a batch.

📖 See also Which LinkedIn scraper returns emails, for what each people endpoint returns.

When is another route a better fit?

You need one record a week. Open LinkedIn and read it. Any API is overhead at that volume.

You need data behind the login. Connection degree, InMail state and who viewed your profile live behind the sign-in, and a cookie-free endpoint reads public pages. LinkedIn's own partner programs are the route for those.

You need a contract on volume. A direct deal with a data vendor gets you an account manager and an agreed throughput. A marketplace is built for breadth and for switching an endpoint when one stops working.

You need verified emails at scale. The people search has a Full + email search ($12 per 1k) mode for that (Verified 2026-10-16). Run it on a small list before you buy a large one.

And the disclosure: we resell these endpoints. The most useful thing in this post is the habit of reading the fields before building on them, which costs nothing and is the right habit whoever you buy the data from.

Conclusion

The quickest way to use a LinkedIn scraper API is one call per company, person-list or job query through Monid: $0.008 for a company profile (Verified 2026-10-16), one key and one balance for every endpoint, about a minute to set up and ready inside your agent whenever you need it. Building your own scrapers works for one page type and costs hours of parsers and upkeep; Monid keeps the fetching and the parsing maintained.

Two things matter more than the endpoint you pick. Keep your own login out of it: a cookie-free endpoint reads public pages, so there is no account of yours to restrict. And read the fields before you build on them, because one company showed three different headcounts in one session and the profile scraper returned an empty array.

How we estimated the time saved: building, running and maintaining your own scraper is roughly 8 to 16 hours per job for the fetch layer, the parser and the first month of repairs, and there are three jobs here (company, people, jobs). That is 24 to 48 hours. The 1 minute is the install, key and first call once you already have a Monid key.

Free next step: run monid discover -q "linkedin company", then monid inspect on one endpoint, then make one small run on a company you know and compare the fields with the company page. Start at monid.ai.

FAQ

What is the best LinkedIn scraper API?

The one that fits the job: a company profile endpoint for account research, a people search for lists and a job search for hiring signals. Monid offers all three under one key, billed per call, so you can change endpoint without changing vendor.

Is there a free LinkedIn scraper?

Free scrapers exist as browser extensions and open source projects, and they work by hand or by login. Through Monid a company lookup is $0.008 (Verified 2026-10-16), with no monthly plan and no minimum, and discovery and inspection cost nothing.

How do I scrape LinkedIn without my account getting restricted?

Use an endpoint that reads public pages from its own infrastructure instead of a tool that takes your session cookie. A cookie tool acts as your account, so any limit it trips lands on yours. The endpoints in this guide never ask for a login.

Can I scrape LinkedIn jobs?

Yes, with /harvestapi/linkedin-job-search by title and location. It returned the title, posting date, description, location, workplace type, application URL and applicant count in our run. Salary came back empty on all three results.

Can an agent or n8n flow scrape LinkedIn?

Yes. An agent reads SKILL.md and calls the endpoints itself, and an n8n flow can call the same endpoints with the provider and endpoint as parameters, so switching one endpoint means changing two strings.

Published August 2026.

linkedin scraper apilinkedin scraperlinkedin scraping apilinkedin job scraperlinkedin company data