Himalayas Jobs Scraper: Remote Jobs API with Salaries avatar

Himalayas Jobs Scraper: Remote Jobs API with Salaries

Pricing

from $0.60 / 1,000 job ads

Go to Apify Store
Himalayas Jobs Scraper: Remote Jobs API with Salaries

Himalayas Jobs Scraper: Remote Jobs API with Salaries

Remote jobs from Himalayas through its public jobs API: title, company, salary range, seniority, categories, the countries and time zones open to candidates, full description and job link. Filter by keyword, country, time zone, seniority, type and date. Pay per job, no personal data.

Pricing

from $0.60 / 1,000 job ads

Rating

0.0

(0)

Developer

Rowcraft

Rowcraft

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

17 hours ago

Last modified

Share

Get remote jobs from Himalayas, a board for remote work with more than 120,000 open jobs from companies that hire across borders. This Himalayas jobs scraper reads the board's public Remote Jobs API, so it is fast, needs no login or key and does not break when a web page changes. Each job comes back as one flat row: title, company, salary range, seniority, employment type, the countries and time zones open to candidates, categories, the full description and the link to the job, as JSON, CSV or Excel.

Filter by keyword, country, time zone, seniority, employment type, category, company and date, or leave everything empty for every job posted in the last 3 days. Schedule it with Only new rows to get a daily feed of new remote jobs for the price of the new jobs only.

Input form of Himalayas Jobs Scraper: Remote Jobs API with Salaries

What you get

One row per job, the same columns for every job:

  • Job: title, employment type (full-time, part-time, contract, temporary, internship), seniority levels, publication and expiry dates, the job page and apply link on Himalayas
  • Company: name, Himalayas company page and slug, logo link
  • Where you can work from: the countries open to candidates (names and ISO codes), whether the job is open worldwide, the accepted time zones as UTC offsets and as text (UTC-8 to UTC-5)
  • Pay: salary from and to, currency, period (year, month, hour) and a readable line such as USD 120,000–160,000 per year, when the company publishes it
  • Categories: the broad group (Developer, Data Science, Sales, Marketing, Design) and the detailed categories Himalayas assigns
  • Texts: a short summary and the full description as plain text, optionally as HTML, with e-mail addresses and phone numbers removed

Why this actor

  • Official public API, read as documented: the browse feed with cursor pagination, the way Himalayas recommends, newest jobs first, and one search request per company you list; no scraping of web pages, no proxies, no headless browser.
  • Filters that matter for remote work: countries open to candidates (with or without worldwide jobs), time zones you can work in, seniority, employment type, category, company, salary published, words to exclude from titles.
  • Clean, stable rows: employment types and salary periods in plain words, country codes next to country names, time zones as numbers and as text, dates in ISO format, 33 fields that never change name.
  • Built for schedules: Only new rows remembers what you already received, so a daily run costs only the new jobs; a webhook can tell Slack, Discord, Make, n8n or Zapier when new jobs arrive.
  • Small and cheap to run: 256 MB of memory is enough, and you pay per job delivered, with a charge cap.

How to use it

  1. Open the Actor and fill in Keywords (the other fields are optional filters).
  2. Set Maximum job ads to a small number for a first try (the default is a safe start).
  3. Click Start. The status line shows progress; the run stops cleanly at your limit or at the charge limit you set in the run options.
  4. Open the Dataset tab and download JSON, CSV, Excel, XML or HTML, or send the rows to Google Sheets, Slack, Make, n8n or Zapier with the Integrations tab.
  5. To run it on a schedule, use Schedules in Apify Console and turn on Only new rows since the last run below: every run then costs only the new rows, and a webhook URL tells you when something new came in.

Input

