Himalayas Remote Jobs API: Eligible Countries + Seniority avatar

Himalayas Remote Jobs API: Eligible Countries + Seniority

Pricing

$0.20 / 1,000 job results

Go to Apify Store
Himalayas Remote Jobs API: Eligible Countries + Seniority

Himalayas Remote Jobs API: Eligible Countries + Seniority

$0.2/1K jobs | Extract remote jobs from recent Himalayas postings with the complete description, seniority, employment type and eligible countries, plus salary when listed. Filter by keyword and posting age. No login or API key.

Pricing

$0.20 / 1,000 job results

Rating

0.0

(0)

Developer

Job Atlas

Job Atlas

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

7 days ago

Last modified

Categories

Share

Himalayas Remote Jobs Scraper + Descriptions (No Login)

$0.2/1K jobs | Extract remote jobs from recent Himalayas postings with the complete description, seniority, employment type and eligible countries, plus salary when listed. Filter by keyword 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 collects remote job postings from Himalayas and lets you filter by keyword, work arrangement and posting age. Every row carries the complete original description in text and HTML, the employer, the posting date, the seniority level, the countries where applicants must be based and a link to the posting. It is ideal for remote-job alerts, salary research and job-board aggregation. Optional AI enrichment and English translation run on us: no key to bring and no extra charge.

It serves a rolling window of recent postings from the public Himalayas jobs feed, up to 200 per run. Himalayas lists far more jobs than this, so treat it as recent remote postings, not the whole Himalayas catalogue.

  • Want more remote boards? Our Dynamite Jobs Actor reads the Dynamite Jobs index. It has no seniority label, and salary is on only some of its rows. Our Jobgether Actor covers Jobgether's remote postings, which carry job function labels more often than a salary.
  • Need jobs that are not limited to one remote board? Use our LinkedIn Actor.

Key Benefits

  • No login or API key: the Actor reads stored postings, so it never asks the Himalayas website for anything on your behalf and you need no account there.
  • Low pricing: $0.20 per 1,000 jobs, with no start fee.
  • Quick to try: ten jobs came back in about 11 seconds of run time in our unfiltered test runs.
  • Complete descriptions: every row has the full original text and HTML. Postings without a verified full description are not delivered.
  • Checked on a schedule: each run's RUN-SUMMARY shows when the source was last checked (sourceFreshAt).
  • No repeats across runs: schedule the same search daily and postings already delivered to you are skipped.

How It Works

  1. Provide your search. Every field is optional. Results come newest first, and an empty search returns the newest stored postings:
    • Keyword (e.g., software engineer, product designer): a case-insensitive phrase matched against the title, the employer name and the complete description. Because it also reads the description, a keyword can match jobs that only mention it.
    • Work arrangements (remote, hybrid, onsite): empty means all. Every posting in our test runs was remote.
    • Posted within (e.g., 48h, 7d, 2w, 1m, or any): default is any.
  2. Run the Actor. Results go to the dataset, and the key-value store holds RUN-SUMMARY with the data freshness, the candidates, the delivery counts and the final status.
  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 jobs per run. The upper bound is 200, and 0 also means 200. Filters and repeat suppression can return fewer.
  • dedupe - Repeat-delivery suppression. On by default. Postings already delivered to your Apify user for the same search are skipped. A non-empty dedupe.key names the alert history, so searches that use the same key share delivery history within your account. If delivery or the ledger cannot be confirmed, the run fails instead of reporting a delivery it cannot prove.
  • filters - Advanced filters over the normalized fields. See "Advanced filters" below.
  • aiEnrichment and translateToEnglish - Optional processing, both off by default. See "Optional AI enrichment and English translation" below.

Cost: you are billed $0.0002 per job delivered, which is $0.20 per 1,000 jobs. There is no start fee, and Apify platform usage for the run is included in that price.

Himalayas shows its own posting date when it is reliable. When it has none, the reported date is the first time the posting was seen, and later refreshes do not make a posting look new.

Postings are returned in the language they were written in. One of our test rows had a Spanish title. Turn on translateToEnglish if you need English display text.

If job data is unavailable or stale, the run fails instead of falling back to scraping the website.

