Himalayas Jobs Scraper (Remote Jobs with Filters)

What is Himalayas Jobs Scraper?

Himalayas Jobs Scraper collects remote job listings from Himalayas by keyword and country, and applies employment type, seniority, salary and posting-date filters to the results. Each job becomes one row: title, company, pay range, location restrictions, categories, publish and expiry dates, excerpt and the Himalayas job link. It reads Himalayas' public job API, so no login is needed.

What data does Himalayas Jobs Scraper extract?

Field	Type	Meaning
guid / url	string	Himalayas job page (canonical link)
title	string	Job title
companyName, companySlug, companyUrl, companyLogo	string	Employer as Himalayas lists it
employmentType	string	e.g. Full Time, Part Time, Contractor, Intern
seniority	array	e.g. ["Senior"], ["Entry-level"]
categories, parentCategories	array	Himalayas job categories
locationRestrictions	array	Countries the job is open to (empty = no country limit)
timezoneRestrictions	array	Allowed UTC offsets (hours)
minSalary, maxSalary, currency, salaryPeriod	number / string	Pay as published; often empty
pubDate, expiryDate	ISO string	Publish and expiry time
excerpt	string	Short summary from the listing
description	string	Full description as plain text (only with "Include full description")
searchQuery, searchCountry	string	The search that found the row
scrapedAt	ISO string	When the row was collected

How to use Himalayas Jobs Scraper

1. Open the actor in Apify and go to the Input tab.
2. Enter keywords, for example python developer. Leave it empty to read the public browse feed, newest first.
3. Optionally set a country restriction (for example Germany), filters and a maximum job count.
4. Click Start and wait for the run to finish. Download the dataset as JSON, CSV or Excel.
5. For scheduled or agent use, call the actor through the Apify API with the same input.

Example input

{
    "keywords": "python developer",
    "country": "Germany",
    "employmentType": "Full Time",
    "maxJobs": 40,
    "fetchDescriptions": true
}

Example output

Real row from a run on 2026-10-23 (input above; trimmed for length):

{
    "position": 1,
    "guid": "https://himalayas.app/companies/novakid-school/jobs/python-backend-developer-fullstack-capable",
    "title": "Python Backend Developer, Fullstack-capable",
    "companyName": "Novakid School",
    "employmentType": "Full Time",
    "seniority": ["Senior"],
    "locationRestrictions": [],
    "minSalary": null,
    "maxSalary": null,
    "salaryPeriod": "annual",
    "pubDate": "2026-10-20T07:43:47.000Z",
    "expiryDate": "2026-12-19T07:43:46.000Z",
    "searchQuery": "python developer",
    "searchCountry": "Germany",
    "description": "Novakid is an online English school for kids. ..."
}

The run returned 40 rows in about 12 seconds (run NMeg78mD0mjtB7PmD); the platform usage of that run was USD 0.00058.

Input parameters

• Keywords: search words for title, skill or company. Empty = browse feed.
• Country restriction: passed to the API as a country filter (for example Germany).
• Employment type: exact label, applied after the fetch.
• Seniority: one label, applied after the fetch.
• Minimum salary: keeps jobs whose top published salary is at least this value. Jobs without salary data are dropped when this is set.
• Posted within days: keeps jobs published in the last N days.
• Max jobs: upper limit for the run (up to 5,000).
• Include full description: adds plain-text descriptions.
• Proxy mode: direct first by default; residential proxy only after blocks.

Pricing

Pay per result: USD 0.0008 per job at the base tier. Volume tiers lower the price for higher Apify plans (the current floor is USD 0.00048 per job). The actor start is billed as well (USD 0.00005).

Measured platform usage: USD 0.00058 for a 40-job run with descriptions, which is about USD 0.015 per 1,000 jobs in compute. Reference: the largest competing Himalayas actor on the Store charges USD 0.001 per dataset item.

Himalayas Jobs Scraper vs. alternatives

• Browse feed or keyword search: the public API serves 20 jobs per page. A single keyword query returns at most 5,000 jobs (250 pages); the browse feed pages through the whole feed by cursor.
• Filters: employment type, seniority and salary are not API filters, so they are applied after each page. A filtered run saves fewer rows than it scans, and you pay only for saved rows.
• Remote-only: every Himalayas job is a remote job. For a cross-board remote feed, use the remote jobs aggregator actor from the same publisher.

Using Himalayas Jobs Scraper with AI agents

The actor has a pay-per-result price and a schema with field descriptions, so an MCP client can call it with a keyword and read the rows directly. Pass maxJobs to bound the cost; the run stops at the limit or at the end of the results, whichever comes first.

FAQ

Does it need a login or proxy? No. The direct API works from Apify's datacenter IPs; the residential option is there only for blocks.

How complete is the salary data? Himalayas publishes salary for a minority of jobs. In the 40-job test run, 4 of 40 rows had a salary; the rest have null salary fields.

Can I combine it with other job sites? Yes. Rows share title, companyName, pubDate and url, so one dataset per source merges cleanly.

Why did a run return fewer rows than Max jobs? Post-fetch filters (employment type, seniority, salary, date) drop rows; the run then reaches the end of results or the page limit.

Is the description complete? It is the HTML description from the API, converted to plain text. Formatting is simplified (lists become "- " lines).

What about errors? If nothing matches or the API stops responding, the actor writes a record named ERRORS in the key-value store and does not charge for rows it did not save.

Support

Open an issue on the actor's Issues tab. Himalayas is a third-party site; this actor is not affiliated with Himalayas.