Remote OK Jobs Scraper

Remote OK scraper that keeps only genuinely remote developer jobs - about 10 real remote roles out of the ~100 rows the feed publishes - as a clean JSON or CSV dataset. Parsed salary, normalised hiring regions, seniority and a ghost-job score flagging expired and stale postings.

Remote OK jobs: genuinely remote roles only

Remote OK's feed is not all remote work. Measured against their live API on 2026-08-15, 90 of 100 listings were not remote roles at all — a barber in Regina, a live-in nanny in Bermuda, store managers, a marine painter, a bell person — plus rows that are not job postings in any sense: Test Job Title, Title TBD, HYGPOOLOP, Looking for Job, Seeking a job.

A scraper that dumps the feed hands you all of that and calls it remote work.

This one requires positive evidence that a listing is actually remote: a blank location (the board's way of saying anywhere), an explicit remote word in any spelling including Remoto, or a country/continent-level region that states eligibility rather than an address. A named town is a desk until the board says otherwise.

The trade is deliberate and worth knowing before you buy: you get roughly 10 real remote jobs instead of 100 rows, most of which were never remote. If you want the raw feed including on-site roles, this is the wrong Actor.

---

Remote OK job data: what each row contains

Identity	stable id across runs, posting URL, direct applyUrl where published
The role	title, company, plain-text description, tags, employment type, seniority
Where	remote flag, the board's own location text, and normalised regions (worldwide / usa / canada / latam / uk / europe / apac / africa / middle_east)
Pay	min, max, currency and period as numbers, annualised on request
When	posted date, expiry where published, age in days
Trust	freshness 0-1, ghostRisk low/medium/high, and ghostReason explaining the verdict in plain words

Ghost job detection: the trust fields

Job boards are full of postings still published but no longer open — filled roles left up for pipeline, evergreen "talent pool" adverts, and listings nothing ever expires. Every row here carries a risk band and the reasons behind it:

{
  "title": "Senior Backend Engineer",
  "company": "Acme",
  "freshness": 0.71,
  "ageDays": 10.4,
  "ghostRisk": "low",
  "ghostReason": ["recent, and nothing contradicts it"]
}

Signals come from what the board actually publishes: age, its own expiry date where there is one, missing application links, and evergreen phrasing. Nothing is inferred by a model. Freshness decays on a 21-day half-life, and a posting with no date scores 0.5 rather than 1.0 — absence of evidence is not evidence of freshness.

Example input: senior React or TypeScript jobs open worldwide or in the US

{
  "query": ["react", "typescript"],
  "regions": ["worldwide", "usa"],
  "seniority": ["senior"],
  "maxAgeDays": 30,
  "maxGhostRisk": "medium",
  "maxItems": 100
}

Every field is optional — run it empty and you get the whole Remote OK feed, filtered to the rows that are genuinely remote — about 10 jobs out of the roughly 100 rows the board publishes, best-first.

• Search terms are OR-ed. ["go", "rust"] returns jobs mentioning either.
• Worldwide jobs match every region filter, because a job open to everyone is open to you.
• minSalary is annualised first, so hourly and monthly rates compare correctly.
• maxItems is your cost ceiling — you are billed per job returned.
• maxPagesPerSource: Remote OK serves its whole feed in one call, so this setting has no effect for this board.

Output: one dataset item per Remote OK job

One dataset item per job, ordered best-first: lowest ghost-job risk, then freshest. Export as JSON, CSV or Excel, or read it from the API like any Apify dataset.

If Remote OK itself returns no jobs — the board is down or has changed its format — the run fails with a clear status message instead of succeeding with an empty dataset, so a failed-run alert on a schedule catches it. A run whose filters match nothing still succeeds, with an empty dataset and a status line saying so. When fewer than half of the rows carry a company or a posted date, the run log prints a WARNING.

Remote OK jobs scraper pricing: a worked cost example

You pay per job returned, on Apify's pay-per-event model, and nothing for platform usage on top: $0.006 per job on the Free and Bronze plans, $0.003 on Silver, $0.002 on Gold, Platinum and Diamond. Rows dropped by your filters are never billed, and a run that returns nothing costs nothing.

Run	Jobs returned	Free / Bronze	Silver	Gold and above
A default run: the feed filtered to genuinely remote jobs	10	$0.06	$0.03	$0.02
A run capped with maxItems: 100 (at most)	100	$0.60	$0.30	$0.20
A run whose filters match nothing	0	$0.00	$0.00	$0.00

maxItems is the hard ceiling: maxItems: 200 can never cost more than $1.20 on the Free plan. Apify's free plan includes a monthly usage credit, so a first run costs nothing out of pocket.

Use cases for Remote OK job data

• Remote developer and engineering jobs. Remote OK skews heavily technical, and every row is checked to be genuinely work-from-home rather than hybrid dressed up as remote.
• Salary benchmarking and compensation data. salaryMin, salaryMax, salaryCurrency and salaryPeriod are numbers, not strings, and minSalary annualises before comparing — so hourly, monthly and yearly postings line up.
• Filtering out expired and stale job postings. ghostRisk, ghostReason and freshness say which listings are probably no longer open, so you can drop them before anyone wastes an application.
• Job market and hiring data. Run it on a schedule and track how hiring, salary ranges, seniority mix and regions move over time.
• Building a job board, job feed or job alerts. id is stable across runs, so diffing today's dataset against yesterday's gives you genuinely new jobs rather than a board reshuffle.
• Recruitment and talent research. Company, title, tags, seniority, employment type and normalised regions on every row.

Export as JSON, CSV or Excel, or read the dataset straight from the Apify API.

How this Remote OK scraper fetches jobs

Remote OK publishes a public, documented, unauthenticated JSON feed and this Actor reads it — paced, budgeted, with an honest user agent. No HTML scraping, no bot-check evasion, no personal data. Job adverts only.

How to scrape Remote OK jobs with this Actor

1. Open the Actor and press Start. With no input it returns the whole Remote OK feed, filtered to the rows that are genuinely remote — about 10 jobs out of the roughly 100 rows the board publishes, best-first.
2. Narrow it when you need to: search terms, hiring regions, seniority, a minimum salary, a maximum ghost-job risk, and maxItems as a hard cost ceiling.
3. Export the dataset as JSON, CSV or Excel, read it through the Apify API, or schedule the run and attach a webhook or an integration (Google Sheets, Make, Zapier, Slack) so new Remote OK jobs arrive on their own.

Related Actors from the same pipeline

• Remote Jobs Aggregator — six boards in one call, deduplicated, with salary parsing and ghost-job scoring
• Himalayas Remote Jobs Scraper — the board with real expiry dates and numeric timezone restrictions
• Remotive Jobs Scraper — a small, hand-curated board of remote tech jobs
• Arbeitnow Jobs Scraper — Germany and Europe, remote and on-site, the largest single feed
• We Work Remotely Jobs Scraper — company split from title, real expiry dates
• Jobicy Remote Jobs Scraper — the cleanest structured salary data for benchmarking
• Dice Jobs Scraper — US tech jobs with salary parsed to the cent

All eight share one schema, one ghost-job model and one set of filters, so a query written for this board runs unchanged against any of the others.

FAQ: scraping Remote OK jobs

Does Remote OK have an official API, and is it legal to scrape Remote OK jobs? Remote OK publishes a public, documented, unauthenticated JSON feed and this Actor reads it — paced, budgeted, with an honest user agent. No HTML scraping, no bot-check evasion, no personal data. Job adverts only.

How many Remote OK jobs can one run return? Remote OK serves its whole feed in one call, roughly 100 rows, and about 10 of those pass the remote check, so a run returns around 10 jobs. maxPagesPerSource has no effect here.

How often should I run this Remote OK scraper, and can I get only the new jobs? A daily schedule keeps the dataset current. id is stable across runs, so diffing today's dataset against yesterday's yields only the genuinely new Remote OK jobs, not a reshuffle; maxAgeDays set to 1 or 2 is the cheaper version of the same idea.

How do I get only fresh, still-open Remote OK jobs? Set maxGhostRisk to low and maxAgeDays to 14 or 21. Every row also carries ghostReason, the plain-language grounds for its rating, so you can apply your own rule instead.

What is a ghost job? A posting that is still published but no longer open: a filled role left up for pipeline, an evergreen "talent pool" advert, or a listing on a board that never expires anything. The ghostRisk band and freshness score flag them from what the board itself publishes — age, expiry dates, missing application links, evergreen phrasing — never from a model's guess.

Does it include salary data? Where Remote OK publishes pay, yes: salaryMin, salaryMax, salaryCurrency and salaryPeriod are parsed into numbers and the original wording stays in salaryRaw. Set salaryOnly to keep only rows with a published salary.

Do I need proxies, a login or an API key? No. Remote OK is read the way it asks to be read, and Apify runs the Actor for you; nothing to install and no credentials to manage.

Can I export Remote OK jobs to CSV, Excel or Google Sheets? Yes. Every run's dataset downloads as JSON, CSV or Excel from the Apify Console or API, and the Google Sheets integration writes rows straight into a sheet.

Is this a remote job scraper I can run as an API? Yes. Apify runs every Actor from its API as well as the Console: start a run over HTTP with the same JSON input shown above, or put it on a schedule, then read the finished dataset as JSON, CSV or Excel. The dataset is the output; there is no separate query endpoint, so a scheduled run plus a dataset read is the API.

Can an AI agent use this Remote OK scraper? Yes, through Apify's own MCP server, which exposes Store Actors as tools to Claude and other MCP clients. Nothing here is agent-specific: the agent sends the same JSON input and reads the same dataset.

How do I drop expired job listings? Set maxGhostRisk to low or medium and they are dropped before they are returned, so you do not pay for them. Every row that is returned carries ghostRisk (low, medium or high), ghostReason (the plain-language grounds, such as "board's own expiry date passed 3 days ago" or "posted 64 days ago") and freshness (0-1, decaying on a 21-day half-life, 0 once a published expiry date has passed), so you can apply your own rule after export instead. maxAgeDays drops anything older than N days, including rows with no posted date.

What does a Remote OK job row not contain? No visa-sponsorship flag, no applicant counts, no recruiter emails or any personal data, and no company size — Remote OK does not publish them in its feed, so they are not invented here. A blank seniority means the board never said; a blank salary means unpublished, not zero.

Want more than one board?

Remote Jobs Aggregator runs this same pipeline across six boards at once — Remote OK, Remotive, Himalayas, Arbeitnow, We Work Remotely and Jobicy — folding duplicates and recording which boards carry each job.

Measured while building it: those six boards barely overlap. Only 1 of 1,513 company+title pairs appeared on more than one. The aggregator is not about removing duplication — there is almost none — it is about getting six boards' worth of distinct jobs from one call.