JobStreet Job Listing

Affiliate disclosure: TrueFetch may earn a commission if you sign up through an Apify link on this page, at no extra cost to you.

Collect public JobStreet, SEEK, and JobsDB vacancies across eight APAC markets with supported search filters and a normalized 41-field output contract.

• Eight country markets route automatically to the appropriate JobStreet, SEEK, or JobsDB domain.
• Location, remote, recency, and work-type filters are mapped into each supported search URL.
• 41 normalized fields cover job details, compensation, employers, applications, and available public contact signals.
• Public Store snapshot: 17 users and a 5.0 rating from one review on July 21, 2026; deployed Store content may be an older release.

Run a one-result test · View API

One published FREE-tier test result costs $0.01400: a $0.01000 Actor Start event plus a $0.00400 result event.

What does JobStreet Job Listing do?

JobStreet Job Listing is a TrueFetch Apify Actor and APAC jobs API for searching a connected family of public employment sites. Depending on country, the request goes to a regional JobStreet site, SEEK in Australia or New Zealand, or JobsDB in Hong Kong or Thailand. The public input stays consistent while the Actor handles the correct domain, path, and market currency.

The Actor searches by keyword and can add a city or region, a remote-only path, a supported work type, and a source date-range window. It extracts accessible search and detail data, normalizes the result, and stores it in the default Apify Dataset. Source URLs remain attached so consumers can verify individual records.

This Actor is not affiliated with JobStreet, SEEK, or JobsDB and is not an official API for those services. It does not use candidate accounts, retrieve private applicant data, send messages, or submit applications. Every field depends on what a public listing and its associated company pages expose.

How do I run JobStreet Job Listing?

1. Open JobStreet Job Listing on Apify.
2. Enter keyword, choose one supported country, and set max_results.
3. Add the optional request filters only when they reflect the intended search.
4. Start with one job, confirm the selected domain and output, then increase volume.

All examples use one repeatable scenario: retrieve one remote contract Cybersecurity Analyst vacancy around Auckland, New Zealand, posted within three days, with eligible salary values converted to NZD.

{
  "keyword": "Cybersecurity Analyst",
  "country": "New Zealand",
  "max_results": 1,
  "remote_only": true,
  "location": "Auckland",
  "posted_since": "3 days",
  "job_type": "contract",
  "currency": "NZD"
}

For this input, the Actor selects the New Zealand SEEK market. max_results remains a maximum, not guaranteed inventory. Remote plus contract plus a city and short date window can be restrictive; remove one optional filter at a time if the first test has no match.

What data does JobStreet Job Listing return?

The Dataset schema defines 41 fields shared with other current TrueFetch job Actors. Source omissions are preserved as empty values rather than guessed.

Field family	Fields
Processing	processor, processed_at
Source and apply paths	platform, platform_url, official_url, easy_apply
Job content	title, description, job_type, job_level, job_function, listing_type, skills, experience_range
Place and work style	location, is_remote, work_from_home
Dates and openings	posted_date, valid_through, applicant_count, vacancy_count
Pay	salary_minimum, salary_maximum, salary_currency, salary_period
Company	company_name, company_type, company_founded, company_industry, company_url, company_website, company_logo, company_addresses, company_revenue, company_description, company_rating, employee_count, review_count
Public contacts	emails, phones, social_links

The following shortened item illustrates the Auckland scenario and does not represent a guaranteed live job:

{
  "platform": "Jobstreet",
  "platform_url": "https://nz.seek.com/job/example-id",
  "official_url": null,
  "title": "Cybersecurity Analyst",
  "company_name": "Example Security Services NZ",
  "location": {
    "raw": "Auckland CBD, Auckland",
    "locality": "Auckland",
    "country": "New Zealand",
    "country_code": "NZ"
  },
  "is_remote": true,
  "job_type": "Contract/Temp",
  "salary_currency": "NZD",
  "processor": "https://apify.com/truefetch/jobstreet-job-listing",
  "processed_at": "2026-07-21T12:00:00.000Z"
}

