# SEEK Jobs Scraper (AU & NZ) (`xtracto/seek-jobs-scraper`) Actor

Scrape job listings from SEEK Australia and New Zealand: title, company, location, salary, work type, classification and the full ad body. No login, no browser.

- **URL**: https://apify.com/xtracto/seek-jobs-scraper.md
- **Developed by:** [Farhan Febrian Nauval](https://apify.com/xtracto) (community)
- **Categories:** Jobs
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.33 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## SEEK Jobs Scraper — Australia & New Zealand Listings with Full Ad Bodies

Scrape job listings from SEEK AU and NZ: title, company, location, salary label, work type,
classification, listing date — and optionally the complete ad body, expiry date, status and
advertiser contact. HTTP-only, no account, no browser.

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `searchQueries` | array | *required* | One search per entry, e.g. `registered nurse` |
| `country` | string | `AU` | `AU` (seek.com.au) or `NZ` (seek.co.nz) |
| `location` | string | — | Optional place filter, e.g. `Sydney`. Also the way past the result ceiling |
| `maxItemsPerQuery` | integer | `100` | Jobs per search |
| `includeDescription` | boolean | `false` | Fetch the full ad body; one extra request per job |

### Output

```jsonc
{
  "_input": "python developer",
  "_source": "S1-jobsearch-api+S2-redux-island",
  "_scrapedAt": "2026-09-09T10:58:11Z",

  "jobId": "94305187",
  "url": "https://www.seek.com.au/job/94305187",
  "title": "Python Developer",
  "teaser": "If you are a Python Developer looking for a change…",
  "bulletPoints": ["…", "…"],

  "companyName": "Just Digital People",
  "advertiserId": "29028300", "advertiserName": "Just Digital People",
  "employerId": "6368", "employerName": "…", "employerUrl": "https://au.seek.com/companies/…",

  "location": "Brisbane QLD",
  "locations": ["Brisbane QLD"],
  "countryCode": "AU",

  "salaryLabel": "$87,790 - $112,607 per annum (pro rata)",
  "workTypes": ["Full time"],
  "workArrangements": ["On-site"],
  "classifications": [
    { "classification": "Information & Communication Technology",
      "subClassification": "Developers/Programmers" }
  ],

  "listingDate": "2026-08-31T04:33:55Z",
  "listingDateDisplay": "9d ago",
  "isFeatured": false,
  "logoUrl": "…",

  // only with includeDescription:
  "abstract": "Join the … team, delivering vital virtual care around Australia",
  "description": "At Amplar Health, we're transforming how healthcare is delivered…",
  "descriptionHtml": "<p>…</p>",
  "status": "Active", "isExpired": false, "isVerified": true, "isLinkOut": true,
  "expiresAt": "2026-10-09T03:44:11.000Z",
  "listedAtUtc": "2026-09-09T03:45:24.586Z",
  "shareLink": "https://au.seek.com/job/94514328?tracking=…",
  "contactMatches": [{ "type": "Phone", "value": "(03) 8622 5666" }]
}
```

### Three things worth knowing

**`totalCount` is not how many jobs you can get.** A bare search reports 163,544 matches, but SEEK
stops serving results after roughly **500 per search** — `pageSize=20` dies after page 27,
`pageSize=100` after page 5. The ceiling is on the result set, not the page size, so asking for
bigger pages does not help. The actor logs a warning when a query matches more than it can reach;
the fix is to narrow the search — add a `location`, or split one broad query into several specific
ones.

**The API names fields in the plural, and the singular forms are always null.** `locations`,
`workTypes` and `classifications` carry the data; `location`, `workType` and `classification` exist
on the object and are permanently empty. This actor reads the plural ones and also emits a
convenience `location` string holding the first label.

**The ad body comes from GraphQL, not the job page.** The page carries it in a
`window.SEEK_REDUX_DATA` island, and that was the first implementation — but the HTML page sits
behind an anti-bot layer that the API host does not: from Apify it answered `403` on every TLS
profile through datacenter proxies, and roughly one request in six through residential, while
`/api/…` and `/graphql` on the *same host* answered 200 throughout. The actor uses
`POST /graphql`, which needs no proxy upgrade and moves ~7 KB instead of a 240 KB page. (The page
also has no `JobPosting` JSON-LD — its only structured-data node is `WebSite`.)

### Errors

| `_error` | Meaning |
|---|---|
| `invalid_input` | Empty search query |
| `no_results` | The search ran and SEEK returned nothing |
| `blocked` | Every TLS profile was refused by the server |
| `network_error` | The ladder never reached the server — DNS, timeout, reset |
| `unexpected_shape` | 200 with a structure this actor was not written against |

A job whose *body* could not be fetched still produces its full search-level row, with
`_detailError` naming the cause — `detail_not_found` (GraphQL has no job for that id, so the
listing was removed or expired), `network_error`, `detail_blocked`, or
`detail_unexpected_shape`. Dropping a real job because one extra request
failed would be the worse outcome. The ad-body fetch repeats the whole TLS ladder once before
giving up, since a page that fails on a truncated body usually succeeds seconds later.

If every query fails, the run itself fails rather than reporting success over an empty dataset.

# Actor input Schema

## `searchQueries` (type: `array`):

One search per entry, e.g. "registered nurse" or "python developer".

## `country` (type: `string`):

Which SEEK storefront to search.

## `location` (type: `string`):

Optional place filter, e.g. "Sydney" or "Melbourne VIC". Also the practical way past the result ceiling described below.

## `maxItemsPerQuery` (type: `integer`):

SEEK stops serving results after roughly 500 per search regardless of how many matched, so values far above that will not be reached.

## `includeDescription` (type: `boolean`):

Fetch each job's full description, expiry date, status and advertiser contact over SEEK's GraphQL endpoint. Costs one extra request per job. Datacenter proxies are fine for it.

## `proxyConfiguration` (type: `object`):

Datacenter proxies are sufficient for SEEK.

## Actor input object example

```json
{
  "searchQueries": [
    "python developer",
    "registered nurse"
  ],
  "country": "AU",
  "maxItemsPerQuery": 100,
  "includeDescription": false,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `overview` (type: `string`):

Dataset items shown in the 'Jobs' view.

## `items` (type: `string`):

Every record this run produced, with all fields, as JSON.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searchQueries": [
        "python developer",
        "registered nurse"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("xtracto/seek-jobs-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "searchQueries": [
        "python developer",
        "registered nurse",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("xtracto/seek-jobs-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searchQueries": [
    "python developer",
    "registered nurse"
  ]
}' |
apify call xtracto/seek-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,xtracto/seek-jobs-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Odl23demJwnUhI2mC/builds/wGVt5ozzcyBBLNzXr/openapi.json