# Himalayas Remote Jobs Scraper (Worldwide) (`axery/himalayas-remote-jobs-scraper`) Actor

Scrape 100,000+ worldwide remote job listings from Himalayas with real numeric salary, seniority, location and timezone restrictions, and incremental mode.

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

## Pricing

from $1.00 / 1,000 results

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?

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

## Himalayas Remote Jobs Scraper (Worldwide)

Scrapes worldwide remote job listings from **himalayas.app** over plain HTTP — no browser, no login, no cookies. It reads Himalayas' official public JSON feed, which currently carries **over 100,000 listings**.

### What makes this different

**Salary that is already numeric — and honestly labelled.** Most job boards publish salary as a display string you cannot sort. Himalayas publishes real numbers, and this Actor passes them through with the currency and period attached, plus a readable `raw` for consistency with the other Actors in the suite:

```json
"salary": {
  "min": 135000, "max": 165000, "currency": "USD",
  "period": "year", "is_estimated": false,
  "raw": "USD 135,000 - USD 165,000 per year"
}
```

`is_estimated` is `false` here because these are advertiser-disclosed figures, not bands the board modelled. Watch the `period` and `currency`: the feed mixes `USD/year` with `GBP/year` and `USD/hour` freely, so never compare the numbers without reading those two fields.

**Location restrictions, not just "remote".** Every listing is remote, so a `remote: true` flag would carry no information. What actually matters is *where you may live* — `location_restrictions` holds that, and is `null` when the role is genuinely open worldwide.

**Cursor pagination, as the API asks.** The feed's own response says offset pagination is deprecated and will be removed. This Actor pages by `nextCursor`, so it will not break when that happens.

**Incremental mode.** Turn on `incremental` and you get only listings not seen before — and are charged only for those rows. A daily monitor costs full price once, then a fraction per day.

**One schema across boards.** Same record shape as the SEEK and JobStreet Actors, with a source-prefixed `job_id`. Merge them into one dataset and dedupe without writing a normalizer.

### Input

| Field | Type | Notes |
|---|---|---|
| `queries` | array | Keywords matched against title, company, excerpt and category tags. Empty = newest listings. |
| `categories` | array | Himalayas category tags, e.g. `Software-Engineering`. Run once unfiltered to discover them. |
| `seniority` | array | `Entry-level`, `Mid-level`, `Senior`, `Manager`, `Director`, `Executive`. |
| `salaryMin` | integer | Compares raw numbers only — see the currency warning above. |
| `maxItems` | integer | Per query. `0` = unlimited, which means the whole 100k+ feed. |
| `includeDescription` | boolean | Off gives a much smaller dataset. |
| `incremental` | boolean | Only listings not seen in previous runs. |
| `proxyConfiguration` | object | Datacenter is enough — the feed is published openly. |

### Known limits

- **Filters are client-side.** The feed takes no query parameters, so keyword, category, seniority and salary filters are applied while pages stream in. A narrow filter reads many pages to fill `maxItems`. That is expected behaviour, not an error, and `RUN_COVERAGE` records it.
- **Currencies and periods are mixed.** `salaryMin` compares raw numbers without conversion. Filter on `salary.currency` and `salary.period` yourself if you need a like-for-like comparison.
- **Salary is present on roughly half of listings.** A null `salary.min` usually means the advertiser disclosed nothing, not a parse failure.
- **No numeric job id.** Himalayas keys listings by URL slug, so `source_job_id` is `company-slug/job-slug`. It is stable, which is what deduplication needs.

### Sister Actors

| Actor | Covers |
|---|---|
| SEEK Jobs Scraper | Australia, New Zealand |
| JobStreet & JobsDB Jobs Scraper | Indonesia, Malaysia, Singapore, Philippines, Thailand, Hong Kong |
| Remote OK Jobs Scraper | Remote OK's public feed — read its README first, the feed has known quality problems |

### Local development

```bash
pip install -r requirements.txt
python test_local.py --max 20 --out sample_output.json
python test_local.py engineer --seniority Senior --salary-min 100000 --max 10
```

`sample_output.json` in this folder is real output from a live run, kept so the schema can be reviewed without running anything.

# Actor input Schema

## `queries` (type: `array`):

Keywords matched against job title, company, excerpt and category tags. Leave empty to stream the newest listings, which is the usual choice for monitoring. Filtering is applied as pages stream in, so a narrow keyword reads more pages to fill your limit.

## `categories` (type: `array`):

Restrict to listings carrying any of these Himalayas category tags, e.g. `Software-Engineering`, `Product-Design`, `Customer-Support`. Tags appear in each row's `categories` field, so run once without a filter to discover the ones you want.

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

Restrict by experience level. Values the board uses include `Entry-level`, `Mid-level`, `Senior`, `Manager`, `Director`, `Executive`.

## `salaryMin` (type: `integer`):

Keep only listings whose advertised maximum is at least this figure. Careful: currencies and periods differ between listings (USD per year and GBP per hour both occur), so this compares raw numbers, not converted ones. Listings with no disclosed salary are excluded when this is set.

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

Maximum listings to return per keyword. Set to `0` for unlimited, which pages through the whole feed — currently over 100,000 listings, so set a limit unless you mean it.

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

Include the full job description as both plain text and HTML. Turn off for a much smaller dataset when you only need titles, companies and salaries.

## `incremental` (type: `boolean`):

Remember job ids between runs and return only listings not seen before. You are charged only for the new rows, so a daily monitor costs a fraction of a full re-scrape after the first run. Ids are stored in this Actor's key-value store under `seen_job_ids`.

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

Apify Proxy settings. Defaults to Residential - Apify's own Datacenter proxy range gets blocked by this feed intermittently (this Actor was flagged by Apify's automated QA after failing from a Datacenter IP), even though a direct residential-ISP connection succeeds every time.

## Actor input object example

```json
{
  "queries": [
    "engineer"
  ],
  "categories": [
    "Software-Engineering"
  ],
  "seniority": [
    "Senior"
  ],
  "salaryMin": 100000,
  "maxItems": 100,
  "includeDescription": true,
  "incremental": false,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

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

One row per remote job: title, company, numeric salary with currency and period, seniority, location and timezone restrictions, category tags, description and apply URL.

## `coverage` (type: `string`):

What the run asked for versus what it returned, including per-query failures and how many feed pages were read.

# 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 = {
    "queries": [
        "engineer"
    ],
    "maxItems": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("axery/himalayas-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 = {
    "queries": ["engineer"],
    "maxItems": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("axery/himalayas-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 '{
  "queries": [
    "engineer"
  ],
  "maxItems": 100
}' |
apify call axery/himalayas-remote-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,axery/himalayas-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/lsATGAl73DrmRfzNr/builds/Gvs8T3XlnHn4q1xkp/openapi.json