# Remote Jobs Feed - RemoteOK, Himalayas & WWR in One Schema (`enhanced_elephant1/remote-jobs-feed`) Actor

Scrape remote jobs from RemoteOK, Himalayas and We Work Remotely into one clean schema. Salaries annualized to comparable USD, cross-posted duplicates merged.

- **URL**: https://apify.com/enhanced\_elephant1/remote-jobs-feed.md
- **Developed by:** [Noah](https://apify.com/enhanced_elephant1) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 job results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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 Feed

Pull remote job listings from **RemoteOK**, **Himalayas** and **We Work Remotely** in one run, and get back a single clean feed: one schema, salaries you can actually compare, and the same job cross-posted to several boards merged into one record.

Most job scrapers hand you one board's raw shape. If you want more than one board, you get incompatible field names, salaries in different units, and the same job three times. This does that reconciliation for you.

### Quick start

Click **Run with defaults**. You get 100 recent remote jobs from all three boards, deduplicated, with no configuration.

To narrow it down:

```json
{
  "searchTerms": ["python", "backend"],
  "minSalaryUsd": 120000,
  "worldwideOnly": true,
  "maxResults": 50
}
```

### What makes the output different

**One schema across three boards.** RemoteOK calls it `position`, Himalayas calls it `title`, We Work Remotely packs `"Company: Role"` into an RSS title. All three come back as `title` and `company`.

**Salaries you can compare.** Himalayas quotes some roles hourly and some annually, in varying currencies. RemoteOK uses `0` to mean "not disclosed". Everything is annualized into `salary_min_usd_year` / `salary_max_usd_year`.

Where a salary is quoted in a currency other than USD it is **not** converted, because a stale exchange rate silently corrupts data. The original figures are kept in `salary_min_raw` / `salary_currency` and `salary_is_normalized` tells you whether a number is comparable. You always know what you are looking at.

**Cross-posted duplicates merged.** The same job on several boards becomes one record. The most complete copy wins, the others are listed in `also_on`, and gaps are filled across copies — so if one board has the salary and another has the description, you get both. A typical run collapses 6-10 cross-postings.

**A worldwide flag that works.** "Anywhere in the World", "Worldwide" and "Global" are all recognized, across three boards' differing conventions.

### Output fields

| Field | Description |
| --- | --- |
| `id` | Stable id, prefixed with the source |
| `source` | `remoteok`, `himalayas` or `weworkremotely` |
| `also_on` | Other boards this job also appeared on |
| `title`, `company`, `company_logo` | Core identity |
| `description_html`, `description_text` | Full description, raw and flattened to text |
| `categories`, `tags`, `seniority` | Classification, unioned across boards when merged |
| `employment_type` | `full_time`, `part_time`, `contract` or `internship` |
| `location_raw`, `location_restrictions`, `timezone_restrictions` | Geography as each board states it |
| `is_worldwide` | True when there is no geographic restriction |
| `salary_min_usd_year`, `salary_max_usd_year` | Annualized USD, null when not comparable |
| `salary_is_normalized` | Whether the USD figures above are trustworthy |
| `salary_min_raw`, `salary_max_raw`, `salary_currency`, `salary_period` | The source's original figures |
| `posted_at`, `expires_at` | ISO-8601 UTC |
| `apply_url`, `source_url` | Where to apply |

### Input options

| Option | Default | What it does |
| --- | --- | --- |
| `sources` | all three | Which boards to pull from |
| `maxResults` | 100 | Jobs returned after dedupe and filtering; 0 for no limit |
| `searchTerms` | none | Keywords across title, company, tags, categories, description |
| `matchAllTerms` | false | Require every term rather than any |
| `minSalaryUsd` | none | Annual floor; excludes undisclosed and unconvertible salaries |
| `maxAgeDays` | none | Recency window; undated jobs are kept |
| `employmentTypes` | all | Filter to specific types |
| `worldwideOnly` | false | Only roles with no geographic restriction |
| `deduplicate` | true | Merge cross-posted duplicates |
| `includeDescription` | true | Turn off for a much smaller dataset |

### Typical uses

- Building a remote job board or newsletter without maintaining three separate integrations
- Salary benchmarking across remote roles, using figures that are actually comparable
- Feeding job descriptions to an LLM — `description_text` is pre-flattened with paragraph structure intact
- Recruiting research on who is hiring remotely, in what categories, at what pay

### Notes

All three sources are public, documented endpoints rather than scraped HTML, so this reads published feeds instead of parsing markup. That means it does not break when a site adjusts its page layout.

If one board is unavailable, the run continues with the others and the status message names what failed. You are never charged for records you did not receive.

### Pricing

$4.00 per 1,000 results. Platform usage costs are included — you are not billed separately for compute.

# Actor input Schema

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

Which boards to pull from. All three by default.

## `maxResults` (type: `integer`):

How many jobs to return after deduplication and filtering. Set 0 for no limit.

## `searchTerms` (type: `array`):

Keywords matched against title, company, tags, categories and description. Leave empty to get every job. Example: python, backend

## `matchAllTerms` (type: `boolean`):

On: a job must match every term. Off: matching any one term is enough.

## `minSalaryUsd` (type: `integer`):

Keep only jobs paying at least this much per year. Jobs with no disclosed salary, or a salary in a currency that cannot be converted without live FX rates, are excluded when this is set.

## `maxAgeDays` (type: `integer`):

Keep only jobs posted within this many days. Jobs with no date are kept. Set 0 for no limit.

## `employmentTypes` (type: `array`):

Keep only these types. Leave empty for all. Jobs where the board did not state a type are excluded when this is set.

## `worldwideOnly` (type: `boolean`):

Keep only jobs with no geographic restriction.

## `deduplicate` (type: `boolean`):

Collapse the same job posted to several boards into one record, keeping the most complete copy and listing the others under 'also\_on'.

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

Include the full job description as both HTML and plain text. Turn off for a much smaller dataset.

## `proxyConfiguration` (type: `object`):

Optional. These are public endpoints and normally need no proxy.

## Actor input object example

```json
{
  "sources": [
    "remoteok",
    "himalayas",
    "weworkremotely"
  ],
  "maxResults": 100,
  "searchTerms": [],
  "matchAllTerms": false,
  "minSalaryUsd": 0,
  "maxAgeDays": 0,
  "employmentTypes": [],
  "worldwideOnly": false,
  "deduplicate": true,
  "includeDescription": true,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

Each record is one job in a single consistent schema across all three boards: salaries annualized to comparable USD, employment type normalized, and cross-posted duplicates merged with the other boards listed under also\_on.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("enhanced_elephant1/remote-jobs-feed").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("enhanced_elephant1/remote-jobs-feed").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 '{}' |
apify call enhanced_elephant1/remote-jobs-feed --silent --output-dataset

```

## MCP server setup

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

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/HqWd8WBrkkZTHqJl2/builds/xnOPXP9oKbw7dMUiD/openapi.json