JOB LISTINGS · AUSTRALIA, NEW ZEALAND
SEEK Jobs | Australia & New Zealand Job Listings
Scrape SEEK Australia and New Zealand job listings by keyword and location: salary, work type, classification, posting date and link, with optional descriptions and SEEK filters.
About this data
Scrape SEEK Australia and New Zealand job listings by keyword and location: salary, work type, classification, posting date and link, with optional descriptions and SEEK filters.
From the actor’s Apify Store listing. The per-call endpoint may return a bounded subset; its own description is below.
Buy per call over x402
One endpoint at api.ssh.autos. Each call is one JSON POST, paid in USDC with no account or API key, and answered in the same HTTP response.
POST /v1/seek/jobs
Live job listings from SEEK (AU or NZ) for a keyword and optional location, with AU server filters (classification, work arrangement, salary, date range, sort): title, advertiser, location, salary label, work type, listing date and URL, up to 50 jobs per call.
Input
Send a JSON body to POST https://api.ssh.autos/v1/seek/jobs.
| Field | Type | Required | Notes |
|---|---|---|---|
keywords | string | required | Job title, skill or company. 2–120 characters |
location | string | optional | Suburb, city, state or region. up to 120 characters |
country | string | optional | one of AU, NZ; default "AU" |
classification | string | optional | AU only: SEEK classification filter. |
workarrangement | string | optional | AU only: work arrangement filter. |
salaryrange | string | optional | AU only: salary range filter. |
daterange | string | optional | AU only: listed within N days. |
sortmode | string | optional | AU only: sort mode. |
maxItems | integer | optional | 1–50; default 20 |
Returned fields
The answer is JSON: records, a list of up to 50, and summary, the run status and counts. Each record has these 14 fields; a field the source does not publish comes back null.
14 fields per record
| Field | Type | Notes |
|---|---|---|
company | string | — |
location | string | — |
salaryText | string | — |
salaryCurrency | string | — |
salaryPeriod | string | — |
employmentType | string | — |
postedDate | string | — |
descriptionExcerpt | string | — |
classification | string | — |
salaryMin | number | — |
salaryMax | number | — |
jobId | string | — |
url | string | — |
country | string | one of AU, NZ |
Example call
npx agentcash@latest fetch https://api.ssh.autos/v1/seek/jobs -m POST -b '{"keywords": "data engineer", "location": "Sydney NSW", "maxItems": 5}'The example values come from the API spec or the actor’s own sample input. Running it is a paid call.
What is and isn’t charged
You pay the call price for
- An answer, including a definitive “not found” or an empty result.
- No matches returns records: [] (charged).
Free
- Invalid input (422), busy (503), source failure (502), timeout (504) and calls whose client hung up are never charged.
- Invalid filters and source failures are not charged.
Prefer a subscription? Run it on Apify
This data source is a public actor on the Apify Store: SEEK Jobs Scraper | Australia & New Zealand Job Listings. Run it with your Apify account and plan for larger, scheduled or exported runs; it may offer more input options than the per-call endpoint.
How x402 payment works
- Your client sends the request. The API answers
402 Payment Requiredwith the price and where to pay. - The client pays from its own wallet: USDC on Base or Solana over x402, or over MPP on Tempo. No account, sign-up or API key.
- The client retries with the payment attached and gets the JSON answer in the same call. You are only charged for answers.
The AgentCash CLI in the example does all three steps for you and pays from your AgentCash wallet. Any x402 or MPP client works the same way.
Machine-readable: openapi.json · llms.txt