JobStreet Job Listing
Pricing
from $3.60 / 1,000 results
JobStreet Job Listing
JobStreet Job Listing provides JobStreet job listings from 8 Asia-Pacific markets with 41 normalized job, salary, company, application, and public contact fields without login.
Pricing
from $3.60 / 1,000 results
Rating
5.0
(1)
Developer
TrueFetch
Maintained by CommunityActor stats
2
Bookmarked
21
Total users
4
Monthly active users
3 days ago
Last modified
Categories
Share
JobStreet Job Listing is a source for JobStreet job listings across 8 Asia-Pacific JobStreet, SEEK, and JobsDB markets and returns 41 normalized job, salary, employer, application, and public contact fields, built for developers and data teams.
- 8 explicit Asia-Pacific markets.
- 8 public inputs with 3 required.
- 41 normalized Dataset fields.
- Market-aware JobStreet, SEEK, or JobsDB routing.
Run a one-result test · View API
Set max_results to 1; the smallest published-result test bills a minimum $0.01000 Actor Start plus one $0.00400 Result, or $0.01400 on FREE.
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.
JobStreet's official regional directory identifies its JobStreet markets and international SEEK and JobsDB partners used across this source family.
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?
- Open JobStreet Job Listing on Apify.
- Enter
keyword, choose one supportedcountry, and setmax_results. - Add the optional request filters only when they reflect the intended search.
- 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_mode |
| 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?
JobStreet Job Listing exposes 8 public inputs in schema order, with 3 required and the rest optional.
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
max_results | integer | Yes | Maximum number of normalized JobStreet listings to return. | 10 |
keyword | string | Yes | Job title, skill, or company query for JobStreet. | Customer Service |
country | select | Yes | Country for the JobStreet regional search. | Philippines |
location | string | No | City, area, or postal code for JobStreet. | — |
posted_since | date | No | Earliest posting date where JobStreet accepts the filter. | — |
remote_only | boolean | No | Return remote roles where JobStreet accepts the filter. | — |
job_type | select | No | Employment type filter accepted by JobStreet. | — |
currency | select | No | Target currency for converting salary amounts returned by JobStreet. | — |
country has 8 accepted values; job_type has 4 accepted values; currency has 166 accepted values. Optional fields have no request effect when omitted; use the live Input schema for types and accepted values.
What platforms and markets does JobStreet Job Listing cover?
JobStreet Job Listing covers 8 country-to-domain mappings across Asia-Pacific.
The country selector contains 8 values: Australia, Hong Kong, Indonesia, Malaysia, New Zealand, Philippines, Singapore, Thailand.
Coverage states where the Actor can form a request; live inventory, relevance, language, and optional field availability still come from the selected public source.
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 public Actor ID is IecFmY1ykFGWdEsUB; the name form truefetch/jobstreet-job-listing is also accepted. This synchronous HTTP call sends the same Auckland search and returns Dataset items:
curl -X POST \"https://api.apify.com/v2/acts/IecFmY1ykFGWdEsUB/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?
JobStreet Job Listing costs $0.00400 per Result on FREE plus $0.01000 per minimum Actor Start event, so the smallest one-result test totals $0.01400.
| Apify tier | Actor Start | Per Result |
|---|---|---|
| FREE | $0.01000 | $0.00400 |
| BRONZE | $0.01000 | $0.00360 |
| SILVER | $0.01000 | $0.00320 |
| GOLD | $0.01000 | $0.00300 |
| PLATINUM | $0.01000 | $0.00300 |
| DIAMOND | $0.01000 | $0.00300 |
Result is billed once for each item written to the default Dataset. Actor Start event count depends on selected memory, with a minimum of one event.
Smallest useful test: $0.01000 + 1 × $0.00400 = $0.01400 on FREE when one item is published. A zero-result run can still incur Actor Start. Prices can change; check live pricing before scheduling volume.
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
How do I get jobstreet job listings by keyword?
Set keyword, country, and max_results, then add only the optional fields present in this Actor's input table. Results are capped by source availability and relevance.
What does “jobstreet jobs api without login” mean for this Actor?
The Actor runs on Apify without asking for a source-site publisher credential; an Apify account and token are still required for authenticated API or MCP calls.
Does JobStreet Job Listing require a source-site login?
No source-site username, password, cookie, or API key appears in the public input. The Actor collects accessible public listings independently of the source.
Why are salary, company, applicant, or contact values empty?
Those values are nullable because public listings do not expose the same detail. Empty means unavailable from the collected source, not zero or false.
Is there a free jobs API?
Apify accounts include platform usage under the current Apify plan, while this Actor bills Actor Start and Result events. Use the one-result calculation in Pricing to evaluate the smallest test.
Can I schedule runs to monitor JobStreet-family vacancies over time?
Yes. Test a small input first, then use Apify schedules and webhooks. Preserve processed_at and source URLs because listings can change, close, or reappear.
How is billing counted for JobStreet Job Listing?
Billing uses Actor Start events and one Result event per default Dataset item. A requested result limit is a cap, not a prepaid bundle or a guarantee of source inventory.
Related TrueFetch Actors
JobStreet Job Listing has three nearby TrueFetch alternatives, each for a different source decision.
- Job Search — Use it for broader multi-board discovery.
- Glints Job Listing — Use it for Glints-specific Asian market filters.
- Indeed Job Listing — Use it for Indeed coverage across 62 countries.
Support
Use the Store page for the run interface, the API page for generated clients, Issues for reproducible bugs, and the TrueFetch community for usage questions.
Run a one-result test · View API
Last Updated: August 10, 2026