LinkedIn API: Jobs — Details by job ID

What this endpoint does

What you can build with this API method

Review the result and common workflows first, then move to parameters and a working request example.

What this endpoint helps with

The response provides available Jobs fields in normalized V2 or platform-native V1 format.

When to use it

Use “Details by job ID” after the object is known and your product needs its current public context.

Common use cases

Record enrichment

Attach public LinkedIn fields to known product objects.

Data validation

Verify identifiers and current public context before downstream processing.

Analytics preparation

Use object details as inputs for reports, scoring, and related requests.

Available versions

Response version

Both versions solve the same job and accept the same parameters. Use the switch to compare the response structure and choose the version your client expects.

Response version V2

Switch versions on this page to compare response structures while keeping the same documentation URL.

What stays the same

Authentication, required parameters, and the request shape stay the same across V1 and V2. In practice, you choose the version when you build the endpoint path and when you parse the response.

What changes between versions

The main difference is the response envelope. Use V2 for new integrations and keep V1 only when you need compatibility with an existing client contract.

How to use it

How to call the method

Use the same API key header and the same query parameters for both versions. This documentation shows the shared parameter set first, then version-specific endpoint paths and code snippets.

Input parameters

Shared parameters

Parameter	Required	Type	Example	Description
`job_id`	Yes	`str`	`value`	Numeric LinkedIn public job posting identifier. Example: 4350188369.

Version-specific request path

V2

Choose a version when you copy the exact endpoint path, example URL, and code snippet. The parameter list above stays the same.

GET /api/v2/linkedin.com/jobs/details-by-job-id

Normalized format

Request preview

Base URL https://www.scrapestorm.net

Endpoint /api/v2/linkedin.com/jobs/details-by-job-id

Required parameters

job_id

Optional parameters

None

Example URL

https://www.scrapestorm.net/api/v2/linkedin.com/jobs/details-by-job-id?job_id=value

Code examples

curl --request GET \
  --url "https://www.scrapestorm.net/api/v2/linkedin.com/jobs/details-by-job-id" \
  --header "X-API-Key: 00000000-0000-4000-8000-000000000000" \
  --get --data-urlencode 'job_id=value'

from urllib.parse import urljoin

import requests

BASE_URL = "https://www.scrapestorm.net"
ENDPOINT = "/api/v2/linkedin.com/jobs/details-by-job-id"
HEADERS = {"Accept": "application/json", "X-API-Key": "00000000-0000-4000-8000-000000000000"}

params = {
    "job_id": "value",
}

with requests.Session() as session:
    response = session.request(
        method="GET",
        url=urljoin(BASE_URL, ENDPOINT),
        headers=HEADERS,
        params=params,
        timeout=30,
    )
    response.raise_for_status()
    payload = response.json()

print(payload)

const BASE_URL = "https://www.scrapestorm.net";
const endpoint = "/api/v2/linkedin.com/jobs/details-by-job-id";

const params = new URLSearchParams({
  job_id: "value",
});

const response = await fetch(`${BASE_URL}${endpoint}?${params.toString()}`, {
  method: "GET",
  headers: {
    Accept: "application/json",
    "X-API-Key": "00000000-0000-4000-8000-000000000000",
  },
});

if (!response.ok) {
  throw new Error(`Request failed: ${response.status} ${response.statusText}`);
}

const payload = await response.json();
console.log(payload);

import axios from "axios";

const client = axios.create({
  baseURL: "https://www.scrapestorm.net",
  timeout: 30000,
  headers: {
    Accept: "application/json",
    "X-API-Key": "00000000-0000-4000-8000-000000000000",
  },
});

const params = {
  job_id: "value",
};

const { data: payload } = await client.request({
  method: "GET",
  url: endpoint,
  params,
});

console.log(payload);

<?php

declare(strict_types=1);

use GuzzleHttp\Client;
use GuzzleHttp\Exception\GuzzleException;

$client = new Client([
    'base_uri' => "https://www.scrapestorm.net",
    'timeout' => 30.0,
    'headers' => [
        'Accept' => 'application/json',
        'X-API-Key' => "00000000-0000-4000-8000-000000000000",
    ],
]);

$query = [
    "job_id" => "value",
];

