Himalayas Jobs Scraper - Search & All Current Remote Jobs avatar

Himalayas Jobs Scraper - Search & All Current Remote Jobs

Pricing

from $2.00 / 1,000 results

Go to Apify Store
Himalayas Jobs Scraper - Search & All Current Remote Jobs

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

kane liu

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

5 days ago

Last modified

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 searchQuery to filter current jobs by title, company, description, excerpt, categories, location, and URLs.
  • Geo filter: enter geo (for example usa, uk, canada, india, worldwide) to match Himalayas locationRestrictions with common region aliases.
  • Industry / category filter: enter industry (for example software-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 / searchRank and/or sourceGeo / sourceIndustry / filterRank.
  • No credentials needed: public API, no login.
  • Attribution built in: source_url and attribution_url point back to Himalayas.

Tutorial

  1. Click Try for free on this Actor page.
  2. Optionally enter searchQuery (for example python, design, customer success).
  3. Optionally enter geo (for example usa, uk, worldwide) and/or industry (for example software-engineering, sales).
  4. To export all current job types from the live feed, leave searchQuery, geo, and industry empty.
  5. Set maxItems to control cost. Prefill 25 is a safe canary size. 0 means no user limit up to the Actor safety cap of 5000 rows.
  6. Click Start and wait for the run to finish.
  7. Open the Dataset tab to download JSON, CSV, Excel, or JSONL.
  8. Check RUN_SUMMARY in 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

FieldTypeDefaultDescription
searchQuerystringemptyOptional keyword or phrase. Filters the live feed locally. Leave empty for all current job types.
geostringemptyOptional region slug or free-text location filter. Common aliases are listed in Common geo slugs. Leave empty for all regions.
industrystringemptyOptional Himalayas category/industry slug. Common values are listed in Common industry / category slugs. Spaces, hyphens, and underscores are accepted.
maxItemsinteger0Maximum 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

FieldDescription
titleJob title.
company_name, company_slug, company_logoCompany identity.
description, excerptFull description and short excerpt when available.
categories, parent_categories, tagsCategory labels from Himalayas (tags mirrors categories).
location, location_restrictionsHuman-readable location and raw restriction list.
salary, salary_min, salary_max, salary_currency, salary_periodSalary fields.
job_type, experience_level, seniorityEmployment type and seniority.
application_link, guid, source_urlApplication / listing URLs.
published_at, expiry_dateEpoch timestamps as strings when present.
sourceSearchQuery, searchRankPresent in keyword mode.
sourceGeoThe geo filter used when set.
sourceIndustryThe industry filter used when set.
filterRankMatch rank (1-based) when geo/industry filters are set without keyword search.
rawOriginal API object.

Run artifacts

ArtifactContents
INPUT_ECHONormalized scope, keyword, geo, industry, limits (presetKeywords always []).
RUN_SUMMARYSource, pages fetched, API totalCount, filters, emitted/duplicate/malformed counts.
ERROR_SUMMARYFailure 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 / inputAlso matchesNotes
usaus, united-states, united states, u.s., u.s.a.United States (most common on current feed)
ukunited-kingdom, united kingdom, england, scotland, wales, britainUnited Kingdom
canadacanadianCanada
germanydeutschland, berlin, munichGermany
indiabangalore, bengaluru, mumbai, delhi, hyderabad, chennai, puneIndia
polandwarsawPoland
philippinesmanilaPhilippines
singaporesingaporeSingapore
mexicoméxicoMexico
spainespana, españa, madrid, barcelonaSpain
australiasydney, melbourneAustralia
netherlandsholland, amsterdamNetherlands
franceparisFrance
portugallisbonPortugal
brazilbrasil, sao paulo, são pauloBrazil
south-africasouth africaSouth Africa
colombiabogota, bogotáColombia
ukrainekyiv, kievUkraine
irelanddublinIreland
japantokyoJapan
europeeu, emeaEurope / EMEA-style labels
apacasia, pacificAsia-Pacific-style labels
latamlatin america, south americaLatin America
worldwideworld wide, anywhere, global, remoteGlobal / remote-friendly labels
remoteremote, worldwide, anywhere, globalSame 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.

SlugExamples of accepted formsTypical use
software-engineeringsoftware engineering, software-engineeringSoftware engineering
fullstack-developmentfullstack development, full-stackFull-stack roles
backend-developmentbackend development, backend-engineeringBackend
frontend-developmentfrontend development, frontendFrontend
web-developmentweb development, web-developmentWeb development
devopsdevops, site-reliability-engineeringDevOps / SRE
cloud-engineeringcloud engineering, cloud-engineeringCloud
ai-engineeringai engineering, ai-engineeringAI / ML engineering
mobile-developmentmobile development, mobile-developmentMobile
data-analysisdata analysis, data-scienceData / analysis
cybersecuritycybersecuritySecurity
salessales, b2b-sales, saas-salesSales family
business-developmentbusiness development, business-developmentBusiness development
account-managementaccount management, account-executiveAccount roles
digital-marketingdigital marketing, growth-marketingMarketing
content-marketingcontent marketing, content-marketingContent marketing
social-media-marketingsocial media marketing, social-media-managementSocial media
customer-successcustomer success, customer-serviceCustomer success / support
talent-acquisitiontalent acquisition, human-resourcesRecruiting / HR
operationsoperations, operations-managementOperations
executive-assistantexecutive assistant, executive-assistantEA / admin
accountingaccounting, financeAccounting / finance
designdesignDesign (when present on feed)
productproductProduct (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 totalCount can exceed 90,000 jobs, so this Actor applies a safety cap of 5000 emitted records when maxItems is unlimited.
  • searchQuery, geo, and industry are local filters over the fetched pages. Public query params such as q, query, search, location, category, and tag were 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.

EventPriceWhen it is charged
apify-actor-start$0.005Automatically once when a normal Actor run starts.
apify-default-dataset-item$2.00 / 1,000Automatically 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.

EndpointPurpose
GET /Readiness and service information.
GET /healthFast health check.
GET /input-exampleLow-cost input compatible with the Actor schema.
GET /openapi.jsonDeployed OpenAPI 3.x contract.

Connect from code or an AI workflow

Actor ID: lentic_clockss/himalayas-jobs-scraper.

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.