# JobsDB Jobs Scraper: Hong Kong and Thailand Job Listings (`accountable_eel/jobsdb-jobs-lookup`) Actor Scrape JobsDB job listings in Hong Kong and Thailand by keyword and location, no login. Salary range, company, work type, posted date and job link for each posting. Filter by title, company or district. Export to Google Sheets. - **URL**: https://apify.com/accountable_eel/jobsdb-jobs-lookup.md - **Developed by:** [Adriana Voss](https://apify.com/accountable_eel) (community) - **Categories:** Jobs, Lead generation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $0.50 / 1,000 job posting returneds This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## JobsDB Jobs Scraper: Hong Kong and Thailand Job Listings **Get JobsDB job postings for Hong Kong or Thailand by keyword and location, one row per posting, with salary range, company, work type and posted date.** Type a job title (or "title @ district"), pick the country, and each matching posting comes back as its own row with a direct job link. No login, no cookies, no key. You are charged per posting returned, and a search with no matches costs nothing. ### Who uses it - **Recruiters and sourcers** watching which companies in Hong Kong or Bangkok are hiring for a role right now. - **Salary and market researchers** comparing the pay range posted for the same job title across districts. - **Sales teams** building lists of companies that are hiring, from the company name and company profile link. - **Job aggregators and Sheets or n8n workflows** that need fresh JobsDB postings on a schedule. Salary is only shown on part of the postings (about 1 in 10 in a 50-posting Hong Kong "engineer" run), and is returned as `null` when the employer did not post one. Full job descriptions are not included: each row carries the posting's one-line teaser and highlight bullets. ### How to use 1. **In the Apify Console.** Open the actor page and click **Start** — the `keywords` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found. 2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token: ```bash curl "https://api.apify.com/v2/acts/accountable_eel~jobsdb-jobs-lookup/run-sync-get-dataset-items?token=" \ -X POST \ -H "Content-Type: application/json" \ -d '{"keywords":["engineer"]}' ``` 3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required. ### Input ```json { "keywords": [ "engineer" ] } ``` One search per line. Write "keywords @ location", or just the keywords and pick a location below. Pick Hong Kong or Thailand under Search settings. Accepted formats: engineer, accountant @ Kowloon, software developer @ Bangkok. ### Output One row per job posting. Missing values are `null`, never `0` or an empty string. Every row carries `jobUrl` (the posting's link), `scrapedAt`, and the search that produced it. Example row (real posting, Hong Kong, 2026-10-11): ```json { "jobId": "95163548", "title": "Assistant Engineer / Engineer", "companyName": "Spectrum Engineering International Limited", "country": "HK", "location": "Lai Chi Kok, Sham Shui Po District", "classification": "Engineering", "workTypes": ["Full time"], "workArrangement": "On-site", "salaryLabel": "$22,000 – $28,000 per month", "postedAt": "2026-10-09T03:50:00Z", "jobUrl": "https://hk.jobsdb.com/job/95163548", "scrapedAt": "2026-10-11T18:38:16.291Z" } ``` Column reference: | query | found | status | searchKeywords | searchLocation | jobCount | totalAvailable | truncated | jobs | jobId | title | companyName | advertiser | companyUrl | location | country | remote | classification | subClassification | workTypes | workArrangement | salaryLabel | teaser | bulletPoints | isFeatured | postedAt | postedAgo | jobUrl | companyLogoUrl | scrapedAt | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | engineer | true | OK | | | | | | \ | | | | \ | | | | \ | | | | | \ | \ | | | | \ | | | 1970-01-01T00:00:00.000Z | A search with no matching postings comes back as one row with `"found": false` and is never charged. ### Pricing Pay-per-event. A flat per-run fee covers session/proxy warmup; you're billed per item only when data is actually found and returned — see `.actor/pay_per_event.json` for exact prices. A miss is never charged. One billable event, **job-returned**, charged once per posting returned. A search with no matches, or whose matches are all filtered out, is never charged. A run of 50 postings used about half a cent of platform compute, and the "Most postings to return per search" and "Stop after this many results" fields cap your spend. ### Example runs Paste any of these into the Input tab and press Start. All three need no key, no token and no account of your own beyond an Apify login. The first was run on 2026-10-11 and returned 50 postings out of 7,048 matching. **Engineer jobs in Hong Kong.** The default shape. ```json { "country": "hk", "keywords": ["engineer"], "maxResults": 20 } ``` **Accountants in Kowloon, posted in the last week, with a pay range shown.** ```json { "country": "hk", "keywords": ["accountant @ Kowloon"], "postedWithin": "week", "maxJobsPerQuery": 100 } ``` **Software developers in Bangkok, remote roles only, skipping recruiters.** ```json { "country": "th", "keywords": ["software developer @ Bangkok"], "remoteOnly": true, "excludeCompanies": ["recruit", "staffing"] } ``` ### Use it from Clay, n8n, Make, or an AI agent This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token. ```bash curl "https://api.apify.com/v2/acts/accountable_eel~jobsdb-jobs-lookup/run-sync-get-dataset-items?token=" \ -X POST \ -H "Content-Type: application/json" \ -d '{"keywords":["engineer"]}' ``` **n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~jobsdb-jobs-lookup/run-sync-get-dataset-items?token=`, Body Content Type `JSON`, JSON Body `{"keywords":["engineer"]}` (swap in an expression from an earlier node for a real value). **Clay.** Add an "HTTP API" column: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~jobsdb-jobs-lookup/run-sync-get-dataset-items?token=`, Body `{"keywords":["{{search}}"]}`, mapping the row's search into the `keywords` array. **MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "jobsdb scraper" — the agent will find and run this actor. # Actor input Schema ## `keywords` (type: `array`): One search per line. Write "keywords @ location", or just the keywords and pick a location below. Pick Hong Kong or Thailand under Search settings. Accepted formats: engineer, accountant @ Kowloon, software developer @ Bangkok. You're only charged for the ones we actually find — a miss costs nothing. ## `testRun` (type: `boolean`): Turn this on to test your input on a small sample before running the full list. Turn it off to process everything. ## `onlyFound` (type: `boolean`): Only keep rows where something was actually found. Misses are always free, whether or not you show them here. ## `includeKeywords` (type: `array`): Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything. ## `excludeKeywords` (type: `array`): Optional. Drop any result that mentions one of these words. Leave empty to skip nothing. ## `maxResults` (type: `integer`): Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit. ## `country` (type: `string`): Which JobsDB site to search. One country per run. ## `defaultLocation` (type: `string`): Used for any line that's just keywords. Write it the way JobsDB does — "Kowloon", "Hong Kong Island", "Bangkok", "Chiang Mai". Leave empty to search the whole country. ## `maxJobsPerQuery` (type: `integer`): JobsDB hands out 100 postings per page and this actor stops at 5 pages (500 postings) per search. You pay per posting returned, so this is also your budget control. ## `postedWithin` (type: `string`): Ask JobsDB for recent postings only. This is applied by JobsDB itself before results are sent, so it makes runs cheaper as well as fresher. ## `titleKeywords` (type: `array`): Optional. Keep only roles whose title contains at least one of these words — e.g. "engineer", "account executive". Case doesn't matter and partial words work. Leave empty to keep every role. ## `excludeTitleKeywords` (type: `array`): Optional. Drop any role whose title contains one of these words — e.g. "intern", "senior". Applied after the include list above, so a role matching both is dropped. ## `companies` (type: `array`): Optional. Keep only roles at companies whose name contains one of these. Partial matches work. ## `excludeCompanies` (type: `array`): Optional. Drop roles at companies whose name contains one of these — handy for filtering out recruitment agencies you already know. ## `locations` (type: `array`): Optional. Narrow a wide search down to particular districts — e.g. "Kwun Tong", "Sathon". Applied to the location JobsDB prints on each posting. ## `remoteOnly` (type: `boolean`): Keep only roles whose location, work arrangement, or title reads as remote. Applied to the postings after they arrive — treat it as a strong filter, not a guarantee. ## `skipDuplicateJobs` (type: `boolean`): On by default. Overlapping searches routinely surface the same role — with this on, each posting is returned, and billed, exactly once per run. ## `columns` (type: `array`): Choose which pieces of information to include in each result row. All are included by default. ## `expandRows` (type: `boolean`): When on, each job posting found gets its own row instead of being grouped under its search. You're still only charged once per search, no matter how many rows it produces. ## `maxConcurrency` (type: `integer`): Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady. ## `proxyConfiguration` (type: `object`): Apify Proxy config. Residential recommended for anti-bot-sensitive targets. ## Actor input object example ```json { "keywords": [ "engineer" ], "testRun": false, "onlyFound": false, "includeKeywords": [], "excludeKeywords": [], "country": "hk", "defaultLocation": "", "maxJobsPerQuery": 50, "postedWithin": "", "titleKeywords": [], "excludeTitleKeywords": [], "companies": [], "excludeCompanies": [], "locations": [], "remoteOnly": false, "skipDuplicateJobs": true, "columns": [ "searchKeywords", "searchLocation", "jobCount", "totalAvailable", "truncated", "jobs", "jobId", "title", "companyName", "advertiser", "companyUrl", "location", "country", "remote", "classification", "subClassification", "workTypes", "workArrangement", "salaryLabel", "teaser", "bulletPoints", "isFeatured", "postedAt", "postedAgo", "jobUrl", "companyLogoUrl" ], "expandRows": true, "maxConcurrency": 5, "proxyConfiguration": { "useApifyProxy": true } } ``` # Actor output Schema ## `results` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "keywords": [ "engineer" ], "includeKeywords": [], "excludeKeywords": [], "titleKeywords": [], "excludeTitleKeywords": [], "companies": [], "excludeCompanies": [], "locations": [] }; // Run the Actor and wait for it to finish const run = await client.actor("accountable_eel/jobsdb-jobs-lookup").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "keywords": ["engineer"], "includeKeywords": [], "excludeKeywords": [], "titleKeywords": [], "excludeTitleKeywords": [], "companies": [], "excludeCompanies": [], "locations": [], } # Run the Actor and wait for it to finish run = client.actor("accountable_eel/jobsdb-jobs-lookup").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "keywords": [ "engineer" ], "includeKeywords": [], "excludeKeywords": [], "titleKeywords": [], "excludeTitleKeywords": [], "companies": [], "excludeCompanies": [], "locations": [] }' | apify call accountable_eel/jobsdb-jobs-lookup --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/jobsdb-jobs-lookup" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/zJOZLr3Tep4qaWbxJ/builds/2U8rk9rtjitqkPKKg/openapi.json