# Remote Jobs Scraper $2/1K — RemoteOK, Remotive, WWR, Himalayas (`nomad-agent/remote-boards-scraper`) Actor 4 remote job boards in one run: RemoteOK, Remotive, WeWorkRemotely, Himalayas. $2/1,000 jobs — cheapest multi-board aggregator. Deduplicated JSON with title, company, salary, apply URL. Delta mode bills each posting once; webhook delivery built in. Made for job-alert bots and hiring research. - **URL**: https://apify.com/nomad-agent/remote-boards-scraper.md - **Developed by:** [Nomad.Dev](https://apify.com/nomad-agent) (community) - **Categories:** Jobs, Lead generation - **Stats:** 9 total users, 7 monthly users, 92.4% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $1.60 / 1,000 job results 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/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows. 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. Actors are written with capital "A". ## 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. The best way to integrate Actors is as follows. - **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use). - **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`. - **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`. - **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`. - **Any other language** — the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ## Remote Jobs Scraper $2/1K — RemoteOK, Remotive, WWR, Himalayas Fetch live remote-only job listings from **4 remote job boards** — RemoteOK, Remotive, WeWorkRemotely and Himalayas — in a single run, merged and deduplicated into one clean dataset. > **Claude / Codex skill to describe and setup this actor: [SKILL.md](https://github.com/Exdenta/OinkAIJobSearch/blob/main/skill/remote-boards-scraper/SKILL.md)** Two features no other remote-jobs scraper on the Store offers: - **Delta mode** (`onlyNewSinceLastRun`) — on a schedule, each posting is returned and **billed exactly once**. Perfect for job-alert bots and newsletters. - **Webhook delivery** (`webhookUrl`) — the run POSTs results straight to your endpoint, no dataset polling needed. ### What remote jobs data does this scraper extract? Each result is one flat JSON record per job posting: | Field | Meaning | |---|---| | `source` | Board the listing came from — `remoteok`, `remotive`, `weworkremotely` or `himalayas` | | `id` | Stable source-side identifier | | `title` | Job title as posted | | `company` | Hiring company / organisation | | `companyLogo` | Company logo URL where the source provides one (RemoteOK, Remotive, Himalayas); `null` for WeWorkRemotely | | `location` | Location / duty station (may include remote hints) | | `url` | Direct link to the posting | | `postedAt` | Posting date where the source provides it; `null` when absent | | `salary` | Salary text where the source provides it; `null` when absent (WeWorkRemotely feeds never include salary) | | `salaryMin` / `salaryMax` | Structured salary range bounds — populated for **RemoteOK** (API exposes numeric `salary_min`/`salary_max`) and **Himalayas** (API exposes numeric `minSalary`/`maxSalary`); `null` for Remotive (free-text `salary` field only, no numeric fields to parse) and WeWorkRemotely (no salary data at all) | | `salaryCurrency` | Currency for `salaryMin`/`salaryMax` — `"USD"` for RemoteOK (submitted as annualized USD-equivalent); Himalayas' reported currency otherwise (may be `null`); `null` for Remotive/WeWorkRemotely | | `salaryPeriod` | Pay period for `salaryMin`/`salaryMax` — `"year"` for RemoteOK, normalized to `"year"` for Himalayas' annual ranges; `null` otherwise | | `jobType` | Employment type where provided — Remotive (`job_type`) and Himalayas (`employmentType`); `null` for RemoteOK/WeWorkRemotely | | `snippet` | Short description excerpt | | `tags` | Source-provided tags/skills list (may be empty) | | `category` | Job category — Remotive and Himalayas; `null` for RemoteOK/WeWorkRemotely | | `scrapedAt` | ISO-8601 UTC timestamp of when the run fetched the listing | **Zero-result sentinels:** if an enabled board returns nothing (temporarily down, blocked, or empty feed), the run emits one small diagnostic row for that board (`_sentinel: true`, `warning`, `docs`) instead of silently dropping it. Sentinel rows are **not billed**. ### How to scrape remote jobs with this Actor 1. Click **Try for free** / **Run** — no login to the target site, no cookies, no proxies to configure. 2. Adjust the input (`keyword`, `titleExclude`, `postedSince`, board toggles, `maxItems`) or keep the defaults. 3. Run it and export the dataset as JSON, CSV or Excel, or read it over the [API](https://docs.apify.com/api/v2). Run it from your own code: ```python from apify_client import ApifyClient client = ApifyClient("") run = client.actor("nomad-agent/remote-boards-scraper").call(run_input={"maxItems": 50}) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item["title"], "—", item["company"], item["url"]) ``` Or a single HTTP call that runs the Actor and returns items in one response: ```bash curl -X POST \ "https://api.apify.com/v2/acts/nomad-agent~remote-boards-scraper/run-sync-get-dataset-items?token=" \ -H "Content-Type: application/json" \ -d '{"maxItems": 50}' ``` ### Input | Field | Type | Default | Notes | |---|---|---|---| | `keyword` | string | `""` | Optional case-insensitive substring matched against job title and company name. Leave empty to return all listings. | | `titleExclude` | array | `[]` | Skip listings whose title or company contains any of these case-insensitive terms. Exclusion twin of `keyword` above. | | `postedSince` | integer | `0` | Only return listings posted within this many days (max `365`). Applied client-side after fetch — see note below. Set `0` to disable and return all fetched listings regardless of age. | | `enableRemoteOK` | boolean | `true` | Scrape listings from RemoteOK. | | `enableRemotive` | boolean | `true` | Scrape listings from Remotive. | | `enableWeWorkRemotely` | boolean | `true` | Scrape tech/programming listings from WeWorkRemotely (Full-Stack, Back-End, Front-End, DevOps/SysAdmin). | | `enableHimalayas` | boolean | `true` | Scrape listings from Himalayas (himalayas.app) — exposes numeric salary ranges, company logo and employment type. | | `onlyNewSinceLastRun` | boolean | `false` | Delta mode. Return only listings not emitted by previous runs (identity remembered in a named key-value store). Ideal for scheduled job-alert runs — each posting is returned and billed once. | | `maxItemsPerSource` | integer | `50` | Maximum number of listings to return from each enabled board (max `500`). Each item returned is a billed dataset result. Set `0` for no limit (not recommended). | | `maxItems` | integer | `150` | Hard cap on the total number of listings returned across all boards (values above `2000` are clamped). Each item returned is a billed dataset result. Set `0` for no limit (not recommended). | | `cacheTtlSeconds` | integer | `1800` | *Advanced.* Reuse a fetch from this many seconds ago instead of hitting the source board again on rapid re-runs. Set `0` to always fetch live. | | `webhookUrl` | string | `""` | *Advanced.* Optional HTTPS endpoint. When set, the run POSTs its listings there in batches of 50 as JSON (`{items, offset, count, total}`) after writing them to the dataset. Best-effort — a webhook failure is logged but never fails the run. | | `webhookSecret` | string | `""` | *Advanced.* Optional shared secret sent as the `X-Webhook-Secret` header on each webhook POST so your endpoint can verify the caller. | > **Billing note:** each returned listing is a billed dataset result. A single run merges four full remote-job-board feeds, so `maxItemsPerSource` (default `50`, max `500`) and `maxItems` (default `150`, max `2000`) cap the cost — set either to `0` for no limit, but expect hundreds of listings per board on an unbounded run. > > `postedSince` is a client-side filter: none of the four source feeds accept a server-side date parameter, so the actor fetches the live feed and then drops listings older than N days by parsing each source's own `postedAt` format (RemoteOK/Remotive: ISO 8601; WeWorkRemotely: RSS `published` date). A listing with a date the actor can't parse is kept rather than silently dropped. ### Output example ```json { "source": "remotive", "id": "1934582", "title": "Backend Engineer (Go)", "company": "Chili Piper", "companyLogo": "https://remotive.com/job/1934582/logo", "location": "Worldwide", "url": "https://remotive.com/remote-jobs/software-dev/backend-engineer-1934582", "postedAt": "2026-06-29T07:00:00", "snippet": "Fully remote backend role...", "salary": "$90k–$120k", "salaryMin": null, "salaryMax": null, "salaryCurrency": null, "salaryPeriod": null, "jobType": "full_time", "category": "Software Development", "tags": ["go", "backend"], "scrapedAt": "2026-07-06T09:15:00+00:00" } ``` RemoteOK **and Himalayas** records carry the numeric salary fields too, since both APIs expose numeric min/max salary directly: ```json { "source": "himalayas", "salary": "$157k–$175k", "salaryMin": 157500, "salaryMax": 175000, "salaryCurrency": "USD", "salaryPeriod": "year", "jobType": "Full Time", "companyLogo": "https://cdn-images.himalayas.app/..." } ``` ### Integrations Export the dataset as JSON, CSV or Excel from the Console, pull it over the [Apify API](https://docs.apify.com/api/v2) (including `run-sync-get-dataset-items` for a single blocking call), wire it into Make/Zapier/n8n, or drive it from an AI agent via the [Apify MCP server](https://apify.com/apify/actors-mcp-server). ### Pricing Pay per event: **$0.005 per Actor start** and **$0.002 per job returned** ($2 per 1,000 jobs — volume discounts bring it down to $1.60/1,000 on higher Apify plans). 100 jobs ≈ $0.21. No subscription, no rental — you pay only for what you fetch. This is the **cheapest 4-board remote-jobs aggregator on the Apify Store** — comparable multi-board scrapers charge $3–15 per 1,000 results. Combine with `onlyNewSinceLastRun` and you never pay for the same posting twice. ### Use cases - Remote-job boards and newsletters - Job-alert bots for remote-first candidates - Remote-hiring market research - Feeding AI matching agents with remote-only supply ### FAQ **Is it legal to scrape remote jobs?** This Actor reads only publicly available job postings — data any visitor can see without logging in. No personal data behind authentication is touched. Review the target site's terms and your local regulations for your specific use case. **Do I need an account on the target site?** No. Postings are fetched from public pages/APIs — no login, cookies or session tokens. **How fresh is the data?** Every run fetches live listings. Results are cached for `cacheTtlSeconds` (default 30 min, set 0 to always hit the source live). Use `postedSince` to additionally filter out listings older than N days. **Can I get only jobs I haven't seen before?** Yes — enable `onlyNewSinceLastRun`. The actor remembers every listing it has emitted (by deduplicated identity, persisted in a named key-value store) and returns only postings not seen in earlier runs. Combined with a schedule, each posting is returned and billed exactly once — ideal for feeding a job-alert bot. **Can it push results to my endpoint?** Yes — set `webhookUrl` (and optionally `webhookSecret`). After writing to the dataset, the run POSTs listings to your URL in batches of 50. Delivery is best-effort and never fails the run. **How many jobs can I get?** `maxItemsPerSource` (default 50, max 500) and `maxItems` (default 150, max 2000) cap the run. Set either to 0 for no limit — not recommended, since every returned item is a billed dataset result and this Actor merges four full remote-job-board feeds. **Something broken or missing?** Open an issue on the Actor's **Issues** tab — it is monitored and reliability fixes ship fast. **Finding this Actor useful?** A quick ⭐ review on the Store page helps other remote-job hunters discover it — and tells us what to build next. ### Related Actors - [Web Developer Jobs Scraper — 10 Boards in One](https://apify.com/nomad-agent/web-dev-bundle) - [AI & ML Engineer Jobs Scraper — 8 Boards in One](https://apify.com/nomad-agent/ml-ai-dev-bundle) - [LinkedIn Jobs Scraper — No Login, No Cookies](https://apify.com/nomad-agent/linkedin-scraper) - [Hacker News Who Is Hiring Scraper — HN Jobs](https://apify.com/nomad-agent/hackernews-scraper) *** **From the maker of [Oink](https://github.com/Exdenta/OinkAIJobSearch)** — an open-source, AI-powered job-search bot for Telegram that runs on these Actors. [Try the free bot](https://t.me/job_search_everyday_bot), get a managed instance at [oinkjobsearch.com](https://oinkjobsearch.com), or browse the [full catalog of 50+ Actors](https://apify.com/nomad-agent). # Actor input Schema ## `keyword` (type: `string`): Optional case-insensitive filter, matched against each listing's title, company and category (not its tags or description — the boards' tag lists are company-wide, so matching them returns unrelated roles). Pass several terms separated by commas to match ANY of them — e.g. "machine learning, ml engineer, data scientist". Hyphens and spaces are interchangeable. Leave empty to return all listings. ## `titleExclude` (type: `array`): Skip listings whose title or company contains any of these case-insensitive terms. Exclusion twin of the keyword filter above. ## `postedSince` (type: `integer`): Only return listings posted within this many days (values outside 0–365 are clamped). Applied client-side after fetching, since none of the 4 source boards support a server-side date filter — postedAt is parsed per source and compared here. Set 0 (default) to disable and return all fetched listings regardless of age. ## `enableRemoteOK` (type: `boolean`): Scrape listings from RemoteOK. ## `enableRemotive` (type: `boolean`): Scrape listings from Remotive. ## `enableWeWorkRemotely` (type: `boolean`): Scrape tech/programming listings from WeWorkRemotely (Full-Stack, Back-End, Front-End, DevOps/SysAdmin). ## `enableHimalayas` (type: `boolean`): Scrape listings from Himalayas (himalayas.app) via its public jobs API. Himalayas exposes numeric salary ranges (min/max/currency) like RemoteOK, plus company logo and employment type. ## `onlyNewSinceLastRun` (type: `boolean`): Delta mode. Remember every listing emitted by previous runs (by deduplicated identity, persisted in a named key-value store) and return ONLY listings not seen before. Great for scheduled runs feeding a job-alert bot — you pay for and receive each posting once. Leave off to return the full current feed every run. ## `maxItemsPerSource` (type: `integer`): Maximum number of listings to return from each enabled board (values above 500 are clamped to 500). Each item returned is a billed dataset result — raising this increases cost. Set 0 for no limit (not recommended; the 4 source boards can each return hundreds of live listings per run). ## `maxItems` (type: `integer`): Hard cap on the total number of listings returned across all boards (values above 2000 are clamped to 2000). Each item returned is a billed dataset result — raising this increases cost. Set 0 for no limit (not recommended). ## `cacheTtlSeconds` (type: `integer`): Reuse a fetch from this many seconds ago instead of hitting the source board again on rapid re-runs. Set 0 to always fetch live. Negative values are treated as 0. ## `webhookUrl` (type: `string`): Optional HTTPS endpoint. When set, the run POSTs its listings to this URL in batches of 50 as JSON ({items, offset, count, total}) after writing them to the dataset. Delivery is best-effort: a webhook failure is logged but never fails the run. ## `webhookSecret` (type: `string`): Optional shared secret sent with each webhook POST as the X-Webhook-Secret header so your endpoint can verify the caller. Only used when Webhook URL is set. ## Actor input object example ```json { "keyword": "python", "titleExclude": [ "intern", "unpaid" ], "postedSince": 0, "enableRemoteOK": true, "enableRemotive": true, "enableWeWorkRemotely": true, "enableHimalayas": true, "onlyNewSinceLastRun": false, "maxItemsPerSource": 50, "maxItems": 150, "cacheTtlSeconds": 1800 } ``` # Actor output Schema ## `dataset` (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 = {}; // Run the Actor and wait for it to finish const run = await client.actor("nomad-agent/remote-boards-scraper").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 = {} # Run the Actor and wait for it to finish run = client.actor("nomad-agent/remote-boards-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{}' | apify call nomad-agent/remote-boards-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=nomad-agent/remote-boards-scraper", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/hJEnrpwrHuqE1jp9E/builds/51niwHr9H8TPFHF2o/openapi.json