Remote Jobs Aggregator: Remote OK + Jobicy in One List avatar

Remote Jobs Aggregator: Remote OK + Jobicy in One List

Pricing

$1.00 / 1,000 jobs

Go to Apify Store
Remote Jobs Aggregator: Remote OK + Jobicy in One List

Remote Jobs Aggregator: Remote OK + Jobicy in One List

The newest remote jobs from Remote OK and Jobicy in one deduplicated list, with salary, location, tags and the apply link. Filter by keyword, location, minimum salary and posting date, or get only new jobs on a schedule. $0.001 per job ($1 per 1,000); duplicates and filtered jobs are free.

Pricing

$1.00 / 1,000 jobs

Rating

0.0

(0)

Developer

fecklesspleb

fecklesspleb

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

7 hours ago

Last modified

Categories

Features

Limited permissions

Share

Remote Jobs Aggregator API: Remote OK and Jobicy in one deduplicated feed

Remote Jobs Aggregator pulls remote job listings from two boards that publish public feeds (the Remote OK API and the Jobicy API) and returns them as one clean JSON dataset. The same job posted on more than one board is merged into a single record, with the other copies listed in alsoListedOn. Filter by keyword, location, salary, date, or Jobicy region and industry, and use only-new mode (onlyNewJobs) on scheduled runs to get only jobs you haven't seen. Each item carries the attribution line the source asks for. You pay $0.001 per job written to the dataset; filtered-out jobs and merged duplicates are free. We Work Remotely is no longer read, because its API terms forbid building a job search service: if a saved input still lists weworkremotely, the run ignores it, writes one free status item, and does not fail.

Who it's for

  • Remote job boards and newsletters that want a deduplicated daily feed with source attribution included.
  • Job seekers who want one list across two remote boards, filtered by stack and minimum salary.
  • Slack and Discord community owners posting new remote roles to a channel.
  • Researchers tracking remote hiring by category, region or published pay.

What data you get

One dataset item per job:

