Try any of 1042 endpoints — live.
Pick an endpoint, load a working example, tweak the params, and send — no signup to try. Results render the way the data deserves; raw JSON, headers & code are one tab away.
Search public LinkedIn job postings by keywords, with optional location and date/seniority/job-type/workplace filters.
What job to search for — title, skill or keyword.
Country, region or city to search in (free text, e.g. 'United States', 'Berlin').
How many jobs to return (1–1000). LinkedIn's guest API caps any single query at ~1000; use filters to narrow. (1–1000)
Only jobs posted within this window (raw f_TPR codes like r86400 also accepted).
Only jobs at this experience level (raw f_E codes 1–6 also accepted).
Only jobs of this employment type (raw f_JT codes F/P/C/T/I/V/O also accepted).
Only jobs with this workplace arrangement (raw f_WT codes 1/2/3 also accepted).
Fetch the full posting per job (description, employment type, seniority, salary) — slower.
Also fetch the employer's company profile (industry, size, HQ) per job — slower.
Page number (easy paging: 1, 2, 3… — page size = max_results). (1–)
Next page: pass the previous response's meta.pagination.next_cursor (the 'Next' button does this automatically).
Advanced: raw result offset (10 jobs/page, must stay < 1000). Prefer `page` or `cursor`. (0–999)
Advanced: LinkedIn numeric geo ID — pins the search to an exact region (more precise than free-text location).
Advanced: the same facets as one object {date_posted, experience, job_type, workplace} — explicit keys here win over the flat params.
Advanced: parallel detail fetches when include_detail=true (1–8). (1–8)
curl -X POST https://api.reefapi.com/linkedin-jobs/v1/jobs/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"keywords":"python developer","location":"United States","max_results":"25"}'Hit Send to run this endpoint live.