Himalayas Remote Jobs Scraper

Export public Himalayas remote jobs with titles, companies, published salaries, location requirements, descriptions and application links. Use the dataset for recruiting research, job-board feeds and hiring analysis. No Himalayas login is required.

Results are limited to the jobs exposed by the public feed. A result limit is a ceiling, not a promise of complete coverage or that a vacancy is still open.

Quick start

Enter a keyword, choose a small result limit and click Start. Open the dataset when the run finishes and download CSV, Excel or JSON.

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

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a public example to see its settings before starting a run:

• Fast Canada remote jobs from Himalayas
• Find engineering remote jobs on Himalayas
• Find sales remote jobs on Himalayas

What you get

One public feed-job row with its identity, title, company, source and application links, plus available compensation, published location restrictions, categories and dates. Description text is optional. Missing scalar values stay null, and application links can fall back to the Himalayas job page rather than an external hiring form.

Who is it for?

• Recruiters reviewing source-linked roles and companies exposed by the public feed.
• Job-board operators preparing structured remote-job samples for downstream feeds.
• Compensation and workforce analysts comparing published salaries and location requirements.
• Product and data developers retrieving public job records for their own applications.

How you can use the data

• Build a sales-role review sheet. Use the existing sales query with a twenty-job cap and descriptions enabled. Keep jobUrl, company, employment type and available salary fields together, and open the vacancy before assuming it remains available.
• Review engineering jobs with Canadian eligibility text. Use the existing engineering category URL and country canada recipe with details off. Unrestricted jobs also qualify. Turning details off removes description text rather than all salary, company, date and category fields.
• Read location and compensation without adding assumptions. Retain published restrictions and salary currency and period. Country is repeated restriction text rather than an inferred country code, and Remote can mean that no restrictions were supplied rather than verified worldwide eligibility.
• Compare retained snapshots in your own workflow. Join canonical job URLs and retain collection times, source dates and summary outcomes. A URL target must be present in the searchable feed and satisfy remaining filters. The Actor does not invent missing jobs, track changes or send alerts itself.

Input settings

Setting / API key	Behavior
Start URLs / startUrls	Optional Himalayas jobs, category, country, company jobs or exact job URLs. Up to 200. With none supplied, use the search settings below.
Search query / searchQuery	Optional keyword, such as sales or data analyst. The form suggests sales. Omitted API input does not imply this keyword.
Location keyword / location	Optional text matched against published applicant location restrictions. No geographic inference. Unrestricted jobs also qualify.
Country path / country	Optional country text or slug, such as canada or united-states. Unrestricted jobs also qualify.
Category or skill path / category	Optional match against published categories and parent categories, such as engineering.
Seniority path / seniority	Optional match against published seniority, such as senior.
Job type path / jobType	Optional employment-type match, such as contractor.
Maximum jobs / maxItems	Upper limit across the run, from 1 to 10,000. Default 20.
Include full job details / includeDetails	Default true. Setting false makes descriptionText null. Available salaries, company URLs, dates and categories remain included.

Filters are combined. A start URL overrides only its matching dimension, while unrelated input filters still apply. For example, an engineering category URL plus country: "canada" requires both engineering and Canadian eligibility (including unrestricted jobs). An exact job URL returns that job only if found in the searchable feed and matching the remaining filters.

The Actor accesses public data directly and has no proxy selector. It does not support active proxy settings. It preserves source order rather than offering a custom sorting control.

For a combined category and country search, use this input recipe:

{
  "startUrls": [{ "url": "https://himalayas.app/jobs/engineering" }],
  "country": "canada",
  "maxItems": 20,
  "includeDetails": false
}

Output data

Each dataset row represents one job. The following is a shortened historical output example, not a claim that this vacancy is currently available:

{
  "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"
}

Fields	Meaning
jobId, title	Job slug and published title.
companyName, companyUrl	Hiring company and its Himalayas page.
jobUrl	Canonical Himalayas job URL. Useful for comparing datasets.
applicationUrl, applyUrl	Application URL and its alias. Fall back to the Himalayas job URL when no application link is supplied.
location, country	Joined published location restrictions, or null. country is not a separately inferred country code.
remoteRegion	The same restriction text, or Remote when none is provided. Not an inferred regional classification.
salaryText, salaryMin, salaryMax	Formatted range and available numeric bounds.
currency, salaryCurrency, salaryPeriod	Published salary currency, its alias and period. Read the period before comparing compensation.
employmentType, seniority	Published employment type and seniority text.
categories, tags, categoryTags	Combined parent/category labels. tags repeats that list and categoryTags contains its first eight entries.
postedAt, validThrough	Published posting and expiration dates, when available.
descriptionText	Plain-text description when enabled and available, otherwise null.
scrapedAt	Extraction timestamp.

