Himalayas Remote Jobs Scraper

Scrape public remote job listings from Himalayas.app and export structured records with companies, salaries, locations, tags, descriptions, and apply links.

What does Himalayas Remote Jobs Scraper do?

Himalayas Remote Jobs Scraper helps you collect remote job listings from Himalayas.app into a clean Apify dataset.

Use it to monitor new roles, build lead lists, enrich job-board data, or analyze hiring demand across remote-first companies.

The actor can start from a Himalayas URL or build a search from keywords and filters. It reads Himalayas' public job feed without login or proxy traffic, avoiding blocked listing and detail pages. Filters are combined. A start URL overrides only the matching input dimension (category, country, seniority, job type, or search query); other input filters still apply. For example, /jobs/engineering with country: "canada" requires both engineering and Canadian eligibility. Country and location filters also allow jobs with no published location restrictions. Location matching uses the published location text, not geographic inference.

It returns one row per job listing.

Each row is designed for CSV, Excel, JSON, API, webhook, and database workflows.

Ready-to-run examples

Start with a small, preconfigured input:

• Find sales remote jobs — Search sales roles with descriptions and available salary fields.
• Find engineering remote jobs — Collect jobs matching the engineering category.
• Find Canada-eligible remote jobs — Include Canada-restricted and unrestricted jobs, without description text. Other available fields remain included.

Quick start

Enter a keyword, set a small result limit, and start the Actor. No login is required. Download the dataset as CSV, Excel or JSON when it finishes.

{
  "searchQuery": "sales",
  "maxItems": 20,
  "includeDetails": true
}

maxItems is an upper limit, not a guaranteed result count. Only jobs exposed by the public feed can be returned.

Who is it for?

• Recruiters: Find remote roles and companies with active hiring signals.
• Job-board operators: Collect structured listings for your own data workflows.
• Analysts: Compare published salaries, locations and categories.
• Developers: Export job records to internal applications through the API.

What data can you extract?

Field	Description
jobId	Himalayas job slug or public identifier
title	Job title
companyName	Hiring company name
companyUrl	Public Himalayas company page
jobUrl	Public Himalayas job page
applicationUrl	Himalayas application link when available
location	Applicant location or country requirement
country	Country/location requirement when published
remoteRegion	Remote region derived from location data
salaryText	Human-readable salary range
salaryMin	Minimum salary value when available
salaryMax	Maximum salary value when available
currency	Salary currency code
salaryCurrency	Salary currency code alias
salaryPeriod	Salary period such as month or year
employmentType	Full-time, contractor, part-time, or similar
seniority	Public seniority/experience description when available
categoryTags	Main category tags shown on the job page
categories	Main tags and categories
tags	Broader public tags found on the job page
postedAt	Public posting date
validThrough	Public expiration date when provided
descriptionText	Plain-text job description
applyUrl	Backward-compatible alias for the application link
scrapedAt	Timestamp of extraction

Pricing

This Actor uses pay-per-event pricing: start is charged once when processing starts, including runs that find no matching jobs, and item is charged for each job record saved to your dataset. See the Pricing tab for current prices and plan discounts. Platform usage, if applicable to your account, is shown separately by Apify.

Example inputs

Search sales roles:

{
  "searchQuery": "sales",
  "maxItems": 25,
  "includeDetails": true
}

Search engineering roles:

{
  "category": "engineering",
  "maxItems": 50,
  "includeDetails": true
}

Search remote roles by country path:

{
  "country": "united-states",
  "searchQuery": "customer support",
  "maxItems": 50,
  "includeDetails": true
}

Start URL examples

You can also provide direct Himalayas URLs:

{
  "startUrls": [
    { "url": "https://himalayas.app/jobs?search=sales" },
    { "url": "https://himalayas.app/jobs/engineering" }
  ],
  "maxItems": 100,
  "includeDetails": true
}

Use start URLs when you already know the exact Himalayas search, category, or company jobs page you want to monitor.

Input settings

startUrls

Optional list of Himalayas URLs to crawl.

If this field is provided, the actor starts from those pages.

searchQuery

Keyword query used on Himalayas job search.

Examples: sales, frontend, data analyst, product manager.

location

Optional free-text location keyword.

Examples: Europe, Canada, United States, Worldwide.

country

Optional country path.

Examples: united-states, canada, united-kingdom.

category

Optional category or skill path.

Examples: engineering, sales, marketing-advertising-pr, project-management.

seniority

Optional seniority path.

Examples: entry-level, mid-level, senior, manager, director, executive.

jobType

Optional job type path.

Examples: full-time, part-time, contractor.

maxItems

Maximum number of jobs to save.

Start with 25 for a smoke test.

includeDetails

Include plain-text descriptions (default: true). Setting this to false omits only description text: available salaries, company URLs, dates and categories are still returned. It is not a URL-only mode.

Output example

{
  "title": "Preconstruction Project Coordinator | South Africa",
  "companyName": "HireHawk",
  "companyUrl": "https://himalayas.app/companies/hirehawk",
  "jobUrl": "https://himalayas.app/companies/hirehawk/jobs/preconstruction-project-coordinator-south-africa",
  "location": "South Africa",
  "salaryText": "USD 1600 - 2000 / month",
  "salaryMin": 1600,
  "salaryMax": 2000,
  "salaryCurrency": "USD",
  "salaryPeriod": "MONTH",
  "employmentType": "Contractor",
  "postedAt": "2026-07-06T08:12:46.000Z",
  "applyUrl": "https://himalayas.app/companies/hirehawk/jobs/preconstruction-project-coordinator-south-africa"
}

