LinkedIn Job details API

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Open one LinkedIn job posting from its url or numeric job ID. Get the full description, the company with its size and website, location, workplace type and remote flag, employment type, industries, applicant and view counts, the apply link and the expiry date. Salary, seniority and benefits appear only when the posting lists them.

Price $1.19 per 1,000 requests ($0.001194 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.

AI prompt

Please help me write a data collection script with the EveryInfra LinkedIn Job details endpoint (linkedin/job_detail).

How the endpoint works:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to linkedin and action to job_detail, and put the parameters inside params.
- Required parameters:
  - url: A LinkedIn job link (linkedin.com/jobs/view/<ID>), a job-search link carrying currentJobId, or the 8 to 12 digit job ID itself. Post, company and profile links do not work.
- Returns one object. Main fields: id, url, title, text, company_name (Company name), company_url (Link to the company page), company_logo (Company logo), location, salary (Pay information), employment_type (Employment type (full-time, part-time,…), seniority (Seniority level), applicant_count (Number of people who have applied to th…); 24 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=linkedin.
- Example request body:
{
  "platform": "linkedin",
  "action": "job_detail",
  "params": {
    "url": "https://www.linkedin.com/jobs/view/4481880537/"
  }
}
- Price: $1.19 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

Name	In	Type	Required	Default	Description
`Authorization`	header	`string`	Yes	-	Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
`platform`	body	`string`	Yes	`linkedin`	Platform identifier, fixed value.
`action`	body	`string`	Yes	`job_detail`	Capability identifier, fixed value.
`url`	body.params	`string`	Yes	-	A LinkedIn job link (linkedin.com/jobs/view/<ID>), a job-search link carrying currentJobId, or the 8 to 12 digit job ID itself. Post, company and profile links do not work.

Code samples

bash

curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "linkedin",
  "action": "job_detail",
  "params": {
    "url": "https://www.linkedin.com/jobs/view/4481880537/"
  }
}'

OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

Field preview

No sample response is available for these parameters yet. This preview shows the response shape and fields from the API definition, with … as placeholders; it is not the result of a live call.

json

{
  "id": "req_…",
  "platform": "linkedin",
  "action": "job_detail",
  "results": {
    "id": …,
    "url": …,
    "title": …,
    "text": …,
    "company_name": …,
    "company_url": …,
    "company_logo": …,
    "location": …,
    "salary": …,
    "employment_type": …,
    "seniority": …,
    "applicant_count": …,
    "posted_at": …,
    "platform": …,
    "apply_url": …,
    "workplace_type": …,
    "is_remote": …,
    "industries": …,
    "benefits": …,
    "view_count": …,
    "job_state": …,
    "country_code": …,
    "expires_at": …,
    "company_employee_count": …,
    "company_website": …
  },
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

Field	Meaning
`id`	The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms.
`url`	Link to the record on the platform.
`title`	Title. null when the platform has no titles (for example text-only posts).
`text`	Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so).
`company_name`	Company name.
`company_url`	Link to the company page.
`company_logo`	Company logo.
`location`	Location description passed through as is; the format varies by platform.
`salary`	Pay information.
`employment_type`	Employment type (full-time, part-time, contract, internship).
`seniority`	Seniority level.
`applicant_count`	Number of people who have applied to the job.
`posted_at`	Publish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it.
`platform`	Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).
`apply_url`	Keeps the platform's own meaning
`workplace_type`	Keeps the platform's own meaning
`is_remote`	Keeps the platform's own meaning
`industries`	Keeps the platform's own meaning
`benefits`	Keeps the platform's own meaning
`view_count`	Views or plays. null means not disclosed, not 0.
`job_state`	Keeps the platform's own meaning
`country_code`	Keeps the platform's own meaning
`expires_at`	Keeps the platform's own meaning
`company_employee_count`	Keeps the platform's own meaning
`company_website`	Keeps the platform's own meaning

Errors and billing

401: Missing or invalid key.
402: Insufficient balance. Top up first.
422: Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
429: Per-minute request limit reached. Wait for Retry-After, then try again.
503: Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
200 empty: No data. No charge.

Errors