Seek Jobs Real-Time Data

The fastest way to collect Seek job postings on Apify. Turn any job search into clean, structured JSON — ready for spreadsheets, dashboards, automations, and AI workflows. Results land in your dataset in real time, as each job is found.

Built for recruiters, talent teams, job boards, market researchers, and builders who need reliable hiring data across Australia, New Zealand, and Asia-Pacific markets — without slow setups or messy exports.

---

Why this Actor

	Seek Jobs Real-Time Data	Typical job data tool
Speed	Fast per-job collection	Often 5–15 s per job
Memory	256–512 MB default	2–4 GB+
Setup	Run in seconds	Often complex configuration
Cost	Low compute, efficient runs	High
Output	Structured JSON, LLM-ready	Often messy or incomplete
Scale	Up to 1,000 jobs per keyword	Often capped lower
Filters	Full Seek Jobs filters	Often keyword-only
Modes	Search · Company jobs · Job links	Usually one mode only
Markets	AU, NZ, UK, SG, HK, ID, TH, MY, PH	Often single region

---

Three ways to collect jobs

Mode	What it does	Best for
Job search	Keyword + location search with full Seek filters	Market scans, role tracking, location-based hiring
Company jobs	All open roles from specific employers	Competitor monitoring, account-based recruiting
Job links	Structured data from individual Seek job URLs	Enriching a list you already have

Enable one or combine all three in a single run.

---

What you get — every job, fully structured

Each record is one job posting with featureType, jobKey, and scrapedAt so you can sort, filter, and join with your own data.

Field	What it tells you
title, company, location, workplaceType	Role, employer, place, on-site/remote/hybrid
jobUrl, applyUrl, companyUrl, companyLogo	Direct links and company branding
descriptionText, descriptionHtml	Full job description (when detail fetch is on)
classification, subClassification	How Seek categorises the role
salary, bulletPoints, jobTypes	Compensation signals, highlights, and employment type
listedAtISO, postedTimeAgo	How fresh the listing is
searchQuery, searchLocation, searchCompany, position	Which search produced this row and its rank
isFeatured, isSponsored	Listing prominence signals
advertiserId, employerId, roleId	Stable identifiers for joins and deduplication

Set includeRaw: true if you need extended record data for custom processing.

featureType values: job (search) · company_job (company jobs) · scrape_by_url (job links)

---

Search like Seek Jobs — get data like a database

Use the same filters job seekers use on Seek:

• Keywords — one search per keyword (e.g. software engineer, registered nurse)
• Title — narrow to a specific role name
• Company — jobs at Atlassian, Canva, or any employer
• Location — Sydney NSW 2000, Melbourne VIC, Auckland, and more
• Employment type — full-time, part-time, contract, casual
• Workplace — on-site, remote, hybrid
• Date posted — any time, past month, week, 3 days, or 24 hours
• Sort — relevance or most recent
• Volume — up to 1,000 jobs per keyword
• Full details — toggle rich descriptions and enriched fields on or off

Supported markets (country)

Code	Market
au	Australia (seek.com.au)
nz	New Zealand (seek.co.nz)
uk	United Kingdom (seek.co.uk)
sg	Singapore
hk	Hong Kong
id	Indonesia
th	Thailand
my	Malaysia (JobStreet)
ph	Philippines (JobStreet)

---

Use cases — real outcomes

• Recruiting pipelines — build candidate-ready job lists by role, location, and seniority
• Job boards and aggregators — feed your product with fresh Seek listings daily
• Market and salary research — track who is hiring, where, and for what skills across APAC
• Competitive intelligence — monitor competitor hiring by company and function
• Sales and BD — spot companies in hiring mode for timely outreach
• Staffing agencies — track demand by region, role, and employer
• AI assistants and agents — summarize listings, score fit, draft outreach, or answer hiring questions
• Data warehouses and CRMs — push JSON into Snowflake, BigQuery, HubSpot, Airtable, or your stack via API

---

LLM and MCP integration

Output is structured JSON — ideal for ChatGPT, Claude, Gemini, LangChain, LlamaIndex, CrewAI, and custom agents. No cleanup step. No manual formatting. Just records your model can read.

Recommended workflow

1. Run the Actor with your keywords, companies, or job links.
2. Pull dataset items via Apify API, webhook, or export JSON/CSV.
3. Pass records to your LLM, vector store, or automation — one job per row.