Data You'll Receive

  • Job details: title, complete description (text and HTML), seniority such as Senior or Director, employment type such as Full Time, posting date.
  • Expiry date (data.application.deadline): the listing's expiry date from Himalayas. Every sample row carried the same date, so treat it as an expiry, not an employer's application deadline.
  • Pay: salary range with currency and period when the posting publishes it (7 of 10 rows in each of our two main test runs), for example USD 148912-254054 annual.
  • Where you can work: the remote arrangement, the countries where applicants must be based (19 of 20 rows in our two main test runs) and time zone offsets in custom.data.timezoneRestrictions.
  • Employer: company name. There is no separate employer link or logo field.
  • Link: the posting URL on Himalayas (data.application.url, the same page as identity.url).
  • Identity: identity.source and identity.externalId, a stable key for comparing runs.

Missing facts stay null, and a known empty list is [].

Sample output data

Here is an example job from this Actor. Descriptions are shortened here; real rows carry the full text.

{
"llm": {
"model": null,
"status": "not_requested",
"provider": null,
"completedAt": null,
"filledFields": [],
"promptVersion": null,
"requestedFields": []
},
"raw": {
"description": "Chamberlain Group\n(CG) is a global leader in intelligent access and Blackstone portfolio company. Powered by our myQ technology, we make access simple [...]",
"descriptionHtml": "<p><a href=\"https://himalayas.app/companies/chamberlain-group\">Chamberlain Group</a> (CG) is a global leader in intelligent access and Blackstone portfolio company. Power [...]"
},
"data": {
"title": "Staff Software Engineer - ML/AI",
"company": {
"url": null,
"name": "Chamberlain Group",
"logoUrl": null,
"sourceId": null,
"department": null
},
"domains": null,
"funding": {
"programme": null
},
"benefits": null,
"locations": null,
"seniority": {
"raw": [
"Senior"
],
"levels": null
},
"domainsRaw": null,
"employment": {
"startDate": null,
"hoursPerWeek": null,
"startDateRaw": null,
"contractTypes": [
"Full Time"
],
"workSchedules": null,
"durationMonths": null,
"hoursPerWeekRaw": null,
"workArrangements": [
"remote"
],
"applicantLocationRequirements": [
"United States"
]
},
"application": {
"url": "https://himalayas.app/companies/chamberlain-group/jobs/staff-software-engineer-ml-ai",
"email": null,
"deadline": "2026-12-15",
"postedAt": "2026-10-16T15:47:11Z",
"directApply": null,
"availability": null,
"applyMethodRaw": null,
"hiringContacts": null,
"referenceNumber": null,
"selectionProcess": null,
"applicantSnapshot": null,
"eligibilityCriteria": null,
"referenceNumberIssuer": null
},
"constraints": {
"visaSponsorship": null,
"securityClearance": null,
"workAuthorization": null,
"locationPreference": null
},
"compensation": {
"raw": "USD 148912-254054 annual",
"exact": null,
"period": "annual",
"maximum": 254054,
"minimum": 148912,
"currency": "USD"
},
"requirements": {
"education": null,
"languages": null,
"experience": null,
"certifications": null,
"requiredSkills": null,
"preferredSkills": null,
"skillsQualifications": null,
"specificRequirements": null
},
"classification": {
"industries": null,
"jobFunctions": null
}
},
"custom": {
"data": {
"guid": "https://himalayas.app/companies/chamberlain-group/jobs/staff-software-engineer-ml-ai",
"locationRestrictions": [
"United States"
],
"timezoneRestrictions": [
-10,
-9,
-8,
-7,
-6,
-5,
14
]
}
},
"identity": {
"url": "https://himalayas.app/companies/chamberlain-group/jobs/staff-software-engineer-ml-ai",
"source": "himalayas",
"externalId": "ebc59b90b401b1ce83e6e53b60d9988835d77744bb1d5c79eecee372567da217"
},
"schemaVersion": "nomad-agent-job-v1"
}

Every row follows the same nomad-agent-job-v1 format with six roots: schemaVersion, identity, data, llm, raw and custom. Source-specific facts sit in custom; custom.schemaId identifies the version of the custom.data shape.

Advanced filters

Use the shared nomad-agent-job-filter-v1 expression format for fields other than the ones above. This example keeps jobs whose published minimum salary is at least 150000 US dollars:

