What is the LinkedIn Jobs API?

LinkedIn Jobs API retrieves public job data from one or more accepted /jobs/view/{slug} URLs. It returns the role, employer, description, location, seniority, employment type, industries, application fields, available salary, and timestamps.

Can I submit a LinkedIn job search page?

No. Each input must be a full http or https LinkedIn URL for one /jobs/view/{slug} detail page; search and collection routes do not pass validation.

Can it find open roles I have not supplied?

No. This product resolves only the public job-detail URLs supplied in urls and does not perform a LinkedIn job search.

What application information is included?

A job record can include an external apply_link and an is_easy_apply signal when the public listing exposes them. The endpoint returns application information but does not submit applications.

Why can salary or application fields be empty?

The public listing may not publish a salary, external application link, or Easy Apply signal, so those optional fields can be null or empty.

How are returned job records billed?

Returned job records are billed at 0.8 SocQ credits each. No result charge is applied when the task produces an empty result set.

LinkedIn Jobs API: Public Job Data

LinkedIn Jobs

A public LinkedIn job listing describes a specific opening through its role, employer, description, location, seniority, employment type, industry, application route, and any published compensation. These details support vacancy tracking, role comparison, recruiting research, and structured job catalogues.

Features

Job detail URL inputProcess one or more public LinkedIn /jobs/view/{slug} pages while rejecting search results and job collection URLs.
Role and employer in one recordReturn the job title, full description, listing URL, and normalized public hiring-company identity together.
Structured employment attributesExpose location, seniority level, employment type, and industries as separate fields instead of leaving them inside the description.
Application and compensation fieldsReturn apply_link, the Easy Apply signal, salary, publication time, and collection time as separate listing fields.

Parameters

Parameters	Required	Description
`urls`	Required	Required list of public LinkedIn job detail URLs. Every URL must use the /jobs/view/{slug} path on linkedin.com or a LinkedIn subdomain.

How to Use

Send known job-detail links, wait for the hiring records to be prepared, and retrieve every available result page.

Filter the input list to public /jobs/view/{slug} detail links.
POST those links in urls to /v1/linkedin/jobs and save task_id.
Query /v1/tasks/{task_id} until the job task reaches a terminal status.
On success, process data.results.items and use next_cursor for any page flagged by has_more.

curl -X POST "https://api.socq.ai/v1/linkedin/jobs" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://www.linkedin.com/jobs/view/software-engineer-at-microsoft-4429527118"]}'

# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is true

Best Use Cases

Vacancy tracking: Use role, employer, location, publication time, and source URL to maintain a structured list of known openings.
Role and requirement comparison: Compare descriptions, seniority, employment type, industry, location, and available salary across selected listings.
Recruiting market research: Group selected openings by employer, location, industry, or employment type to study visible hiring patterns.
Application route management: Use apply_link and the Easy Apply signal to route each saved listing to its available application path.

Pro Tips

Extract and deduplicate the job identifier from /jobs/view/ links so alternate URL forms do not create repeated listings.
Treat salary as optional source data because many listings omit it and exposed values may not share one format.
Validate apply_link before presenting it as an outbound action in a downstream interface.
Keep created_at and collected_at separate so publication time is not confused with the time the listing was retrieved.

Use these APIs when you need a different type of public LinkedIn data.

LinkedIn Profiles API — Normalize public profile identity, roles, location, visible audience counts, experience, education, and skills from profile URLs.
LinkedIn Companies API — Normalize public company descriptions, websites, logos, visible audience and employee counts, industries, locations, and specialties.
LinkedIn Posts API — Collect public post text, authors, visible engagement, media, publication time, type, and hashtags from supported URLs.

Combine LinkedIn data with public data from other supported social platforms.