# Remote Jobs Scraper - Himalayas, Remote OK, We Work Remotely (`tinyrex/remote-jobs-scraper`) Actor

Remote jobs from Himalayas, Remote OK, We Work Remotely, Working Nomads and Arbeitnow in one run via official APIs. Salary, location rules, full description, dedupe and monitoring. Pay per job.

- **URL**: https://apify.com/tinyrex/remote-jobs-scraper.md
- **Developed by:** [TinyRex](https://apify.com/tinyrex) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.80 / 1,000 jobs

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 Scraper: Himalayas, Remote OK, We Work Remotely & more

Get **remote jobs from 5 job boards in one run**: **Himalayas**, **Remote OK**, **We Work Remotely**, **Working Nomads** and **Arbeitnow**. Search by job title or skill, filter by the countries candidates may live in, employment type, seniority and salary, and get clean, structured jobs with company, location rules, salary range, tags and the full description. You pay only for the jobs you get.

**Why this one:** **$0.80 per 1,000 jobs with full descriptions**, while single-board remote job scrapers on the Store charge about $1 per 1,000 and multi-board aggregators $2–15 per 1,000. It reads the boards' **official public APIs and RSS feeds** (no fragile HTML scraping, no browser), so runs are fast and reliable. Jobs removed by your filters, cross-board duplicates and already-seen jobs are **free**.

### Why this scraper

- **5 boards, one schema.** Himalayas (100,000+ remote jobs, server-side search, salaries), Remote OK, We Work Remotely, Working Nomads and Arbeitnow (Europe/Germany), all normalized to the same fields.
- **Cross-board dedupe.** The same job is often posted on several boards; only the first copy is kept (and duplicates are free).
- **Location rules that matter for remote work.** `locationRestrictions` and `timezoneRestrictions` tell you who can actually apply. Filter by candidate country (e.g. *Germany*, *US*, *Bosnia and Herzegovina*) and keep or drop "worldwide" jobs.
- **Salary when published.** Min, max, currency and period (mostly Himalayas and Remote OK). Turn on *Only jobs with a salary* to keep only those.
- **Monitoring built in.** Turn on *Only new jobs* and schedule the Actor daily to get only jobs you have not seen yet.
- **Fast and cheap to run.** Hundreds of jobs in under 30 seconds at 256 MB.

### What you get

| Field | Example |
|---|---|
| source, sourceName, jobId | himalayas, Himalayas, senior-python-engineer-1234 |
| title, company, companyLogo | Senior Python Engineer, Acme, logo URL |
| location, locationRestrictions, timezoneRestrictions | Germany, Austria; \[Germany, Austria]; \[0, 1, 2] |
| employmentType, seniority | fulltime, \[Senior] |
| categories, tags | \[Developer], \[python, django] |
| salary | {min: 90000, max: 120000, currency: USD, period: year} |
| postedAt, expiresAt | 2026-10-06T19:35:42Z |
| url, applyUrl | job page on the board, application link |
| descriptionText | full job description as plain text |

### How to use

1. Add one or more **job titles / keywords** (e.g. *python*, *react developer*, *customer support*, *product designer*). A job matches when every word appears in its title, company, tags or categories (or choose *title only* / *anywhere*). Leave empty to get the newest remote jobs.
2. Pick the **job boards** (all five by default).
3. Optional filters: **candidate countries**, employment type, seniority, posted within N days, only jobs with a salary.
4. Run and download the results as JSON, CSV, Excel or HTML, or use them via the API, webhooks or integrations (Google Sheets, Make, Zapier, n8n, Slack).

#### Example input

```json
{
  "keywords": ["python", "customer support"],
  "sources": ["himalayas", "remoteok", "weworkremotely", "workingnomads", "arbeitnow"],
  "countries": ["Germany"],
  "includeWorldwide": true,
  "publishedWithinDays": 7,
  "maxResultsPerSearch": 200
}
```

#### Example output (shortened)

```json
{
  "source": "himalayas",
  "sourceName": "Himalayas",
  "jobId": "senior-python-engineer-1234",
  "title": "Senior Python Engineer",
  "company": "Acme",
  "location": "Germany, Austria",
  "locationRestrictions": ["Germany", "Austria"],
  "employmentType": "fulltime",
  "seniority": ["Senior"],
  "salary": { "min": 90000, "max": 120000, "currency": "USD", "period": "year" },
  "postedAt": "2026-10-06T19:35:42.000Z",
  "url": "https://himalayas.app/companies/acme/jobs/senior-python-engineer-1234",
  "applyUrl": "https://acme.com/careers/123",
  "descriptionText": "About the role ..."
}
```

### Monitoring new jobs

Set **Only new jobs** to true and add a schedule (for example daily). Each run returns only jobs that were not returned before for the same **State key**. The first run returns all matching jobs as the baseline. *Max jobs per keyword and board* counts already-seen jobs too, so a daily run stops as soon as it reaches jobs you already have.

### Run report

- **`SEARCHES`**: for every board and keyword, jobs fetched and saved, and any error.
- **`SUMMARY`**: totals for the run (fetched, filtered, duplicates, already seen, saved).

### Pricing

Pay per event:

- **Job** (`job`): one charge per job saved to your dataset, full description included.
- **Free:** jobs removed by your filters, cross-board duplicates and already-seen jobs in monitoring mode.

See the *Pricing* tab for the current price. Set a maximum cost per run and the Actor stops gracefully when it is reached.

### Limitations

- Himalayas is searched on its server; Remote OK (about 100 newest jobs), We Work Remotely (newest jobs feed), Working Nomads (newest jobs) and Arbeitnow (newest pages) are read as feeds and filtered locally, so they add the freshest jobs rather than full history.
- Salary, seniority and timezone data depend on what each board publishes.
- No recruiter names, emails or phone numbers are extracted. Only the job ad itself.
- **Attribution:** the boards ask that you link back to the job URL and mention them as the source if you republish their jobs (`url` and `sourceName` are included for that). Himalayas and Remote OK do not allow resubmitting their jobs to aggregators such as Google Jobs, LinkedIn or Jooble.

### Use with AI agents (MCP)

This Actor works as a tool for AI agents through the **Apify MCP server** at `https://mcp.apify.com`. Connect Claude, Cursor, VS Code, n8n or any other MCP client to `https://mcp.apify.com?tools=tinyrex/remote-jobs-scraper` and the agent can run it from a plain-language request, for example: *"Find remote senior React jobs open to candidates in Germany, posted this week, with salary"*. Results come back as clean, structured JSON at the same pay-per-result price, and filtered or duplicate jobs stay free.

📘 **Step-by-step guide with Python, JavaScript, curl and MCP examples:** [How to scrape remote jobs from Himalayas, Remote OK, We Work Remotely and more in one run](https://emirmrkaljevic.github.io/tinyrex-data-tools/remote-jobs-api-himalayas-remoteok-weworkremotely/)

### Related actors

- [Greenhouse / Lever / Ashby Jobs Scraper](https://apify.com/tinyrex/ats-jobs-scraper): Jobs straight from company career sites on Greenhouse, Lever, Ashby, Personio, Teamtailor or Recruitee.
- [Arbeitsagentur & EURES Jobs Scraper](https://apify.com/tinyrex/dach-jobs-scraper): Official job listings for Germany, Austria, Switzerland and the EU.
- [Workday Jobs Scraper](https://apify.com/tinyrex/workday-jobs-scraper): All jobs from companies that hire on Workday, with full descriptions.
- [Tech Stack Detector](https://apify.com/tinyrex/tech-stack-detector): Enrich hiring companies with their tech stack, email provider and DMARC for sales outreach.

### FAQ

**Is it legal?** The Actor reads public job ads through the official public APIs and RSS feeds that these job boards provide for sharing their jobs. It does not log in and does not collect candidate or recruiter data. Follow each board's attribution terms when you republish jobs, and use the data in line with your local laws.

**How fast is it?** Usually a few hundred jobs in under 30 seconds.

**Can I get all remote jobs, not only a keyword?** Yes. Leave keywords empty and set a higher *Max jobs per keyword and board*.

# Actor input Schema

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

Each keyword is a separate search, e.g. python, react developer, product designer, customer support. A job matches when every word of the keyword appears (see 'Match keywords in'). Leave empty to get the newest remote jobs.

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

Himalayas (largest, server-side search, salaries), Remote OK, We Work Remotely, Working Nomads and Arbeitnow (Europe/Germany). All use their official public APIs or feeds.

## `maxResultsPerSearch` (type: `integer`):

Maximum jobs saved per keyword and job board. 0 = no limit.

## `matchIn` (type: `string`):

Where the keyword words must appear.

## `countries` (type: `array`):

Only jobs open to candidates in these countries (names or ISO codes, e.g. Germany, US, Bosnia and Herzegovina). Himalayas filters on the server; other boards are matched on their location text. Leave empty for all.

## `includeWorldwide` (type: `boolean`):

With a country filter, also keep jobs open worldwide.

## `employmentType` (type: `array`):

Only these types. Jobs without a type on the board are kept.

## `seniority` (type: `array`):

Seniority filter, applied by Himalayas.

## `publishedWithinDays` (type: `integer`):

Only jobs posted in the last N days. 0 = any time.

## `onlyWithSalary` (type: `boolean`):

Keep only jobs that publish a salary range (mostly Himalayas and Remote OK).

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

Adds the full description as plain text. Same price either way.

## `dedupeAcrossSources` (type: `boolean`):

The same job is often posted on several boards. Keep only the first copy (same title + company). Duplicates are free.

## `arbeitnowRemoteOnly` (type: `boolean`):

Arbeitnow also lists on-site jobs in Germany. Keep only remote ones.

## `arbeitnowPages` (type: `integer`):

Arbeitnow has no search; the newest pages are read and filtered (about 300 jobs per page).

## `onlyNewJobs` (type: `boolean`):

Return only jobs not returned by previous runs with the same state key. Ideal for daily schedules. The first run returns everything.

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

Name of the monitoring state. Use different keys for different schedules.

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

Not needed normally.

## Actor input object example

```json
{
  "keywords": [
    "python"
  ],
  "sources": [
    "himalayas",
    "remoteok",
    "weworkremotely",
    "workingnomads",
    "arbeitnow"
  ],
  "maxResultsPerSearch": 100,
  "matchIn": "titleAndTags",
  "countries": [],
  "includeWorldwide": true,
  "employmentType": [],
  "seniority": [],
  "publishedWithinDays": 0,
  "onlyWithSalary": false,
  "includeDescription": true,
  "dedupeAcrossSources": true,
  "arbeitnowRemoteOnly": true,
  "arbeitnowPages": 2,
  "onlyNewJobs": false,
  "stateKey": "default",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

Normalized remote jobs from all boards.

## `searches` (type: `string`):

For every board and keyword: jobs fetched and saved, errors.

## `summary` (type: `string`):

Totals for the 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": [
        "python"
    ]
};

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

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

```

## MCP server setup

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

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/cRhZieDd8WvOcVIQj/builds/2O6BPgeicMkqr7bbl/openapi.json