# Remote Jobs Scraper — RemoteOK, WWR, Himalayas & Arbeitnow (`pixflor/remote-jobs-aggregator`) Actor

Scrape remote jobs from four boards at once into one normalized, deduplicated dataset: title, company, salary, tags, location and apply link. Cross-posted duplicates removed automatically.

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

## Pricing

from $2.00 / 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.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#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

## Remote Jobs Scraper — RemoteOK, WWR, Himalayas & Arbeitnow

Four remote job boards, one clean spreadsheet. Title, company, salary, tags, location and
apply link — with cross-posted duplicates removed automatically.

No API key. No login. Set a filter, press start, export CSV or JSON.

***

### Why one Actor instead of four

Every other remote-jobs scraper covers a single board. If you want decent coverage you run
four of them, learn four different schemas, and then dedupe by hand — because the same role
gets posted to several boards at once.

This does all of that for you:

- **One schema** across all four sources. `salaryMin` means the same thing everywhere.
- **Cross-board deduplication.** Matched on company plus title, keeping the richest copy —
  the one that actually lists a salary. On a typical run that's ~14 duplicates removed from
  \~415 jobs.
- **Every source carries a `source` label**, so you can still filter back down to one board.

***

### What you get

| Column | Example |
|---|---|
| `title` | Senior Backend Engineer |
| `company` | Acme Corp |
| `source` | `remoteok` |
| `url` | direct apply link |
| `salaryMin` / `salaryMax` / `salaryCurrency` | `120000` / `160000` / `USD` |
| `location` / `locationRestrictions` | Anywhere · `["US","EU"]` |
| `employmentType` / `seniority` | Full-Time · Senior |
| `tags` / `categories` | `["golang","postgres"]` · `["Programming"]` |
| `excerpt` | plain-text summary, HTML stripped |
| `description` | full listing |
| `publishedAt` / `expiresAt` | ISO 8601 |

***

### Typical uses

- **Job aggregators and newsletters.** Schedule it daily, filter by tag, publish the results.
- **Recruiting and market research.** Who is hiring for what, and at what advertised pay.
- **Salary benchmarking.** Filter with *Only jobs with salary data* and analyse the band.
- **Lead generation.** Companies actively hiring are companies actively spending.
- **Feeding a model or an LLM.** Consistent field names, one row per job.

***

### Example input

```json
{
  "sources": ["remoteok", "weworkremotely", "himalayas", "arbeitnow"],
  "searchQuery": "backend",
  "postedWithinDays": 7,
  "sortBy": "publishedAt",
  "maxItems": 200
}
```

Salary research only:

```json
{
  "sources": ["remoteok", "himalayas"],
  "withSalaryOnly": true,
  "sortBy": "salary",
  "maxItems": 500
}
```

A single board, no dedupe:

```json
{ "sources": ["weworkremotely"], "deduplicate": false, "maxItems": 100 }
```

***

### Settings that matter

- **`sources`** — keep all four for coverage. Arbeitnow skews EU/DACH; the other three are
  global.
- **`deduplicate`** — leave on unless you specifically want to see which boards carry the
  same role.
- **`withSalaryOnly`** — powerful but aggressive. Most boards don't publish pay, so expect
  this to keep well under a fifth of listings.
- **`postedWithinDays`** — the most useful filter for a scheduled run. Set it to `1` and
  you get only what's new since yesterday.
- **`maxItems`** — your cost ceiling. Set it deliberately.

***

### Pricing

Pay per event — you pay for jobs returned, not for runtime.

| Event | Price |
|---|---|
| Actor start | $0.002 per run |
| Job scraped | $0.002 each |

**1,000 jobs ≈ $2.00.** You're charged per *unique* job after deduplication, so you never
pay twice for the same role appearing on two boards.

***

### Reliability

Every source is an official API or public RSS feed — RemoteOK's JSON API, We Work Remotely's
RSS, the Himalayas jobs API and the Arbeitnow job board API. No HTML parsing, no headless
browser, no bot-detection workarounds. Layout changes on those websites don't affect this
Actor.

Requests retry with exponential backoff, and **one board being down degrades the run instead
of failing it** — you still get the other three, and the log says which one was missing.

***

### Notes

- Data is aggregated from the four boards' own public interfaces and provided **as-is**.
  Job listings change and expire constantly; a row is a snapshot at `scrapedAt`.
- Salary fields are only populated when the board publishes them, which is a minority of
  listings. `null` means "not advertised", not "unpaid".
- Deduplication matches on company and normalised title. Two genuinely different roles with
  identical titles at the same company will collapse into one — turn `deduplicate` off if
  that matters to you.

***

### Questions or a bug?

Open an issue on the **Issues** tab with your input JSON and the run ID. That's usually
enough to reproduce it immediately.

# Actor input Schema

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

Which boards to pull from. Leave all four selected for the widest coverage — deduplication removes anything cross-posted.

## `searchQuery` (type: `string`):

Only keep jobs whose title, company, tags or summary contain this text. Case-insensitive.

## `company` (type: `string`):

Only jobs from companies whose name contains this text.

## `tag` (type: `string`):

Match against the job's tags and categories, e.g. golang, design, marketing, devops.

## `employmentType` (type: `string`):

Partial match on employment type, e.g. full, part, contract, internship.

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

Keep jobs whose advertised maximum is at least this. Note most boards do not publish salary, so this filter is aggressive.

## `withSalaryOnly` (type: `boolean`):

Drop everything that doesn't advertise pay. Typically keeps well under a fifth of listings.

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

Only jobs published in the last N days. 0 means no date filter.

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

The same role is often posted to several boards. Matches on company plus title and keeps the richest copy — the one with salary data and the fullest description.

## `sortBy` (type: `string`):

How to order results before they are returned.

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

Hard cap on rows returned. This is your cost ceiling.

## Actor input object example

```json
{
  "sources": [
    "remoteok",
    "weworkremotely",
    "himalayas",
    "arbeitnow"
  ],
  "searchQuery": "backend",
  "tag": "golang",
  "minSalary": 0,
  "withSalaryOnly": false,
  "postedWithinDays": 0,
  "deduplicate": true,
  "sortBy": "publishedAt",
  "maxItems": 100
}
```

# 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("pixflor/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 = {}

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

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).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 pixflor/remote-jobs-aggregator --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=pixflor/remote-jobs-aggregator",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/5lrh5T1kKssmeyVve/builds/CoO8o7kv4A9qO7lOk/openapi.json