FieldWhat it does
keywordsWords that must appear in the job title, any of them (engineer, python, customer success); empty = all jobs
countriesCountries open to candidates, names or ISO codes (Germany, DE, United Kingdom)
postedAfter24 hours, 3 days, 2 weeks, today, a date or a timestamp; default 3 days; empty = the whole feed
maxItemsStop after this many jobs (default 500, 0 = all)
seniority, employmentTypesEntry-level to Executive; full-time, part-time, contract, temporary, internship, volunteer
categories, companiesExact category names, broad or detailed (Developer, Data Science, Product Manager); company names or slugs (gitlab)
timezonesUTC offsets you can work in (UTC+1, -5, +05:30); jobs without a time-zone requirement always match
includeWorldwide, worldwideOnlyKeep worldwide jobs next to your countries (default on), or only worldwide jobs
withSalaryOnly, excludeKeywords, keywordsInDescriptionOnly jobs with a published salary; drop titles with these words; match keywords in the description too
includeDescription, includeHtmlDescriptionPlain-text description and summary (default on); the HTML version as well
onlyNew, stateName, notifyUrl, notifyWhenEmptySee Automation below
requestIntervalMsPause between API requests, default 1,000 ms

Example: senior and mid-level engineering jobs open to candidates in Germany or worldwide, that accept UTC+1, posted in the last 3 days, with a salary.

{
"keywords": ["engineer", "developer"],
"countries": ["Germany"],
"timezones": ["UTC+1"],
"seniority": ["Senior", "Mid-level"],
"withSalaryOnly": true,
"postedAfter": "3 days",
"maxItems": 200
}

Output

33 fields per row. Empty values are null, never missing, so CSV and Excel columns are stable.

FieldTypeExample
idstringhimalayas:toptal/sales-recruiter
jobIdstringtoptal/sales-recruiter
sourcestringHimalayas
titlestringSenior Backend Engineer
companyNamestringToptal
companySlugstringtoptal
companyUrlstringhttps://himalayas.app/companies/toptal
companyLogoUrlstringhttps://cdn-images.himalayas.app/i9lxmh7lp781wbkei83sm23go57q
urlstringhttps://himalayas.app/companies/toptal/jobs/sales-recruiter
applyUrlstringhttps://himalayas.app/companies/toptal/jobs/sales-recruiter
employmentTypestringFull-time
senioritystringMid-level, Senior
seniorityLevelsarray["Mid-level", "Senior"]
workplaceTypestringRemote
isRemotebooleanTrue
locationstringRemote (United States, Canada)
worldwidebooleanFalse
countriesarray["United States", "Canada"]
countryCodesarray["US", "CA"]
timezonesarray[-8, -7, -6, "… 1 more"]
timezoneTextstringUTC-8 to UTC-5
parentCategoriesarray["Developer"]
categoriesarray["Backend Engineer", "Software Engineer", "Python Developer"]
salaryMinnumber120000
salaryMaxnumber160000
salaryCurrencystringUSD
salaryPeriodstringyear
salaryTextstringUSD 120,000–160,000 per year
publishedAtstring2026-10-11T18:46:27.000Z
expiresAtstring2026-12-10T18:46:26.000Z
excerptstringToptal is a global network of top talent in business, design, and t…
descriptionTextstringAbout the role You will build and run our payment services…
descriptionHtmlstring

About the role

You will build…

Example rows

Two real rows from a run (long texts shortened here, complete in the dataset):

