Himalayas Jobs Scraper - Search & All Current Remote Jobs
Pricing
from $2.00 / 1,000 results
Himalayas Jobs Scraper - Search & All Current Remote Jobs
Search current Himalayas remote jobs by keyword or export all current job types with salary, categories, location restrictions, apply links, and normalized fields.
Pricing
from $2.00 / 1,000 results
Rating
0.0
(0)
Developer
kane liu
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
5 days ago
Last modified
Categories
Share
Himalayas Jobs Scraper - Search & Export All Current Remote Jobs
Search or filter Himalayas remote jobs by keyword, geo, and industry/category, or export current listings of every job type with salary, categories, location restrictions, and application links as a clean Dataset. This Actor uses the public Himalayas jobs API with offset pagination and returns normalized, deduplicated job records ready for spreadsheets, dashboards, recruitment pipelines, or AI agent workflows.
There are no preset keywords, geos, or industries. Leave filters empty to collect all current job types from the live feed, or set searchQuery, geo, and/or industry to narrow results. Every row includes the original API object in a raw field.
Why use this Himalayas Scraper?
- Keyword search: enter
searchQueryto filter current jobs by title, company, description, excerpt, categories, location, and URLs. - Geo filter: enter
geo(for exampleusa,uk,canada,india,worldwide) to match HimalayaslocationRestrictionswith common region aliases. - Industry / category filter: enter
industry(for examplesoftware-engineering,sales,digital-marketing) to match Himalayas categories and parent categories. - All job types by default: empty input does not hard-code categories or keywords; it collects the live paginated feed as-is.
- Structured output: title, company, salary, categories, location restrictions, employment type, seniority, application link, and timestamps.
- Original raw data: each row keeps the unmodified upstream API object.
- Deduplication: response-local duplicates and malformed rows are skipped, with counts in
RUN_SUMMARY. - Filter provenance: filtered rows include
sourceSearchQuery/searchRankand/orsourceGeo/sourceIndustry/filterRank. - No credentials needed: public API, no login.
- Attribution built in:
source_urlandattribution_urlpoint back to Himalayas.
Tutorial
- Click Try for free on this Actor page.
- Optionally enter
searchQuery(for examplepython,design,customer success). - Optionally enter
geo(for exampleusa,uk,worldwide) and/orindustry(for examplesoftware-engineering,sales). - To export all current job types from the live feed, leave
searchQuery,geo, andindustryempty. - Set
maxItemsto control cost. Prefill25is a safe canary size.0means no user limit up to the Actor safety cap of 5000 rows. - Click Start and wait for the run to finish.
- Open the Dataset tab to download JSON, CSV, Excel, or JSONL.
- Check
RUN_SUMMARYin the key-value store for pages fetched, source counts, and duplicates.
Example inputs
All-current job types (bounded canary):
{"maxItems": 25}
Keyword search:
{"searchQuery": "python","maxItems": 25}
Geo + industry filter:
{"geo": "usa","industry": "software-engineering","maxItems": 50}
Keyword + geo + industry:
{"searchQuery": "python","geo": "canada","industry": "backend-development","maxItems": 25}
Input and output examples
Input fields
| Field | Type | Default | Description |
|---|---|---|---|
searchQuery | string | empty | Optional keyword or phrase. Filters the live feed locally. Leave empty for all current job types. |
geo | string | empty | Optional region slug or free-text location filter. Common aliases are listed in Common geo slugs. Leave empty for all regions. |
industry | string | empty | Optional Himalayas category/industry slug. Common values are listed in Common industry / category slugs. Spaces, hyphens, and underscores are accepted. |
maxItems | integer | 0 | Maximum matching jobs to emit. 0 means no user limit up to the safety cap of 5000. Maximum 5000. |
Unsupported aliases such as query, keyword, keywords, category, categories, location, tag, and tags are rejected. Use the canonical fields above.
Output item example
{"id": "senior-python-engineer","record_type": "job","title": "Senior Python Engineer","company_name": "Example Co","company_slug": "example-co","categories": ["Software-Engineering", "Python"],"location": "United States, Canada","salary": "$90,000-$130,000/USD/yr","salary_min": 90000,"salary_max": 130000,"job_type": "Full Time","experience_level": "Senior","application_link": "https://himalayas.app/companies/example-co/jobs/senior-python-engineer","source_url": "https://himalayas.app/companies/example-co/jobs/senior-python-engineer","source": "himalayas","sourceSearchQuery": "python","searchRank": 1,"sourceGeo": "usa","sourceIndustry": "software-engineering","attribution_url": "https://himalayas.app","crawled_at": "2026-07-16T09:00:00+00:00","raw": {"title": "Senior Python Engineer", "companyName": "Example Co"}}
In all-current-jobs mode, filter provenance fields are absent. In keyword mode, rows include sourceSearchQuery and searchRank. In geo/industry-only mode, rows include sourceGeo / sourceIndustry and filterRank as applicable.
Output fields
| Field | Description |
|---|---|
title | Job title. |
company_name, company_slug, company_logo | Company identity. |
description, excerpt | Full description and short excerpt when available. |
categories, parent_categories, tags | Category labels from Himalayas (tags mirrors categories). |
location, location_restrictions | Human-readable location and raw restriction list. |
salary, salary_min, salary_max, salary_currency, salary_period | Salary fields. |
job_type, experience_level, seniority | Employment type and seniority. |
application_link, guid, source_url | Application / listing URLs. |
published_at, expiry_date | Epoch timestamps as strings when present. |
sourceSearchQuery, searchRank | Present in keyword mode. |
sourceGeo | The geo filter used when set. |
sourceIndustry | The industry filter used when set. |
filterRank | Match rank (1-based) when geo/industry filters are set without keyword search. |
raw | Original API object. |
Run artifacts
| Artifact | Contents |
|---|---|
INPUT_ECHO | Normalized scope, keyword, geo, industry, limits (presetKeywords always []). |
RUN_SUMMARY | Source, pages fetched, API totalCount, filters, emitted/duplicate/malformed counts. |
ERROR_SUMMARY | Failure type and safe message when a run fails. |
Common geo slugs
geo is matched against Himalayas locationRestrictions and related free-text fields. Use either a short slug or free text. Multi-word values may use spaces or hyphens.
| Slug / input | Also matches | Notes |
|---|---|---|
usa | us, united-states, united states, u.s., u.s.a. | United States (most common on current feed) |
uk | united-kingdom, united kingdom, england, scotland, wales, britain | United Kingdom |
canada | canadian | Canada |
germany | deutschland, berlin, munich | Germany |
india | bangalore, bengaluru, mumbai, delhi, hyderabad, chennai, pune | India |
poland | warsaw | Poland |
philippines | manila | Philippines |
singapore | singapore | Singapore |
mexico | méxico | Mexico |
spain | espana, españa, madrid, barcelona | Spain |
australia | sydney, melbourne | Australia |
netherlands | holland, amsterdam | Netherlands |
france | paris | France |
portugal | lisbon | Portugal |
brazil | brasil, sao paulo, são paulo | Brazil |
south-africa | south africa | South Africa |
colombia | bogota, bogotá | Colombia |
ukraine | kyiv, kiev | Ukraine |
ireland | dublin | Ireland |
japan | tokyo | Japan |
europe | eu, emea | Europe / EMEA-style labels |
apac | asia, pacific | Asia-Pacific-style labels |
latam | latin america, south america | Latin America |
worldwide | world wide, anywhere, global, remote | Global / remote-friendly labels |
remote | remote, worldwide, anywhere, global | Same family as worldwide |
Any other free-text value is also accepted and matched as-is (plus hyphen/space variants). Live probes show Himalayas public API does not expose a reliable server-side location query, so geo filtering is applied on the paginated feed returned at run time.
Common industry / category slugs
industry maps to Himalayas categories and parentCategories. Spaces, hyphens, and underscores are interchangeable. Values below are grounded on recent feed frequency plus product-relevant stacks.
| Slug | Examples of accepted forms | Typical use |
|---|---|---|
software-engineering | software engineering, software-engineering | Software engineering |
fullstack-development | fullstack development, full-stack | Full-stack roles |
backend-development | backend development, backend-engineering | Backend |
frontend-development | frontend development, frontend | Frontend |
web-development | web development, web-development | Web development |
devops | devops, site-reliability-engineering | DevOps / SRE |
cloud-engineering | cloud engineering, cloud-engineering | Cloud |
ai-engineering | ai engineering, ai-engineering | AI / ML engineering |
mobile-development | mobile development, mobile-development | Mobile |
data-analysis | data analysis, data-science | Data / analysis |
cybersecurity | cybersecurity | Security |
sales | sales, b2b-sales, saas-sales | Sales family |
business-development | business development, business-development | Business development |
account-management | account management, account-executive | Account roles |
digital-marketing | digital marketing, growth-marketing | Marketing |
content-marketing | content marketing, content-marketing | Content marketing |
social-media-marketing | social media marketing, social-media-management | Social media |
customer-success | customer success, customer-service | Customer success / support |
talent-acquisition | talent acquisition, human-resources | Recruiting / HR |
operations | operations, operations-management | Operations |
executive-assistant | executive assistant, executive-assistant | EA / admin |
accounting | accounting, finance | Accounting / finance |
design | design | Design (when present on feed) |
product | product | Product (when present on feed) |
Himalayas category inventory changes over time. If a slug is rare or unused on the current feed pages scanned, the run can succeed with zero rows and a clear RUN_SUMMARY.
Data source and search boundary
This Actor uses the public Himalayas endpoint https://himalayas.app/jobs/api with limit and offset pagination.
- Live probes show the API page size is hard-capped at 20 jobs per request.
- The API
totalCountcan exceed 90,000 jobs, so this Actor applies a safety cap of 5000 emitted records whenmaxItemsis unlimited. searchQuery,geo, andindustryare local filters over the fetched pages. Public query params such asq,query,search,location,category, andtagwere observed not to change results.- This is a current-feed snapshot, not a separate historical search index.
Pricing
Pay per event. No subscription. Apify displays the effective event price before each run.
| Event | Price | When it is charged |
|---|---|---|
apify-actor-start | $0.005 | Automatically once when a normal Actor run starts. |
apify-default-dataset-item | $2.00 / 1,000 | Automatically for each item written to the default Dataset. |
For example, a run returning 100 job records costs $0.205 in Actor events: $0.005 to start plus $0.200 for results. Platform usage costs are charged to the user in addition to these Actor events when the Actor is configured that way.
Both listed events are Apify synthetic events: the platform accounts for them automatically.
Live View and Standby endpoints
Data collection stays in normal Actor runs. The standby service is an honest operational surface only.
| Endpoint | Purpose |
|---|---|
GET / | Readiness and service information. |
GET /health | Fast health check. |
GET /input-example | Low-cost input compatible with the Actor schema. |
GET /openapi.json | Deployed OpenAPI 3.x contract. |
Connect from code or an AI workflow
Actor ID: lentic_clockss/himalayas-jobs-scraper.
Related Actors
Use this Actor when Himalayas is the source of record. Keep other job boards as separate Actors so attribution and freshness stay clear.
FAQ and support
Does it search Himalayas by keyword? Yes, via local filtering of the live paginated feed. Set searchQuery.
Can I filter by region or industry? Yes. Use geo and/or industry. See the slug tables above. Filtered rows include sourceGeo / sourceIndustry provenance.
Does empty input use preset keywords? No. Empty input collects all current job types from the live feed (subject to maxItems / safety cap).
What happens when there are no matches? If any of searchQuery, geo, or industry is set and nothing matches, the run succeeds with zero Dataset rows and a clear RUN_SUMMARY. Source failures write ERROR_SUMMARY and fail.
Why is there a 5000 safety cap? Himalayas totalCount can exceed 90k. Unlimited full-history dumps would be expensive and slow; use maxItems deliberately.
Where can I report a problem? Include the Actor run ID, RUN_SUMMARY or ERROR_SUMMARY, and one example source_url.
Explore more tools from lentic_clockss on Apify.