# Remote Jobs Aggregator (Himalayas, Remote OK, Jobicy) (`pavel.tashev/remote-jobs-aggregator`) Actor

Collect remote jobs from Himalayas, Remote OK and Jobicy in one clean, de-duplicated dataset with salaries, locations and source links. Filter by keyword, location and date.

- **URL**: https://apify.com/pavel.tashev/remote-jobs-aggregator.md
- **Developed by:** [Pavel Tashev](https://apify.com/pavel.tashev) (community)
- **Categories:** Jobs, AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 job listing saveds

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### What does Remote Jobs Aggregator do?

**Remote Jobs Aggregator collects remote job listings from [Himalayas](https://himalayas.app), [Remote OK](https://remoteok.com), and [Jobicy](https://jobicy.com) into one clean, de-duplicated dataset.** Every job comes in the same format: title, company, location, salary range, employment type, seniority, tags, plain-text description, posting date and a link to the original listing.

Filter by **keywords**, **location** and **posting date**, then export to JSON, CSV or Excel, or pull the results through the API. Because it runs on the Apify platform, you also get scheduling, webhooks, integrations (Make, Zapier, n8n, Google Sheets) and run monitoring.

### Why use Remote Jobs Aggregator?

- **Three job boards, one schema.** No need to learn three APIs with different field names, date formats and salary conventions.
- **Duplicates removed.** The same job posted on several boards is saved once, and you are not charged for the duplicate.
- **Built on official public APIs.** The job boards publish these feeds for reuse, so runs are fast and reliable.
- **Clean text.** Descriptions are converted from HTML to readable plain text, broken characters are repaired, and email addresses are removed.
- **Salary data where the board provides it**, split into minimum, maximum, currency and period.

Typical uses: remote job boards and newsletters, job alerts on a schedule, salary and hiring-trend research, recruiting market maps, and giving AI agents a live source of remote jobs.

### How to scrape remote jobs

1. Click **Try for free**.
2. Enter **Keywords**, for example `python, data engineer`, or leave the field empty for all jobs.
3. Optionally set **Location** (for example `Europe, Germany, Worldwide`) and **Posted within (days)**.
4. Click **Start**. Most runs finish in under a minute.
5. Open the **Output** tab. The **Overview** view shows title, company, location, salary and job link; **Details** shows everything else.

### Input

| Field | Description | Default |
|---|---|---|
| **Keywords** | Comma-separated. A job matches if its title, tags or description contain all words of at least one keyword. Up to 5 keywords. | empty (all jobs) |
| **Job boards** | Himalayas, Remote OK, Jobicy | all three |
| **Location** | Comma-separated text matched against the job's location. Add `Worldwide` to keep jobs open to everyone. | any |
| **Posted within (days)** | Only jobs from the last N days. | any date |
| **Maximum jobs per job board** | 1–2,000 | 100 |
| **Include job descriptions** | Turn off for a smaller dataset. | on |
| **Remove duplicates** | Same company and job title across boards. | on |

Example input:

```json
{
  "keywords": "python, data engineer",
  "location": "Europe, Worldwide",
  "postedWithinDays": 7,
  "maxResultsPerSource": 200
}
```

### Output

Each job is one item in the dataset. A real example from a run on 15 September 2026 (description shortened):

```json
{
  "id": "himalayas:engineer-senior-engineer-python-packaging-client-facing",
  "source": "Himalayas",
  "sourceUrl": "https://himalayas.app/companies/openteams/jobs/engineer-senior-engineer-python-packaging-client-facing",
  "title": "Engineer/Senior Engineer - Python Packaging (Client Facing)",
  "company": "OpenTeams",
  "location": "United States",
  "remote": true,
  "employmentType": "Full Time",
  "seniority": "Mid-level, Senior",
  "salaryMin": 85000,
  "salaryMax": 200000,
  "salaryCurrency": "USD",
  "salaryPeriod": "year",
  "salary": "USD 85,000–200,000 / year",
  "tags": ["Python Packaging", "Software Engineer", "Build Systems Engineering"],
  "category": "Developer",
  "description": "Who We Are\n\nEvery organization runs on intelligence: years of accumulated knowledge, decisions, and context...",
  "postedAt": "2026-09-06T18:04:37+00:00",
  "attribution": "Job listing from Himalayas — https://himalayas.app",
  "scrapedAt": "2026-09-15T00:58:07+00:00"
}
```

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel. A per-board summary (jobs fetched, saved, duplicates, errors) is saved in the key-value store as `SOURCES_REPORT`.

### Output fields

| Field | Meaning |
|---|---|
| `id` | Unique ID, `source:sourceId` |
| `source`, `attribution` | Job board name and the credit line to show with the job |
| `sourceUrl` | Original listing on the job board; use it as the apply link |
| `title`, `company`, `companyLogo` | Job and employer |
| `location`, `remote` | Where the job is open (`Worldwide` when unrestricted) and whether it is remote |
| `employmentType`, `seniority`, `category`, `tags` | Classification, as provided by the board |
| `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryPeriod`, `salary` | Salary range and a readable summary, when published |
| `description` | Plain-text description, emails removed |
| `postedAt`, `scrapedAt` | Posting and collection time (ISO 8601, UTC) |

### How much does it cost to scrape remote jobs?

This Actor uses **pay-per-event pricing**: you pay a small fee for each job saved to your dataset, and nothing for duplicates or jobs filtered out. See the **Pricing** tab for the current price per 1,000 jobs. Platform compute is included. You can set a maximum cost per run and the Actor stops cleanly when it is reached.

### Tips

- **Schedule a daily run** with **Posted within (days)** set to `1` for a fresh job feed. The boards update their data a few times a day, so running more often adds nothing.
- **Keywords are matched as whole words.** `java` does not match `javascript`; list both if you want both.
- **Remote OK returns about 100 of its newest jobs** and Jobicy up to 200 per keyword, so their counts are smaller than Himalayas.

### Sources and attribution

Data comes from the public APIs these job boards publish for reuse; keep the source link and attribution when you display jobs. Each board sets its own conditions:

- **Himalayas:** link back to the job URL on Himalayas and mention Himalayas as the source. Do not submit Himalayas jobs to third-party sites such as Jooble, Neuvoo, Google Jobs or LinkedIn Jobs.
- **Remote OK:** link back (without `nofollow`) to the job URL on Remote OK and mention Remote OK as the source. Do not use the Remote OK logo. Remote OK does not allow its content to be used for AI training.
- **Jobicy:** credit Jobicy with a direct link to the source and send apply buttons to the original job URL.

The `attribution` and `sourceUrl` fields on every job make this easy. You are responsible for following these conditions when you publish or reuse the data.

### Related tools

Research the companies behind the jobs:

- [Company Career Page Jobs Scraper](https://apify.com/pavel.tashev/company-jobs-scraper): get all open jobs from company career pages (Greenhouse, Lever, Ashby and more).
- [European Company Registry Lookup](https://apify.com/pavel.tashev/european-company-registry-lookup): look up official company records in 8 European registries and the LEI database.
- [Website Tech Stack Detector](https://apify.com/pavel.tashev/website-tech-stack-detector): detect the CMS, frameworks, analytics and hosting of any website.

### FAQ and support

**Does it collect personal data?** No. It collects job listings only, and removes email addresses found in descriptions.

**Why did a job board return fewer jobs than expected?** Check `SOURCES_REPORT` in the key-value store. A board that is temporarily unavailable is reported there and in the run's status message; the other boards still run.

**Missing a job board or a field?** Open an issue in the **Issues** tab. Requests for new boards and custom job-data pipelines are welcome.

# Actor input Schema

## `keywords` (type: `string`):

Comma-separated job keywords, for example "python, data engineer". A job matches if its title, tags or description contain all words of at least one keyword. Leave empty for all jobs. Up to 5 keywords.

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

Public job-board APIs to collect from.

## `location` (type: `string`):

Comma-separated places the job must be open to, for example "Germany, Europe, Worldwide". Matches the job's location text. Include "Worldwide" to keep jobs open to everyone. Leave empty for any location.

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

Only return jobs posted in the last N days. Leave empty for any date.

## `maxResultsPerSource` (type: `integer`):

Stop collecting from a job board after this many matching jobs. Remote OK returns about 100 recent jobs and Jobicy up to 200 per keyword.

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

Full job description as plain text. Turn off for a smaller dataset.

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

Skip a job when the same company and job title were already saved from another job board. Duplicates are not charged.

## Actor input object example

```json
{
  "keywords": "python",
  "sources": [
    "himalayas",
    "remoteok",
    "jobicy"
  ],
  "maxResultsPerSource": 100,
  "includeDescription": true,
  "deduplicate": true
}
```

# Actor output Schema

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

No description

## `sourcesReport` (type: `string`):

No description

# 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": "python",
    "sources": [
        "himalayas",
        "remoteok",
        "jobicy"
    ]
};

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

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

```

## MCP server setup

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