Missing optional scalar values are generally null. Missing categories are empty arrays. The Actor does not supply private employer/applicant records or apply to jobs.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

Pay-per-event pricing charges start once when processing begins, including searches with no matching jobs, and item for each saved job record. Empty searches do not create job rows or item charges.

See the Pricing tab for current rates and plan discounts.

Tips for best results

• Begin with a small saved-job cap and focused filters. Narrow filters can still require scanning many feed pages.
• Combine URL and input filters deliberately. A URL overrides only its matching dimension, leaving unrelated filters active.
• Keep salary currency and period beside numeric bounds. Published amounts are not automatically comparable across units.
• Read location restrictions rather than inferring eligibility. Unrestricted jobs can pass country and location filters.
• Inspect RUN-SUMMARY before comparing exports. Deadline or page limits can leave partial results even when fewer rows than requested were saved.

Limits and caveats

Coverage is limited to searchable public feed jobs, with no promise that a vacancy remains open. Exact job URLs must be present in that feed and match the remaining filters. The Actor does not provide private employer or applicant records, apply to jobs or invent missing records. No Himalayas login is required, and this Actor is not affiliated with Himalayas.

One run accepts at most two hundred start URLs and processes at most two hundred search pages within a 270-second processing budget. It can stop with fewer rows than requested. Source order is preserved without a custom sort. Start URLs override only their matching filter dimension, and country or location filters include unrestricted jobs using text matching rather than inferred geographic eligibility.

Completed searches without matching jobs succeed with an empty dataset. RUN-SUMMARY records per-page counts, reasons when applicable and whether the deadline or page cap made coverage incomplete. RUN-CHECKPOINT records saved progress. Request, response, essential storage and billing failures fail explicitly rather than pretending to be no matches.

Optional salary, date and other fields can be null, and categories can be empty arrays. Application URLs fall back to the Himalayas job page when absent. Disabling details makes description text null while other available fields remain. The Actor uses direct public access without a proxy selector and does not support active proxy settings. Repeat-export comparisons, alerts and monitoring require your own workflow.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~himalayas-remote-jobs-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "searchQuery": "sales",
  "maxItems": 20,
  "includeDetails": true
}
JSON

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": 20,
  "includeDetails": true
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

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

API and integrations notes

This asynchronous request returns a run, not the jobs. After it reaches a terminal status, retrieve its defaultDatasetId and list that dataset's items. Dataset exports and Apify webhooks can connect results to spreadsheets, CRMs or your own database. Those integrations require separate setup.

MCP and AI agents

You can ask your AI assistant to collect data with Himalayas Remote Jobs Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Himalayas Remote Jobs Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

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

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Himalayas Remote Jobs Scraper by Fetch Cat, or give it the identifier fetch_cat/himalayas-remote-jobs-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Himalayas Remote Jobs Scraper to collect up to 5 sales jobs with descriptions enabled. Keep company names, source links and published salary currency and period, leaving missing values unknown.”
• “Collect up to 5 jobs from https://himalayas.app/jobs/engineering with country canada and details off. Include published location restrictions, noting that unrestricted jobs can qualify and description text is omitted.”
• “Retrieve up to 5 sales jobs with country canada and details enabled. Keep canonical job URLs and collection times for my own later comparison, and inspect RUN-SUMMARY for partial coverage without inferring worldwide eligibility.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can I collect Himalayas remote jobs without an account?

No Himalayas login is needed. An Apify account/token is used for the API examples above. Only the public feed's searchable coverage is supported.

Can I filter jobs by country or category?

Yes. Combine country, category, searchQuery and the other supported filters. Country/location filters include unrestricted jobs and use text matching, not inferred geographic eligibility.

Why are there fewer jobs than maxItems?

There may be fewer matching public records, or the run may have reached its processing limit. Check RUN-SUMMARY for completion and partial-result information. Broaden restrictive filters if appropriate. Increasing the item limit does not guarantee more matches.

Why are salary fields empty or application links on Himalayas?

Some listings do not publish salaries or an external application link. Salary fields then remain null. The application URL falls back to the Himalayas job page. Disabling includeDetails affects description text only.

Can I export the data or use another job source?

Download CSV, Excel or JSON from the dataset, or retrieve items through the API. For other sources, see the related Actors below. Their coverage and inputs differ.

Related Actors

• LinkedIn Public Company Profiles Scraper — enrich companies found through job listings.
• Indeed Jobs Scraper — research hiring on another job source.
• LinkedIn Jobs Scraper — collect cross-source hiring data.
• Google Jobs Scraper — find listings aggregated in Google Jobs.
• Google Maps Lead Finder — collect complementary local business leads.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