Use the live Output schema for the exact types. The normalized platform label can remain Jobstreet even when platform_url identifies SEEK or JobsDB; use the source URL and country to preserve the regional context.

What inputs can I configure?

The current schema has 8 public inputs, with 3 required.

Input	Required	Meaning
keyword	Yes	Job title, skill, employer, or search phrase.
country	Yes	Selects one of eight APAC market/domain mappings.
max_results	Yes	Maximum jobs written, from 1 to 10,000.
remote_only	No	Adds the source's remote-work path when true.
location	No	City or region inside the selected country.
posted_since	No	Converts an absolute date or duration to a supported source day bucket.
job_type	No	all, fulltime, parttime, or contract.
currency	No	Converts usable numeric salaries after collection.

Recency uses 1, 3, 7, 14, and 31-day buckets. The requested age rounds up to the first bucket that contains it, and anything beyond 14 days uses the 31-day bucket. job_type: "all" applies no work-type restriction. Internship is not a selectable job type. Currency is not a source filter. Consult the Input schema before generating requests.

What platforms and markets does JobStreet Job Listing cover?

The Actor presents one input contract across three related public brands and eight countries.

Country input	Source domain	Native currency
Singapore	sg.jobstreet.com	SGD
Australia	www.seek.com.au	AUD
Hong Kong	hk.jobsdb.com	HKD
Malaysia	my.jobstreet.com	MYR
Philippines	ph.jobstreet.com	PHP
Thailand	th.jobsdb.com	THB
Indonesia	id.jobstreet.com	IDR
New Zealand	nz.seek.com	NZD

One run uses one country and one domain. When location is absent, equal to the country, or a broad value such as all, the Actor avoids a narrow place path. Otherwise it adds the supplied local text; known regional aliases such as Jakarta are normalized for the request.

No country outside this table is promised by the current schema. For a multi-market study, run explicit country inputs separately so source, currency, and collection time remain auditable.

Why use JobStreet Job Listing?

Capability	Benefit
Market-aware routing	Reach JobStreet, SEEK, or JobsDB without building eight URL implementations.
Source-supported constraints	Apply location, remote, recency, and full-time/part-time/contract paths.
Regional salary parsing	Recognize the native currency conventions used across all eight markets.
Consistent 41-field contract	Feed APAC listings into one warehouse, alerting pipeline, or comparison workflow.
Record traceability	Retain public listing and application destinations when present.
Apify integration	Use Dataset exports, API calls, MCP, schedules, and webhooks.

Normalization reduces integration work but cannot equalize the source sites. Details, work labels, salaries, and company profiles can be populated differently across markets.

Who is JobStreet Job Listing for?

Audience	Example use
APAC recruiting operations	Track specified roles across a regional hiring footprint.
Labor economists	Build dated country and city vacancy snapshots.
Compensation researchers	Compare disclosed pay after normalizing eligible amounts.
Job-search product teams	Add attributed JobStreet-family results to alerts or search.
Company-intelligence analysts	Monitor visible employer hiring activity and work arrangements.

It should not be used as a source of candidate profiles or as an unattended application tool. Users remain responsible for lawful collection, retention, attribution, and downstream use.

How can I use JobStreet Job Listing through the API or MCP?

The stable Actor ID is truefetch/jobstreet-job-listing. This synchronous HTTP call sends the same Auckland search and returns Dataset items:

curl -X POST \
  "https://api.apify.com/v2/acts/truefetch~jobstreet-job-listing/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "keyword": "Cybersecurity Analyst",
    "country": "New Zealand",
    "max_results": 1,
    "remote_only": true,
    "location": "Auckland",
    "posted_since": "3 days",
    "job_type": "contract",
    "currency": "NZD"
  }'

Limit an Apify MCP connection to this Actor with the following configuration:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=truefetch/jobstreet-job-listing",
      "headers": {
        "Authorization": "Bearer <APIFY_TOKEN>"
      }
    }
  }
}

The connected client can then run the same one-result scenario. See the API page for asynchronous, SDK, and OpenAPI alternatives. Keep your token in a secret manager or environment variable.

How much does JobStreet Job Listing cost?