[
{
"id": "himalayas:encharge-ai/ai-compiler-engineer",
"jobId": "encharge-ai/ai-compiler-engineer",
"source": "Himalayas",
"title": "AI Compiler Engineer",
"companyName": "EnCharge AI",
"companySlug": "encharge-ai",
"companyUrl": "https://himalayas.app/companies/encharge-ai",
"companyLogoUrl": "https://cdn-images.himalayas.app/bvi7nourt8fsmj6yi9paey3labxe",
"url": "https://himalayas.app/companies/encharge-ai/jobs/ai-compiler-engineer",
"applyUrl": "https://himalayas.app/companies/encharge-ai/jobs/ai-compiler-engineer",
"employmentType": "Full-time",
"seniority": "Mid-level",
"seniorityLevels": [
"Mid-level"
],
"workplaceType": "Remote",
"isRemote": true,
"location": "Remote (Germany)",
"worldwide": false,
"countries": [
"Germany"
],
"countryCodes": [
"DE"
],
"timezones": [
1
],
"timezoneText": "UTC+1",
"parentCategories": [
"Developer",
"Data Science"
],
"categories": [
"Compiler Engineer",
"Software Engineer",
"AI Engineer",
"… 6 more"
],
"salaryMin": 190000,
"salaryMax": 255000,
"salaryCurrency": "USD",
"salaryPeriod": "year",
"salaryText": "USD 190,000–255,000 per year",
"publishedAt": "2026-10-11T20:44:14.000Z",
"expiresAt": "2026-12-10T20:44:13.000Z",
"excerpt": "EnCharge AI is a leader in advanced AI hardware and software systems for edge-to-cloud computing.",
"descriptionText": "EnCharge AI is a leader in advanced AI hardware and software systems for edge-to-cloud computing. EnCharge’s robust and scalable next-gen…"
},
{
"id": "himalayas:isla/senior-backend-engineer",
"jobId": "isla/senior-backend-engineer",
"source": "Himalayas",
"title": "Senior Backend Engineer",
"companyName": "Isla",
"companySlug": "isla",
"companyUrl": "https://himalayas.app/companies/isla",
"companyLogoUrl": "https://cdn-images.himalayas.app/al01o8mwqdpvaij9y7w2o79n54m6",
"url": "https://himalayas.app/companies/isla/jobs/senior-backend-engineer",
"applyUrl": "https://himalayas.app/companies/isla/jobs/senior-backend-engineer",
"employmentType": "Full-time",
"seniority": "Senior",
"seniorityLevels": [
"Senior"
],
"workplaceType": "Remote",
"isRemote": true,
"location": "Remote (Ireland)",
"worldwide": false,
"countries": [
"Ireland"
],
"countryCodes": [
"IE"
],
"timezones": [
1
],
"timezoneText": "UTC+1",
"parentCategories": [
"Developer"
],
"categories": [
"Backend Engineer",
"NodeJS Developer",
"Cloud Engineer",
"… 6 more"
],
"salaryMin": 80000,
"salaryMax": 92000,
"salaryCurrency": "EUR",
"salaryPeriod": "year",
"salaryText": "EUR 80,000–92,000 per year",
"publishedAt": "2026-10-11T20:02:41.000Z",
"expiresAt": "2026-12-10T20:02:40.000Z",
"excerpt": "Senior Node. js & Cloud Engineer🕙 Role details: This is a full time role (40 hours per week) 💷 Salary: €80,000 - 92,000 🌍 Location: Irela…",
"descriptionText": "Senior Node.js & Cloud Engineer\n🕙 Role details: This is a full time role (40 hours per week)\n💷 Salary: €80,000 - 92,000\n🌍 Location: Irela…"
}
]

Results can be downloaded as JSON, CSV, Excel, XML or HTML from the Dataset tab, or read through the Apify API.

Results of Himalayas Jobs Scraper: Remote Jobs API with Salaries in the Apify dataset view

Pricing

Pay per result. You pay for each job ad delivered to your dataset, nothing else: no subscription, no minimum, no charge for rows your filters drop or for the requests behind them.

Your Apify planPrice per 1,000 rowsPrice per row
Free plan$0.90$0.0009
Starter plan$0.80$0.0008
Scale plan$0.70$0.0007
Business plan and above$0.60$0.0006

Example: 1,000 job ads cost $0.90 on the Free plan and $0.60 on the Business plan. The Apify platform usage of a run (compute, storage) is small for this actor — well under one cent per 1,000 rows — and is billed by Apify separately, as for every Actor. A start event of $0.00005 is charged once per run (Apify default). Cap your spend: set Maximum total charge in the run options. The actor stops cleanly when the cap is reached and you keep everything delivered until then. The run summary (RUN_SUMMARY in the key-value store) says why a run stopped.

Automation: only new rows, notifications, schedules

Only new rows since the last run. Turn on onlyNew and the actor remembers every job ad it delivered to you (in a key-value store named rowcraft-himalayas-jobs-scraper-state in your Apify account). The next run with the same stateName skips what you already have and you pay only for new rows. The first run delivers everything that matches. Use a different stateName for each schedule or search so they keep separate memories.

