Remote OK Jobs Scraper · Salary & tag filters · $0.8/1K
Pricing
$0.80 / 1,000 results
Remote OK Jobs Scraper · Salary & tag filters · $0.8/1K
Collect recent Remote OK remote jobs by skill tag, keyword, location and minimum salary for job boards, recruiting, salary research and market analysis. Full descriptions, pay ranges, tags, dates and links. No login. $0.8/1K jobs.
Pricing
$0.80 / 1,000 results
Rating
0.0
(0)
Developer
MLG Data
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
5 days ago
Last modified
Categories
Features
Share
Remote OK Jobs Scraper
Scrape Remote OK jobs from its public recent-listings feed and export the results as CSV or JSON. This Remote OK API alternative turns job records into consistent rows with titles, descriptions, locations, salary ranges, tags, posting dates, verification status, and links back to the original listings.
Use one run for a snapshot of recent jobs or request several skill tags in the same run. The actor removes duplicate listings across tags, applies the optional filters, and stops at the result limit you choose. Its dataset is suited to job search, research, and scheduled updates without requiring a login.
What data can you extract from Remote OK?
Each dataset item represents one job. The field names below are the exact keys in the JSON output. The source does not publish every value for every listing, so an unavailable value is null. Array fields remain arrays and salary amounts remain numbers in JSON.
| Field | Description | Example |
|---|---|---|
id | Stable identifier from the public feed | "1136795" |
source | Short source identifier | "remoteok" |
sourceUrl | Link to the original Remote OK job listing | "https://remoteok.com/remote-jobs/…" |
applyUrl | Application link supplied by the feed; often the listing page | "https://remoteok.com/remote-jobs/…" |
title | Published job title | "Senior Software Engineer Case Execution" |
description | Full job description converted from markup to readable text | "Responsibilities and qualifications…" |
type | Employment type if the feed begins publishing it | null |
workMode | Work arrangement represented by this board | "remote" |
location | Location text on the job, if present | "New York City" |
experienceLevel | Experience category if the feed begins publishing it | null |
salaryMin | Published minimum annual salary in USD | 190000 |
salaryMax | Published maximum annual salary in USD | 220000 |
currency | Salary currency when an amount is published | "USD" |
salaryPeriod | Period for a published salary | "year" |
companyName | Employer display name | "<redacted>" |
companySlug | Slug derived from the employer display name | "<redacted>" |
companyUrl | Employer website if the feed supplies one | null |
companyLogoUrl | Logo link if the feed supplies one | null |
tags | Skill and category tags on the job | ["python", "backend"] |
markets | The same source tags for combined job datasets | ["python", "backend"] |
postedAt | Posting timestamp supplied by the feed | "2026-08-16T00:00:03+00:00" |
expiresAt | Expiration date if the feed begins publishing it | null |
scrapedAt | Time this run collected the feed, in UTC | "2026-09-27T03:58:51+00:00" |
dataSource | Readable attribution name | "Remote OK" |
dataSourceUrl | Source home page for attribution | "https://remoteok.com" |
verified | Explicit verification flag, or null when not supplied | null |
original | Explicit original-listing flag, or null when not supplied | null |
The output includes both tags and markets so the same job can fit pipelines that expect either field. These arrays contain the same values; they are not two different classifications. companySlug is a convenience value generated from the employer name. The feed does not currently provide a dependable employer website, expiration date, experience category, or employment type, so those fields are null rather than guessed.
The applyUrl value comes directly from the feed. On many jobs it points to the Remote OK listing itself, where the application path can be followed. Do not assume it is an external application form. Keep sourceUrl with any export so a reader can return to the listing and so published uses can provide attribution to Remote OK.
How to scrape Remote OK
- Leave
tagsempty for the general recent feed, or add one or more skill tags such aspythonanddesign. - Optionally enter a keyword, location text, minimum salary, or verification preference. Choose
maxResultswhen you need a bounded dataset. - Run the actor and inspect the resulting dataset. Each item is one unique job across all requested tags.
- Download the dataset as CSV or JSON, or use its dataset link in a scheduled workflow.
The default input requests the general recent feed. A tag creates a separate feed request, so asking for several tags can broaden coverage beyond a single feed window. The actor checks the job identifier before output: a listing that appears under several tags is emitted once. Filters are applied after the feed is received; a narrow keyword does not cause the source to search its full historical archive.
Input
| Name | Type | Default | Description |
|---|---|---|---|
tags | string array | [] | Fetch a recent feed for each skill or category tag. Empty means the general feed. |
keywordFilter | string | "" | Case-insensitive substring match across title, employer name, and tags. |
locationFilter | string | "" | Case-insensitive substring match against the listed location. |
minSalary | integer | 0 | Remove jobs whose published maximum annual salary is below this USD amount. Jobs without salary data remain. |
includeUnverified | boolean | true | When false, keep only jobs explicitly marked verified by the source. |
filterNonTech | boolean | false | Remove a short list of clearly non-technical titles. This is a title rule, not a comprehensive job classifier. |
maxResults | integer | 0 | Stop after this many unique matching jobs across all tags. Zero means no actor-side cap. |
webhookUrl | string | "" | Optional receiving endpoint for output batches after collection. |
webhookSecret | string | unset | Optional secret sent in the X-Scraper-Secret header with webhook batches. |
proxyConfiguration | object | proxy enabled | Network settings for fetching the public feed. |
A realistic run that collects up to 50 Python-tagged jobs:
{"tags": ["python"],"maxResults": 50}
This input produced 50 jobs in the validation run. Every returned item had an ID, source link, title, description, employer display name, posting date, and at least one tag. The exact jobs change as the public feed changes, so a new run will have different records or ordering.
For a broader category comparison, set tags to several values and keep maxResults at zero or above the combined number you want. If you need strict salary completeness, inspect salaryMin and salaryMax after export: the minSalary filter intentionally retains jobs with no reported salary. This behavior avoids silently removing potentially relevant listings just because compensation was omitted.
Output example
This abbreviated item comes from the successful 50-job validation run. The employer identity, links, and description are shortened here; the dataset contains the full source values and a working listing link.
{"id": "1136795","source": "remoteok","sourceUrl": "https://remoteok.com/remote-jobs/…-1136795","applyUrl": "https://remoteok.com/remote-jobs/…-1136795","title": "Senior Software Engineer Case Execution","description": "About <redacted>…","type": null,"workMode": "remote","location": "New York City","experienceLevel": null,"salaryMin": 190000,"salaryMax": 220000,"currency": "USD","salaryPeriod": "year","companyName": "<redacted>","companySlug": "<redacted>","companyUrl": null,"companyLogoUrl": null,"tags": ["dev", "front end", "python", "customer support", "design", "admin", "exec", "senior", "ops", "sys admin", "medical", "engineer", "backend", "digital nomad"],"markets": ["dev", "front end", "python", "customer support", "design", "admin", "exec", "senior", "ops", "sys admin", "medical", "engineer", "backend", "digital nomad"],"postedAt": "2026-08-16T00:00:03+00:00","expiresAt": null,"scrapedAt": "2026-09-27T03:58:51.669191+00:00","dataSource": "Remote OK","dataSourceUrl": "https://remoteok.com","verified": null,"original": null}
Salary amounts in this example are source values. Many other jobs have null salary fields. The timestamps are separate: postedAt is the source's posting time and scrapedAt is when this actor read the feed. Comparing repeated snapshots by id makes it possible to spot newly appearing jobs without treating an existing listing as new each time it is collected.
Use cases
- Job board operators can add recent remote openings to a catalog and retain the original listing link for attribution and verification.
- Recruiters can watch selected skill tags, remove duplicate jobs across categories, and review new openings in their area of interest.
- Salary researchers can collect the subset of jobs with published compensation and compare ranges by tag or listed location.
- Career advisors can build shortlists around a skill and a location phrase, then inspect the full description on the linked listing.
- Market analysts can save daily snapshots and observe how the visible recent feed changes over time. A snapshot reflects the available feed, not every job ever posted.
- Workflow owners can send output batches to an HTTPS endpoint when a run completes, with an optional shared secret header.
For comparisons over time, store the run date and deduplicate on id. A single listing can appear under several categories and may remain visible across many daily runs. The posting date identifies the job's source timestamp; it does not mean the listing was first discovered during your most recent run.
How much does it cost to scrape Remote OK?
The actor price is $0.80 per 1,000 output jobs, with platform usage included. Charges scale with the number of dataset items produced. At that rate, 50 jobs cost $0.04, 100 jobs cost $0.08, and 1,000 jobs cost $0.80. These are price examples, not a promise that a single request contains 1,000 jobs.
The general feed exposes about 100 recent jobs. A tagged feed also exposes about 100 recent jobs, and overlap between tags reduces the combined unique count. A run with several tags may therefore produce fewer items than the sum of its feed sizes. Set maxResults to control the upper bound on dataset items and inspect the actual item count after each run. If a budget cap applies to the run, output stops when that cap is reached.
Tips for best results
Start with the general feed to see which tags are actually appearing in current listings. Use the exact skill or category text you care about in tags; each tag is requested separately. For a broad export, include several distinct tags rather than many near synonyms, since similar tags may return the same jobs. The actor deduplicates them by source ID, so duplicates do not inflate the output count.
Use keywordFilter for a quick refinement after category selection. It matches a substring in the title, employer name, or tag values. It does not search the full description, and it cannot reveal jobs outside the recent feed returned by the source. locationFilter checks only the source's location field. It will exclude a job whose location field is empty even if the description mentions a country or city.
Choose a small maxResults for inspection, then raise it for scheduled collection. A run with a 50-job limit is enough to confirm your tag and output format. If you want the full visible feed, leave the limit at zero. For broader tracking, schedule repeated runs and compare IDs from one dataset to the next. The source changes continuously, so repeated snapshots are more useful than assuming an older listing can be reached by pagination.
Set includeUnverified to false only when the explicit verification marker matters to your workflow. The feed omits that marker on many listings; those jobs are excluded in strict mode. filterNonTech removes only a small set of obvious non-technical title phrases. Inspect results yourself if the distinction between technical and non-technical roles is important to your analysis.
Limits
The public feed is a recent window of roughly 100 jobs per request. An offset parameter returned the same job IDs during source checks, so this actor does not claim historical pagination. Adding tags can reach other recent category windows, but it does not guarantee a complete archive. Result counts also depend on how many jobs meet your filters and how much categories overlap.
The source does not consistently provide salary, verification, logo, or location information. In the observed general feed, salary appeared on a minority of jobs and verification was explicitly marked on only a few. The actor keeps missing values null. It does not invent an employment type, an employer website, an expiration date, or an experience level. When a salary is present, the output labels it in USD per year; verify compensation details on the linked listing before using them in a decision.
The site may revise its feed format, categories, or access rules. A run can also return fewer results if a tag has little recent activity. Webhook delivery happens after dataset output. If the receiving endpoint is unavailable, the dataset still contains the collected jobs and a warning appears in the run log. A webhook response does not change the source data or the dataset item count.
Use with automated workflows
A recurring workflow can ask for: “Collect up to 50 recent Python jobs, keep the source links, and report which IDs were not present yesterday.” Another can ask for: “Collect recent design and operations jobs, show the published salary ranges, and list rows whose location is blank.” Both tasks use the actor's structured fields and work best when the workflow stores previous snapshots for comparison.
For a webhook pipeline, provide an HTTPS webhookUrl and, if your receiver uses one, a webhookSecret. The actor sends JSON objects with a jobs array in batches of up to 50. The secret is placed in the request header, not in dataset items. The receiver should use the job id to avoid duplicate processing across repeated runs.
FAQ
Is it legal to collect these jobs?
The actor reads publicly available job data without a login. Your use still needs to respect the site's terms, attribution requirements, privacy law, and the rules that apply in your jurisdiction. Link back to the original Remote OK listing when displaying a job elsewhere. Avoid using any contact details or personal information for unrelated outreach.
Do I need to configure a proxy?
The default network setting is ready to use. In the observed source checks, the public JSON feed responded without a challenge. If the source blocks a session or rate limits requests, the shared fetch layer can rotate the session and escalate its connection method. Most users can leave proxyConfiguration at the default.
How fast is a run?
The actor makes one feed request when no tags are supplied, or one request per distinct tag. The verified 50-job run completed on the hosted platform in about 21 seconds, including startup and output. Larger tag lists, network retries, or a slow webhook receiver can take longer. The public feed size, rather than an actor pagination loop, bounds the work per tag.
Can I schedule and monitor it?
Yes. Schedule repeated runs and compare result IDs across datasets. A daily snapshot is often a better fit for a changing recent feed than a one-time export. Monitor item count and required fields; a sudden drop can mean fewer matching jobs, a source change, or a network problem. Read the run log when output is unexpectedly empty.
Can I export the results to a spreadsheet?
Yes. Download the default dataset as CSV for a spreadsheet or as JSON for a data pipeline. Each output item becomes a row. Nested tag arrays may be represented as text in a CSV export, while JSON preserves their array shape. Keep the source link and job ID columns when merging exports from different dates.
Why is a field empty?
The public feed omits several fields on some or all jobs. An empty location, salary, or logo means the value was not supplied for that listing. verified: null means the source did not provide an explicit boolean, not that the listing failed a separate verification check. Source pages can also change after the run, so inspect the linked listing for the latest details.
Can I collect every older Remote OK job?
No. The public JSON feed exposes a recent window and the tested offset parameter did not change its IDs. Tagged requests expand the visible categories, and scheduled snapshots preserve what was visible on each run, but this actor does not promise full historical coverage. Use postedAt and scrapedAt together when reporting the time span of an export.
Integrations
Use the default dataset link through the platform API, download CSV or JSON, set a schedule, or connect a webhook receiver. A receiving service can process each jobs batch and upsert records by id. Keep the Remote OK source link in downstream records, especially if listings are displayed publicly. The output fields remain stable even when an optional source value is missing, which makes incremental imports easier to maintain.
Use with AI agents (MCP)
Add this actor to any MCP client (Claude, Cursor, VS Code, n8n and others) with one URL:
https://mcp.apify.com?tools=mlg14/remoteok-scraper
The actor returns one dataset item per Remote OK job: title, company, location, salary range, tags, posting date, description and listing link. Set a small maxResults to keep runs bounded, and check the dataset is not empty before using it.
Prompt 1: "Find 20 recent Python jobs on Remote OK."
{"tags": ["python"],"maxResults": 20}
Prompt 2: "Get Remote OK jobs that pay at least $120,000 a year."
{"minSalary": 120000,"maxResults": 20}
Prompt 3: "List recent senior design jobs on Remote OK open to Europe."
{"tags": ["design"],"keywordFilter": "senior","locationFilter": "Europe","maxResults": 20}
Support
Open an issue on the Issues tab; we reply within 24h and add fields on request.