JobsDB Scraper

Search JobsDB (Hong Kong and Thailand) by keyword, location or a pasted search URL and get every matching job as clean JSON — with the full description and the salary split into min / max / interval (100 jobs in 24 s on 17 Oct 2026). Put your searches on a daily schedule: each run marks which jobs are new since your last run, so you only read the new ones.

More countries in one run: the same searches work in SEEK Jobs Scraper, which reads JobsDB, JobStreet and SEEK — pick any of Hong Kong, Thailand, Malaysia, Singapore, the Philippines, Indonesia, Australia and New Zealand under countries.

Call it from a script or a schedule

curl -X POST "https://api.apify.com/v2/acts/northbell~jobsdb-jobs-scraper/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"searches":["marketing"],"maxJobsPerSearch":50}'

The response is the rows themselves (a JSON array). To run it on a timetable instead, save the input as a task in Apify Console and add a Schedule; n8n, Make and Zapier run it through their Apify app with the same input.

**Measured, not estimated:** 501 jobs in 85 s, about **$0.0064 of Apify platform usage per 1,000 jobs** at 512 MB (our running cost — included in the price, nothing on top) (2026-09-30).

How "new since last run" works

The Actor remembers which jobs each search returned last time. A job it has not seen before is marked isNewSinceLastRun: true. JobsDB returns jobs newest first, so a daily run with Max jobs above a day's volume catches every new listing. If the whole search fits within Max jobs, the comparison is exact and jobs that disappeared come back as type: "closed" rows. If the search is bigger than Max jobs, a job only counts as new when it was also posted after your previous run — so an old job that merely moved into view is never reported as new.

Filters (title, location text, salary, remote) never change the comparison, so changing a filter never makes jobs look new.

What you get

Field
title, company, location, locations	as listed
classification, subClassification	the site's job category
workType, workArrangement, remote	full time / contract…, on-site / hybrid / remote
salaryText	the salary exactly as shown
salaryMin, salaryMax, salaryCurrency, salaryInterval	read from that text — null when it has no number (e.g. "Competitive"), never guessed
description	the full job text, HTML stripped (turn off with Include the full description)
teaser, bulletPoints	the summary the employer wrote for the search page
postedAt, isFeatured	listing date, and whether it is a paid featured ad
isNewSinceLastRun	true / false, or null on the first run (unknown, not "old")
jobUrl	link to the job on JobsDB
search, country	which of your searches returned it

Input

Put one search per line in Searches (e.g. marketing) and optionally a Location (e.g. Kowloon). Pick one or more Countries. JobsDB shows at most the newest ~500 jobs of any one search, so split very broad searches by location or use Posted within. Or set the filters on the site and paste the result page into Search URLs (e.g. https://hk.jobsdb.com/marketing-jobs) — every filter the site has then applies. Many searches in one run are cheaper than one run each.

A search the site refuses comes back as an error row and the run carries on.

Example output

One real row from a test run (long text shortened here with …).

{
  "type": "job",
  "provider": "jobsdb",
  "search": "marketing",
  "country": "HK",
  "jobId": "95102542",
  "title": "E-Commerce Manager - DTC / US Market (Fashion)",
  "company": "Wealth Glow Limited",
  "location": "Lai Chi Kok, Sham Shui Po District",
  "locations": [
    "Lai Chi Kok, Sham Shui Po District"
  ],
  "classification": "Retail & Consumer Products",
  "subClassification": "Management - Store",
  "workType": "Full time",
  "workArrangement": "On-site",
  "remote": false,
  "salaryText": "$30,000 – $45,000 per month",
  "salaryMin": 30000,
  "salaryMax": 45000,
  "salaryInterval": "month",
  "salaryCurrency": "HKD",
  "teaser": "Lead e-commerce operations and drive growth for a US-focused DTC brand on Shopify.",
  "bulletPoints": [],
  "postedAt": "2026-10-07T01:35:06.000Z",
  "isFeatured": false,
  "jobUrl": "https://hk.jobsdb.com/job/95102542",
  "companyUrl": null,
  "countryCode": "HK",
  "employmentType": "Full time",
  "seniority": "manager",
  "employmentTypes": [
    "full-time"
  ],
  "description": "About the role\nWe are looking for a strategic, data-driven, and results-oriented E-Commerce Manager to lead the day-to-day operations and accelerate the growth …",
  "isNewSinceLastRun": false
}

Get only the new jobs every morning (3 steps)

1. Open this Actor in Apify Console, fill in your searches, set What to return to Only jobs that are new since the last run, and click Save as a new task.
2. On the task, add a Schedule — for example daily at 07:00.
3. Open the task's Integrations tab and connect Slack, email, Google Sheets (or Zapier / Make / a webhook). Each morning you get only the new jobs.

You pay only for the new jobs plus $0.01 per run, so a quiet day costs about a cent. When you export by hand, pick the Jobs view: 13 tidy columns, title first, instead of every raw field.

Pricing

$0.80 per 1,000 jobs, plus $0.01 per run. Closed-job rows and errors are free. With Only jobs that are new since the last run, a daily schedule only pays for the new ones.

For AI agents

For a fast answer call with {"searches": ["marketing"], "countries": ["HK"], "maxJobsPerSearch": 20, "includeDescription": false} — a few seconds. The defaults (up to 200 jobs with full descriptions) can take about a minute, which is longer than many agent tool timeouts. Each row has type: job, closed or error. isNewSinceLastRun: null means "no previous run to compare with".

Same filters on every site (10/2026): experience level (read from the title: intern → executive, returned as a seniority column) and employment type (the site's own words normalised into full-time / part-time / contract / temporary / internship, returned as employmentTypes). They only narrow what is returned — no extra requests, no extra cost.

Zero rows is never ambiguous. The run's status message says why, per search — e.g. "zzz": no results on the site, results found but all removed by your filters or nothing new since the last run — and the OUTPUT record in the run's key-value store has the same as JSON: perSearch[].status is ok, no-results, all-filtered, nothing-new or error, with listed, read, returned, new and closed. Set summaryRows: true to get it as free type: "summary" rows instead.

Same core columns on every northbell job scraper (15 job sites + 10 company-career-page scrapers), so you can stack them into one table: jobId, title, company, location, countryCode (ISO, job sites), remote (true / false / null), employmentType (the site's own words), postedAt, jobUrl, salaryMin, salaryMax, salaryCurrency, salaryInterval, isNewSinceLastRun. Unknown is null, never a guess.

More job scrapers from northbell

Job sites: SEEK · JobStreet · JobsDB · Instahyre · Reed · InfoJobs · XING · Dice · HelloWork · Computrabajo · Foundit · jobs.ch · jobup.ch · Arbeitsagentur · Arbeitnow · Visa Sponsorship Jobs.

Company career pages with exact new/closed tracking: Greenhouse · Lever · Workday · AI companies.