FieldWhat it holds
id, uidThe job's ID on its board, and a stable key source:id.
source, sourceNameremoteok or jobicy, and the board's display name.
title, companyName, companyLogoJob title, company and logo URL when the board gives one.
location, isRemoteRegion or location text as published (e.g. Anywhere, USA).
employmentType, employmentTypeRawThe board's job type normalized to FULL_TIME, PART_TIME, CONTRACTOR, TEMPORARY, INTERN, VOLUNTEER, PER_DIEM, OTHER (a value that fits none of them, such as Permanent) or null; and the board's own text, e.g. Full-Time. When a board lists several types the more specific one wins (Full-Time, Contract is CONTRACTOR).
seniority, category, tagsAs published by the board (not every board has every field).
postedAt, expiresAtISO 8601 timestamps.
url, applyUrlJob page and apply link.
salaryMin, salaryMax, salaryCurrency, salaryPeriod, salaryText, salarySourcePay when the board gives it (salarySource: "source") or when a range is found in the description ("description").
descriptionText / descriptionHtmlFull description, if includeDescription is on. Personal e-mail addresses, phone numbers and "Recruiter: name" lines are replaced with placeholders unless redactContacts is off.
attributionThe credit line the source asks for, e.g. "Job data from Jobicy (https://jobicy.com). Credit Jobicy and send Apply clicks to the job URL."
alsoListedOnOther boards where the same job was found (when dedupe is on).
dedupeKeyHash of company, title and first location (same recipe and values as the ATS Jobs Scraper's dedupeKey).
crossSourceKeyHash of company (legal form such as Inc or GmbH removed) and title, with no location. The same job found by the ATS Jobs Scraper or the Workday Jobs Scraper gets the same key. null when the company or title is missing.
scrapedAtWhen the run read the job.

Sample item (real output, run without descriptions):

{
"id": "157680",
"source": "jobicy",
"sourceName": "Jobicy",
"title": "Staff Software Engineer, Containers",
"companyName": "Chainguard",
"companyLogo": "https://jobicy.com/data/server-nyc0409/galaxy/mercury/2025/06/e4b6aacf-221.jpeg",
"location": "Canada, Germany, UK, USA",
"isRemote": true,
"employmentType": "FULL_TIME",
"employmentTypeRaw": "Full-Time",
"seniority": "Senior",
"category": "Software Engineering",
"tags": [],
"postedAt": "2026-10-28T16:55:29+00:00",
"expiresAt": null,
"url": "https://jobicy.com/jobs/157680-staff-software-engineer-containers",
"applyUrl": "https://jobicy.com/jobs/157680-staff-software-engineer-containers",
"salaryMin": 205000,
"salaryMax": 231000,
"salaryCurrency": "USD",
"salaryPeriod": "YEAR",
"salaryText": null,
"salarySource": "source",
"attribution": "Job data from Jobicy (https://jobicy.com). Credit Jobicy and send Apply clicks to the job URL.",
"uid": "jobicy:157680",
"alsoListedOn": [],
"scrapedAt": "2026-10-29T01:03:49.025052+00:00"
}

How to use it

Every input is optional. An empty input runs in default mode: it returns 8 jobs, taking turns between Remote OK and Jobicy (usually the 4 newest from each; if one board has fewer, or Jobicy is skipped for its hourly limit, the other fills the rest), without descriptions, and the log says Default mode: no sources or filters given, returning up to 8 of the newest jobs from remoteok, jobicy without descriptions. That costs at most $0.008. The default used to include We Work Remotely; that board was removed, so the 8-job cap is now filled from the two remaining boards (still $0.008, under the $0.01 public-default cap). Raise Max jobs in total (0 = no limit) and turn on Include description for a full pull. Click Start, then export from the Output tab.

Input fieldLabelNotes
sourcesSourcesremoteok, jobicy. Empty = both. weworkremotely is still accepted so old saved inputs start, but it is not read; a free status item explains why.
keywordsKeywords (any)Matches title, tags or category, case-insensitive.
excludeKeywordsExclude title keywordsDrops jobs whose title contains any of these.
searchInDescriptionMatch keywords in description tooDefault false.
locationsLocations (any)Matches location or region text, e.g. USA, Europe, Anywhere.
requireSalaryOnly jobs with a salaryDefault false.
minSalaryUsdMinimum yearly salary (USD)Compares the top of the range, converted to a rough yearly USD figure. Jobs without a salary are dropped when this is set.
postedWithinDaysPosted within last N days1–365. Jobs without a posting date are kept.
wwrCategoriesWe Work Remotely categoriesNo longer used. We Work Remotely is not read. A value here has no effect; the field is kept so old saved inputs still start.
jobicyGeoJobicy regione.g. usa, europe, canada.
jobicyIndustryJobicy industrye.g. dev, marketing, design-multimedia.
jobicyTagJobicy tagOptional. Passed unchanged to Jobicy's API as tag. Jobicy's API docs describe tag as a keyword search: the API page says it is applied to the job title; the OpenAPI spec (2.2.19) says across available job content and accepts 3–50 characters (ASCII). This Actor does not check the value or filter on it. Empty = not sent. No effect on Remote OK.
dedupeMerge duplicates across boardsDefault true. Same company and title (normalized) = one job; the newest copy is kept.
onlyNewJobsOnly new jobsDefault false. Seen jobs are remembered for 120 days.
stateStoreNameState store nameDefault remote-jobs-aggregator-state. Also stores the Jobicy hourly limit.
includeDescriptionInclude descriptionDefault false (was true before GAP8).
descriptionFormatDescription formattext, html or both.
redactContactsRemove contact details from descriptionsDefault true. Replaces personal e-mail addresses (shared mailboxes such as jobs@ or careers@ are kept), phone numbers and "Recruiter: name" lines in descriptions. Rule-based, so unusual formats can be missed.
maxTotalJobsMax jobs in totalDefault 8. 0 = no limit. With a cap and no filters, each board stops after twice the cap, so capped runs are fast. Boards take turns up to the cap: one matching job from each board in sources order (Remote OK first by default), newest first within each board. When a board runs out, the other fills the rest.

Example input (Python or backend jobs paying at least $100k a year, posted in the last week, only new ones):

{
"sources": [
"remoteok",
"jobicy"
],
"keywords": [
"python",
"backend"
],
"minSalaryUsd": 100000,
"postedWithinDays": 7,
"onlyNewJobs": true
}

Things to know:

  • Jobicy hourly limit. Jobicy asks API users to poll at most once an hour. If Jobicy was read less than 60 minutes ago (tracked in the state store), it is skipped for that run with a log message, and the other boards still run.
  • Jobicy page size. Jobicy is asked for 100 jobs per request (count=100), the limit on Jobicy's API page; its OpenAPI spec (2.2.19) allows up to 200. More jobs come from Jobicy's cursor pages (same filters, up to 50 requests), so a maxTotalJobs above 100 is still reached when Jobicy has enough matching jobs. At most 5,000 Jobicy jobs are read per run. The default 8-job run makes one Jobicy request.
  • Salary periods. Some boards publish hourly or monthly pay. Check salaryPeriod before comparing numbers. Remote OK's salary fields are meant to be yearly USD, but some employers enter an hourly rate there; a Remote OK range whose top is $500 or less is labelled HOUR, everything else YEAR.
  • Text encoding. Remote OK sends some titles, company names, locations and descriptions with garbled characters (for example ’ instead of an apostrophe, or México). The Actor repairs these before writing the item; text that is already correct is left as is.
  • Rough salary conversion. minSalaryUsd converts to a yearly figure with fixed rough exchange rates (USD, EUR, GBP, CAD, AUD); it is a filter, not an accurate conversion.
  • RUN_SUMMARY in the default key-value store shows jobs pushed, duplicates merged, HTTP requests, stoppedByCostLimit and per-source counts.

Chain with other jobs Actors

This Actor is one of four jobs Actors that share one job format and one set of keys (ATS Jobs Scraper, Workday Jobs Scraper, Career Site Jobs Feed). You can pass the dataset of a run of any of them in datasetId; this run then skips the jobs that are already there. All four inputs below are optional and off by default: without them a run behaves exactly as before.

InputDefaultWhat it does
datasetIdemptyID of a dataset from an earlier run (this Actor or another jobs Actor). Its job items are read before any board. For an Apify integration, put {{resource.defaultDatasetId}} here. When empty and the run was started by an Apify integration, the integration payload's resource.defaultDatasetId is tried.
datasetModemergemerge: the earlier jobs are copied into this run's dataset first (free, no job event), then the new jobs follow, so the dataset is the combined, deduplicated list. exclude: nothing is copied; the dataset has only the new jobs.
datasetMatchByuiduid: a job counts as already there when the same posting (same uid) is in the earlier dataset. uidOrCrossKey: also when the same company and title (crossSourceKey) is there from any source; this can merge one title posted in several cities.
suiteOutputfalsetrue: every job item has all fields of the shared format in the shared order (missing ones null or []). Values are not changed. Jobs copied from datasetId are kept as they were.
  • A job that is already in the earlier dataset is dropped before it is pushed, so it is never charged. Only new jobs are charged (one job event each, same price as today) and only new jobs count toward maxTotalJobs.
  • Status items and expired or unresolved records in the earlier dataset are not copied. At most 100,000 items are read.
  • datasetId asks Apify for read-only access to that one dataset, so chaining works with this Actor's limited permissions; the run gets no access to your other storages. Only a dataset given in datasetId is granted this way, so the payload fallback may not be readable; give the dataset in datasetId.
  • If the dataset cannot be read, or datasetMode or datasetMatchBy has an unknown value, the run ends with one free status item (status "error") and no jobs, as for other invalid input in this Actor.
  • onlyNewJobs and its state (remote-jobs-aggregator-state) work as before and are applied too.
  • The run summary (RUN_SUMMARY in the key-value store) gets a previousDataset block with the counts read, copied and skipped.

Pricing

This Actor uses pay-per-event pricing: $0.001 per job written to the dataset. That is $1.00 per 1,000 jobs. There is no separate start fee in this Actor's pricing (as listed on October 28, 2026; the Pricing tab on the Store page is the source of truth).

You are charged only for jobs that end up in your dataset. Jobs removed by your filters, jobs skipped in only-new mode and duplicates are not charged.

ExampleJobsCost
Default run (empty input)8$0.008
Daily new remote jobs, filtered to one stack40$0.04
One full pull of both boards, maxTotalJobs 0 (illustration)600$0.60
A month of daily only-new runs at 40 new jobs a day1,200$1.20

Rows are illustrations, not measured board sizes.

Worked example: 1,000 jobs × $0.001 = $1.00.

To cap spend, set Maximum cost per run in the run options (or maxTotalChargeUsd via the API). The Actor stops cleanly when the next job would go over the limit and records stoppedByCostLimit: true in the run summary.

How it compares

What this Actor is built for:

  • Two boards with public feeds (Remote OK and Jobicy) in one dataset.
  • Cross-board dedupe, salary and region filters, an attribution field and only-new-jobs mode.

Remote OK and Jobicy also publish their feeds directly. Calling them yourself is fine if you handle dedupe, salary parsing, the Jobicy rate limit and attribution.

We deliberately read only boards that publish a public feed or API for reuse. Other remote boards are not included.

Integrations and API

The actor ID is fecklesspleb/remote-jobs-aggregator (in API URLs: fecklesspleb~remote-jobs-aggregator).

n8n, Make and Zapier. Each has an Apify integration with a "run Actor" action. Pick fecklesspleb/remote-jobs-aggregator, paste the input JSON shown below, then read the results from the run's default dataset in the next step. To process only new jobs on a schedule, turn on Only new jobs and run it from a schedule (Apify Schedules or a trigger in your automation tool).

Webhooks and schedules. Apify Schedules can run the Actor on a cron, and a webhook on "run succeeded" can call your own endpoint with the run ID.

HTTP API. Run the Actor and get the items back in one call. This waits for the run to finish, so use it for small runs:

APIFY_API="https://api.apify.com/v2/actors"
curl -X POST "$APIFY_API/fecklesspleb~remote-jobs-aggregator/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"sources": ["remoteok", "jobicy"], "keywords": ["python", "backend"], "minSalaryUsd": 100000, "postedWithinDays": 7, "onlyNewJobs": true}'

Python (pip install apify-client):

from decimal import Decimal
from apify_client import ApifyClient
client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("fecklesspleb/remote-jobs-aggregator").call(
run_input={
"sources": [
"remoteok",
"jobicy"
],
"keywords": [
"python",
"backend"
],
"minSalaryUsd": 100000,
"postedWithinDays": 7,
"onlyNewJobs": True
},
max_total_charge_usd=Decimal("5"), # optional spend cap
)
# apify-client 3.x returns a Run object; on 1.x/2.x use run["defaultDatasetId"]
for item in client.dataset(run.default_dataset_id).iterate_items():
print(item)

JavaScript / Node.js (npm install apify-client):

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fecklesspleb/remote-jobs-aggregator').call(
{
"sources": [
"remoteok",
"jobicy"
],
"keywords": [
"python",
"backend"
],
"minSalaryUsd": 100000,
"postedWithinDays": 7,
"onlyNewJobs": true
},
{ maxTotalChargeUsd: 5 }, // optional spend cap
);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Results can also be exported from the dataset as JSON, CSV, Excel, XML or RSS from the Apify Console or the dataset API.

