← Catalog · Jobs in Germany · Actor

How to get remote job listings you can actually apply to, from six job boards

28 Oct 2026 · benthepythondev

A lot of jobs labelled "Remote" aren't open to everyone. Some are limited to one country, a region or a time zone. Others ask for office days. The Remote Jobs Aggregator Actor on Apify reads six boards: Arbeitnow, Jobicy, Himalayas, RemoteOK, Remotive and Working Nomads. It merges duplicate title/company pairs into one row and returns everything in one dataset, whichever board a job came from.

What you get

Each row is one job. The fields in a real run look like this:

• title, company, location: the job title, the employer, and the board's location text (for example "APAC, EMEA, USA")
• salary: the pay range when the board gives one, otherwise null
• description: the full job text
• work_type and job_type: for example "Remote" and "Full-time"
• seniority: for example "senior"
• tags: the board's categories, such as "DevOps & Infrastructure"
• url, platform, posted_date: the link to the listing, which board it came from, and when it was posted
• job_id, scraped_at: a stable id and the time of the run
• is_new, monitor_id, first_seen_at: used when you run it as a feed of only new jobs

The README also describes eligibility fields that say who can apply:

• remote_scope: worldwide, restricted or unknown
• eligible_locations: the countries or regions named, such as ["United States", "Canada"] or ["EMEA"]. A time zone rule like "CET +/- 3 hours" becomes Europe
• eligibility_evidence: the sentence the answer came from, so you can check it yourself
• work_arrangement: hybrid when the text asks for office days, otherwise remote

When the employer's own sentence disagrees with the board's label, the sentence wins. A job filed under "Worldwide" that says "must be authorized to work in the United States" comes back as restricted.

Example output

Here is a trimmed excerpt from a real call. The description is cut short:

{
  "title": "Senior Software Engineer, Internal Tooling",
  "company": "RevenueCat",
  "location": "APAC,  EMEA,  USA",
  "salary": null,
  "description": "RevenueCat gives app businesses the infrastructure and tools to build, run, and improve their monetization. ...",
  "work_type": "Remote",
  "job_type": "Full-time",
  "tags": [["DevOps & Infrastructure"]],
  "url": "https://jobicy.com/jobs/154567-senior-software-engineer-internal-tooling",
  "posted_date": "2026-10-05T08:23:32+00:00",
  "platform": "jobicy",
  "scraped_at": "2026-10-05T12:31:03.025883",
  "job_id": "469065a79c5b43d4726100f6",
  "seniority": "senior",
  "is_new": false
}

The README shows the eligibility fields of a restricted row like this:

{
  "location": "Worldwide",
  "remote_scope": "restricted",
  "eligible_locations": ["United States"],
  "eligibility_evidence": "Applicants must be eligible to live and work in the US",
  "work_arrangement": "remote"
}

Use cases

1. Job hunting from a specific country. Set eligibleFrom to where you can work from (for example Germany, India, Brazil, Europe, EMEA or LATAM). The run keeps worldwide jobs plus jobs whose named places include you. A job for Europe or EMEA passes for Germany, but a job for the United States doesn't. Add excludeHybrid to drop jobs that want office days.
2. A scheduled hiring feed. Turn on onlyNew and schedule the Actor so each run returns only jobs it hasn't seen before. The Actor's page has a ready example for new remote Python jobs, daily.
3. Sending jobs to other tools. Export JSON, CSV or Excel, send rows to Google Sheets, or connect the dataset to n8n, Make, Zapier, Slack or email. The README links n8n templates for email alerts and for Google Sheets plus Slack.
4. One merged dataset for analysis. Every board names its fields differently (one calls the employer company_name, another nests it in a company object). This Actor maps them all to one shape, so you can compare boards without writing a parser for each one.

How to run it on Apify

1. Open the Actor on Apify.
2. Pick the boards you want and set eligibleFrom if you only want jobs you can apply to. Turn on includeUnclearEligibility if you also want jobs where the listing names no location.
3. Start the run, then download the dataset or call it through the Apify API.
4. If you want a recurring feed, turn on onlyNew and add a schedule.

Pricing, per the README: $15 per 1,000 jobs on the Free plan until November 9, 2026, then $6 per 1,000 jobs on Free from that date, with lower rates on paid plans. A small run-start charge applies even when a run returns nothing. The README puts a 20-job run at 512 MB at about $0.30 on Free now, or $0.12 from November 9.

There's no RapidAPI listing for this Actor. Use the Apify API to call it from code.

Honest limits

• The eligibility reading is pattern-based and only works in English. A requirement written in an unusual way can be missed.
• City names outside the US aren't mapped to a country. An Arbeitnow job in "Berlin" stays unknown.
• A phrase like "+ 35 other countries" only gives you the countries it actually names.
• Many listings name no location at all. In the README's sample of 179 jobs from all six boards (October 26, 2026), 117 were restricted, 10 worldwide and 52 unknown. Jobs with unknown scope are dropped when you filter by eligibleFrom, unless you turn on includeUnclearEligibility.
• salary is often null, because many boards don't publish pay.
• The boards are fetched at the same time. If one is down, you still get rows from the others and the log names the board that failed, so a run can have gaps.
• The real example row above came from a call that didn't include the eligibility fields. Check your own output before you build on remote_scope.

Affiliate if you still need an Apify account: apify.com/?fpr=qolupv. I may earn a commission; the price you pay does not change.