JobStreet API: where it went, and how to get South-East Asian jobs data

Search for the JobStreet API and the first thing worth knowing is that it no longer exists as its own thing. JobStreet - the dominant job board across Malaysia, Singapore, the Philippines and Indonesia - has been owned by SEEK since 2014, and in February 2024 SEEK finished folding it, along with Jobsdb in Hong Kong and Thailand, into one unified platform built over three years for an estimated AUD$180 million. The brands survived. The separate technology did not. Whatever you are trying to do with JobStreet programmatically today, the answer routes through SEEK’s developer platform, and this post maps what that platform will and will not do for you.

The short answer

There is exactly one official JobStreet integration surface: the SEEK API, at developer.seek.com. It is a public, well-documented GraphQL platform, and its docs are explicit that it is enabled across the SEEK Group’s APAC markets - SEEK in Australia and New Zealand, Jobstreet in Singapore, Malaysia, the Philippines and Indonesia, and Jobsdb in Hong Kong and Thailand. One integration posts to all eight markets, and ads surface on the local Jobstreet and Jobsdb boards.

If you had a JobStreet integration before the migration, it ran on the legacy APOS or Adloader systems. Those are gone: SEEK consolidated the Jobstreet platform in late 2023 and Jobsdb in January 2024, ran a bridge for legacy integrations during the transition, and moved hirers onto the SEEK API. A vendor advertising “JobStreet API integration” in 2026 means a SEEK API integration, whether they have updated the brochure or not.

And the same one-sentence catch applies here that applies in Australia: SEEK’s own documentation states that the SEEK API does not offer programmatic job search capabilities. It is a hirer-side platform. You can post ads and pull applications back. You cannot query the listings.

What the SEEK API does for JobStreet markets

Three use cases, all built for recruitment software acting on behalf of employers. Job Posting pushes a vacancy from your ATS onto the boards, with market-specific locations, custom questions and variable pricing. Application Export (Optimised Apply) pulls candidate applications back into your software. Apply with SEEK lets candidates pre-fill your forms from their profile. Access runs on OAuth client credentials issued after an Integration Request form, and SEEK configures each hirer relationship during onboarding - there is no self-serve key. We walked through the auth model, the schema and the one read-shaped query in the SEEK API deep dive; all of it applies verbatim to JobStreet, because it is the same API.

If you are an ATS or HR-tech vendor with customers hiring in South-East Asia, this is genuinely good news: the docs are public, the GraphQL schema is inspectable before you commit, and one partner onboarding covers eight markets. Budget for a real onboarding rather than an afternoon, and start at the Integration Request form.

What it will not do: read the market

The other two people searching for a JobStreet API - the developer who wants postings in JSON and the analyst who wants South-East Asian hiring data in rows - get nothing from the official route. There is no endpoint that lists jobs, no filter, no keyword search. The reasoning is the marketplace moat: listings are what a job board sells, and every dominant regional board reaches the same conclusion, whether by never opening a read API or by retiring one.

Because the demand is real and unmet, an ecosystem sits in the gap. RapidAPI hosts JobStreet wrappers built on the internal JSON endpoints the site’s own front end uses, and scraping vendors like Apify sell JobStreet scrapers priced per result. Be clear-eyed about what you inherit with either: internal endpoints carry no compatibility promise and change without notice, automated access sits against the site’s terms (a question for your counsel, not a blog post), and scraper output ships the standard problems - the same vacancy duplicated across markets, expired listings that still render, and no signal for when a role actually closed. Fine for a weekend experiment. Expensive the moment a product depends on it.

The open layer underneath, with numbers

The honest disclosure first: JobsPipe does not index JobStreet. Our South-East Asia coverage comes from sources that publish postings openly and are collected directly - LinkedIn, Indeed, public Workday tenants, Workable, SmartRecruiters, Lever and Y Combinator - deduplicated into one record per vacancy and liveness-checked, so closed roles leave the corpus instead of haunting it.

Measured against the live database on the day this post published: 39,349 active postings across the six Jobstreet and Jobsdb markets. Singapore leads with 22,333, then the Philippines (13,233), Malaysia (1,959), Indonesia (671), Thailand (617) and Hong Kong (536). Vietnam, outside the SEEK footprint entirely, adds another 563. The skew is worth saying out loud: this corpus leans toward multinationals, tech companies and employers hiring through global ATSs and LinkedIn, so JobStreet’s long tail of local and SME advertising is broader than what we see. What the corpus gives you in exchange is structure - every record verified open, carrying extracted skills and an ISCO-08 occupation code, with salary fields populated when the employer stated one.

Querying the region in one request

Countries, cities, skills and freshness are filters here, not scraping projects:

curl -X POST "https://api.jobspipe.dev/v1/jobs/search" \
  -H "Authorization: Bearer jp_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "job_country_code_or": ["SG", "MY", "PH"],
    "job_location_or": ["Singapore", "Kuala Lumpur", "Manila"],
    "skills_or": ["python", "aws"],
    "posted_at_max_age_days": 30,
    "limit": 25
  }'

Add job_title_or for title matching, or swap the skills filter for occupation_code_or to sweep an occupation regardless of how the title is phrased. Each record returns job_title, company, the url pointing at the original listing, date_posted, seniority, salary fields with currency where stated, and a status plus closed_at so you know when a vacancy died. The free tier is 1,000 jobs a month, no card and no partner review.

So which path is yours

• Posting jobs to JobStreet from your product. The SEEK API is the only real option and it is a good one. One integration, eight APAC markets, public docs.
• Migrating a legacy JobStreet integration. APOS and Adloader are retired; the migration guides on developer.seek.com cover the transition, and the destination is the same SEEK API.
• Reading the market. No official route exists, and the platform unification made one less likely, not more. Either accept the cost and fragility of scraping, or read the layer where employers publish the same vacancies openly - the jobs API comparison covers every option in that category.