# Remote Jobs Aggregator: 5 job boards in one feed (`subimpact/remote-jobs-aggregator`) Actor

Remote jobs from Remote OK, We Work Remotely, Remotive, Jobicy and Himalayas merged into one deduplicated JSON feed: title, company, apply link, tags, salary, location limits and description. Filter by keyword and age. From $1.00 per 1,000 jobs.

- **URL**: https://apify.com/subimpact/remote-jobs-aggregator.md
- **Developed by:** [subimpact](https://apify.com/subimpact) (community)
- **Categories:** Jobs, Lead generation, Developer tools
- **Features:** Limited permissions
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.70 / 1,000 job scrapeds

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 API — 5 remote job boards in one feed

Remote job listings from **Remote OK**, **Remotive**, **We Work Remotely**, **Jobicy** and **Himalayas**, normalised into one schema, filtered by your keywords and categories, cross-board duplicates merged, and delivered as clean JSON — one row per job.

- One row per job with title, company, URLs, tags, category, job type, location restrictions, salary, posted date and a plain-text description (up to 20,000 characters).
- `keywords`, `categories` and `postedWithinDays` filters narrow the feed before anything is delivered.
- Cross-posted jobs are merged: one row, with every board it appeared on in `alsoListedOn`.
- `maxJobs` (default 200) caps a run, so a default run costs about $0.20.
- **$1.00 per 1,000 jobs** ($0.001 per delivered job). Error rows are never charged.

### Output example

A real row from a live run (description shortened here for readability — the actor returns the full text, up to 20,000 characters):

```json
{
  "jobId": "himalayas:director-erp-business-applications",
  "source": "himalayas",
  "title": "Director, ERP + Business Applications",
  "companyName": "C1",
  "companyLogo": "https://cdn-images.himalayas.app/84lsct298b9vbr86var7315t0y1z",
  "url": "https://himalayas.app/companies/c1-ai/jobs/director-erp-business-applications",
  "applyUrl": "https://himalayas.app/companies/c1-ai/jobs/director-erp-business-applications?utm_source=api",
  "tags": ["ERP-Director", "Enterprise-Applications-Director", "ERP-Program-Director", "Director-Of-Business-Applications", "IT-Director", "Director"],
  "category": "ERP-Director",
  "jobType": "Full-time",
  "locationRestrictions": ["United States"],
  "salaryMin": 175000,
  "salaryMax": 195000,
  "salaryCurrency": "USD",
  "salaryPeriod": "yearly",
  "postedAt": "2026-11-15T07:34:31.000Z",
  "description": "C1 Company Overview\n\nC1: 1 Contact, 1 Connection, 1 Choice\nC1 is the foremost, single-source provider of advanced communications and data technology for business. … [trimmed] … Pay Range\n$175,000 - $195,000\nBase pay ranges are estimated. Actual base pay will be based on education, experience, location, certifications, skill set, and any other relevant factors. … Originally posted on Himalayas",
  "alsoListedOn": [],
  "scrapedAt": "2026-11-15T08:44:17.239Z",
  "status": "ok",
  "error": null
}
```

### Input

```json
{
  "sources": ["remoteok", "remotive", "weworkremotely", "jobicy", "himalayas"],
  "keywords": ["python", "data engineer"],
  "categories": ["software", "developer"],
  "postedWithinDays": 30,
  "maxJobs": 200,
  "dedupe": true
}
```

| Input | Type | Default | What it does |
| --- | --- | --- | --- |
| `sources` | array | all five | Boards to query: `remoteok`, `remotive`, `weworkremotely`, `jobicy`, `himalayas`. Unknown names are ignored with a warning. |
| `keywords` | array | `[]` | Keep jobs whose **title, tags or company** contains at least one term (case-insensitive). Empty = no keyword filter. |
| `categories` | array | `[]` | Keep jobs whose **category or tags** match at least one term (case-insensitive substring), e.g. `software`, `design`, `marketing`. Empty = all categories. |
| `postedWithinDays` | integer | `30` | Drop jobs older than this many days (`0` = no date filter, max 365). Jobs whose board publishes no date are kept. |
| `maxJobs` | integer | `200` | Hard cap on **delivered** rows per run (1–10,000), applied after filtering and dedupe. 200 rows ≈ $0.20. |
| `dedupe` | boolean | `true` | Merge the same job posted on several boards (normalised company + title) into one row; the other boards go into `alsoListedOn`. |

Every run makes **one request per board** and only pages deeper while it still needs candidates, so a default five-board run is five HTTP requests. Boards are queried through their public feeds — no login, cookie or API key is used.

### Fields

| Field | Comes from |
| --- | --- |
| `jobId` | `<source>:<board id>` — Remote OK job id, Remotive job id, We Work Remotely URL slug, Jobicy job id, Himalayas URL slug. |
| `source` | Board the row came from: `remoteok`, `remotive`, `weworkremotely`, `jobicy`, `himalayas`. |
| `title` | Board's job title (We Work Remotely's `Company: Title` is split, company removed). |
| `companyName` | Board's company field (We Work Remotely: the part before the colon in the item title). |
| `companyLogo` | Board's logo URL (Remotive, Jobicy, Himalayas). Null on Remote OK and We Work Remotely when the feed has none. |
| `url` | Canonical job page on the board — keep it when you display the row (Remote OK and Remotive require a followable link back). |
| `applyUrl` | Separate application link when the board exposes one (Remote OK `apply_url`, Himalayas `applicationLink`); otherwise the job URL. |
| `tags` | Remote OK tags, Remotive tags, We Work Remotely skills, Jobicy industry + level, Himalayas categories + seniority. |
| `category` | Remotive category, We Work Remotely category, Jobicy first industry, Himalayas parent category. Null on Remote OK (no category). |
| `jobType` | Employment type normalised to Full-time, Part-time, Contract, Freelance, Internship, Temporary or Permanent. |
| `locationRestrictions` | Applicant location restrictions as a list, e.g. `["USA Only"]`, `["Canada", "United States"]`, `["Worldwide"]`. |
| `salaryMin`, `salaryMax` | Salary as published by the board. Remote OK USD figures, Remotive free-text salary parsed (`$35,3k- $52k` → 35300/52000), Jobicy and Himalayas numeric fields. Null when the board gives none. |
| `salaryCurrency` | ISO currency of the salary figures (USD, EUR, GBP, CAD, …). |
| `salaryPeriod` | `yearly`, `monthly`, `weekly`, `daily` or `hourly` — figures are **not** annualised, compare like with like. |
| `postedAt` | Board's publication date converted to ISO 8601 UTC (Remotive's naive timestamps are treated as UTC). Null when the board publishes none. |
| `description` | Job description as plain text: HTML unescaped, tags and scripts removed, whitespace collapsed, cut at 20,000 characters. Remote OK's double-encoded UTF-8 is repaired. |
| `alsoListedOn` | Other boards that carried the same normalised company + title and were merged into this row (`[]` when unique or dedupe off). |
| `scrapedAt` | ISO timestamp of the run. |
| `status` | `ok` for a job row; `error` for a board-level failure row (that board could not be fetched) — error rows are never charged and carry no job data. |
| `error` | Failure message on `status: "error"` rows, otherwise `null`. |

