/seek/jobs/search

POST /api/seek/jobs/search

Price: 5 credits

Search SEEK job ads by keyword and location with filters (classification, subclassification, work type, work arrangement, salary range, listing date, sort order). Returns job cards with id, title, teaser, salary, company, classifications, work types and arrangements, locations, key bullet points, featured flag, listing date, and company logo.

How to use it

Search SEEK (Australia/New Zealand job board) for job ads. Filter by keyword, where (location text), classification (top-level industry) and subclassification, work_type (full/part time, contract, casual), work_arrangement (on-site/hybrid/remote), salary_min+salary_max+salary_type, date_range (last N days), and sort_mode. Each result has id, url, title, teaser, salary, company_name, advertiser_id/employer_id, role_id, classifications (industry + subclassification), work_types, work_arrangements, locations (label + area/region), bullet_points, is_featured, listing_date, and image (company logo).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string — Search keyword (default: ""; examples: "software engineer")
• where string — Location text, resolved to a region server-side (default: ""; examples: "All Sydney NSW")
• count integer required — Max result count (examples: 20; min: 1)
• site_key string — Market: AU-Main (Australia) or NZ-Main (New Zealand) (default: "AU-Main"; one of: "AU-Main", "NZ-Main")
• classification string nullable — Top-level job classification (one of: "1200", "6251", "6304", "1203", "1204", "7019", "6163", "1206", "6076", "6263", "6123", "1209", "6205", "1210", "1211", "1212", "6317", "6281", "1214", "1216", "6092", "6008", "6058", "1220", "6043", "6362", "1223", "7020", "6246", "1225")
• subclassification integer nullable — Job subclassification id (child of a classification) (examples: 6302)
• work_type string nullable — Work type (one of: "242", "243", "244", "245")
• work_arrangement string nullable — Work arrangement (on-site, hybrid, remote) (one of: "1", "2", "3")
• salary_min integer nullable — Minimum salary; requires salary_max and salary_type (min: 0)
• salary_max integer nullable — Maximum salary; requires salary_min and salary_type (min: 0)
• salary_type string nullable — Salary basis for salary_min/salary_max (annual or hourly) (one of: "AnnualPackage", "HourlyRate")
• date_range string nullable — Listed within the last N days (one of: "1", "3", "7", "14", "31")
• sort_mode string — Result ordering (relevance or listed date) (default: "KeywordRelevance"; one of: "KeywordRelevance", "ListedDate")

Response

• @type string (default: "SeekJobCard")
• id string required
• url string required
• teaser string nullable
• salary string nullable
• company_name string nullable
• advertiser_id string nullable
• employer_id string nullable
• role_id string nullable
• classifications array (default: [])
  • @type string (default: "SeekSearchClassification")
  • classification string nullable
  • classification_id string nullable
  • subclassification string nullable
  • subclassification_id string nullable
• work_types array (default: [])
• work_arrangements array (default: [])
• locations array (default: [])
  • @type string (default: "SeekSearchLocation")
  • label string nullable
  • country_code string nullable
  • area string nullable
  • region string nullable
• bullet_points array (default: [])
• is_featured boolean nullable
• listing_date string nullable
• listing_date_display string nullable
• image string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.