Search Jobindex jobs
Job ads on Jobindex (Denmark) for keywords, with the site's filters: area, category, employment type, working hours, posting age and home workplace, sorted by relevance or date. Each result has the title, company with profile link, website, followers and rating, area, addresses with coordinates, posting date and application deadline, summary and apply link. facets lists the ids for areas, categories, employment types, hours and posting age. 20 per page; pass next_page back as page.
Every response includes credits_used: the credits this call cost.
Parameters
| name | type | description |
|---|---|---|
q | string | Keywords (title, skill or company). Example: python |
area | string | Area ids, comma separated (facets.areas; e.g. 15182 Greater Copenhagen). |
category | string | Category ids, comma separated (facets.categories; e.g. 1 IT development). |
employment_type | string | 1 permanent, 2 temporary, 3 student job, 4 apprentice, 5 graduate, 6 internship, 8 flex job, 9 volunteer, 10 youth job, 11 freelance, 12 hourly; comma separated. |
hours | string | 1 full time, 2 part time; comma separated. |
posted | 0 | 7 | 30 | Posting age in days. |
home_workplace | 1 | 1 = jobs with a home workplace. |
sort | relevance | date | Order. |
page | integer | Page number (from 1). |
Every endpoint also takes fresh, raw, fields (see lean responses and caching).
Example
curl "https://api.api.sh/jobindex/v1/search?q=python" \
-H "x-api-key: $APISH_KEY" import os, requests
res = requests.get(
"https://api.api.sh/jobindex/v1/search",
params={"q": "python"},
headers={"x-api-key": os.environ["APISH_KEY"]},
timeout=120,
)
res.raise_for_status()
data = res.json() const url = new URL("https://api.api.sh/jobindex/v1/search");
url.searchParams.set("q", "python");
const res = await fetch(url, { headers: { "x-api-key": process.env.APISH_KEY } });
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const data = await res.json(); Response
A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).