Himalayas remote jobs, companies, salaries and talent as JSON
Himalayas offers a free jobs feed and job search.
- endpoints
- 20
- credits per call
- 1–2
1 credit per call≈ $1/1,000 calls1,000 free credits, no card
- Senior Software Engineer
- employment_type
- Full Time
- updated_at
- 2026-10-26
- updated_timestamp
- 1,793,013,430
- Python Tutorial Writer
- employment_type
- Contractor
- updated_at
- 2026-10-13
- updated_timestamp
- 1,791,898,071
- Python Video Course Instructor
- employment_type
- Contractor
- updated_at
- 2026-10-13
- updated_timestamp
- 1,791,898,066
20 active endpoints, on 1 and 2 credit tiers.
- POST/himalayas/v1/search1 credit
- POST/himalayas/v1/search-advanced1 credit
- POST/himalayas/v1/feed1 credit
- POST/himalayas/v1/job2 credits
- POST/himalayas/v1/related-jobs1 credit
- POST/himalayas/v1/region-jobs2 credits
- POST/himalayas/v1/company1 credit
- POST/himalayas/v1/company-jobs1 credit
Run the call yourself, on the real endpoint
Change a parameter and press Try it. The response on the right is what your code will receive.
Himalayas API
5 of 20 endpoints, ready to run
Search remote jobs with Himalayas' filters
// Press "Try it" and this pane shows exactly what the // live site returned this second — including an empty // result, if that is the truth. No key, no account.
What Himalayas endpoints does ReefAPI ship?
20 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
Every parameter, every allowed value →
Missing a Himalayas endpoint, or need a source we don't have yet?Contact us real people · same-day reply.How the Himalayas API works
Himalayas is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.
No OAuth app, no request signing, no per-site account. One key covers all 694 engines.
Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.
Credits, not seats. Failed and blocked calls are never charged, and nothing is cached: every call reads the source live.
One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.
From a remote-job search to the employer's pay and benefits
Search remote jobs, open the listings you want, then read what the employer offers and pays.
20 jobs a page with salary range, location and timezone restrictions, categories, description and apply link, plus the total.
The full listing with skills, education and experience requirement, posting date and apply-before date.
Size, founding year, CEO, markets, tech stack, benefits, website and social links.
Pay per role from the company's own job posts, with currency and countries.
Min, median and max pay for the role in that country.
A list of open remote roles with the employer's profile, listed pay, benefits and the market pay for the same role.
curl -X POST https://api.reefapi.com/himalayas/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"keyword":"python"}'{
"ok": true,
"data": { … },
"meta": {
"api": "himalayas",
"endpoint": "search",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}What a Himalayas field actually contains
Fields that read differently from how they look. Each row was measured on live Himalayas data on 2026-11-16.
| Field | What it holds |
|---|---|
| updated_at (search, feed, company-jobs) | When Himalayas last updated the job, not when it was first posted. On 10 job pages it equalled the page's "Posted on" date 8 times and was later twice (posted 2026-10-28, updated 2026-11-15). |
| posted_on (job, search-advanced, region-jobs) | The date the job page prints as "Posted on". It matched the page on 10 of 10 jobs. |
| salary.min, salary.max, salary.currency, salary.period | The pay the employer listed, in its own currency and period (annual, monthly, hourly). Only 37 of 200 search rows across 10 job types listed a figure; salary.listed says whether there is one. salary.currency can be set without a figure. |
| location_restrictions, worldwide | The countries an applicant must be based in. An empty list with worldwide true means open to every country (859 such jobs on 2026-11-16). |
| timezone_restrictions | The UTC offsets the employer hires in, as numbers (-5, 0, 5.5). The job page prints them as UTC-5, UTC+0, UTC+5.5; they matched on 10 of 10 jobs. |
| talent-search country | Himalayas' own country list: people based in that country or authorized to work there. Python + Canada listed 88 people; about half of the first 20 lived elsewhere and listed Canada as a country they may work in. |
| apply_before | The latest date the job stays listed. Employers can close a job earlier; job then answers not found with the date it closed. |
Search with a keyword returns at most 5,000 results (250 pages of 20). Without a keyword every page is served: the 57,856 United States jobs paged past page 400.
Himalayas coverage, measured
Every number below comes from 297 live calls on 2026-11-16; 259 of 260 lookups answered, and the one that did not was a title Himalayas has no salary data for.
119,538 open remote jobs. Keyword searches return up to 5,000 results (250 pages of 20); searches without a keyword and the feed walk every job. Three feed pages returned 60 jobs with no repeats.
Country, worldwide, seniority, employment type, company and hiring timezone each changed the total (Germany 8,513 of 119,538; UTC+5.5 7,206; contractor 16,306). Salary range, market, benefit and several companies at once: python in Germany 998, at least $100,000 a year 175, fintech 40.
On 10 job pages across 10 job types, 120 of 120 values matched: title, company, salary range, currency, pay period, location requirements, posting date, apply-before date, job type, experience level and hiring timezones. 21 of 21 records opened from search results matched.
34,849 remote-friendly companies; by market (fintech 450), technology (React 5,094), benefit (healthcare 10,761) or country (Germany 2,592). Profiles had size, founding year, markets, about and website on 11 of 11 checked; tech stack and benefits on 8 of 11.
636,505 public talent profiles; by role (python 231) and country (python in Canada 88). Profiles carry experience, education, skills and links; salary expectations on 70 of 120 search rows.
Pay per country for 116 countries, per role and seniority within a country (Germany: 99 roles from 287 salaries), and every reported salary for one role (United States senior software engineer: 1,463). Ranked statistics: 11,467 skills, 250 countries.
Most jobs list no salary (37 of 200 search rows). Paid pinned jobs sit at the top of page 1 of most searches. Search pages come from Himalayas' cache; with sort=recent, pages fetched minutes apart repeated up to 9 jobs in one test (0 in the final test), so de-duplicate on job_id or use feed. No date-posted or visa-sponsorship filter exists on Himalayas.
What people build with Himalayas
The jobs this data is most often used for.
endpoints
credits per call
Feed a remote-job board or alert service with full Himalayas listings, salary ranges and apply links.
Track which companies hire remotely in a country, region or timezone, and for which roles.
Benchmark remote pay by role, seniority and country.
Build lead lists of remote-first companies with size, markets, tech stack and benefits.
What Himalayas data costs
The cheapest call here is 1 credit, so $15/mo (Pro) buys 10,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.
- 1,000 free credits on signup, no card
- One key, all 694 APIs, one credit pool
- Failed and blocked calls are never charged
- Credits roll over and never expire
Call it in two lines
Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.
curl -X POST https://api.reefapi.com/himalayas/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"keyword":"python"}'import os
import requests
REEF_KEY = os.environ["REEF_KEY"]
r = requests.post(
"https://api.reefapi.com/himalayas/v1/search",
headers={"x-api-key": REEF_KEY},
json={
"keyword": "python"
},
timeout=90,
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up Himalayas.
Is there an official Himalayas API?▾
Himalayas offers a free jobs feed and job search. This API returns those jobs and also company profiles, company salaries and benefits, the talent marketplace, salary benchmarks and remote-work statistics as JSON; no Himalayas account is needed.
Which search filters work?▾
Each was checked against the unfiltered count on 2026-11-16 (119,538 jobs): United States 57,856, Germany 8,513, Germany without worldwide jobs 7,666, worldwide only 859, senior 46,369, executive 3,232, contractor 16,306, internship 1,590, company micro1 456, UTC-5 70,718, UTC+5.5 7,206. search-advanced on python in Germany (998): salary at least $100,000 a year 175, at most $60,000 43, fintech companies 40, companies with healthcare benefits 213.
How accurate is the data?▾
On 10 job pages across 10 job types, title, company, salary range, currency, pay period, location requirements, posting date, apply-before date, job type, experience level and hiring timezones matched the API on 120 of 120 values. 21 records opened from search results kept the same title, company and salary.
How many jobs can I page through?▾
A keyword search returns up to 5,000 jobs (250 pages of 20). A search without a keyword, or the feed action, walks every open job; three consecutive feed pages returned 60 jobs with no repeats.
Does it return salaries?▾
When the employer lists one: min, max, currency and pay period on each job. Most Himalayas jobs list none (37 of 200 search rows on 2026-11-16). The salary actions add benchmarks: salaries gives min, median and max in USD per title, seniority and country (senior product manager in the United States: $63,900 to $366,000, median $214,950, 486 data points); salary-role lists every reported salary for a role in a country.
Can I get company data?▾
Yes. company returns employee range, founding year, CEO, employee countries, markets, open positions, about text, the tech stack by category, benefits by category, website and social links. company-salaries returns pay per role from the company's own job posts, company-benefits each benefit with its description, and company-jobs every open job.
What is in a talent profile?▾
The public himalayas.app/@name page: headline, availability, location, countries the person may work in, salary expectations, job categories, skills, portfolio and LinkedIn links, what they are looking for, about, each job with company, dates, description and skills, education and tech stack.
What does statistics return?▾
Himalayas' ranked lists: skills, job categories or countries by number of open jobs, and countries or industries by number of remote companies, 200 rows a page. The skills list held 11,467 entries; Python led with 12,908 open jobs on 2026-11-16.
What is the Himalayas API?▾
Himalayas API is a ReefAPI endpoint group for remote jobs, companies, salaries and remote talent from himalayas. It returns live JSON through POST requests under /himalayas/v1.
Is the Himalayas API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. Himalayas calls use the same shared credit balance as every other ReefAPI engine.
Do I need a Himalayas login or account?▾
No login to Himalayas is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the Himalayas data?▾
The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the Himalayas API use?▾
Himalayas actions currently cost 1-2 credits per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.
Can I call Himalayas from an AI assistant or MCP client?▾
Yes. Connect ReefAPI once through MCP and your assistant can call himalayas actions with the same key, credit pool and JSON envelope used by normal REST requests.
32 Jobs & Hiring APIs on the same key
One key, one credit pool, one response envelope. If you are pulling Himalayas, you are one call away from the rest of the category — no second contract, no second integration.
Need something this API does not do?
Name the endpoint, the field, or a source we do not carry yet. We ship new APIs every week and you would be first to get the key. Real people read every message and reply the same day.
Try it on your own data before you pay anything
The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 693 APIs, and the same envelope everywhere.
Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts. Field notes were captured on 2026-11-16.