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

One feature no other remote-jobs scraper on the Store offers:

• Webhook delivery (webhookUrl) — the run POSTs results straight to your endpoint, no dataset polling needed.

What remote jobs data does this scraper extract?

Published postings follow nomad-agent-job-row-v1. The shared fields carry source identity, title and company, parsed locations, dates, the complete plain-text body when available, source markup when usable, and work type. Unavailable scalar facts are null; no parsed location is []. Source-only facts appear in versioned custom.data only when mapped there. See the Output example section for the exact dataset fields and diagnostic rows.

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, postedWithin, 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.

Run it from your own code:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
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:

curl -X POST \
  "https://api.apify.com/v2/acts/nomad-agent~remote-boards-scraper/run-sync-get-dataset-items?token=<YOUR_APIFY_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.
postedWithin	string	any	Keep only jobs published inside this window. Use any for no date filter, or a duration — 1h, 24h, 3d, 2w, 6m. Jobs the source published no date for are kept rather than dropped. Applied client-side, since none of the 4 source boards support a server-side date filter. Replaces postedSince, still accepted for existing integrations.
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.
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.

postedWithin 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 outside the window 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

Every row follows nomad-agent-job-row-v1, the one shape shared by all of this fleet's job Actors. A row carries every field; null means the source did not publish that fact, and locations: [] means no usable location was parsed from the posting. Nothing is guessed.

{
  "schemaVersion": "nomad-agent-job-row-v1",
  "recordType": "posting",
  "source": "remote_boards",
  "id": "a1b2c3",
  "url": "https://example.com/remote_boards/jobs/a1b2c3",
  "title": "Senior Backend Engineer",
  "company": "Example Company",
  "locations": [
    "Bilbao",
    "Spain"
  ],
  "postedAt": "2026-09-02T00:00:00Z",
  "deadline": null,
  "description": "The complete posting body as plain text, exactly as the source published it — never truncated.",
  "descriptionHtml": "<p>The complete posting body as the source's own markup.</p>",
  "workType": "remote",
  "custom": {
    "schemaId": "nomad-agent-job-custom-remote-boards-v1",
    "data": {
      "category": "…",
      "tags": "…"
    }
  },
  "category": null,
  "companyLogo": null,
  "jobType": null,
  "location": null,
  "salary": null,
  "salaryCurrency": null,
  "salaryMax": null,
  "salaryMin": null,
  "salaryPeriod": null,
  "scrapedAt": null,
  "snippet": null,
  "tags": null
}

Field	Meaning
schemaVersion	Always "nomad-agent-job-row-v1".
recordType	"posting" for a job, "diagnostic" for a row reporting something about the run itself.
source	Which job source the posting came from, from the collector registry's vocabulary — not the Actor name.
id	Stable identifier for the posting within source.
url	Canonical public URL of the posting on the source site.
title	Job title exactly as the source publishes it, untruncated.
company	Employer name as published.
locations	Places the role is based, most specific first — e.g. ["Bilbao", "Spain"].
postedAt	When the source published the posting, ISO-8601 UTC (YYYY-MM-DDTHH:MM:SSZ).
deadline	Closing date for applications as an ISO-8601 calendar date (YYYY-MM-DD).
description	The complete posting body as plain text — never truncated, never summarised.
descriptionHtml	The posting body as the source's own markup, preserving lists, headings and links.
workType	Working arrangement: "remote", "hybrid" or "onsite".
custom	Facts only this source publishes, as {"schemaId", "data"}.

Deprecated fields

This Actor is on a paid integration contract, so the fields it published before this shape are still emitted alongside the ones above during a transition window, unchanged:

category companyLogo jobType location salary salaryCurrency salaryMax salaryMin salaryPeriod scrapedAt snippet tags

They will be removed once the integrations reading them have moved. Nothing above changes when they go.

A run also emits diagnostic rows — recordType: "diagnostic" with a warnings array — when it has something to report, such as a source returning nothing. They are never billed and are easy to filter out on recordType.

Integrations

Export the dataset as JSON, CSV or Excel from the Console, pull it over the Apify API (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.

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.

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 postedWithin to additionally filter out listings older than N days.

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
• AI & ML Engineer Jobs Scraper — 8 Boards in One
• LinkedIn Jobs Scraper — No Login, No Cookies
• Hacker News Who Is Hiring Scraper — HN Jobs

---

From the maker of Oink — an open-source, AI-powered job-search bot for Telegram that runs on these Actors. Try the free bot, get a managed instance at oinkjobsearch.com, or browse the full catalog of 50+ Actors.