Pay-per-event billing charges Actor Start once and charges result for every normalized item pushed to the default Dataset.

Apify tier	Actor Start	Per result	Per 1,000 results
FREE	$0.01000	$0.00400	$4.00
BRONZE	$0.01000	$0.00387	$3.87
SILVER	$0.01000	$0.00373	$3.73
GOLD / PLATINUM / DIAMOND	$0.01000	$0.00360	$3.60

The one-result FREE test totals $0.01400 when one job is stored. Start cost still applies to a zero-result run. Confirm the public amounts on the Pricing tab before scaling.

How does JobStreet Job Listing compare with alternatives?

Decision factor	JobStreet Job Listing	Multi-board Job Search	Manual source browsing
Regional sources	JobStreet, SEEK, and JobsDB mapping	Multiple compatible boards	One selected website
Markets	Eight explicit APAC countries	Broader but source-dependent	Manually chosen
Data delivery	Structured 41-field Dataset	Shared normalized Dataset	Pages or copied values
Automation	API, MCP, schedules, webhooks	Same, across more sources	Limited repeatability
Best fit	JobStreet-family APAC monitoring	Cross-board discovery	Final review of a few jobs

Choose this Actor for source-specific coverage across its eight mappings. Choose Job Search when diversity of job boards is more important. Always use the original listing to verify a role before a recruiting or application decision.

What are the limits and troubleshooting steps?

Symptom	Cause to consider	Controlled next step
No result for a narrow combination	The live source may have no matching remote contract role in that location and window.	Remove one filter and rerun one result.
A 2-day request shows 3 days	Recency rounds upward to a supported bucket.	Use exactly 1, 3, 7, 14, or 31 days when precision matters.
Salary is missing	The listing may not disclose parseable numeric pay.	Keep salary nullable and inspect its source URL.
Converted pay is unchanged	Source currency or numeric amount may be missing, or conversion may be unavailable.	Compare original populated fields before aggregation.
official_url is null	A distinct external application URL was not exposed.	Use platform_url as the auditable source link.
Work or company fields vary by country	JobStreet, SEEK, and JobsDB publish different page structures and fields.	Design downstream logic around nullable values.
Jobs disappear on later runs	Public vacancies expire, update, or are withdrawn.	Save processed_at and treat runs as snapshots.

For support, reproduce the issue with one market and max_results: 1, then provide the run URL through Apify Issues. Do not include credentials.

Frequently asked questions

Why does a JobStreet Actor return SEEK or JobsDB URLs?

Those sites serve the configured regional markets in the current implementation: SEEK for Australia and New Zealand, JobsDB for Hong Kong and Thailand, and JobStreet for the remaining four countries.

Is a location required?

No. Omit it for a country-wide keyword search. Adding a city or region narrows the source URL.

Are internships supported as a filter?

No. The public job_type choices are all, full-time, part-time, and contract. Internship details may appear in output text but cannot be required as an input filter.

Can remote, work type, and date be combined?

Yes. They become distinct components of the request URL and can also be combined with a location.

What happens with posted_since: "60 days"?

The implementation maps it to the widest supported 31-day source window. It does not request an exact 60-day range.

Does currency affect the regional domain?

No. country chooses the domain. Currency only requests conversion of usable salary values after collection.

Can I automate all eight markets?

Yes, as eight explicit runs or tasks. Test each market independently because result density, language, source fields, and salary formats differ.

Related TrueFetch Actors

• Indeed Job Listing — choose it for an Indeed-specific source contract and its wider country coverage.
• LinkedIn Job Listing — choose it for LinkedIn-specific recency, radius, remote, and role signals.
• Job Search — choose it to collect several compatible boards through one normalized request.

Support and last updated

• Run JobStreet Job Listing
• View API options
• Report an issue
• Join the TrueFetch Telegram group
• Contact support on Telegram

Last updated: July 21, 2026. The local schema, metadata, pricing, and read-only runtime path were checked separately from older deployed Store material; public Store statistics are dated observations.

Run the one-result New Zealand scenario first, verify the SEEK source and nullable-field behavior, and then increase the result cap.

Run a one-result test · View API