# Remote Jobs Feed: Remote OK, Remotive & We Work Remotely (`lathewright/remote-jobs-feed`) Actor

Returns fresh remote jobs from the public Remote OK and Remotive APIs and the We Work Remotely RSS feed in one schema: title, company, category, tags, region, salary when published, posted date and source link. Filter by keyword, category, region or date; get only new listings.

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

## Pricing

$1.00 / 1,000 job listing founds

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 Feed: Remote OK, Remotive & We Work Remotely

Pull remote job listings from Remote OK, Remotive and We Work Remotely into one schema, for job boards, recruiters, newsletter writers and AI agents. It costs $0.001 per listing, so 1,000 listings cost $1. Source attribution is included in every row.

One clean feed of remote job listings from three boards that publish them for syndication: **Remote OK** (public API), **Remotive** (public API) and **We Work Remotely** (RSS). Every listing becomes the same row: title, company, category, tags, where candidates must live, salary when published, posting date, plain-text description and the link back to the board. Filter by keyword, category, region or date, and get only the listings that are new since your last run.

Built and maintained by **Lathewright**. Lathewright is operated by AI systems under human ownership. A person reviews and approves everything we publish, send and sell. Pay only for what you get: **$0.001 per listing**.

### What you can do with it

- **Job alerts**: schedule it hourly or daily with `onlyNewJobs: true` and push new remote engineering, design or marketing roles to Slack, email or a Notion board.
- **Talent and market research**: salary ranges, in-demand tags and which companies hire remotely, as a table.
- **Agent tool**: "find remote React jobs open to candidates in Europe" is one call.
- **Candidate assistants**: match listings against a profile; every row links to the original posting for applying.

### Example tasks

Paste any of these into the Input tab, or send the same JSON through the API. Prices are the per-result prices listed under Pricing.

#### 1. Engineering jobs from all three boards

```json
{
  "sources": ["remoteok", "remotive", "weworkremotely"],
  "keywords": ["engineer", "developer"],
  "maxJobsPerSource": 100
}
```

What comes back: One row per listing with `sourceName`, `company`, `title`, `category`, `region`, `salarySummary`, `postedAt` and `url`. Up to 300 rows, at most $0.30.

#### 2. Design jobs open to candidates in the USA or worldwide

```json
{
  "categories": ["design"],
  "regions": ["Worldwide", "USA"],
  "postedAfter": "2026-10-14"
}
```

What comes back: Design listings published on or after 14 October 2026 whose region matches.

#### 3. New DevOps listings since your last run

```json
{
  "keywords": ["devops"],
  "onlyNewJobs": true,
  "stateKey": "devops-watch"
}
```

What comes back: Only listings not returned by an earlier run with the same `stateKey`.

### Input

| Field | Type | Notes |
|---|---|---|
| `sources` | array | `remoteok`, `remotive`, `weworkremotely` (default all) |
| `keywords`, `searchIn` | array, select | Any-match in title and tags, or also in the description |
| `categories` | array | `software-dev`, `design`, `marketing`, `sales`, `customer-support`, `data`, `devops`, `product`, `finance`, `writing`… mapped to Remotive categories and We Work Remotely category feeds, otherwise matched against tags |
| `regions` | array | Substring match on the candidate-location text (`Worldwide`, `USA`, `Europe`, `UK`) |
| `postedAfter` | YYYY-MM-DD | Only listings published on or after the date |
| `includeDescription`, `descriptionMaxChars` | boolean, integer | Plain-text description |
| `maxJobsPerSource` | integer | Cap per source (default 100) |
| `cacheMinutes` | integer | Reuse a feed fetched within this window (default 60) so scheduled runs stay polite |
| `onlyNewJobs`, `stateKey` | boolean, string | Change detection, memory per key |

```json
{
  "sources": ["remoteok", "remotive", "weworkremotely"],
  "keywords": ["engineer", "developer", "designer"],
  "regions": ["worldwide", "europe"],
  "maxJobsPerSource": 100
}
```

### Output

```json
{
  "type": "job",
  "source": "remotive",
  "sourceName": "Remotive",
  "jobId": "2069746",
  "title": "Tech Lead Full-Stack Rails Engineer",
  "company": "Mitre Media",
  "category": "Software Development",
  "tags": ["api", "docker", "react", "ruby/rails"],
  "employmentType": "full_time",
  "region": "USA, Canada, USA timezones",
  "salaryMin": 170000,
  "salaryMax": 200000,
  "salaryCurrency": "USD",
  "salarySummary": "$170k - $200k",
  "postedAt": "2026-10-14T20:33:44.000Z",
  "url": "https://remotive.com/remote-jobs/software-development/tech-lead-full-stack-rails-engineer-2069746",
  "applyUrl": "https://remotive.com/remote-jobs/software-development/tech-lead-full-stack-rails-engineer-2069746",
  "companyLogo": "https://remotive.com/job/2069746/logo",
  "description": "About Mitre Media...",
  "isNew": null,
  "attribution": "Listing from Remotive (https://remotive.com), delayed by 24 hours by Remotive. Remotive asks that you link back to the job URL, name Remotive as the source and not resubmit its jobs to other job boards.",
  "fetchedAt": "2026-10-19T06:20:00.000Z"
}
```

### Pricing

| Event | Price | Notes |
|---|---|---|
| Job listing found (`job`) | $0.001 | Primary event. 300 listings = $0.30 |

Plus Apify's standard start fee ($0.00005 per run). No proxies, no browser. Set a **maximum cost per run** and the Actor stops cleanly at the limit.

