Remote OK Jobs Scraper

The latest remote jobs on Remote OK — company, location, tags, USD salary range, apply link and full description — through Remote OK's public API, with every row linking back to Remote OK as the source. Leave the search empty for everything currently listed, or filter by words and tags. Schedule it and you get only the jobs posted since the last run.

Try it now — the input is already filled in. Press Start: the example searches (engineer, marketing) return 100 rows — 79 different remote jobs, since a job can match both — from Remote OK in about 20 seconds, for about $0.09.

title	company	salaryMin	salaryMax	tags
Senior React Full stack Developer	Lemon.io	80000	200000	dev, engineer, remote
Senior Software Engineer Case Execution	Pivotal Health	190000	220000	dev, front end, python
Customer Support Specialist	Ultimate Marketing	50000	90000	customer support

The salary is Remote OK's own USD range field (12 of these 79 jobs have one), never a number guessed from the text, and every row links back to Remote OK as the source. Scheduled, each run marks which jobs are new since the last one.

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. 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	as listed (location is where remote hires may live, often empty)
tags	Remote OK's tags (dev, design, marketing…)
salaryMin, salaryMax, salaryCurrency, salaryInterval	the USD yearly range when the employer gave one — null otherwise
description	the full job text
postedAt, applyUrl, source	when it was posted, the apply link, and "Remote OK"

Data comes from Remote OK's public API, which asks that every listing links back to Remote OK and names it as the source — each row's jobUrl is that link and source is "Remote OK"; please keep both if you republish. The API returns the latest jobs (about 100, plus up to 100 more for a one-word tag search), so schedule it to build up a history. | isNewSinceLastRun | true / false, or null on the first run (unknown, not "old") | | jobUrl | link to the job on Remote OK | | search | which of your searches returned it |

Input

Put one search per line in Searches (e.g. engineer) and optionally a Location (e.g. Europe). Or set the filters on the site and paste the result page into Search URLs (e.g. https://remoteok.com/remote-dev-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": "remoteok",
  "search": "engineer",
  "jobId": "1137407",
  "title": "VP Pricing & Packaging",
  "company": "Delinea",
  "location": "Redwood City",
  "remote": true,
  "tags": [
    "design",
    "saas",
    "salesforce",
    "infosec",
    "vfx",
    "dev",
    "…"
  ],
  "salaryMin": 300000,
  "salaryMax": 340000,
  "salaryCurrency": "USD",
  "salaryInterval": "year",
  "description": "About Delinea:\nDelinea is a pioneer in securing human and machine identities through intelligent, centralized authorization, empowering organizations to seamles…",
  "postedAt": "2026-09-19T00:00:16.000Z",
  "jobUrl": "https://remoteOK.com/remote-jobs/remote-vp-pricing-packaging-delinea-1137407",
  "applyUrl": "https://remoteOK.com/remote-jobs/remote-vp-pricing-packaging-delinea-1137407",
  "source": "Remote OK",
  "countryCode": null,
  "employmentType": null,
  "seniority": "executive",
  "employmentTypes": [],
  "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: 11 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.

Don't know which companies to watch? The Greenhouse Jobs Scraper searches 4,800 companies by job title — no company names needed — and reports exactly which matching roles are new or closed each run.

For AI agents

For a fast answer call with {"searches": ["engineer"], "maxJobsPerSearch": 20} — a few seconds. The defaults (up to 200 jobs) 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 · Instahyre · Reed · InfoJobs · XING · Dice · HelloWork · Computrabajo · Foundit · jobs.ch · Arbeitsagentur · Arbeitnow · Remote OK · We Work Remotely.

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