Notification when the run ends. Put a webhook address in notifyUrl and the actor sends one JSON POST with the number of new rows, links to the dataset (JSON and CSV) and the run. It works out of the box with Slack and Discord incoming webhooks (the message is in text and content), with Make, n8n and Zapier catch hooks, and with your own endpoint. By default it is sent only when there is at least one new row; notifyWhenEmpty sends it every time.

Schedules. Create a schedule in Apify Console (hourly, daily, weekly or cron) with onlyNew on. A daily schedule gives you a feed of new job ads for the price of the new rows only.

Integrations. Send the results to Make, n8n, Zapier, Google Sheets, Slack, Google Drive, Airtable or any webhooks from the Integrations tab of the Actor, with no code. Apify also offers native actions for Make, n8n and Zapier.

API, SDKs and AI agents. Every run is available through the Apify API and the official JavaScript and Python clients; the Actor can also be called by AI agents through the Apify MCP server. The example input in the API tab is a working call.

Use cases

  • Job alerts for remote workers: a daily feed of new jobs that accept your country and time zone, straight into Slack, Telegram or a sheet.
  • Remote job boards and newsletters: fill a niche board (a stack, a language, a region) with fresh remote jobs, keeping the link to Himalayas as its terms ask.
  • Salary research: pay ranges by seniority, category and country for thousands of remote jobs, in one table.
  • Hiring-market intelligence: which companies hire remotely, for which roles, open to which countries and time zones; spot companies that start hiring in your market.
  • AI agents and automations: give an agent a clean, filtered list of current remote jobs through the Apify API or the MCP server.

Ready-made examples, each with the input filled in (open one and press Start, or save it as your own task):

What this actor does not do

  • Apply to jobs, read applicants, or deliver recruiter names, e-mail addresses or phone numbers.
  • Read the Himalayas website pages, talent profiles or company ratings; only the public jobs API is used.
  • Page through the search endpoint: robots.txt of himalayas.app excludes numbered pages on job paths, so the actor reads only the first search page of each company you list and applies every other filter on the documented browse feed.
  • Submit jobs to Jooble, Neuvoo, Google Jobs or LinkedIn Jobs; the Himalayas terms do not allow that, and neither should you (see Data source).
  • Log in, use proxies or solve CAPTCHAs: the public API needs none of that.

Limits and fair use

  • One request per second by default (500 ms at the lowest). Each request returns 20 jobs, the API maximum, so reading one day of the feed (6,694 new jobs in one 24-hour count, October 2026) takes about 6 minutes, 3 days about 17 minutes and 7 days about 40 minutes or more. Narrow filters do not make the run shorter, because the filters are applied on the feed; the date limit does. Companies are the exception: each company you list costs one request (its 20 newest jobs), and the feed is read only for a company that has more jobs than that inside your date limit.
  • postedAfter is your main speed control: 24 hours with Only new rows on a daily schedule is the cheapest way to follow the market. Leaving it empty reads the whole feed (about 120,000 jobs, about 6,000 requests, more than an hour); raise the run timeout in the run options and set maxItems or a charge cap for that.
  • A run stops by itself 90 seconds before its timeout (60 minutes by default), keeps everything delivered and says time limit in the run summary; with Only new rows the next run continues without repeats.
  • The feed is served through a cache, so the newest jobs can appear up to about two hours after Himalayas publishes them.
  • If the API answers with a rate limit (HTTP 429) the actor waits and retries; if it keeps refusing, the run stops and keeps everything delivered (see stoppedAt and error in the run summary).
  • Salaries are published by some companies only (roughly one job in three); withSalaryOnly keeps those.

Data source

The data comes from the Himalayas Remote Jobs API, the public JSON interface of himalayas.app. No key, login or cookie is needed and no path excluded by robots.txt is read. The API page says that anyone can use the interface, asks users to link back to the job URL on Himalayas and to mention Himalayas as the original source, and asks that jobs are not submitted to third-party sites such as Jooble, Neuvoo, Google Jobs or LinkedIn Jobs. Every row therefore carries the job link (url) and the source (source: Himalayas); if you publish the jobs, keep both and follow those terms. Rowcraft is independent and not affiliated with or endorsed by Himalayas; the name belongs to its owner.

