---
title: "Does LinkedIn have a jobs API? What the official APIs offer - JobsPipe"
description: "No. LinkedIn's job APIs let approved partners post jobs and sync applications, not read listings. Who gets access, what people use instead, and India data."
canonical: https://jobspipe.dev/guides/linkedin-jobs-api
date_published: 2026-05-26
date_modified: 2026-09-30
author: Dvir Atias
---

# Does LinkedIn have a jobs API?

By [Dvir Atias](https://jobspipe.dev/about) · Updated Sep 30, 2026

No. LinkedIn has no API that lets you search or read its job listings. The job-related APIs LinkedIn documents, which are the Job Posting API, Apply Connect, Apply with LinkedIn and Recruiter System Connect, are partner integrations: they let an applicant tracking system send jobs to LinkedIn and receive applications back, under an agreement signed with LinkedIn. Teams that need LinkedIn postings as data use a third-party jobs API or a scraping tool instead.

## Does LinkedIn have a jobs API you can read job listings from?

No. The question usually comes from one of two people. The first has a product that needs job listings: a job board, a sourcing tool, a sales team that watches who is hiring, a labour-market dashboard. They want to send a title, a company or a location and get LinkedIn’s postings back as JSON. The second has jobs of their own and wants them to appear on LinkedIn without a recruiter typing each one into the website.

LinkedIn built APIs for the second person and none for the first. Its developer [product catalog](https://developer.linkedin.com/product-catalog) lists the Talent products as Apply Connect, Apply with LinkedIn, Job Posting, Recruiter System Connect and Talent Hub, and describes Job Posting as the way to “post jobs on LinkedIn with ATS or job distribution tool”. The [Talent Solutions documentation](https://learn.microsoft.com/en-us/linkedin/talent/) describes the same set. Every one of them moves data between LinkedIn and the system an employer already uses to hire. None of them is a search over LinkedIn’s job listings.

So the honest short answer has two halves. If you want to publish jobs to LinkedIn, an official API exists, and it is open to approved partners only. If you want to read jobs from LinkedIn, no official API exists at any price, and the rest of this guide explains what LinkedIn does offer, who can use it, and what teams use when they need the listings as data.

## What do LinkedIn’s official APIs actually offer?

The table lists each API that comes up when people search for a LinkedIn jobs API, with what it does and who can use it. Each name links to LinkedIn’s own documentation, which LinkedIn publishes on Microsoft Learn.

| LinkedIn API | What it does | Returns job listings? | Who can use it |
| --- | --- | --- | --- |
| Job Posting API | Posts, updates and closes jobs on LinkedIn on behalf of an employer | No. Jobs go in | Approved Talent Solutions partners under a signed API agreement; not accepting new partnerships |
| Job Posting Status API | Returns the current status of jobs your own customers posted | Only the jobs you posted | Approved Talent Solutions partners under a signed API agreement |
| XML job feeds | Lets LinkedIn ingest an employer's or an applicant tracking system's jobs from a feed file | No. Jobs go in | Employers and applicant tracking systems that publish a feed in LinkedIn's format |
| Apply Connect | Posts jobs from an applicant tracking system and returns the applications made on LinkedIn | No. Your jobs go in, their applications come back | Approved Talent Solutions partners under a signed API agreement, then a certification |
| Apply with LinkedIn | Fills an application form on a career site from the candidate's profile | No | Existing partners only; not accepting new partners |
| Recruiter System Connect | Syncs candidate information between an applicant tracking system and LinkedIn Recruiter | No | Approved Talent Solutions partners under a signed API agreement |
| Sign in with LinkedIn and Share on LinkedIn | Signs a member in and posts to the feed on their behalf | No | Open to every developer, self-service |
| Marketing APIs | Runs advertising campaigns and manages company pages | No | Approval through the developer portal |

**The Job Posting API** is the one most often mistaken for a jobs API. LinkedIn’s [overview](https://learn.microsoft.com/en-us/linkedin/talent/job-postings/api/overview) says it “enables authorized third parties such as clients, ATS systems, and job distributors to post jobs directly to LinkedIn on behalf of customers”. A partner sends a job with a title, a description, a location and an apply link, and later updates, renews or closes it. The [job sync reference](https://learn.microsoft.com/en-us/linkedin/talent/job-postings/api/sync-job-postings) covers two kinds of job: basic jobs, and promoted jobs that go into the paid job slots of a LinkedIn Recruiter customer. Data flows into LinkedIn. Nothing in the reference returns jobs that other companies posted.

**The Job Posting Status API** is the only read in the job stack, and it is narrow. LinkedIn’s [status documentation](https://learn.microsoft.com/en-us/linkedin/talent/job-postings/api/check-job-posting-status) explains why it exists: after a job is posted, its state on LinkedIn can change, for example when members report it and it is closed, and partners had no way to see that. The status API lets a partner “retrieve up-to-date statuses of their customer posted jobs”. It answers one question, which is what happened to the jobs you sent.

**XML feeds** are the older route to the same place. The [XML feed guide](https://learn.microsoft.com/en-us/linkedin/talent/job-postings/xml-feeds-development-guide) describes a file, with a job ID, a title, a description, a location and an apply URL for each job, that LinkedIn ingests. It is again a way in, not a way out.

**Apply Connect** is where LinkedIn now points new integrations. The [Apply Connect overview](https://learn.microsoft.com/en-us/linkedin/talent/apply-connect/apply-connect-overview) describes it as an integration between an applicant tracking system and LinkedIn that lets members apply without leaving LinkedIn: the partner posts jobs on behalf of its customers and receives the applications directly in its own system. **Apply with LinkedIn** fills in an application form on an employer’s career site from the candidate’s profile, and **Recruiter System Connect** “synchronizes customers’ candidate information between your ATS and LinkedIn Recruiter”, in the words of [its overview](https://learn.microsoft.com/en-us/linkedin/talent/recruiter-system-connect). These are about applicants and candidates, not listings.

The remaining APIs are unrelated to jobs but share the name. Sign in with LinkedIn and Share on LinkedIn are the permissions every developer can switch on. The [Marketing API Program](https://learn.microsoft.com/en-us/linkedin/marketing/) covers advertising campaigns, reporting, lead forms and company pages, and its [Community Management API](https://learn.microsoft.com/en-us/linkedin/marketing/community-management/community-management-overview) manages company pages, posts, comments and page analytics. A company’s feed post that says “we are hiring” is a post, not a job listing, and these APIs do not reach LinkedIn Jobs.

## Can you read LinkedIn job listings through any official API?

No. There is no documented endpoint that takes a job title, a company or a place and returns LinkedIn’s listings, and there is no partner tier that adds one. The catalog of Talent products is the full list, and each product in it is built for an employer’s own hiring data.

The terms point the same way. The [LinkedIn API Terms of Use](https://www.linkedin.com/legal/l/api-terms-of-use) say “You may not store any Content, except in the specific circumstances outlined”, and they bar an application from accessing, storing or displaying LinkedIn content obtained by “scraping, crawling, spidering or using any other technology or software to access LinkedIn content outside the APIs”. An approved partner therefore cannot add scraped listings to an official integration either. The official APIs are designed for a company and its own jobs, applicants and campaigns, and the terms keep them that way.

This matters when you read other pages on the subject. A page that promises an “official LinkedIn job search API” is describing either the posting APIs above or a third-party product. Knowing which saves a partner application that was never going to return listings.

## Who can get access to LinkedIn’s job APIs, and how?

LinkedIn’s [Getting Access page](https://learn.microsoft.com/en-us/linkedin/shared/authentication/getting-access) sorts every permission into two groups. Open permissions are “the only permissions that are available to all developers without special approval”, and there are three of them: `profile` and `email` from Sign in with LinkedIn using OpenID Connect, and `w_member_social` from Share on LinkedIn. You add them yourself from the Products tab of your app in the developer portal. Everything else needs explicit approval from LinkedIn.

For jobs, the same page sends developers to the [Talent Solutions partner application](https://business.linkedin.com/hire/ats-partners/partner-application) and names four programmes: Recruiter System Connect, Apply Connect, Apply with LinkedIn and Premium Job Posting. The Job Posting API overview states the condition plainly: use is “restricted to those developers approved by LinkedIn”, who “need to meet certain criteria and sign an API agreement with data restrictions”. In practice the partners are applicant tracking systems and job distributors that post on behalf of many employers.

Two of the programmes are closed to newcomers as this guide is written:

-   The Job Posting API overview opens with a notice: “We are currently not accepting new partnerships for LinkedIn’s Job Posting API”, and tells anyone who wants job-posting access to request Apply Connect instead.
-   The [Apply with LinkedIn page](https://learn.microsoft.com/en-us/linkedin/talent/apply-with-linkedin/apply-with-linkedin) says LinkedIn is “currently not accepting any new partners” for it while a new version is developed.

For a partner that is accepted, the documentation describes the path:

-   Create the API applications, one for production and one for development and testing, and ask your LinkedIn business development contact for the partner onboarding form.
-   Build against a test organisation that LinkedIn sets up, where test jobs are closed frequently.
-   Create a child application for each customer, so that every employer you post for has its own key under your parent application.
-   Have each customer accept the LinkedIn Jobs Terms and Conditions before any job is posted, and keep a record of who accepted and when. The overview also bars partners from marketing the integration as a “free way to post jobs to LinkedIn”.
-   For Apply Connect, pass the [certification](https://learn.microsoft.com/en-us/linkedin/talent/apply-connect/apply-connect-certification): you demonstrate LinkedIn’s test cases to your business development contact, and “upon successful certification, LinkedIn provisions your production API key”.

Authentication is OAuth 2.0 throughout. LinkedIn’s [authentication overview](https://learn.microsoft.com/en-us/linkedin/shared/authentication/authentication) describes two flows: member authorization, the 3-legged flow in which a member grants your app access to their own account, and application authorization, the 2-legged flow for calls that are not made on behalf of one member. The open permissions use the first. The job status calls use the second, through client credentials.

On limits, LinkedIn’s [rate limiting page](https://learn.microsoft.com/en-us/linkedin/shared/api-guide/concepts/rate-limits) says calls are limited per application and per member over a 24-hour period that resets at midnight UTC, that a limited request receives a 429 response, and that “standard rate limits are not published in documentation”: you look up the limit for each endpoint in your app’s Analytics tab. The pages linked here state no price and no approval timeline for the Talent programmes. What each LinkedIn surface costs in practice is worked through in the [LinkedIn API cost guide](https://jobspipe.dev/guides/linkedin-api-cost), and the endpoint, the request body and the batch limits of the posting API are in [posting jobs to LinkedIn via API](https://jobspipe.dev/blog/linkedin-api-post-job).

## What do people use instead of an official LinkedIn jobs API?

Since LinkedIn sells no read access, a market of third-party products fills the gap. They fall into two groups. Scraping tools fetch LinkedIn’s job pages on request and hand back what they parsed, priced per result or per request. Jobs APIs hold postings from many sources in one schema and let you filter by source. The table puts the common choices side by side. Prices and free allowances are each vendor’s published figures, with the month they were checked.

| API | What the data is | Price entry point | Free tier or trial | LinkedIn coverage | Checked |
| --- | --- | --- | --- | --- | --- |
| JobsPipe · Pricing ↗ | Aggregated postings | $49/month for 25,000 jobs | 1,000 jobs to start | LinkedIn postings as one of 30+ sources, selected with a source filter | September 2026 |
| Apify · Pricing ↗ | Scraper platform | LinkedIn Jobs Scraper $1 per 1,000 results | $5 a month of free usage | A community-maintained LinkedIn jobs scraper you run and pay for per result | September 2026 |
| Bright Data · Pricing ↗ | Scraper platform | Web Scraper API $1.50 per 1,000 records, 5,000 free a month | Free tier on several APIs | A ready-made LinkedIn job scraper inside its Web Scraper API | September 2026 |
| Scrapingdog · Pricing ↗ | Scraper platform | $40/mo for 200,000 credits | 100 free credits | LinkedIn Jobs request = 5 credits | September 2026 |
| Fantastic.jobs · Pricing ↗ | Aggregated postings | $95/mo for 20,000 jobs, up to $900/mo for 500,000 | 7-day free trial | LinkedIn, Wellfound and Y Combinator jobs in its Job Board API | September 2026 |

The scraping tools differ mostly in who does the running. On Apify you start a community-maintained scraper and pay for what it returns: the LinkedIn Jobs Scraper by curious\_coder charges $1 per 1,000 results on paid plans and $2 on the free plan. Bright Data packages the same job as a managed product: the Web Scraper API, which includes ready-made LinkedIn and Indeed job scrapers, costs $1.50 per 1,000 records pay as you go, with 5,000 free records a month. Scrapingdog sells credits, and a LinkedIn Jobs request costs 5 credits. In each case you ask for a search and receive that search’s results, so covering a market means deciding which searches to run and how often to repeat them. A longer comparison of these tools is in [LinkedIn scrapers compared](https://jobspipe.dev/guides/best-linkedin-scrapers).

A jobs API works the other way round. The postings are already stored, so you filter them instead of fetching them: Fantastic.jobs describes its corpus as jobs from 200,000+ career sites, plus over 10 million jobs a month from LinkedIn, Wellfound and Y Combinator, and JobsPipe serves LinkedIn postings as one of 30+ sources. The practical differences are that one request can cover every matching posting rather than one search page, that the same job posted on LinkedIn and on the employer’s own career site comes back once, and that a posting keeps its first-seen date and its open or closed status after it leaves the search results.

Whichever you pick, ask the same questions of it. How old is the newest posting it returns for a query you care about? Does it tell you when a job closed? Does it return the full description or a truncated card? What happens to your bill when you re-check the same jobs every day? A one-week test with your real queries answers these better than any feature list, including this one.

## How do you get LinkedIn job postings from the JobsPipe API?

JobsPipe is a jobs API: one endpoint, `POST /v1/jobs/search`, over postings from 30+ sources in one record shape. You can see that shape before you sign up, because the sandbox needs no key:

Try it without a key

```
curl -d '{"limit":3}' https://api.jobspipe.dev/v1/sandbox/jobs/search
```

Only `/v1/sandbox/*` needs no key.

With a free key, add `source_or` to keep only postings whose source is LinkedIn, and the usual filters to narrow them. This asks for account executive roles in the United States posted in the last week:

```
curl https://api.jobspipe.dev/v1/jobs/search \
  -H "Authorization: Bearer jp_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "source_or": ["linkedin"],
    "job_title_or": ["account executive"],
    "job_country_code_or": ["US"],
    "posted_at_max_age_days": 7,
    "limit": 25
  }'
```

Each result carries `job_title`, `company`, `url` pointing at the original posting, `date_posted`, `last_seen_at`, `status` and a `sources` list that names every source the posting was seen on. Leave `source_or` out and the same query runs across every source, which is usually what a product wants: most questions asked as “LinkedIn jobs” are questions about who is hiring. The free plan includes 1,000 jobs to start. The fields and a sample response for LinkedIn postings are on the [LinkedIn jobs API page](https://jobspipe.dev/linkedin-jobs-api).

## Is it legal to collect LinkedIn job data yourself?

LinkedIn’s contracts say no. The [User Agreement](https://www.linkedin.com/legal/user-agreement) has members agree not to “develop, support or use software, devices, scripts, robots or any other means or processes” to “scrape or copy the Services”. LinkedIn’s [Crawling Terms and Conditions](https://www.linkedin.com/legal/crawling-terms) add that automated crawling “without the express permission of LinkedIn is strictly prohibited”. A contract binds the people who accepted it, and breaking it can lead to blocked access or a civil claim.

US courts have dealt with a separate question: whether scraping pages that anyone can view is a federal computer crime. In [hiQ Labs v. LinkedIn](https://cdn.ca9.uscourts.gov/datastore/opinions/2022/04/18/17-16783.pdf), the Ninth Circuit on April 18, 2022 affirmed, after the Supreme Court had sent the case back, a preliminary injunction that stopped LinkedIn from blocking hiQ’s access to public member profiles. The court found that hiQ had raised serious questions about whether the Computer Fraud and Abuse Act applies to data that is open to the public.

That ruling is narrower than it is often described. It was a decision on a preliminary injunction, about one US statute and about member profiles rather than job postings. It did not decide whether scraping breaches the User Agreement, and it says nothing about privacy, copyright or database law in other countries. This section is general information, not legal advice. If your product depends on the answer, ask a lawyer who knows your jurisdiction and your use.

## What does LinkedIn job data look like for India?

Many of the people asking this question are building for India, so here are figures for India alone. LinkedIn’s official APIs are the same in every country: the partner programmes above are the only ones, and none of them reads listings in India either. What differs is the postings themselves.

Among JobsPipe’s active postings located in India on September 30, 2026, 51.0% carried LinkedIn as their source and 46.1% carried Indeed. Every other source together made up 2.9%. That mix describes the sources JobsPipe includes, not the Indian market as a whole: Indian job boards that are not among those sources, such as Naukri, do not appear in it. The [Naukri API page](https://jobspipe.dev/sources/naukri) covers that board.

| India postings | All sources | LinkedIn source |
| --- | --- | --- |
| Postings that state a salary | 0.4% | 0.5% |
| Postings flagged remote | 5.2% | 4.8% |
| Postings with a seniority label | 53.8% | 79.6% |

Three things follow for anyone building on India postings:

-   **Do not rely on a salary filter.** Only 0.4% of India postings state a salary, and 0.5% of those whose source is LinkedIn. A filter on pay removes almost everything, so rank by title, seniority and recency instead.
-   **Seniority is the usable structured field.** 79.6% of India postings from LinkedIn carry a seniority label, against 53.8% across all sources.
-   **Remote is a small slice.** 5.2% of India postings are flagged remote, and 4.8% of those from LinkedIn, so a remote-only product in India is working with a narrow set.

To read India postings from one source, combine the country and source filters:

```
{
  "source_or": ["linkedin"],
  "job_country_code_or": ["IN"],
  "job_title_or": ["data analyst"],
  "limit": 25
}
```

The shares are a view of what postings say, measured on one day, not a survey of the Indian labour market. Country-level remote figures for twenty countries are on the [remote jobs API page](https://jobspipe.dev/remote-jobs-api).

## Which option fits what you are building?

**You want your own jobs on LinkedIn.** Check whether your applicant tracking system is already a LinkedIn partner. If it is, publishing is a setting, not a project. If you are the applicant tracking system, the route is the partner application and Apply Connect.

**You are building a job board, an aggregator or job alerts.** You need listings from many employers, kept current, with closed jobs marked. That is a jobs API. Test two or three with the searches your users will run.

**You want hiring signals for sales or research.** You care about which companies are hiring for which roles, not about one website. A multi-source jobs API gives you the company, the role and the dates in one schema; the source is a detail.

**You need a one-off sample for analysis.** A scraping tool priced per result is the smallest commitment. Read the legal section above first, and keep the sample small.

## Methodology: how this page was checked

JobsPipe wrote this guide, and JobsPipe sells a jobs API that appears in the comparison table. Every statement about LinkedIn’s APIs, access rules and terms was read from LinkedIn’s own pages on September 30, 2026, and each is linked where it is made and listed under Sources. Vendor prices and free allowances come from each vendor’s published page, stored with the wording and the date checked. The India figures are shares of JobsPipe’s active postings with country India on September 30, 2026, one row per posting, rounded to one decimal; they describe those postings, not the whole market. LinkedIn changes its programmes without notice, so check the linked pages before you plan around any of this.

## Sources

-   [LinkedIn Job Posting API overview (Microsoft Learn)](https://learn.microsoft.com/en-us/linkedin/talent/job-postings/api/overview)
-   [LinkedIn: sync basic or promoted jobs (Microsoft Learn)](https://learn.microsoft.com/en-us/linkedin/talent/job-postings/api/sync-job-postings)
-   [LinkedIn: check job posting statuses (Microsoft Learn)](https://learn.microsoft.com/en-us/linkedin/talent/job-postings/api/check-job-posting-status)
-   [LinkedIn XML feeds development guide (Microsoft Learn)](https://learn.microsoft.com/en-us/linkedin/talent/job-postings/xml-feeds-development-guide)
-   [LinkedIn Apply Connect overview (Microsoft Learn)](https://learn.microsoft.com/en-us/linkedin/talent/apply-connect/apply-connect-overview)
-   [LinkedIn Apply Connect certification (Microsoft Learn)](https://learn.microsoft.com/en-us/linkedin/talent/apply-connect/apply-connect-certification)
-   [Apply with LinkedIn development (Microsoft Learn)](https://learn.microsoft.com/en-us/linkedin/talent/apply-with-linkedin/apply-with-linkedin)
-   [LinkedIn Recruiter System Connect overview (Microsoft Learn)](https://learn.microsoft.com/en-us/linkedin/talent/recruiter-system-connect)
-   [LinkedIn Talent Solutions API overview (Microsoft Learn)](https://learn.microsoft.com/en-us/linkedin/talent/)
-   [Getting access to LinkedIn APIs (Microsoft Learn)](https://learn.microsoft.com/en-us/linkedin/shared/authentication/getting-access)
-   [LinkedIn API authentication overview (Microsoft Learn)](https://learn.microsoft.com/en-us/linkedin/shared/authentication/authentication)
-   [LinkedIn API rate limiting (Microsoft Learn)](https://learn.microsoft.com/en-us/linkedin/shared/api-guide/concepts/rate-limits)
-   [LinkedIn Marketing API Program (Microsoft Learn)](https://learn.microsoft.com/en-us/linkedin/marketing/)
-   [LinkedIn Community Management API overview (Microsoft Learn)](https://learn.microsoft.com/en-us/linkedin/marketing/community-management/community-management-overview)
-   [LinkedIn developer product catalog](https://developer.linkedin.com/product-catalog)
-   [LinkedIn Talent Solutions partner application](https://business.linkedin.com/hire/ats-partners/partner-application)
-   [LinkedIn API Terms of Use](https://www.linkedin.com/legal/l/api-terms-of-use)
-   [LinkedIn User Agreement](https://www.linkedin.com/legal/user-agreement)
-   [LinkedIn Crawling Terms and Conditions](https://www.linkedin.com/legal/crawling-terms)
-   [hiQ Labs v. LinkedIn, Ninth Circuit opinion of April 18, 2022](https://cdn.ca9.uscourts.gov/datastore/opinions/2022/04/18/17-16783.pdf)
-   [Apify LinkedIn Jobs Scraper actor](https://apify.com/curious_coder/linkedin-jobs-scraper)
-   [Bright Data Web Scraper API pricing](https://brightdata.com/pricing/web-scraper)
-   [Scrapingdog pricing](https://www.scrapingdog.com/pricing/)
-   [Fantastic.jobs API page](https://fantastic.jobs/api)

## FAQ

Does LinkedIn have a jobs API?+

Not one that reads job listings. LinkedIn documents several job-related APIs under LinkedIn Talent Solutions: the Job Posting API, Apply Connect, Apply with LinkedIn and Recruiter System Connect. All of them connect an applicant tracking system to LinkedIn so that jobs and applications can move between the two, and all of them require LinkedIn's approval and a signed agreement. None returns LinkedIn's job listings for a search.

Is there a free LinkedIn jobs API?+

LinkedIn offers no free API for reading jobs, because it offers no API for reading jobs at all. The permissions LinkedIn opens to every developer cover signing a member in and posting to the feed. Third-party options have free allowances: Apify includes a free plan with $5 a month to spend on Actors, and JobsPipe's free plan includes 1,000 free credits, one time.

How do I get a LinkedIn API key for jobs?+

You apply to become a LinkedIn Talent Solutions partner. LinkedIn's documentation says the job APIs are restricted to developers it has approved, who must meet its criteria and sign an API agreement with data restrictions. The Job Posting API is not accepting new partnerships, and LinkedIn directs applicants to Apply Connect. A self-service developer app gives you sign-in and sharing permissions only.

Can I post jobs to LinkedIn through an API?+

Yes, if you are an approved partner, usually an applicant tracking system or a job distributor posting on behalf of employers. Employers normally reach LinkedIn through the applicant tracking system they already use rather than by integrating directly. The posting guide on this site walks through the endpoint, the authentication and the limits.

Can I search LinkedIn jobs by title, company or location with the official API?+

No. The only job-related read in LinkedIn's documentation is the Job Posting Status API, and it returns the status of jobs that your own customers posted through your integration. There is no documented endpoint that takes a job title, a company or a location and returns LinkedIn's listings.

Is it legal to scrape LinkedIn jobs?+

LinkedIn's User Agreement prohibits scraping its services, and its API Terms of Use prohibit partners from using content obtained that way. In hiQ Labs v. LinkedIn, a US appeals court in 2022 left in place an order that stopped LinkedIn from blocking access to public profiles while the case continued. That ruling concerned one US statute and did not settle the contract question. This is not legal advice; ask a lawyer about your own case.

Is there a LinkedIn jobs API for India?+

LinkedIn's official APIs are the same in every country, so the answer does not change for India. For reading postings located in India through JobsPipe, filter on the country code IN. On September 30, 2026, 51.0% of JobsPipe's active India postings carried LinkedIn as their source and 0.4% stated a salary.

Related

[Product

LinkedIn jobs through the JobsPipe API: the fields and a sample response.

](https://jobspipe.dev/linkedin-jobs-api)[Guide

LinkedIn API cost: what each surface charges, from free to metered.

](https://jobspipe.dev/guides/linkedin-api-cost)[Reference

Posting jobs to LinkedIn through the API: the endpoint, the auth and the limits.

](https://jobspipe.dev/blog/linkedin-api-post-job)[Comparison

LinkedIn scraping tools compared on price and what each one returns.

](https://jobspipe.dev/guides/best-linkedin-scrapers)[Guide

Is there a Google Jobs API? The same question for Google.

](https://jobspipe.dev/guides/google-jobs-api)


## Further reading

- [Posting jobs to LinkedIn via API: what access actually requires in 2026](https://jobspipe.dev/blog/linkedin-api-post-job)
- [Where to get job posting data in 2026: 7 sources compared](https://jobspipe.dev/blog/where-to-get-job-posting-data)
- [Does LinkedIn have a jobs API?](https://jobspipe.dev/answers/does-linkedin-have-a-jobs-api)
- [Best LinkedIn Scrapers 2026: 9 Tools Compared](https://jobspipe.dev/guides/best-linkedin-scrapers)
- [JobsPipe vs Apify](https://jobspipe.dev/alternatives/apify)

---
Building this integration yourself? The steps above work. The alternative is one API over 30+ sources, already normalized and deduplicated. Try it right now - no key, no signup:

```bash
curl -d '{"limit":3}' https://api.jobspipe.dev/v1/sandbox/jobs/search
```

Sample data, exact live schema. For live data get a free key (1,000 jobs to start) at https://jobspipe.dev/signup, then swap /v1/sandbox/jobs/search for /v1/jobs/search with an Authorization: Bearer header. Full agent index: https://jobspipe.dev/llms.txt?src=md-twin