Remote Jobs Scraper: 3 Boards, One Feed

Every remote job from Himalayas, Arbeitnow and We Work Remotely, merged into one normalised feed with salary, region, tags and apply links.

Built on the public feeds these boards publish for syndication. No key, no login, no bot wall, and no LinkedIn/Indeed scraping.

Why merged matters

Each board names the same thing differently: position vs title vs text, salary as 0 vs null vs a string, and each has its own idea of what "remote" means. You get one shape:

Field	Example
title, company, companyLogo	Senior Backend Engineer, Toptal
location, isWorldwide	Anywhere in the World, true
salaryMin, salaryMax, salaryCurrency, salaryPeriod	120000, 160000, USD, yearly
employmentType, seniority	Full-time, Senior
tags	["python","backend","aws"]
postedAt, expiresAt	ISO 8601, normalised across all three
url	direct apply link
description	plain text, HTML stripped
source	which board it came from

Cross-posted duplicates removed

The same role is routinely posted to more than one board at once. dedupeAcrossBoards (on by default) keeps the first copy and drops the rest, and duplicates are not charged.

Example input

{
  "sources": ["himalayas", "arbeitnow", "weworkremotely"],
  "keywords": ["python", "backend"],
  "excludeKeywords": ["intern"],
  "worldwideOnly": true,
  "minSalary": 100000,
  "maxJobsPerSource": 200
}

Filters

• keywords / excludeKeywords, match title, tags and description
• companies, track specific employers
• regions, e.g. ["europe", "united states"]. Worldwide roles always match, since they're open everywhere
• worldwideOnly, only roles with no geographic restriction
• minSalary, drops jobs with no published salary

Filtered-out and deduplicated jobs are not charged.

Do you need an API key? No. Is there a free tier? Yes.

The two things people search for in this category, measured, are free and API key: remote jobs api, jobicy remote jobs api.

So, plainly:

• No API key. Nothing to register for, nothing to rotate, no key to leak in a repo. The source is a public API published deliberately by its owner.
• No proxy setup. The source does not bot-wall datacenter addresses, so the default works.
• Pay per result, not per month. There is no subscription and no minimum. Rows that error or that your filters drop are not charged.
• Free to try. Run it with the prefilled input and see real rows before deciding anything.

Who this is for

• Job boards & newsletters: a ready-made aggregated feed, refreshed on a schedule
• Recruiters: see who's hiring for a role across the whole remote market at once
• Job seekers & tooling: one query instead of three tabs
• Market researchers, which skills, which salaries, which regions, over time
• AI / dataset builders: clean normalised job data with real salary ranges

The three boards, and why three

A remote jobs API built on one board inherits that board's blind spots. These three overlap least, and each publishes a public feed with no key:

Board	What it is strongest at	Salary published
Himalayas	breadth, structured fields, tags	often
Arbeitnow	European and Germany-based remote roles	rarely
We Work Remotely	the long-running board, strong in programming and design	rarely

The same role is frequently posted to more than one, so dedupeAcrossBoards keeps the first copy and duplicates are not charged. A hundred raw postings is regularly sixty real ones.

Every row carries the same field names whichever board it came from, plus a source naming that board, so a single export is directly filterable and you can tell where anything came from.

Notes

• Salary is only present when the board publishes it. Himalayas often does; Arbeitnow and WWR usually don't. minSalary therefore drops most WWR and Arbeitnow rows by design.
• RemoteOK is deliberately not included. Its free public API returns largely spam listings (companies posting other companies' names as job titles, nonsense locations); its real inventory sits behind a paid API. Shipping a source known to return garbage would only cost you money.
• wwrCategory picks which We Work Remotely feed to read: all, programming, design, devops, sales, support, product, management.
• If one board is temporarily down, the others still return. The failure comes back as a single error row and is not charged.
• Set a max charge per run in the run options for a hard spend ceiling. The Actor honors it and stops cleanly.

Pricing

Pay per result. One row = one job. Board failures come back as error rows and are not charged, and neither are duplicates or anything your filters removed.