Privacy: no personal data

Rowcraft actors are built not to collect personal data:

  • The API returns job and company fields only. Nothing about applicants, recruiters or Himalayas users is requested.
  • E-mail addresses, phone numbers, personal profile links and contact-person names written inside job descriptions are removed before the row is saved.

You are responsible for using the data in line with the law that applies to you.

Other Rowcraft actors

All Rowcraft actors read official or public sources, deliver flat rows without personal data and support only-new runs and notifications:

FAQ

Which jobs are included? Every job in the public Himalayas feed: remote jobs from companies all over the world, in engineering, data, product, design, sales, marketing, customer support, operations, finance, education and more. Several thousand new jobs are added each day (6,694 in one 24-hour count in October 2026), and most jobs carry an expiry date about 60 days after publication.

How do the country and worldwide filters work? Each job lists the countries whose residents may apply; a job with no list is open worldwide. With countries set you get the jobs that accept one of your countries plus, by default, the worldwide ones; turn off Include jobs open worldwide to drop those, or use Only jobs open worldwide for the opposite.

How does the time-zone filter work? Many remote jobs require overlap with certain time zones. Type the UTC offsets you can work in (UTC+1, -5, +05:30); a job matches when it accepts one of them. Jobs without a time-zone requirement always match.

How do categories work? Every job has one or two broad categories (parentCategories, such as Developer, Data Science, Sales) and a list of detailed ones (categories, such as Backend Engineer or Python Developer). The filter matches exact names from either list, not parts of names, so Developer does not return a sales job tagged "Business Developer". Run once without the filter to see the names in your field.

Can I search in the job description? Yes: turn on Search keywords in the description too. Without it the keywords are matched in the title only, which is more precise.

Why does a narrow search still take minutes? The actor reads the documented browse feed newest first and filters it here, because the numbered pages of the search endpoint are excluded by the site's robots.txt. The time depends on the date range (postedAfter), not on the number of matches: one day is about 6 minutes, three days about 17, a week about 40 or more. Searches by company are fast: one request per company.

Is the salary always there? No, only when the company publishes it; then you get the range, the currency and the period. Use Only jobs with a salary to keep those jobs only.

Can I republish these jobs on my own job board? The Himalayas API page allows backfilling job boards when you link back to the job URL on Himalayas and name Himalayas as the source, and it does not allow submitting the jobs to Jooble, Neuvoo, Google Jobs or LinkedIn Jobs. Read the terms on the API page before you publish anything.

Why are some jobs older than my date limit missing, or some newest ones late? The feed is cached for up to about two hours, and the run stops at the first page that is entirely older than postedAfter. Jobs published in that window appear on the next run; with Only new rows you never get the same job twice.

How much does it cost? $0.90 per 1,000 job ads on the Free plan, less on paid plans (see Pricing). You pay only for rows delivered to your dataset; set a maximum total charge in the run options to cap a run.

How do I get the results into Slack, Google Sheets, Make, n8n or Zapier? Use the Integrations tab of the Actor for the data, and the notifyUrl field for a message when a run ends (Slack and Discord webhooks work directly; catch hooks of Make, n8n and Zapier too).

Can I call it from code or from an AI agent? Yes: through the Apify API, the JavaScript and Python clients, and the Apify MCP server. The API tab shows a working example with the input of this Actor.

Is it legal to use this data? The actor reads the official API described in the Data source section and delivers company and job data without personal data. The licence of the source is described above. How you use the data is your responsibility under the law that applies to you.

Does it collect personal data? No. Contact persons, e-mails and phone numbers are removed and fields about people are never requested. See the Privacy section.

The run finished with 0 rows. Did I pay? No: with no rows delivered nothing is charged apart from the start event. Check the run summary (RUN_SUMMARY) for warnings, widen the filters, or run with Only new rows off if everything matching was already delivered to you.

Support and reviews

Problems, missing fields, questions: open an issue on the Issues tab of this Actor. We answer within one working day and fix confirmed bugs in the next release; the changelog lists every change.

If this Actor saved you time, a short review on its page helps other users find it and helps us keep improving it.