# LinkedIn Jobs Scraper API: Job Postings as JSON

> Search LinkedIn job postings by keyword and location, then fetch one posting’s full detail — over LinkedIn’s public guest surface, no login.

Search LinkedIn Jobs and Get LinkedIn Job Details cover LinkedIn job search end to end. Search LinkedIn Jobs takes a keyword and a location and returns matching postings with their title, company, location, posting date, a salary hint where LinkedIn publishes one, and the job id to pass into the detail call. Get LinkedIn Job Details takes that job id — or a job URL, or a urn:li:jobPosting URN — and returns the full posting: complete description, seniority level, employment type, job function, industries, applicant count and how long ago it was posted. Both read LinkedIn’s public GUEST job-search surface, the same pages a signed-out visitor can browse — no LinkedIn account or session cookie is required, and they route over datacenter exits rather than the residential pool the platform reserves for its authenticated Voyager scrapers. The exact rate is on this page’s FAQ, generated from the catalog. This pair is deliberately separate from the linkedin-* Voyager profile-lookup operations, which are a different, cookie-authenticated tier priced on their own — the two should not be confused, and this cluster is jobs only.

## Operations

- [Search LinkedIn Jobs](https://upapi.io/apis/social-media/linkedin-jobs-search) (6 units): Search LinkedIn job postings by keyword and location. Returns title, company, location, posting date, salary hint and the job id you pass to linkedin-jobs-detail. Reads LinkedIn's public guest surface — no LinkedIn account or cookie is required.
- [Get LinkedIn Job Details](https://upapi.io/apis/social-media/linkedin-jobs-detail) (6 units): Fetch one LinkedIn job posting: full description, seniority level, employment type, job function, industries, applicant count and posting age. Accepts the job id from linkedin-jobs-search, a job URL or a urn:li:jobPosting URN. Reads LinkedIn's public guest surface — no LinkedIn account or cookie is required.

## Frequently asked questions

### Do I need a LinkedIn account to search jobs?

No. Both operations read LinkedIn’s public guest job-search surface — the pages a signed-out visitor can already browse — and authenticate only with your upAPI key.

### What can I pass into Get LinkedIn Job Details?

The job id returned by Search LinkedIn Jobs, the full job posting URL, or a urn:li:jobPosting URN — whichever you already have on hand.

### How is this different from upAPI’s other LinkedIn operations?

This pair is jobs only, runs over datacenter exits, and needs no LinkedIn account. The separate linkedin-* profile-lookup operations are cookie-authenticated, run over the residential proxy pool, and carry their own per-call rate — a different surface, priced on its own.

### How much does this cost?

Every operation in this cluster costs 6 weighted units per call, drawn from your plan’s pooled monthly quota — see upapi.io/pricing for what a unit costs on each tier.

### How fresh is the data — is it cached?

Search LinkedIn Jobs is cached for 5 minutes; Get LinkedIn Job Details is cached for 1 hour. A repeat call inside a cached window returns the cached response and is billed nothing.

Last updated 2026-10-20.