# Himalayas Remote Jobs Scraper + Only New Jobs (`nomad-agent/himalayas-scraper`) Actor

$0.1/1K jobs | Extract Himalayas remote jobs in bulk with full descriptions, employment type and salary when listed. Filter by keyword, country and posting age. No login or API key.

- **URL**: https://apify.com/nomad-agent/himalayas-scraper.md
- **Developed by:** [Nomad.Devs](https://apify.com/nomad-agent) (community)
- **Categories:** Jobs
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.05 / 1,000 job 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?

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

## Himalayas Jobs Scraper (No Login) + Full Descriptions

$0.1/1K jobs | Extract Himalayas remote jobs in bulk with full descriptions, employment type and salary when listed. Filter by keyword, country and posting age. No login or API key. Independent, unofficial tool. Not affiliated with or endorsed by Himalayas.

### Himalayas Remote Jobs Bulk Scraper

Our scraper reads remote jobs from Himalayas, the remote-jobs platform, and lets you filter by keyword, the countries a job is open to, employment type and posting age. Every row carries the complete original description as text and HTML, plus the title, employer, posting date and a link to the posting on Himalayas. It is ideal for remote job alerts, hiring-market analytics, and remote job boards and newsletters. Job data is from [Himalayas](https://himalayas.app), and each row links back to its Himalayas posting.

- Want Himalayas together with other remote boards in one run? Our [Remote Jobs Scraper — RemoteOK, Remotive, WWR, Himalayas](https://apify.com/nomad-agent/remote-boards-scraper) reads Himalayas, RemoteOK, Remotive and We Work Remotely in one run.
- Want to search many job boards at once? Our [All Jobs Scraper — 21 Job Boards in One](https://apify.com/nomad-agent/all-jobs-scraper) searches many boards in one run.
- Browse all our job-board scrapers: https://apify.com/nomad-agent

#### Key Benefits

- No login or API key: nothing to set up and no account at risk.
- Low pricing: $0.10 per 1,000 jobs, plus a flat $0.00005 per run.
- Complete descriptions: a posting whose description cannot be verified is left out, so every row has the full original text.
- Fresh data: we refresh the newest Himalayas postings about three times an hour, so a run sees jobs from the last few hours.
- No repeats across runs: schedule the same search daily and postings you already received are skipped.

### How It Works

1. Provide your search. Every field is optional:
   - `queries` (e.g., `software engineer`): a posting matches when its title or description contains every word of a query, as whole words. Several queries match any of them.
   - `locations` (e.g., `United States`): a city, region, country name or two-letter country code.
   - `locationTypes` (`remote`, `hybrid`, `onsite`), `employmentTypes` and `postedWithin` (e.g., `7d`, `any`) narrow it further. While one is set, a posting whose source does not state that fact is left out.
2. Run the Actor. Filters are applied to all stored postings before the limit is counted, so you get the newest matches. The `RUN-SUMMARY` record of the run says what was applied.
3. Run the same search again and you get only postings you have not received yet. Set `dedupe.enabled` to `false` to see everything again.

More settings:

- `maxItems` - Maximum number of jobs to return. Default is 50. Zero, or anything above 200, means 200.
- `dedupe` - Skips postings already delivered to your account for the same search. Set `key` to keep separate alert histories.

**A rolling collection, not the whole site.** Each refresh reads the newest 200 Himalayas postings and we keep them, so the collection holds many thousands of recent remote jobs, but not the whole catalogue, which Himalayas puts at over 100,000. Narrow a broad search with `queries`, `locations` and `postedWithin`.

Himalayas lists the countries a job is open to, not a workplace, so the `locations` field of each row is empty. The `locations` filter matches those countries: `United States` finds jobs open to US applicants, and a job that lists no country cannot match a country filter.

Pay is published on some postings only; when Himalayas shows no amount, `salary` is empty. `deadline` is the date Himalayas lists the job until, 60 days after posting, not an application cutoff.

A job that has closed can stay in the collection for up to 30 days, so confirm it is still open on the original page before you apply.

#### Data You'll Receive

- Job details: title, complete description (text and HTML), posting date, listing end date, employment type and salary when published.
- Employer: company name.
- Work arrangement: always `remote`; the countries a job is open to feed the `locations` filter.
- Links: the original Himalayas posting URL.
- Stable `source` and `id` fields to deduplicate across runs.
- Applicant regions: `applicantLocations` lists where the posting says an applicant may live (`null` when the source states nothing, `[]` when it states no restriction); `locations` stays the physical place.

#### Sample output data

Here is an example job from this Actor:

```json
{
  "schemaVersion": "nomad-agent-job-row-v4",
  "source": "himalayas",
  "id": "189ae8543d84f83ea1dc63c485978e1ec926434081cd5a9d5c4ca10757e9b5f8",
  "url": "https://himalayas.app/companies/bright-vision-technologies/jobs/azure-platform-engineer-2624209033",
  "title": "Azure Platform Engineer",
  "company": "Bright Vision Technologies",
  "locations": [],
  "applicantLocations": null,
  "postedAt": "2026-10-13T21:17:44Z",
  "deadline": "2026-12-12",
  "description": "Bright Vision Technologies\nis a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States.\nThis is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential.\nJob Title:\nAzure Platform Engineer\nLocation:\n100% Remote (U.S.)\nPosition Type:\nFull-time, Direct W2\nSalary Range:\n$133,000 … (shortened here)",
  "descriptionHtml": "<a href=\"https://himalayas.app/companies/bright-vision-technologies\">Bright Vision Technologies</a> is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States.<br><br>This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential.<br><br><b>Job Title:</b> Azure Platform En … (shortened here)",
  "workType": "remote",
  "salary": "USD 133000-158000 annual",
  "employmentTypes": [
    "Full-time"
  ],
  "hiringContacts": []
}
```

### Himalayas Jobs API

Results are stored in a dataset that you can export as CSV, JSON or Excel, or read on demand through the Apify API. Schedule the Actor, or connect it to Make, n8n, Zapier or an MCP client through the Apify integrations.

#### Support and Feedback

We improve these scrapers from your feedback. If something breaks or you need a filter:

- Open an issue on the Actor's Issues tab
- If this Actor saved you time, a short review on the Store helps other users find it.

### Run evidence

- Fill rates measured on 2026-10-13 (UTC) over the newest 200 stored Himalayas postings, with the code of this Actor run locally against the stored postings (not a platform run): complete description 200 of 200, locations 0 of 200, posting date 200 of 200, listing end date (always 60 days after posting) 200 of 200, work arrangement 200 of 200, employment type 200 of 200, salary 98 of 200, hiring contact 0 of 200.
- Try-it prefill (`software engineer`, `United States`, last 7 days, 20 jobs) returned 20 rows, 20 with complete descriptions, in the same local check.

***

**Independent tool.** We built and run this Actor ourselves. Himalayas does not operate, sponsor or endorse it, and its name is used only to say which site the data comes from.

# Actor input Schema

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

Match postings whose title or description contains every word of a query, as whole words, ignoring case. A posting matches when any query matches. Empty: no filter.

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

City, region, country name or two-letter ISO country code. Countries match by name, code or native name; EU and Europe expand to their countries. Empty: no filter.

## `locationTypes` (type: `array`):

remote, hybrid or onsite. Postings whose arrangement the source does not state are left out. Empty: no filter.

## `employmentTypes` (type: `array`):

Full-time, Part-time, Contract or Internship. Postings whose type the source does not state are left out. Empty: no filter.

## `postedWithin` (type: `string`):

Positive duration in hours, days, weeks, or 30-day months, at most 36500 days; any disables the filter. Uses the first inventory admission date when the source has no posting date.

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

Maximum returned jobs. Zero, or anything above 200, means 200.

## `dedupe` (type: `object`):

Suppress confirmed repeat deliveries for the same Apify user and search.

## `schemaVersion` (type: `string`):

Version marker for database-only simple job search. Version 1 inputs remain valid.

## Actor input object example

```json
{
  "queries": [
    "software engineer"
  ],
  "locations": [
    "United States"
  ],
  "locationTypes": [],
  "employmentTypes": [],
  "postedWithin": "7d",
  "maxItems": 20,
  "dedupe": {
    "enabled": true,
    "key": ""
  },
  "schemaVersion": "nomad-agent-simple-inventory-search-v2"
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `runSummary` (type: `string`):

One record describing this run: what was attempted, what was delivered, and anything that degraded. Written to the run's key-value store under RUN-SUMMARY.

# 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": [
        "software engineer"
    ],
    "locations": [
        "United States"
    ],
    "postedWithin": "7d",
    "maxItems": 20,
    "dedupe": {
        "enabled": true,
        "key": ""
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("nomad-agent/himalayas-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": ["software engineer"],
    "locations": ["United States"],
    "postedWithin": "7d",
    "maxItems": 20,
    "dedupe": {
        "enabled": True,
        "key": "",
    },
}

# Run the Actor and wait for it to finish
run = client.actor("nomad-agent/himalayas-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": [
    "software engineer"
  ],
  "locations": [
    "United States"
  ],
  "postedWithin": "7d",
  "maxItems": 20,
  "dedupe": {
    "enabled": true,
    "key": ""
  }
}' |
apify call nomad-agent/himalayas-scraper --silent --output-dataset

```

## MCP server setup

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