Search LinkedIn Jobs
View all LinkedIn Data API endpoints →Search with a required keyword and optional geocode, company ID, date_posted, remote, experience_level, job_type and other listing filters. The live first-page response contained 25 data records with id, title, url, listed_at, location, is_easy_apply, is_promote and a company object with id, name, url, verified and logo. The response also supplied page, total, has_more and metadata echoing the keyword and location filter. Iterate page numbers, deduplicate by job id and stop according to returned continuation signals; the reported total does not guarantee every listing is retrievable.
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/search-jobs API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/linkedin-scraper/search-jobs?key=<API_KEY>&keyword=software+engineer&page=1&geocode=103644278'
Query Result
Use Cases
- Build a user-selected remote-job alert from a keyword, location and posting window.
- Collect time-stamped vacancy samples for a labor-market research dataset.
- Export source-linked job summaries to CSV while deduplicating on listing ID.
- Compare newly observed roles across industries and seniority levels for workforce planning.
Frequently asked questions
Which location value should I send?
Use geocode, not a free-text city name. Resolve a city or country with search-location first. The observed job search used geocode=103644278 for the United States.
How should I fetch the next page?
Start with page=1 and request later page numbers while has_more permits. Deduplicate job IDs, check success for each response and use a bounded collection loop. total is a reported count, not a promise that all results can be fetched.