# Remote Jobs Aggregator: Remote OK + We Work Remotely (`ctriolab/remote-jobs-aggregator`) Actor

Remote job postings from the official public feeds of Remote OK and We Work Remotely in one format: title, company, allowed locations, parsed salary, posted date, category, level, tags and URL. Cross-board duplicates removed, daily only-new mode.

- **URL**: https://apify.com/ctriolab/remote-jobs-aggregator.md
- **Developed by:** [Ctrio Lab](https://apify.com/ctriolab) (community)
- **Categories:** Jobs
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 84.6% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.56 / 1,000 jobs

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Remote Jobs Aggregator: Remote OK + We Work Remotely

Get live **remote job postings** from **Remote OK** and **We Work Remotely** in one clean table. Every row has the same fields whatever board it came from: title, company, allowed locations, parsed salary (min, max, currency, period), posted date, category, experience level, tags and the original job URL. Jobs listed on both boards are merged, so you get each job once.

Only official public feeds are used: the Remote OK API and the We Work Remotely public RSS feed. Both boards publish them for reuse with credit. No login, no proxy, no captcha, no HTML scraping, so runs are fast (about 20 seconds) and cheap.

### What you get

| Field | Example |
|---|---|
| `title` | Senior Backend Engineer |
| `company` | DuckDuckGo |
| `location` | Anywhere in the World |
| `locations` | \["USA", "Canada"] |
| `worldwide` | true |
| `remote` | true |
| `category` | software-development |
| `experienceLevel` | senior |
| `employmentType` | Full-Time |
| `salary` | $140,000 - $200,000 |
| `salaryMin`, `salaryMax` | 140000, 200000 |
| `salaryCurrency`, `salaryPeriod` | USD, year |
| `postedAt`, `expiresAt` | 2026-10-25T07:31:02.000Z |
| `url` | https://weworkremotely.com/remote-jobs/... |
| `source`, `sourceName` | weworkremotely, We Work Remotely |
| `alsoListedOn` | \[{ "source": "remoteok", "url": "https://remoteok.com/remote-jobs/..." }] |
| `tags` | \["python", "backend"] |
| `descriptionText` | full text (optional) |

### How to use

1. Pick the boards (both by default).
2. Add filters if you want: keywords (title and tags), categories, allowed locations (e.g. `US`, `Europe`, `Germany`, `APAC`), experience level, minimum yearly salary, posted within (e.g. `7 days`).
3. Run. For a daily feed, turn on **Only new jobs**, give the search a **watchlist name** and schedule the Actor once a day.

Example input:

```json
{
  "keywords": ["python", "data engineer"],
  "locations": ["Europe"],
  "postedWithin": "7 days",
  "minSalary": 60000,
  "includeJobsWithoutSalary": true
}
```

Wrong inputs (unknown board or category, unreadable period like "last week") stop the run at once with a clear message, before any job is fetched or charged.

### Filters in detail

- **Keywords**: a job matches if its title or any tag contains one of the phrases (case-insensitive). Exclude keywords drop jobs by title.
- **Categories**: one shared list (software development, design, DevOps, product, data, customer support, sales and marketing, management and finance, other). We Work Remotely categories are used as given; Remote OK jobs are sorted by title and tags.
- **Allowed locations**: matched against the job's location restriction with common aliases (`US` also matches "USA", "Americas"; `Europe` also matches "EMEA"). Worldwide jobs are kept too unless you turn that off.
- **Experience level**: read from the job title (intern, junior, mid, senior, lead, manager, executive), because neither board has a reliable level field.
- **Minimum salary**: the top of the range converted to a yearly amount (hourly x 2080, monthly x 12). Remote OK salaries are yearly USD. We Work Remotely has no salary field, so the salary is read from the "Salary" or "Compensation" line of the description when there is one.

### Pricing

You pay per job saved to the dataset (see the Pricing tab), plus a tiny start fee. Duplicates removed across boards are never charged. Use **Maximum jobs** to cap a run.

### Credit the sources

The boards allow reuse of their feeds on one condition: credit them. If you show these jobs on your site or app, **mention Remote OK or We Work Remotely as the source and link to the job's `url`** (Remote OK asks for a normal followed link). Every row carries `source`, `sourceName` and `url` for this. Do not use the Remote OK logo without its permission.

Sources: [Remote OK API](https://remoteok.com/api) and [We Work Remotely public RSS feed](https://weworkremotely.com/remote-job-rss-feed).

### Why only these two boards?

We checked the terms of every popular remote board on 2026-10-26 and only kept boards whose public feed may be reused by others. Boards whose API terms forbid passing jobs to other platforms or aggregators, or forbid commercial use, are left out on purpose. This keeps your data use clean.

### FAQ

**How many jobs per run?** Usually 500 to 600 unique live remote jobs without filters (Remote OK returns its newest ~100, We Work Remotely around 450 across its category feeds).

**How fresh is the data?** As fresh as the boards' feeds; both update several times a day. Running more than a few times a day brings nothing new.

**Can I use it from an AI agent?** Yes. Call the Actor through the Apify API or the Apify MCP server and read the dataset.

**Something broke?** Open an issue on the Issues tab. If one board fails, the run still returns the other board's jobs and the run summary (`RUN_SUMMARY`) shows the error.

Made by [Ctrio Lab](https://ctriolab.com). Other job data Actors: [ATS Jobs Scraper](https://apify.com/ctriolab/ats-jobs-feed) (Greenhouse, Lever, Workday and more) and [SEEK, JobStreet and JobsDB scraper](https://apify.com/ctriolab/asia-jobs-scraper).

# Actor input Schema

## `sources` (type: `array`):

Boards to collect from. Both publish an official public feed that allows reuse with credit and a link back to each job.

## `keywords` (type: `array`):

Keep jobs whose title or tags contain any of these words or phrases, e.g. "python", "data engineer". Leave empty for all jobs.

## `excludeKeywords` (type: `array`):

Drop jobs whose title contains any of these words, e.g. "intern".

## `categories` (type: `array`):

One shared category list for every board. Leave empty for all categories.

## `locations` (type: `array`):

Keep jobs open to candidates in these countries or regions, e.g. "US", "Europe", "Germany", "APAC", "LATAM". Matched against the job's location restriction. Leave empty for any location.

## `includeWorldwide` (type: `boolean`):

When you set allowed locations, also keep jobs open anywhere in the world.

## `experienceLevels` (type: `array`):

Read from the job title (the boards have no reliable level field). Titles without a level word count as "mid".

## `minSalary` (type: `integer`):

Keep jobs whose top of range, converted to a yearly amount, is at least this number (in the job's currency, mostly USD). 0 = no salary filter.

## `includeJobsWithoutSalary` (type: `boolean`):

With a minimum salary set, also keep jobs that do not publish a salary.

## `postedWithin` (type: `string`):

Only jobs posted in this period, e.g. "24 hours", "7 days", "2 weeks", or since a date like 2026-10-01. Leave empty for all live jobs.

## `includeDescription` (type: `boolean`):

Add the full job description as plain text (larger dataset).

## `maxItems` (type: `integer`):

Stop after this many jobs. 0 = no limit. You pay per saved job.

## `onlyNewJobs` (type: `boolean`):

Save only jobs this watchlist has not returned before. Schedule the Actor daily to get a feed of fresh postings.

## `watchlistName` (type: `string`):

Separate memory for "Only new jobs". Use a different name for each schedule or search.

## Actor input object example

```json
{
  "sources": [
    "remoteok",
    "weworkremotely"
  ],
  "keywords": [
    "engineer"
  ],
  "includeWorldwide": true,
  "minSalary": 0,
  "includeJobsWithoutSalary": false,
  "postedWithin": "7 days",
  "includeDescription": false,
  "maxItems": 0,
  "onlyNewJobs": false,
  "watchlistName": "default"
}
```

# Actor output Schema

## `jobs` (type: `string`):

All saved remote job postings in the overview table.

## `summary` (type: `string`):

Jobs fetched and matched per board, duplicates removed and any board errors.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "engineer"
    ],
    "postedWithin": "7 days"
};

// Run the Actor and wait for it to finish
const run = await client.actor("ctriolab/remote-jobs-aggregator").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keywords": ["engineer"],
    "postedWithin": "7 days",
}

# Run the Actor and wait for it to finish
run = client.actor("ctriolab/remote-jobs-aggregator").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "keywords": [
    "engineer"
  ],
  "postedWithin": "7 days"
}' |
apify call ctriolab/remote-jobs-aggregator --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ctriolab/remote-jobs-aggregator"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/h93urRzSKefUTaZ6m/builds/a6eNA8J1DwY8eG43W/openapi.json