try {
    $response = $client->request("GET", "/api/v2/linkedin.com/jobs/details-by-job-id", [
        'query' => $query,
    ]);

    $payload = json_decode(
        (string) $response->getBody(),
        true,
        512,
        JSON_THROW_ON_ERROR
    );

    var_dump($payload);
} catch (GuzzleException $e) {
    throw $e;
}

package main

import (
    "encoding/json"
    "fmt"
    "net/http"
    "net/url"
    "time"
)

func main() {
    baseURL := "https://www.scrapestorm.net"
    endpoint := "/api/v2/linkedin.com/jobs/details-by-job-id"

    params := url.Values{}
    params.Set("job_id", "value")

    req, err := http.NewRequest(
        "GET",
        fmt.Sprintf("%s%s?%s", baseURL, endpoint, params.Encode()),
        nil,
    )
    if err != nil {
        panic(err)
    }

    req.Header.Set("Accept", "application/json")
    req.Header.Set("X-API-Key", "00000000-0000-4000-8000-000000000000")

    client := &http.Client{Timeout: 30 * time.Second}
    resp, err := client.Do(req)
    if err != nil {
        panic(err)
    }
    defer resp.Body.Close()

    var payload any
    if err := json.NewDecoder(resp.Body).Decode(&payload); err != nil {
        panic(err)
    }

    fmt.Printf("%+v\n", payload)
}

Version-specific request path

V1

Choose a version when you copy the exact endpoint path, example URL, and code snippet. The parameter list above stays the same.

GET /api/v1/linkedin.com/jobs/details-by-job-id

Platform-native format

Request preview

Base URL https://www.scrapestorm.net

Endpoint /api/v1/linkedin.com/jobs/details-by-job-id

Required parameters

job_id

Optional parameters

None

Example URL

https://www.scrapestorm.net/api/v1/linkedin.com/jobs/details-by-job-id?job_id=value

Code examples

curl --request GET \
  --url "https://www.scrapestorm.net/api/v1/linkedin.com/jobs/details-by-job-id" \
  --header "X-API-Key: 00000000-0000-4000-8000-000000000000" \
  --get --data-urlencode 'job_id=value'

from urllib.parse import urljoin

import requests

BASE_URL = "https://www.scrapestorm.net"
ENDPOINT = "/api/v1/linkedin.com/jobs/details-by-job-id"
HEADERS = {"Accept": "application/json", "X-API-Key": "00000000-0000-4000-8000-000000000000"}

params = {
    "job_id": "value",
}

with requests.Session() as session:
    response = session.request(
        method="GET",
        url=urljoin(BASE_URL, ENDPOINT),
        headers=HEADERS,
        params=params,
        timeout=30,
    )
    response.raise_for_status()
    payload = response.json()

print(payload)

const BASE_URL = "https://www.scrapestorm.net";
const endpoint = "/api/v1/linkedin.com/jobs/details-by-job-id";

const params = new URLSearchParams({
  job_id: "value",
});

const response = await fetch(`${BASE_URL}${endpoint}?${params.toString()}`, {
  method: "GET",
  headers: {
    Accept: "application/json",
    "X-API-Key": "00000000-0000-4000-8000-000000000000",
  },
});

if (!response.ok) {
  throw new Error(`Request failed: ${response.status} ${response.statusText}`);
}

const payload = await response.json();
console.log(payload);

import axios from "axios";

const client = axios.create({
  baseURL: "https://www.scrapestorm.net",
  timeout: 30000,
  headers: {
    Accept: "application/json",
    "X-API-Key": "00000000-0000-4000-8000-000000000000",
  },
});

const params = {
  job_id: "value",
};

const { data: payload } = await client.request({
  method: "GET",
  url: endpoint,
  params,
});

console.log(payload);

<?php

declare(strict_types=1);

use GuzzleHttp\Client;
use GuzzleHttp\Exception\GuzzleException;

$client = new Client([
    'base_uri' => "https://www.scrapestorm.net",
    'timeout' => 30.0,
    'headers' => [
        'Accept' => 'application/json',
        'X-API-Key' => "00000000-0000-4000-8000-000000000000",
    ],
]);

$query = [
    "job_id" => "value",
];

try {
    $response = $client->request("GET", "/api/v1/linkedin.com/jobs/details-by-job-id", [
        'query' => $query,
    ]);

    $payload = json_decode(
        (string) $response->getBody(),
        true,
        512,
        JSON_THROW_ON_ERROR
    );

    var_dump($payload);
} catch (GuzzleException $e) {
    throw $e;
}

