# Remote Jobs Aggregator: Himalayas, RemoteOK, Jobicy & More (`lepidata/remote-jobs`) Actor

One normalized feed of remote job listings from Himalayas, RemoteOK, Jobicy and Arbeitnow, filterable by keyword. Deduplicated. $0.90 per 1,000 jobs.

- **URL**: https://apify.com/lepidata/remote-jobs.md
- **Developed by:** [Lepi Data](https://apify.com/lepidata) (community)
- **Categories:** Jobs, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.90 / 1,000 unique 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: Himalayas, RemoteOK, Jobicy & More

One normalized feed of remote job listings from **Himalayas, Remote OK, Jobicy and Arbeitnow**, filterable by keyword, location and age, with cross-source duplicates removed. Every job is credited and linked to its original posting.

### What you get

One row per unique job:

- `source` and `sourceCredit`: which board it came from (Himalayas, Remote OK, Jobicy or Arbeitnow)
- `originalUrl`: the job's own page on that board (for Himalayas, its Himalayas page). Applicants should go there.
- `title`, `company`, `location`, `tags`, `jobTypes`, `salary` when the board gives one, `postedAt`
- a plain-text `description` with personal emails and phone numbers removed
- `attribution`: how the source asks to be credited
- `changeType`: new, updated or unchanged since your last run

No company logos are included.

### Duplicates and billing

The same job is often posted on several boards. Jobs from different boards with the same company and title are treated as duplicates; only the newest copy is returned. Separate postings on the same board are kept. **You are charged only for unique jobs returned after duplicate removal and your filters.**

### Crediting the sources

If you show these jobs anywhere, credit the source the way it asks, and check each board's own terms for your use:

- **Himalayas:** keep the Himalayas link (`originalUrl`) with each job. **Do not repost Himalayas jobs to Google Jobs, LinkedIn, Jooble, Neuvoo or any other job site or aggregator.**
- **Jobicy:** keep Jobicy credited as the original source, link to `originalUrl`, and send applicants there. Don't present the jobs as your own postings.
- **Remote OK:** mention Remote OK as the source and link to `originalUrl` with a normal, followed link (no `rel="nofollow"`). Don't use the Remote OK logo.
- **Arbeitnow:** link back to `originalUrl`.

### Freshness

This Actor reads one shared, regularly refreshed copy of each board; it does not contact the boards during your run. Jobicy is refreshed about once an hour, Himalayas, Remote OK and Arbeitnow about once a day, following each board's usage rules. `sourceFetchedAt` on every row shows when its board was last refreshed. Coverage: Jobicy's last 7 days, Remote OK's latest listings (about 100), Arbeitnow's newest remote jobs, and Himalayas' newest 2,000 listings.

### Input

- `sources`: any of `himalayas`, `remoteok`, `jobicy`, `arbeitnow` (default: all four)
- `keywords`: keep jobs whose title, tags or company contain any of these words; `excludeKeywords`: drop jobs that contain any of these
- `locations`, `postedWithinHours`, `maxJobs` (default 1,000, newest first)
- `onlyNewSinceLastRun` + `stateKey`, `startFromNow`, `includeDescriptions`, `emailPolicy`

### Example row

From a test run on Oct 11 2026 (description shortened):

```json
{
  "source": "remoteok",
  "sourceCredit": "Remote OK",
  "originalUrl": "https://remoteok.com/remote-jobs/remote-manager-clinical-data-management-edetek-1137481",
  "jobId": "remoteok:1137481",
  "title": "Manager Clinical Data Management",
  "company": "EDETEK",
  "location": null,
  "tags": ["exec", "design", "medical", "digital nomad"],
  "jobTypes": [],
  "salary": null,
  "postedAt": "2026-10-10T08:00:08.000Z",
  "description": "Manager, Clinical Data Management leads clinical data management team to handle project management documentation…",
  "attribution": "Source: Remote OK (https://remoteok.com). If you show this job, mention Remote OK and link to originalUrl with a normal followed link (no rel=\"nofollow\"). Do not use the Remote OK logo.",
  "sourceFetchedAt": "2026-10-11T18:46:59.932Z",
  "changeType": "new"
}
```

### Pricing

**$0.90 per 1,000 unique jobs** (pay per event `job`), the same price on every Apify plan. Free: duplicates removed, `source-error`, `baseline-saved`, `charge-limit-reached` and `free-plan-limit` rows. Set a maximum charge per run and the Actor stops cleanly when it is reached.

**Free-plan limit:** Apify Free-plan accounts get up to 25 jobs per run, from at most 2 of the selected job boards per run (later boards are skipped with a free `run-limit-reached` row). Paid Apify plans get full results from all four boards.

**Capacity and maintenance:** the shared job feed has a daily read limit across all users. If it is used up, boards not yet read are skipped with a free `service-busy` row (try again after 00:00 UTC). During maintenance, a run returns a single free `service-paused` row. These rows are never charged.

### Not affiliated

This Actor is not affiliated with or endorsed by Himalayas, Remote OK, Jobicy or Arbeitnow. The jobs belong to those boards and their employers.

# Actor input Schema

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

Which job boards to read. Each source's jobs are fetched at most once per hour and reused by your runs in between.

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

Only jobs whose title or tags contain at least one of these words (case-insensitive). Leave empty for all jobs.

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

Drop jobs whose title, tags or company contain any of these words.

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

Only jobs whose location text contains at least one of these (case-insensitive), e.g. "USA", "Europe", "Anywhere". Jobs that list no location are left out when this is set.

## `postedWithinHours` (type: `integer`):

Only jobs posted in the last N hours. Leave empty for everything the sources currently list.

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

Stop after this many job rows (newest first).

## `onlyNewSinceLastRun` (type: `boolean`):

Return only jobs added or changed (title, location or description text) since your previous run with the same state key. The first run returns everything.

## `startFromNow` (type: `boolean`):

First run records the current jobs without returning or charging for them (one free baseline-saved row per source). Later runs return only new or changed jobs.

## `stateKey` (type: `string`):

Name for this monitor. Use different keys for different searches so they don't overwrite each other.

## `includeDescriptions` (type: `boolean`):

Include the plain-text job description (personal emails and phone numbers removed).

## `emailPolicy` (type: `string`):

Personal emails and phone numbers are always removed.

## Actor input object example

```json
{
  "sources": [
    "himalayas",
    "remoteok",
    "jobicy",
    "arbeitnow"
  ],
  "keywords": [
    "developer",
    "designer"
  ],
  "maxJobs": 1000,
  "onlyNewSinceLastRun": false,
  "startFromNow": false,
  "stateKey": "default",
  "includeDescriptions": true,
  "emailPolicy": "keep-role"
}
```

# Actor output Schema

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

All job and status rows from this run.

# 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": [
        "developer",
        "designer"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("lepidata/remote-jobs").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": [
        "developer",
        "designer",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("lepidata/remote-jobs").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": [
    "developer",
    "designer"
  ]
}' |
apify call lepidata/remote-jobs --silent --output-dataset

```

## MCP server setup

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

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/9V8HhB2r2So7MRubi/builds/mV9na6LCH0dPHyFiX/openapi.json