Example: one job record for an LLM prompt

{
  "featureType": "job",
  "jobKey": "93190629",
  "title": "Software Engineer",
  "company": "Atlassian",
  "location": "Sydney NSW",
  "workplaceType": "Hybrid",
  "jobTypes": ["Full time"],
  "descriptionText": "Join our engineering team building scalable products for millions of users...",
  "salary": "$120,000 – $150,000 per year",
  "classification": "Information & Communication Technology",
  "subClassification": "Engineering - Software",
  "bulletPoints": ["Flexible working", "Career growth", "Global team"],
  "listedAtISO": "2026-07-08T03:50:44.091Z",
  "postedTimeAgo": "2d ago",
  "jobUrl": "https://www.seek.com.au/job/93190629",
  "searchQuery": "software engineer",
  "searchLocation": "Sydney NSW 2000",
  "position": 1,
  "scrapedAt": "2026-07-11T12:00:00.000Z"
}

Apify MCP (Model Context Protocol)

Connect the Apify MCP server so AI assistants can:

• Run this Actor from natural-language instructions
• Read job results directly in the chat
• Chain with other Actors — enrich contacts, send alerts, update spreadsheets

Example MCP conversation:

User: "Find 50 software engineer jobs in Sydney posted this week and summarize top employers"

→ MCP runs Seek Jobs Real-Time Data with jobKeywords, jobLocation=Sydney NSW 2000, jobDatePosted=week
→ MCP reads dataset items
→ LLM summarizes hiring trends and top companies

API quick start

curl -X POST "https://api.apify.com/v2/acts/YOUR_ACTOR_ID/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "enableJobSearch": true,
    "jobKeywords": ["software engineer"],
    "jobLocation": "Sydney NSW 2000",
    "jobDatePosted": "week",
    "jobsPerQuery": 50,
    "fetchJobDetails": true,
    "country": "au"
  }'

Fetch results: GET https://api.apify.com/v2/datasets/{datasetId}/items?format=json

Dataset views in Apify Console: Overview (core fields) and Full details (includes descriptions)

Export as JSON, CSV, Excel, RSS, or via API.

---

Input reference

Job search

Input	Type	Default	Description
enableJobSearch	boolean	true	Turn keyword search on or off
jobKeywords	string[]	["software engineer"]	Search keywords — one run per keyword
jobTitle	string	—	Title filter
jobCompany	string	—	Company filter
jobLocation	string	"Sydney NSW 2000"	Location
jobTypes	enum[]	all	fulltime, parttime, contract, casual
jobRemote	enum[]	all	onsite, remote, hybrid
jobDatePosted	enum	any	any, month, week, 3days, day
jobSort	enum	relevance	relevance or date
jobsPerQuery	integer	25	Max jobs per keyword (1–1000)

Company jobs

Input	Type	Default	Description
enableCompanyJobs	boolean	false	Collect jobs from company profiles
companyNames	string[]	[]	Company names (e.g. Atlassian, Canva)
jobsPerCompany	integer	25	Max jobs per company (1–1000)

Job links

Input	Type	Default	Description
enableScrapeByUrl	boolean	false	Collect data from individual job links
jobUrls	string[]	[]	Seek job page URLs

Output and global

Input	Type	Default	Description
fetchJobDetails	boolean	true	Full description and enriched fields
includeRaw	boolean	false	Attach extended record data
webhookUrl	string	—	Optional URL for real-time record delivery (Zapier, Slack, CRM)
webhookFormat	enum	json	json (full record) or slack (message)
country	string	au	Target market (au, nz, uk, sg, hk, id, th, my, ph)
maxItems	integer	10000	Max total records across all modes
proxyConfiguration	object	residential AU	Connection settings (target-market residential recommended)

Full schema: Input tab on Apify Console or .actor/input_schema.json in this repository.

---

Output reference

Each dataset row is one job record. Filter by featureType:

featureType	Description
job	Job from keyword search
company_job	Job from company jobs mode
scrape_by_url	Job from job links mode

Traceability fields on search results:

• searchQuery — keyword that produced this row
• searchLocation — location used in the search
• position — rank in results for that query

Export formats: JSON, CSV, Excel, RSS, or via API.

---

Webhook delivery (optional)

Every record is always saved to the Apify dataset first. If you set webhookUrl in the Output section, each new record is also POSTed in real time to your endpoint — useful for CRMs, Slack, Zapier, Make, or custom pipelines.

