Get LinkedIn Job Details
View all LinkedIn Data API endpoints →Supply job_id from a job-search or company-jobs result. The documented sample has a data object with id, title, description, company, country_code, location, location_geocode, employment_status, level, listed_at, expire_at, job_url, workplace_types, work_remote_allowed and salary metadata. include_skills requests additional skill information and can increase request consumption. The salary object includes salary_exists and may not describe a usable pay range. This endpoint retrieves a listing; it does not submit an application.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/linkedin-scraper/get-job-detail API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/linkedin-scraper/get-job-detail?key=<API_KEY>&job_id=<job_id>'
Query Result
Use Cases
- Expand a saved search hit into a full job-research record.
- Prepare an applicant-controlled reading list with original job_url links.
- Enrich a sampled subset of vacancies for skill-demand analysis.
- Review workplace type and employment level before adding a role to a curated job feed.
Frequently asked questions
Where does job_id come from?
Use the id returned by search-jobs or get-company-jobs. An old example ID may no longer resolve, so obtain a current listing before requesting details.
Are salary and skills always included?
No. Check salary_exists and preserve missing values. Skills are optional through include_skills, which can increase request consumption; a detail request does not guarantee every field is available.