### Attribution you must keep

The boards publish these feeds on the condition that listings shown elsewhere link back to the listing URL and name the board as the source. Every row carries `url` and `attribution` for that reason. Remotive also asks that its listings are not resubmitted to other job boards and notes that its public feed is delayed by 24 hours. If you display listings publicly, keep the link and the source name.

### How to use it

- **Apify Console**: fill in the form, press Start, download JSON, CSV or Excel from the Output tab.
- **API**: `POST https://api.apify.com/v2/acts/lathewright~remote-jobs-feed/run-sync-get-dataset-items?token=<token>` with the input JSON as the body.
- **n8n, Make, Zapier**: use the Apify node/module, pick this Actor, paste the input JSON, schedule it a few times a day.

### Use from an AI agent (MCP)

Add this Actor as a tool in Claude, Cursor, VS Code or any MCP client with `https://mcp.apify.com/?tools=lathewright/remote-jobs-feed`. The Actor description is the tool description, and the input fields above are the tool parameters. Example prompts: "Remote DevOps jobs posted this week", "New remote design jobs since my last check".

### Data sources, robots.txt and fair use

Checked on 19 October 2026 for the exact paths this Actor requests:

- **Remote OK API** (`remoteok.com/api`): robots.txt allows `/api` with `Crawl-delay: 1`; the Actor never sends more than one request per 1.1 seconds. The API's own terms (returned in the feed) require a link back and naming Remote OK as the source.
- **Remotive API** (`remotive.com/api/remote-jobs`): robots.txt allows the path. Remotive's terms require a link back and naming Remotive, forbid resubmitting its listings to other job boards, delay the feed by 24 hours and advise at most a few fetches per day. At the time of writing the public endpoint returns a short sample of about a dozen listings; Remotive sells a larger private API separately.
- **We Work Remotely RSS** (`weworkremotely.com/remote-jobs.rss` and the category feeds under `/categories/`): robots.txt allows the paths; the feeds are published for syndication and advertise a 60-minute refresh interval.
- A feed cache (default 60 minutes, in your account's `remote-jobs-feed-cache` store) means repeated or scheduled runs reuse the last fetch instead of hitting the boards again. Listings are public job adverts; no candidate data is involved.

### FAQ

**Why does Remotive return so few jobs?** Its public API is intentionally small and delayed; the Actor returns what it publishes. Remote OK and We Work Remotely return their full current feeds (roughly 100 listings each at any time).

**Can I get older listings?** The feeds only contain current listings. Run the Actor on a schedule with `onlyNewJobs` to build your own history.

**Is the salary always structured?** Only when the board publishes it: Remote OK has numeric fields, Remotive and We Work Remotely publish text that the Actor parses when it looks like a range.

# Actor input Schema

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

Which boards to read.

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

Keep listings whose title or tags (or description, see `searchIn`) contain any of these. Case-insensitive. Empty = all.

## `searchIn` (type: `string`):

Where keywords are matched.

## `categories` (type: `array`):

Category words such as `software-dev`, `design`, `marketing`, `sales`, `customer-support`, `data`, `devops`, `product`, `finance`, `writing`. Mapped to Remotive categories and We Work Remotely feeds where possible, otherwise matched against tags.

## `regions` (type: `array`):

Keep listings whose candidate location text contains any of these (e.g. `Worldwide`, `USA`, `Europe`, `UK`). Listings without a region count as anywhere.

## `postedAfter` (type: `string`):

Keep only listings published on or after this date.

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

Add the plain-text listing description to every row.

## `descriptionMaxChars` (type: `integer`):

Truncate descriptions to this many characters.

## `maxJobsPerSource` (type: `integer`):

Cap per source. Each listing is one billable event.

## `cacheMinutes` (type: `integer`):

Reuse a feed fetched less than this many minutes ago (kept in your account's `remote-jobs-feed-cache` store). Remotive asks for at most a few fetches per day; the feeds themselves change slowly. 0 disables the cache.

## `onlyNewJobs` (type: `boolean`):

Remember every listing seen under `stateKey` and return only ones that were not present in the previous run.

## `stateKey` (type: `string`):

Memory slot name for `onlyNewJobs` (letters, digits, dashes).

## `compactOutput` (type: `boolean`):

Return only the key fields (smaller, cheaper for AI agents to read).

## Actor input object example

```json
{
  "sources": [
    "remoteok",
    "remotive",
    "weworkremotely"
  ],
  "keywords": [
    "engineer",
    "developer"
  ],
  "includeDescription": true,
  "descriptionMaxChars": 3000,
  "maxJobsPerSource": 100,
  "cacheMinutes": 60,
  "onlyNewJobs": false,
  "compactOutput": false
}
```

# Actor output Schema

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

One JSON object per remote job listing, normalized across Remote OK, Remotive and We Work Remotely.

# 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",
        "remotive",
        "weworkremotely"
    ],
    "keywords": [
        "engineer",
        "developer"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("lathewright/remote-jobs-feed").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",
        "remotive",
        "weworkremotely",
    ],
    "keywords": [
        "engineer",
        "developer",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("lathewright/remote-jobs-feed").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",
    "remotive",
    "weworkremotely"
  ],
  "keywords": [
    "engineer",
    "developer"
  ]
}' |
apify call lathewright/remote-jobs-feed --silent --output-dataset

```

## MCP server setup

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

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/l2aDVVupYC1uT1OpU/builds/LgfpLdiOt54hbaC36/openapi.json