Use with AI agents / MCP

AI agents can run this Actor as a tool through Apify's MCP server. Add this server URL to your MCP client (Claude, Cursor, VS Code, OpenAI Agents SDK, LangChain and others) and sign in with OAuth, or send your Apify token as Authorization: Bearer <token>:

https://mcp.apify.com?tools=fecklesspleb/remote-jobs-aggregator

The tool is named fecklesspleb--remote-jobs-aggregator. Agents can also find it with search-actors and run it with call-actor. The run returns a dataset ID; read the jobs with get-dataset-items, and pass fields (for example title,companyName,location,salaryMin,salaryMax,salaryPeriod,url) to keep the response small.

Minimal tool input:

{"sources": ["remoteok", "jobicy"], "keywords": ["python"], "maxTotalJobs": 3}

A real output item (from Jobicy) is in the sample earlier on this page. The previous worked example for this input used a We Work Remotely row; that board is no longer read, so that sample was removed rather than replaced with an unverified item.

Tips for agents:

  • Cost is $0.001 per job returned. Set maxTotalJobs, and maxTotalChargeUsd in the run options (callOptions in call-actor), to cap a run.
  • Keyword and location filters are case-insensitive substring matches, so prefer distinctive words.
  • Check salaryPeriod before comparing salaries; some boards publish hourly or monthly pay.
  • Link back to url and keep attribution when you show jobs to people; the boards ask for it.
  • A row with "type": "status" is a free, uncharged note, and its message says why: "No jobs: N/M sources could not be read ... See RUN_SUMMARY." (status "warning"; details in RUN_SUMMARY in the run's key-value store) or "Invalid input, nothing was fetched or charged: ..." (status "error"; error says what to fix).

Common searches this Actor answers

  • remote jobs API in JSON
  • Remote OK API without code
  • Jobicy remote jobs feed
  • remote developer jobs with salary
  • a daily list of new remote jobs in Google Sheets or Slack
  • deduplicated remote job listings from several boards

FAQ

What happens if a job source is down, slow or blocks the run? The run still ends SUCCEEDED. Each request has a 10 s timeout in the demo (40 s otherwise) and only a couple of retries, and no new request is started about 40 s into the demo or 20 s before the run's timeout. If nothing could be read, the dataset gets one free record such as {"type": "status", "status": "warning", "message": "No jobs: 2/2 sources could not be read (...). See RUN_SUMMARY.", "error": "..."} with the reason, and the details are in RUN_SUMMARY. This record is not charged; filter on type if you only want data rows.

Is there a Remote OK API I can use without writing code? Yes: Remote OK publishes a free JSON API, and this Actor wraps it together with Jobicy, so you can call one endpoint and get filtered, deduplicated jobs. Remote OK asks that you link back to the job URL and mention Remote OK as the source when you show its jobs. The attribution field carries that note on every item.

How are duplicates detected? Two jobs are treated as the same when the normalized company name and title match. The newest copy is kept and the others are listed in alsoListedOn. Turn dedupe off to keep every copy.

How do I get only worldwide or only US jobs? Use locations (e.g. Anywhere, Worldwide, USA), which matches each board's location text. For Jobicy, jobicyGeo filters at the source. Boards word locations differently, so test your list on a small run first.

Why did Jobicy return nothing? Most likely it was read less than an hour ago and skipped to respect Jobicy's hourly limit. The log says so. Run again after an hour.

Can I post new remote jobs to Slack or a Google Sheet? Yes. Schedule the Actor with onlyNewJobs on, and use the Apify integration in n8n, Make or Zapier to send each new item on.

Do I need an API key or login? No. The Actor reads public endpoints and needs no account on the source site. You only need an Apify account to run it. It obeys robots.txt and rate-limits requests per host. robots.txt is checked again on every redirect, so a URL that redirects to a disallowed path or another host is not followed. If a host's robots.txt can't be read (a server error, a network failure or a page that isn't a robots file), that host is skipped for the run and RUN_SUMMARY says why. A missing robots.txt means no rules.