Setting	Description
webhookUrl	Your endpoint (https). Leave empty to use dataset only.
webhookFormat	json — full job object. slack — compact Slack incoming-webhook message.

Webhook delivery is best-effort: a failed webhook never stops the run or prevents dataset writes.

Example — search with Slack alerts

{
  "enableJobSearch": true,
  "jobKeywords": ["data analyst"],
  "jobLocation": "Melbourne VIC",
  "jobsPerQuery": 50,
  "webhookUrl": "https://hooks.slack.com/services/YOUR/WEBHOOK/URL",
  "webhookFormat": "slack"
}

Example — search with JSON webhook to your CRM

{
  "enableJobSearch": true,
  "jobKeywords": ["product manager"],
  "jobLocation": "Sydney NSW 2000",
  "fetchJobDetails": true,
  "webhookUrl": "https://your-crm.example.com/api/jobs",
  "webhookFormat": "json"
}

---

Quick start examples

Software roles in Sydney — full details

{
  "enableJobSearch": true,
  "jobKeywords": ["software engineer"],
  "jobLocation": "Sydney NSW 2000",
  "jobDatePosted": "week",
  "jobSort": "date",
  "jobsPerQuery": 50,
  "fetchJobDetails": true,
  "country": "au"
}

Jobs at a specific company

{
  "enableJobSearch": true,
  "jobKeywords": ["engineer"],
  "jobCompany": "Atlassian",
  "jobLocation": "Sydney NSW 2000",
  "jobsPerQuery": 100
}

All jobs from employer profiles

{
  "enableCompanyJobs": true,
  "companyNames": ["Atlassian", "Canva", "Xero"],
  "jobsPerCompany": 50,
  "fetchJobDetails": true,
  "country": "au"
}

Import specific job links

{
  "enableScrapeByUrl": true,
  "jobUrls": [
    "https://www.seek.com.au/job/93190629"
  ],
  "fetchJobDetails": true
}

Fresh listings only — fast summary mode

{
  "enableJobSearch": true,
  "jobKeywords": ["nurse"],
  "jobLocation": "Brisbane QLD",
  "jobDatePosted": "day",
  "jobSort": "date",
  "jobsPerQuery": 75,
  "fetchJobDetails": false,
  "country": "au"
}

High-volume APAC market scan

{
  "enableJobSearch": true,
  "jobKeywords": ["machine learning", "data scientist", "AI engineer"],
  "jobLocation": "Sydney NSW 2000",
  "jobsPerQuery": 500,
  "fetchJobDetails": true,
  "country": "au"
}

New Zealand search

{
  "enableJobSearch": true,
  "jobKeywords": ["software developer"],
  "jobLocation": "Auckland",
  "jobsPerQuery": 100,
  "country": "nz"
}

---

Performance and reliability

• Residential proxy (target market recommended) — best results and consistent throughput. Default is AU; match proxy country to your country input.
• Default memory: 512 MB — enough for high-volume runs with multiple keywords and companies.
• Streaming output — each job is written to the dataset immediately; nothing is buffered in memory for long runs.
• Webhook delivery — optionally POST each new record to your URL in real time (dataset is always the primary output).
• Smart search expansion — automatically broadens coverage when you request large result sets.
• Concurrent collection — multiple keywords, companies, and job details are processed efficiently for faster results at 512 MB memory.

---

Limitations and compliance

• This is an unofficial tool — not affiliated with Seek or JobStreet.
• Use responsibly and comply with applicable laws and Seek's Terms of Service.
• Some fields (e.g. salary) appear only when employers publish them.
• Listing availability can change; expired postings may return summary data only.

---

Contact and custom work

Need something beyond this Actor? I design and build custom data solutions and full-stack products for teams that want results — not experiments.

Email: dubem115@gmail.com
GitHub: github.com/DrunkCodes

Reach out for:

• Custom Apify Actors — any website, job board, or data source
• Seek and hiring data projects — pipelines, alerts, and dashboards at scale
• LLM and MCP integrations — connect your data to ChatGPT, Claude, and agent workflows
• Web apps and automation — data tools, internal platforms, SaaS products, and client-facing apps
• Any data collection project — lead generation, market research, monitoring, and enrichment at scale

Whether you need a one-off data feed or a production system, I can help you ship it.

---

Seek Jobs Real-Time Data · by DrunkCodes