SEEK job search

GET https://api.api.sh/seek/v1/search
1 credit / call jobs & b2b try it in the playground →

Jobs on SEEK (Australia or New Zealand) with the site's filters: location and distance, sort, listing date, work type, work arrangement, classification, salary range. total is SEEK's count. Each job: id, title, url, company, advertiser, location, locations, classification, sub_classification, classifications, work_types, work_arrangements, salary (as advertised), teaser, bullet_points, listed_at, listed_label, featured, logo and raw. Pass next_page back as page; null on the last page.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
q string Keywords. Example: python
location string Suburb, city, region or state, e.g. Sydney, Melbourne VIC 3000, Auckland. Example: Sydney
country au | nz Which SEEK site.
distance integer Radius around the location, in km.
sort relevance | date Order.
date_range 1 | 3 | 7 | 14 | 31 Listed within this many days.
work_type string Comma-separated: full_time, part_time, contract, casual.
work_arrangement string Comma-separated: on_site, hybrid, remote.
classification string Classification ids, comma-separated (e.g. 6281 Information & Communication Technology; ids appear in jobs[].classifications).
sub_classification string Sub-classification ids, comma-separated.
salary_min integer Minimum salary.
salary_max integer Maximum salary.
salary_type annual | monthly | hourly What the salary range means (default annual).
page integer Page number. Pass next_page from the previous response; null on the last page.
per_page integer Jobs per page (default 22, max 100).

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/seek/v1/search?q=python" \
  -H "x-api-key: $APISH_KEY"

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).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.