Tips for best results

Use a narrow search query when you want highly relevant listings.

Use a category path when you want broad coverage in one job family.

Use maxItems to control run size and cost.

For comparisons over time, retain your datasets and compare jobs by jobUrl; the Actor does not track changes or send alerts itself.

Export to CSV when sharing with recruiting or sales teams.

Use JSON when sending results into an internal pipeline.

Common use cases

Track remote engineering jobs.

Monitor hiring by companies in a target market.

Build a salary benchmark for remote roles.

Find companies hiring remote sales teams.

Create a daily new-postings alert.

Enrich CRM accounts with active hiring signals.

Analyze which countries receive the most remote roles.

Integrations

Send new jobs to Slack using Apify webhooks.

Export datasets to Google Sheets with Make or Zapier.

Load job records into Airtable for recruiting operations.

Send company hiring signals to HubSpot or Salesforce.

Store historical runs in BigQuery, Snowflake, or PostgreSQL.

Trigger downstream enrichment actors after each run.

API usage

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/himalayas-remote-jobs-scraper').call({
  searchQuery: 'sales',
  maxItems: 25,
  includeDetails: true,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient

client = ApifyClient('MY-APIFY-TOKEN')
run = client.actor('fetch_cat/himalayas-remote-jobs-scraper').call(run_input={
    'searchQuery': 'sales',
    'maxItems': 25,
    'includeDetails': True,
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~himalayas-remote-jobs-scraper/runs?token=MY-APIFY-TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"searchQuery":"sales","maxItems":25,"includeDetails":true}'

MCP usage

Use this actor from Claude Desktop, Claude Code, or any MCP-compatible client through the Apify MCP server.

MCP URL format:

https://mcp.apify.com/?tools=fetch_cat/himalayas-remote-jobs-scraper

Claude Code setup:

$claude mcp add apify https://mcp.apify.com/?tools=fetch_cat/himalayas-remote-jobs-scraper

Claude Desktop JSON config:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com/?tools=fetch_cat/himalayas-remote-jobs-scraper"
    }
  }
}

Example prompts:

• "Find 25 remote sales jobs on Himalayas and summarize salary ranges."
• "Scrape remote engineering jobs and group them by company."
• "Collect 50 customer support jobs and export the dataset as CSV."

Scheduling

You can schedule this actor to run every day, every week, or at a custom interval.

Scheduling is useful when you monitor fresh job postings.

Use a stable search query and compare new dataset rows between runs.

Data quality notes

Some job pages do not publish salary data.

Some jobs are restricted to a specific country.

Some jobs may expire after the actor collects them.

The actor returns null for fields that are not publicly available.

FAQ

Can I scrape Himalayas remote jobs without an account?

Yes. This actor collects public job listing and job detail data visible on Himalayas without logging in.

Can I filter by country or category?

Yes. Use country, category, searchQuery, or direct startUrls to target the jobs you need.

Troubleshooting

Why did I get fewer jobs than maxItems?

The selected query or filter may have fewer public results available at run time.

Try a broader query or remove a restrictive filter.

Why is salary missing for some jobs?

Not every Himalayas listing publishes salary data.

When salary is absent, the salary fields are returned as null.

Why does applyUrl point to Himalayas?

Himalayas sometimes routes applications through its own job detail page.

The job URL is still the correct public page for the opening.

Limits

This actor only extracts public information available without logging in.

It does not apply to jobs for you.

It does not bypass access controls.

It does not guarantee that a job remains open after scraping.

Each run accepts at most 200 start URLs and processes at most 200 search pages within a 270-second processing budget. maxItems is an upper limit, not a guaranteed count. Searches and direct-URL lookups are limited to jobs exposed by the public feed. A direct URL is matched exactly; a missing match never produces an invented job row.

Completed searches with no matching jobs succeed with an empty dataset. RUN-SUMMARY records the reason, per-page counts and whether a deadline or page cap made the result incomplete; RUN-CHECKPOINT records saved work. Systemic request, response, storage and billing failures fail the run. Already-started runs cannot be resurrected to replay output; use a fresh run.

The default memory is 256 MiB, with a 512 MiB ceiling. Customer charge limits are checked before fetching more work. Requests use direct access without proxy traffic. This Actor is not affiliated with Himalayas.

Related scrapers

• Google Maps Lead Finder — collect local business leads and company contact signals.
• LinkedIn Public Company Profiles Scraper — enrich companies found through job listings.
• Indeed Jobs Scraper — compare hiring demand across another job source.
• LinkedIn Jobs Scraper — collect job listings for cross-source hiring research.
• Google Jobs Scraper — find job listings aggregated in Google Jobs.

Use related actors together to compare remote hiring demand across multiple sources.

Support

If a run fails or output looks incomplete, open an issue from the Actor page and include only non-sensitive details:

• The input JSON you used.
• The expected output, such as the job title or company you expected to see.
• The actual output you received, including an empty dataset if applicable.
• A reproducible public URL from Himalayas, when your report is about a specific search or job page.
• The Apify run ID and any relevant log message.

Small reproducible inputs make issues easier to diagnose. Never post tokens, cookies or proxy credentials.