Remote Jobs Scraper: RemoteOK, WWR, Jobicy | $0.50 per 1,000 avatar

Remote Jobs Scraper: RemoteOK, WWR, Jobicy | $0.50 per 1,000

Pricing

from $0.35 / 1,000 results

Go to Apify Store
Remote Jobs Scraper: RemoteOK, WWR, Jobicy | $0.50 per 1,000

Remote Jobs Scraper: RemoteOK, WWR, Jobicy | $0.50 per 1,000

Scrape remote jobs from Remote OK, We Work Remotely, Jobicy, Working Nomads and Arbeitnow in one feed: title, company, location, eligible countries, salary, job type, level, tags, posted date and description. Duplicates across boards are removed. Filter by keyword, location, date and salary.

Pricing

from $0.35 / 1,000 results

Rating

0.0

(0)

Developer

vøiddo

vøiddo

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

Scrape remote jobs from Remote OK, We Work Remotely, Jobicy, Working Nomads and Arbeitnow in one feed: title, company, location, eligible countries, salary, job type, level, tags, posted date and description. Duplicates across boards are removed. Filter by keyword, location, date and salary.

  • Pay per result row: the platform usage of the run is included, and a run that finds nothing has no result charges.
  • No login, no cookies, no account on the remote job boards: public pages only.
  • Export to JSON, CSV, Excel, XML or HTML, or read the rows through the Apify API.
  • Start it from the Console, on a schedule, through the API, or as a tool for agents over MCP.
  • Tested every day on its example input, with the rows checked, and repaired when a check fails.

What you can use it for

  • Remote job boards and newsletters: one daily feed from five boards, duplicates removed, with source and link.
  • Job seekers and career coaches: every remote role for a skill or title, filtered by location, salary and date.
  • Remote salary benchmarks: compare the salary ranges Remote OK and Jobicy publish by title, currency and period.
  • Hiring market research: count which companies hire remotely, in which categories, levels and countries.

What you get

Every result is one row in the run's dataset. Download it as JSON, CSV, Excel or HTML, or read it through the Apify API. The main fields:

FieldMeaning
titleTitle
companyCompany
locationLocation
salaryMinSalary from
salaryMaxSalary to
salaryCurrencyCurrency
sourceNameBoard
publishedAtPosted
urlJob

Example row:

{
"source": "jobicy",
"sourceName": "Jobicy",
"jobId": "156580",
"title": "Senior Backend Engineer (Go)",
"company": "Canonical",
"companyLogo": "https://jobicy.com/data/server-nyc0409/galaxy/mercury/2025/06/b4d068a9-221-1.png",
"companyWebsite": null,
"headquarters": null,
"location": "Europe",
"countries": [],
"worldwide": false,
"remote": true,
"employmentTypes": [
"Full-Time"
],
"seniority": "Senior",
"categories": [
"Software Engineering"
],
"tags": [],
"salaryMin": 95000,
"salaryMax": 190000,
"salaryCurrency": "EUR",
"salaryPeriod": "year",
"publishedAt": "2026-10-23T09:26:42Z",
"expiresAt": null,
"descriptionText": "Canonical is a leading provider of open source software and operating systems.",
"url": "https://jobicy.com/jobs/156580-senior-backend-engineer-go",
"scrapedAt": "2026-10-23T12:30:05Z"
}

How to use it

  1. Open the Input tab (or call the actor through the API, see below).
  2. Fill in Search terms, Maximum jobs per board; the form opens with a working example.
  3. Set Maximum results to cap the size and the cost of the run.
  4. Click Start. Rows appear on the Output tab while the run works.
  5. Download the dataset, or connect it to Google Sheets, Make, Zapier, n8n or a webhook.

Input

FieldTypeRequiredDescription
keywordsarraynoJob titles, skills or words such as python, designer or customer support. A job is kept when a term is in its title, tags or category. Each term is also read as a Remote OK tag, which reaches 100 more of its jobs. Leave empty for every job.
searchDescriptionsbooleannoAlso keep jobs whose description holds a search term. Default: false.
excludeKeywordsarraynoDrop jobs whose title holds any of these words, such as senior or intern.
sourcesselectnoThe boards to read, in this order. A job found on an earlier board is not repeated from a later one. Allowed: remoteok, weworkremotely, jobicy, workingnomads, arbeitnow.
maxJobsPerBoardintegernoOptional. Stop reading a board after this many kept jobs and go on to the next one, so the first board does not fill the whole run. Empty: every kept job, up to Maximum results.
locationsarraynoOnly jobs whose location or eligible countries name one of these, such as USA, Europe, Germany or Canada. USA also finds United States, UK United Kingdom and Europe EU and EMEA. Leave empty for every location.
includeWorldwidebooleannoWith locations set, also keep jobs open to people anywhere in the world. Default: true.
postedWithinselectnoOnly jobs published in that period. Allowed: any, 1day, 3days, 7days, 14days, 30days. Default: "any".
salaryOnlybooleannoOnly jobs whose board gives a salary (Remote OK and Jobicy give one for about a quarter and a half of their jobs). Default: false.
includeDescriptionbooleannoReturn each job's description as plain text. Switch it off for smaller rows. Default: true.
maxItemsintegernoThe run stops after this many result rows. It also caps what one run can cost. Default: 500.
proxyConfigurationobjectnoLeave as is: the run starts on the cheapest network the site accepts and switches to Apify Proxy automatically when the site blocks it. Pick proxy groups here only to force one specific network.

