/seek/jobs

POST /api/seek/jobs

Price: 10 credits

Get a full SEEK job ad by id or job URL: title, abstract, full HTML and plain-text description, salary, classification and subclassification, work type, location, advertiser (id, name, verified status, registration date), status and expiry, phone number, listed and expiry dates, company branding logo and cover images, promotional video, key selling-point bullets, screening questions, and recruiter contacts.

How to use it

Fetch a single SEEK job ad by numeric id (e.g. 92619307) or job URL. Returns one item with title, abstract (short summary), description (plain text) and description_html, salary, classification and subclassification (with ids), work_type, location, advertiser (id, name, is_verified, registration_date), status, is_expired/is_verified/is_link_out, is_private_advertiser, has_role_requirements, phone_number, listed_at/expires_at, posted_time, share_url, image (company logo)/cover/thumbnail, video_url, bullets (key selling points), questions (application screening questions), and contacts (recruiter email/phone matched from the ad).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job string required — SEEK job id or a job page URL containing it (examples: "92619307", "https://www.seek.com.au/job/92619307"; minLength: 1)

Response

• @type string (default: "SeekJob")
• id string required
• url string required
• abstract string nullable
• description string nullable
• description_html string nullable
• salary string nullable
• classification string nullable
• classification_id string nullable
• subclassification string nullable
• subclassification_id string nullable
• work_type string nullable
• work_type_ids array (default: [])
• location string nullable
• location_ids array (default: [])
• advertiser object nullable
  • @type string (default: "SeekJobAdvertiser")
  • id string nullable
  • name string nullable
  • is_verified boolean nullable
  • registration_date string nullable
• status string nullable
• is_expired boolean nullable
• is_verified boolean nullable
• is_link_out boolean nullable
• is_private_advertiser boolean nullable
• has_role_requirements boolean nullable
• phone_number string nullable
• listed_at string nullable
• expires_at string nullable
• posted_time string nullable
• share_url string nullable
• image string nullable
• cover string nullable
• thumbnail string nullable
• video_url string nullable
• bullets array (default: [])
• questions array (default: [])
• contacts array (default: [])
  • @type string (default: "SeekJobContact")
  • type string nullable
  • value 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 — Job not found or no longer advertised (well-formed but nonexistent or expired job id) 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.