{
"schemaVersion": "nomad-agent-inventory-search-v1",
"keyword": "software engineer",
"postedWithin": "7d",
"maxItems": 100,
"filters": {
"schemaVersion": "nomad-agent-job-filter-v1",
"expression": {
"all": [
{"field": "data.compensation.minimum", "operator": "gte", "value": 150000},
{"field": "data.compensation.currency", "operator": "eq", "value": "USD"}
]
}
},
"dedupe": {"enabled": true, "key": ""}
}

Salaries come in several currencies, so pair a salary rule with a currency rule. In one of our test runs, a salary rule alone let through a posting paid in Polish zloty. With AI turned off, filters check source facts only, and unknown values do not satisfy ordinary comparisons.

With AI enrichment on, rows that visibly fail your filter are removed before any AI call, and unknown values are checked again after enrichment.

Optional AI enrichment and English translation

Both are independent opt-ins, off by default, funded by us. You do not supply an API key, and they are not billed separately.

{
"schemaVersion": "nomad-agent-inventory-search-v1",
"keyword": "software engineer",
"maxItems": 50,
"aiEnrichment": {"enabled": true, "accuracy": "silver"},
"translateToEnglish": true,
"dedupe": {"enabled": true, "key": ""}
}
  • AI enrichment fills supported unknown fields and records its provenance in llm. It cannot overwrite a known source fact. Jobs whose requested enrichment fails are withheld, so you can get fewer rows.
  • Translation turns selected display text into English. raw.description and raw.descriptionHtml always keep the original text, and filters run on the normalized values before translation.
  • Only when you turn them on, description text goes to OpenRouter for extraction, and selected display text goes to DeepL for translation. The configured routes deny provider data collection but do not guarantee zero retention or EU-only processing. Extracted facts and translations may be cached by us.
  • Without enrichment, llm.status is not_requested. When enrichment runs, the key-value store also holds OWNER-USAGE, which separates actual provider costs from unpriced token counts.
  • The top-level accuracy field is a compatibility override for aiEnrichment.accuracy. It never turns enrichment on by itself.

Himalayas API

Results are stored in a dataset that you can export as CSV, JSON or Excel, or read on demand through the Apify API. Use latest as the build and keep the build number your run returns if you need to reproduce a result.

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.

Good to know

  • Coverage follows the recent part of the public Himalayas jobs feed that we stored and could verify with a complete description. The Actor does not read the website at run time.
  • Restrictive filters, repeat suppression or a narrow postedWithin can produce zero results. A successful run status alone does not prove complete coverage, so check the dataset and RUN-SUMMARY together.

Migrating from the previous release

  • schemaVersion must be nomad-agent-inventory-search-v1. Inputs from the previous release, which used source-specific fields, fail with migration guidance. Replace them with keyword or filters.
  • identity.externalId is the source's own posting ID as represented in this output, and it may be spelled differently from earlier releases. The stable key is the pair (identity.source, identity.externalId). Update stored comparison keys; existing delivery history can permit a one-time repeat.
  • custom now carries source facts under a new custom.schemaId. The other five roots keep the nomad-agent-job-v1 contract.
  • Relative posting-age windows are limited to 36500 days. Use any for an unrestricted search.

Run evidence

  • Test run on 2026-10-16, build 1.0.5, run v38fd5HmgF6l4ofyO: keyword software engineer, 10 jobs, 8 different employers, all 10 with a complete description. Run time 11.5 seconds.
  • A second run without a keyword (KKheZjAeled5gFHRJ) returned 10 jobs from 10 different employers, all posted on 2026-10-16.
  • In the first run the source had been checked 2 minutes before the run started (sourceFreshAt 16:46 UTC, run at 16:48 UTC).
  • Salary was present on 7 of 10 rows in each of those two runs, an expiry date and a posting URL on all 20, and applicant countries on 19 of 20.
  • Filter test, run ReHBGDWY1Ba7azaqs: keyword software engineer with the salary and currency rules from "Advanced filters" returned 10 jobs, all paid in USD with a minimum of at least 150000. The same salary rule without the currency rule (DTEiJoFxYnc3eDz3O) also returned a PLN posting.
  • Cost per run = jobs delivered x $0.0002.
  • The collector behind this Actor reads up to 200 postings of the newest part of the Himalayas feed per pass, while Himalayas reports a catalogue far larger than that and its total changes between responses.

Job Atlas

Explore the Job Atlas job-data and matching Actors. Use latest and keep the build number each run returns.

Product guide | Source and client examples | Setup skill | Setup guide


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.