### Pricing

**$1.00 per 1,000 jobs** — $0.001 per delivered, deduplicated job row. You are charged only for rows that reach your dataset; source-level error rows and filtered-out listings are free. `maxJobs` (default 200) bounds a run at about $0.20, and Apify's per-run spend limits are respected: the run stops cleanly when the charge limit or `ACTOR_MAX_PAID_DATASET_ITEMS` is reached.

### Source terms and attribution

The actor keeps every board's attribution requirements in the data itself:

- **Remote OK** — [remoteok.com/api](https://remoteok.com/api) terms require a *followable* link back to the job URL and mentioning Remote OK as the source. `url` is always the remoteok.com job URL and `source` is `remoteok`, so keeping both satisfies this. Do not use the Remote OK logo without written permission; the name "Remote OK" is fine.
- **Remotive** — [remotive.com/api-documentation](https://remotive.com/api-documentation) requires linking back to the Remotive URL and naming Remotive as the source, and forbids re-posting Remotive jobs on third-party job sites (Jooble, Neuvoo, Google Jobs, LinkedIn Jobs, …). `url` is the remotive.com job page.
- **We Work Remotely** — public RSS feed; `url` points at the weworkremotely.com job page.
- **Jobicy** — public API; `url` points at the jobicy.com job page.
- **Himalayas** — public API; `url` points at the himalayas.app job page and `applyUrl` carries their `utm_source=api` link.

### Notes, limits and rate limits

- **Volume per board.** One Remote OK request returns its latest ~100 jobs; We Work Remotely's RSS carries 100 recent jobs; Remotive's public endpoint returns a small sample (16 jobs when measured on 2026-11-15, with its `search`/`category`/`limit` parameters seemingly ignored for anonymous callers); Jobicy returns up to 100 per page and Himalayas 20 per page, both paginated with a cursor. The actor pages Jobicy and Himalayas at most 3 and 10 times per run respectively, and never queries a board more than once for a filter.
- **Rate limits.** These are free public endpoints. Remotive asks for at most ~4 requests per day; Jobicy asks clients to cache responses; Remote OK suspends clients that hammer or strip attribution; Himalayas prefers its cursor over the deprecated offset. A run needs one page per board, so scheduled runs are gentle — do not schedule this actor more often than you need fresh listings.
- **Dates are board dates.** Some boards (Remote OK, Remotive, Jobicy, Himalayas) publish timestamps; We Work Remotely publishes an RSS date. `postedWithinDays` keeps undated rows, since dropping them would silently lose listings.
- **Salaries vary in basis.** Values are passed through as published, with `salaryPeriod` telling you the basis. Remotive's free-text salaries are parsed best-effort; a salary that cannot be parsed is `null` rather than a guess.
- **Dedupe is conservative.** Company and title are compared after lower-casing and removing legal suffixes/remote markers, so "Acme Inc — Senior Engineer (Remote)" and "Acme — Senior Engineer" merge, while different roles with similar titles do not.
- **Blocking.** Some boards sit behind Cloudflare/bot protection and may answer a datacenter IP with 403/429. The actor makes one retry, then records that board as a `status: "error"` row and keeps the other boards' results; the run fails only if **all** selected boards fail.
- **No proxy is used** by default. If a board starts blocking your runs, rerun later or narrow `sources`.

### Local development

```bash
npm ci
npm test          # offline: saved fixtures in test/fixtures, no network
node test/live.mjs  # live smoke run over all five boards (no dataset, no charges)
```

# Actor input Schema

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

Job boards to merge, one per line or as a list. Allowed values: remoteok, remotive, weworkremotely, jobicy, himalayas. Leave the default (all five) to search every board; unknown names are ignored.

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

Only keep jobs whose title, tags or company name contains at least one of these terms (case-insensitive). Leave empty for no keyword filter, e.g. \["python", "data engineer"].

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

Only keep jobs whose category or tags match at least one of these values (case-insensitive substring), e.g. \["developer", "design", "marketing"]. Leave empty for all categories.

## `postedWithinDays` (type: `integer`):

Drop jobs older than this many days. 0 = no date filter. Jobs whose source publishes no date are kept.

## `maxJobs` (type: `integer`):

Hard cap on delivered jobs per run (counts rows actually pushed to the dataset, after filtering and dedupe). At $1 per 1,000 jobs the default 200 costs about $0.20.

## `dedupe` (type: `boolean`):

Merge the same job posted on several boards into one row: normalised company name + title. The other boards are listed in alsoListedOn.

## Actor input object example

```json
{
  "sources": [
    "remoteok",
    "remotive",
    "weworkremotely",
    "jobicy",
    "himalayas"
  ],
  "keywords": [],
  "categories": [],
  "postedWithinDays": 30,
  "maxJobs": 200,
  "dedupe": true
}
```

# Actor output Schema

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

One dataset item per job: jobId, source, title, company, URLs, tags, category, job type, location restrictions, salary (min/max/currency/period), posted date, plain-text description, alsoListedOn and status. Source-level failures appear as status=error rows (never charged).

# 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 = {
    "sources": [
        "remoteok",
        "remotive",
        "weworkremotely",
        "jobicy",
        "himalayas"
    ],
    "maxJobs": 200
};

// Run the Actor and wait for it to finish
const run = await client.actor("subimpact/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 = {
    "sources": [
        "remoteok",
        "remotive",
        "weworkremotely",
        "jobicy",
        "himalayas",
    ],
    "maxJobs": 200,
}

# Run the Actor and wait for it to finish
run = client.actor("subimpact/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 '{
  "sources": [
    "remoteok",
    "remotive",
    "weworkremotely",
    "jobicy",
    "himalayas"
  ],
  "maxJobs": 200
}' |
apify call subimpact/remote-jobs-aggregator --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,subimpact/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/A0jxshxf1OJHQzFfN/builds/ZmpOokAhBZ2qUxEL6/openapi.json
