Seek Jobs Scraper | $0.90/1K — Australia & NZ, Salary + Bullets

For AU/NZ recruiters, job aggregators building Australian boards, and market researchers tracking ANZ hiring trends — Seek is the dominant source with 10,000+ NZ and hundreds of thousands of AU listings.

Pricing: $0.90/1,000 jobs — one flat per-result rate; salary, seniority, bullet points and optional descriptions are all included, with no add-on fees.

Zero auth. Zero proxy. No scraping — pure official Seek v5 API endpoint, verified live 2026-05-31 at HTTP 200 with no blocking.

Scrape job postings from Seek.com.au (Australia) and Seek.co.nz (New Zealand) via the public Seek v5 search API. No auth, no proxy, no scraping hacks — pure official-endpoint access.

Features

• Dual market: Australia (AU-Main) and New Zealand (NZ-Main) in one actor
• Rich schema: 23 fields including salary, work type, seniority (11 levels), remote type, classification, teaser, bullet points, and parse_confidence
• Multi-query batch: run multiple search queries in one actor run
• Optional descriptions: toggle full job description HTML + text (extra request per job)
• Smart filters: post-fetch keyword, location, remote-only filters
• parse_confidence: per-result quality score (0.0–1.0) — no competitor offers this

Output schema

Field	Description
job_id	Seek numeric job ID
title	Job title
company	Employer name
location	Full location label (e.g. "Sydney CBD, Sydney NSW")
area	Broader area (e.g. "All Sydney NSW")
country_code	AU or NZ
remote_type	remote / hybrid / onsite / null
seniority	intern / entry / mid / senior / lead / staff / principal / manager / director / vp / executive
salary	Salary label (e.g. "$100K – $120K per year")
work_type	Full time / Part time / Contract / Casual
listing_date	ISO 8601 date when posted
url	Job listing URL on seek.com
teaser	Short job description teaser
classification	Industry category (e.g. "Information & Communication Technology")
subclassification	Sub-category (e.g. "Engineering - Software")
is_featured	True if promoted/sponsored listing
bullet_points	Up to 3 key selling points from the listing
description_html	Full HTML description (when includeDescriptions=true)
description_text	Plain text description (when includeDescriptions=true)
global_id	Unique ID across all our actors: seek:<job_id>
parse_confidence	Data quality score 0.0–1.0
warnings	List of data quality warning codes
scraped_at	ISO 8601 run timestamp

Pricing

Pay Per Event — one flat rate per job delivered to your dataset.

Event	Rate / 1K	When charged
job-result	$0.90	Every job returned — salary, seniority, bullet points and (optional) descriptions all included

No proxy cost — this actor uses the Seek public JSON API directly.

Pricing example

Run	Jobs	Approx cost
Quick scan (200 jobs, no desc)	200	$0.18
Full run (1,000 + descriptions)	1,000	$0.90
Salary-focused (500 rows w/ salary)	500	$0.45

You are only charged for jobs actually delivered. Empty queries and blocked requests are not charged. Turning on includeDescriptions fetches an extra page per job (billed by Apify as platform compute, not as an extra per-result fee from us).

Usage

{
  "searchQueries": ["software engineer", "data scientist"],
  "siteKey": "AU-Main",
  "where": "Sydney NSW",
  "maxItems": 500,
  "includeDescriptions": false
}

Output sample

{
  "job_id": "80123456",
  "title": "Senior Software Engineer",
  "company": "Atlassian",
  "location": "Sydney CBD, Sydney NSW",
  "country_code": "AU",
  "remote_type": "hybrid",
  "seniority": "senior",
  "salary": "$140K - $180K per year",
  "work_type": "Full time",
  "listing_date": "2026-06-01T00:00:00+00:00",
  "classification": "Information & Communication Technology",
  "subclassification": "Engineering - Software",
  "is_featured": false,
  "bullet_points": ["Flexible work model", "Equity package", "5 weeks leave"],
  "parse_confidence": 1.0,
  "scraped_at": "2026-06-05T10:00:00+00:00"
}

FAQ

Do I need an API key or proxy? No. This actor uses Seek's official public v5 API — verified at HTTP 200 with no blocking. Zero credentials needed.

Australia or New Zealand? Set siteKey to AU-Main for Seek.com.au or NZ-Main for Seek.co.nz. Both in one actor.

Can I filter by industry? Yes — use classificationId (e.g. 6281 for ICT). Get category IDs from Seek's facet response or their public sitemap.

What if a query returns 0 results? The actor logs the query as empty and exits cleanly — no crash, no charge for empty pages.

Technical notes

• Endpoint: https://www.seek.com.au/api/jobsearch/v5/search — public, no auth required
• Verified live 2026-05-31: 10 rapid requests served with HTTP 200, no blocking
• Australia: 780+ results for "python developer"; New Zealand: 10,000+ total jobs
• Job descriptions sourced from data-automation="jobAdDetails" on individual job pages
• Not affiliated with Seek Limited. For commercial scraping at scale, review Seek's Terms of Service.

Use with AI agents (MCP)

This actor is available via Apify's MCP server. Connect it to any MCP-compatible agent (Claude, n8n, Make) to pull live AU/NZ job data on demand — no code required.

https://mcp.apify.com/?tools=bovi/seek-jobs-scraper

Vs. competitors

Feature	This actor	Generic AU job scrapers
Australia + New Zealand in one	Yes	Usually one country
Salary label (structured)	Yes	Rarely
Bullet points (selling points)	Yes (up to 3)	No
Featured/sponsored flag	Yes	No
Industry classification	Yes (2-level)	No
parse_confidence	Yes	No
Zero proxy / official API	Yes	Often HTML scrape
Price	$0.90/1K	$3–5/1K

Seek's v5 API reflects live listings. Schedule daily runs and compare job_id sets to detect new openings in your target classification automatically.

Integrations

Built for AU/NZ recruiters, job aggregators, and labor-market researchers tracking hiring trends across Australia and New Zealand — the JSON/dataset output drops into the tools you already run, no glue code:

• n8n / Make / Zapier — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: n8n, Make, Zapier.
• Webhooks — fire your own endpoint the moment a run finishes, to push results straight into your pipeline (docs).
• MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client so an AI agent can pull this data mid-conversation (guide).
• API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all Apify integrations.

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Greenhouse, Lever & Ashby Job Scraper
• Glassdoor Scraper
• Naukri Jobs Scraper
• Indeed Employer Intelligence
• Hiring Signal Monitor
• Ashby Job Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.