Example input:

{
"keywords": [
"engineer",
"developer"
],
"maxItems": 20,
"maxJobsPerBoard": 6
}

Pricing

You pay per result row in the dataset (the current price per 1,000 results is on the Pricing tab). A run that finds nothing produces no rows and no result charges. Set Maximum results to cap what a single run can cost.

Limits and notes

  • One run reads every board you chose, about 4,000 jobs in all on a normal day: Remote OK's 100 newest plus 100 per search term, We Work Remotely's main and category feeds, Jobicy's last 7 days, Working Nomads' newest 41 and Arbeitnow's remote jobs.
  • Rows come board by board in the order of Job boards, newest first within a board. A job with the same company and title as one already returned (the same job posted on two boards) is left out.
  • source and sourceName say which board the job comes from, and url is the job on that board. The boards ask that apps showing their jobs name them and link to the job there.
  • location is the board's own text (Anywhere in the World, USA, Europe ...); countries lists the eligible countries where We Work Remotely gives them; worldwide is true when the location says anywhere or worldwide and no list of countries narrows it, and empty when the board gives no location.
  • salaryMin and salaryMax come from Remote OK (US dollars a year) and Jobicy (with currency and period); a salary written into a description stays in the text.
  • seniority comes from Jobicy; companyWebsite and headquarters from We Work Remotely; Arbeitnow jobs are kept only when Arbeitnow marks them remote.
  • Remote OK's own anti spam sentence at the end of each description (a code word and a tag for applicants) is removed, and its broken accented letters are repaired.
  • E-mail addresses, phone numbers and handles are removed from the text. Recruiter names are not collected.
  • Not affiliated with Remote OK, We Work Remotely, Jobicy, Working Nomads or Arbeitnow.
  • Only publicly visible data is collected. No login, no paywalled content, no personal contact details.
  • The actor reads only pages that the site's robots.txt leaves open to automated access.
  • Sites change their pages from time to time. The actor is checked automatically and repaired when a check fails.
  • Each run sends one short usage record to the developer: the Actor and run IDs, the number of results, whether the run succeeded (and if not, the kind of error, such as "blocked" or "input problem"), whether the account is on a paid Apify plan, how the run was started (for example from the Console, the API or a schedule) and a one-way fingerprint of the account (a hash, not the account ID), so that repeat runs of one account count once. It contains nothing from your input or results.

Run it through the API

Python, with the apify-client package:

from apify_client import ApifyClient
client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("v0iddo/remote-jobs-scraper").call(run_input={"keywords": ["engineer", "developer"], "maxItems": 20, "maxJobsPerBoard": 6})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item)

JavaScript, with the apify-client package:

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('v0iddo/remote-jobs-scraper').call({"keywords": ["engineer", "developer"], "maxItems": 20, "maxJobsPerBoard": 6});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

One HTTP call that waits for the run and returns the rows (for runs that finish within 5 minutes):

curl -X POST "https://api.apify.com/v2/acts/v0iddo~remote-jobs-scraper/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
-H "Content-Type: application/json" \
-d '{"keywords": ["engineer", "developer"], "maxItems": 20, "maxJobsPerBoard": 6}'

Use it from an agent (MCP)

Claude, Cursor, VS Code and other MCP clients can call this actor as a tool through the Apify MCP server. Add it to the client's MCP configuration:

{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com?tools=v0iddo/remote-jobs-scraper",
"headers": {
"Authorization": "Bearer <YOUR_APIFY_TOKEN>"
}
}
}
}

Then ask, for example: "List the remote Python jobs open to people in Europe posted this week, with salary and board."

FAQ

Do I need an account on the remote job boards, cookies or an API key?

No. The actor reads only what every visitor of the remote job boards can see, without logging in. You only need an Apify account to start it.

How many results can one run return?

Up to 20,000 rows per run. Without a limit it stops at 500. Set Maximum results to the number you need; large jobs can also be split into several runs or scheduled.

How am I charged?

Per result row in the dataset, at the price on the Pricing tab for your Apify plan. The platform usage of the run is included in that price. A run that finds nothing produces no rows and no result charges, and your spending limit for a run is always respected.

Why did my run return no results?

The status message of the run says why: nothing matched the input, the input was not a page the actor understands, the page is closed to automated access by robots.txt, or the site refused every network the actor tried. Check the input against the example above and run it again with a small limit.

Can I run it on a schedule?

Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.

Which formats can I export?

JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.

Is collecting this data allowed?

The actor collects only what the remote job boards publishes to every visitor, without a login, and it reads only pages that robots.txt leaves open. Public data can still be personal data under laws such as the GDPR, and sites have their own terms: make sure your use of the data follows the rules that apply to you.

What happens when the remote job boards changes its pages?

Automated tests run the actor every day on the example input and check the rows, not only that the run finished. When a check fails, the actor is repaired and rebuilt; the build history on this page shows each update.

Something is missing or wrong. Where do I report it?

Open an issue on the Issues tab of this actor with the run link. Requests for a new field are welcome too.