# Remote Jobs Scraper: RemoteOK & We Work Remotely (`datalantern/remote-jobs`) Actor

Export current remote jobs from Remote OK and We Work Remotely in one table: title, company, category, tags, location, job type, salary, posting date and job link.

- **URL**: https://apify.com/datalantern/remote-jobs.md
- **Developed by:** [Data Lantern](https://apify.com/datalantern) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Stats:** 1 total users, 0 monthly users, 75.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Remote Jobs Scraper: RemoteOK & We Work Remotely

**Remote Jobs Scraper** exports current remote job listings from **Remote OK** and **We Work Remotely** in one consistent table: job title, company, category, tags, location, job type, salary range, posting date, job link and the full description. Filter by keyword, posting age or minimum salary and download the jobs as CSV, Excel or JSON for a job board, a newsletter, hiring-trend research or sales prospecting.

### What can this tool do?

- Combine two of the biggest remote job boards into one clean, de-duplicated list, newest first.
- Filter by keyword (title, company, category, tags or location), by how recently a job was posted, and by minimum yearly salary.
- Return salary ranges where the board publishes them (Remote OK) with currency and pay period.
- Include the company website where We Work Remotely lists it, and the full job description as plain text (or leave it out for a compact export).
- Run it on a schedule to track new remote openings every day.

### What data does it return?

One row per job. Example values from a real run:

| Field | Example |
|---|---|
| `source` | weworkremotely |
| `sourceName` | We Work Remotely |
| `jobId` | salesloft-principal-software-engineer-ai |
| `title` | Principal Software Engineer, AI |
| `company` | Salesloft |
| `companyWebsite` | http://salesloft.com/ |
| `category` | Full-Stack Programming |
| `tags` | \["UI/UX Design"] (skills from We Work Remotely; Remote OK gives topic tags such as `python`) |
| `location` | Anywhere in the World, United States of America |
| `jobType` | Full-Time |
| `salaryMin` / `salaryMax` | null (Remote OK jobs with a published range, for example 120000 / 160000) |
| `salaryCurrency` / `salaryPeriod` | null (USD / year when a salary exists) |
| `postedAt` | 2026-09-30T07:31:24.000Z |
| `expiresAt` | 2026-10-30T07:31:24.000Z |
| `jobUrl` | https://weworkremotely.com/remote-jobs/salesloft-principal-software-engineer-ai |
| `applyUrl` | link to the job page where the application starts |
| `descriptionText` | Headquarters: United States, Remote\nJob Title: Principal Software Engineer, AI… |

- Missing values are `null`, so every row has the same fields.
- Salaries come from Remote OK only and are yearly amounts in US dollars. We Work Remotely does not publish salaries in its feed.
- Remote OK does not publish job types or categories, so those are `null` for its jobs. We Work Remotely's skill tags are generated by that site and can be broad.

### How to use it

1. Choose the job boards and, optionally, keywords such as `python`, `designer` or `customer support`.
2. Optionally set how recent the jobs must be and a minimum salary.
3. Click **Start**, then download the jobs as CSV, Excel or JSON, or read them through the API.

### Pricing

Pay per job: **$1.50 per 1,000 jobs**, plus $0.005 per run. You only pay for jobs you receive. Set a maximum cost per run in the run options.

### Use it through the API, AI agents, and integrations

Schedule it daily, call it from your code with the Apify API, or connect it to Make, Zapier, n8n, Google Sheets or an AI agent through Apify's MCP server.

### Is it legal?

This tool reads the public job feeds that Remote OK and We Work Remotely publish for their listings. It does not log in or bypass access controls. It outputs job postings only: no names of recruiters or posters are collected, and personal email addresses inside descriptions are replaced with "\[email removed]". Every row carries the job's source name and a link back to the original listing. If you republish these jobs, credit the source and link to the original job page, as Remote OK's terms ask. You are responsible for how you use the data.

### FAQ

**How many jobs will I get?** These boards only publish their currently open jobs: about 100 from Remote OK and about 250 from We Work Remotely at a time (more when you add keywords, because Remote OK is asked for each topic separately). Run the tool daily to build a longer history.

**Why is Remotive not included?** Remotive's terms do not allow passing its jobs on to other job sites and limit access to a few requests a day, so it is left out on purpose.

**Why are salary fields empty?** Most listings do not publish pay. Remote OK includes it when the company provides it.

### Feedback

Found a bug or need a field added? Open an issue on the **Issues** tab. We usually respond within 24 hours.

# Actor input Schema

## `sources` (type: `array`):

Which remote job boards to read.

## `keywords` (type: `array`):

Optional. Keep jobs where any keyword appears in the title, company, category, tags or location, for example "python", "designer" or "customer support". Leave empty for all jobs.

## `postedWithinDays` (type: `integer`):

Only jobs posted in the last N days. 0 means any age.

## `minSalary` (type: `integer`):

Only jobs that publish a salary with at least this yearly amount. Only Remote OK publishes salaries. 0 means no salary filter.

## `includeDescription` (type: `boolean`):

Adds the full job description as plain text. Turn off for a compact export.

## `maxResults` (type: `integer`):

Stop after this many jobs (newest first). 0 means no limit.

## Actor input object example

```json
{
  "sources": [
    "remoteok",
    "weworkremotely"
  ],
  "keywords": [
    "engineer"
  ],
  "postedWithinDays": 0,
  "minSalary": 0,
  "includeDescription": true,
  "maxResults": 30
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "sources": [
        "remoteok",
        "weworkremotely"
    ],
    "keywords": [
        "engineer"
    ],
    "maxResults": 30
};

// Run the Actor and wait for it to finish
const run = await client.actor("datalantern/remote-jobs").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "sources": [
        "remoteok",
        "weworkremotely",
    ],
    "keywords": ["engineer"],
    "maxResults": 30,
}

# Run the Actor and wait for it to finish
run = client.actor("datalantern/remote-jobs").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "sources": [
    "remoteok",
    "weworkremotely"
  ],
  "keywords": [
    "engineer"
  ],
  "maxResults": 30
}' |
apify call datalantern/remote-jobs --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,datalantern/remote-jobs"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/fgVPPBAb6KPe6E6qu/builds/zgSdYo7NkdneZBgvT/openapi.json