package main

import (
    "encoding/json"
    "fmt"
    "net/http"
    "net/url"
    "time"
)

func main() {
    baseURL := "https://www.scrapestorm.net"
    endpoint := "/api/v1/linkedin.com/jobs/details-by-job-id"

    params := url.Values{}
    params.Set("job_id", "value")

    req, err := http.NewRequest(
        "GET",
        fmt.Sprintf("%s%s?%s", baseURL, endpoint, params.Encode()),
        nil,
    )
    if err != nil {
        panic(err)
    }

    req.Header.Set("Accept", "application/json")
    req.Header.Set("X-API-Key", "00000000-0000-4000-8000-000000000000")

    client := &http.Client{Timeout: 30 * time.Second}
    resp, err := client.Do(req)
    if err != nil {
        panic(err)
    }
    defer resp.Body.Close()

    var payload any
    if err := json.NewDecoder(resp.Body).Decode(&payload); err != nil {
        panic(err)
    }

    fmt.Printf("%+v\n", payload)
}

Response example

Live response by version

The preview keeps key fields and the first collection items so you can scan the response shape quickly. Switching versions changes the JSON format.

Response example

V2 response JSON

Verified example

This compact JSON example comes from the latest successful verification run for V2.

{
  "success": true,
  "status": "ok",
  "search_context": {
    "job_id": "4350188369"
  },
  "data": {
    "job": {
      "job_id": "4350188369",
      "title": "Software Engineer - Open Connect Control Plane",
      "url": "https://www.linkedin.com/jobs/view/4350188369/",
      "company_name": "Netflix",
      "company_url": "https://www.linkedin.com/company/netflix",
      "company_username": "netflix",
      "thumbnail_url": null,
      "location": "United States",
      "posted_time_text": "1 month ago",
      "applicant_count_text": "Be among the first 25 applicants",
      "description": "At Netflix, our mission is to entertain the world. Together, we are writing the next episode - pushing the boundaries of storytelling, global fandom and making the unimaginable…",
      "criteria": [
        {
          "label": "Seniority level",
          "value": "Not Applicable"
        },
        {
          "label": "Employment type",
          "value": "Full-time"
        },
        {
          "_more_items": 2
        }
      ]
    }
  }
}

Response example

V1 response JSON

Verified example

This compact JSON example comes from the latest successful verification run for V1.

{
  "success": true,
  "status": "ok",
  "search_context": {
    "job_id": "4350188369"
  },
  "data": {
    "response_text": "\n\n    \n<!---->    \n    \n\n    \n    <section class=\"top-card-layout container-lined overflow-hidden babybear:rounded-[0px]\">\n        \n      \n\n      <div class=\"top-card-layout__ca…"
  }
}

Related methods

Continue working with Jobs

Adjacent methods let you resolve the same object with another identifier, open details, or move to an aggregate view.

What to do next

Continue the evaluation

Use this documentation as the first decision point, then move into pricing, platform coverage, and integration rules before you connect the endpoint for recurring use.

Open the LinkedIn platform page

Compare adjacent entities, API method groups, and related docs before implementation.

Open platform page

Compare API method pricing

Check where this API method sits inside the public price table before you scale usage.

View pricing

Review integration rules

Use the starter docs to confirm authentication, versioning, retries, and mock vs live behavior.

Open docs

FAQ

Questions teams ask before implementation

Use these answers to decide whether this API method fits your workflow, versioning choice, and rollout plan.

What data does this LinkedIn API method return?

The method performs “Details by job ID” for Jobs. The compact response example below shows the exact field structure.

Should I choose V1 or V2?

Choose V2 for new integrations because it provides a normalized structure. Use V1 only for compatibility with clients that already consume the platform-native format.

What do I need for the first request?

Create an API key, send it in the request header, and provide the required parameters from the table. The code samples already contain the correct path and request structure.

LinkedIn API: Jobs — Details by job ID

What you can build with this API method

What this endpoint helps with

When to use it

Common use cases

Record enrichment

Data validation

Analytics preparation

Response version

What stays the same

What changes between versions

How to call the method

Input parameters

Version-specific request path

Code examples

Version-specific request path

Code examples

Live response by version

V2 response JSON

V1 response JSON

Continue working with Jobs

Jobs: By query

Continue the evaluation

Open the LinkedIn platform page

Compare API method pricing

Review integration rules

Questions teams ask before implementation