# Remote Jobs API — 5 Boards, One Schema, No Emails | $1.5/1K (`steadyrow/remote-jobs`) Actor

Fresh remote jobs from Remote OK, Jobicy, We Work Remotely, 4 Day Week and Arbeitnow in one unified schema, taken from their official public APIs and feeds. Filter by keyword, location and date. Monitor mode returns only jobs you have not received before. Job data only, no recruiter contacts.

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

## Pricing

from $1.50 / 1,000 jobs

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 API — 5 Boards, One Schema, No Emails | $1.5/1K

Fresh remote jobs from **Remote OK, Jobicy, We Work Remotely, 4 Day Week and Arbeitnow**, normalised into one clean schema. Every board is read through its **official public API or RSS feed**, nothing is scraped from pages, and every row carries the source link and a ready-made credit line, so you can use the data the way the boards ask you to.

Turn on **monitor mode** and a daily run returns only the jobs you have not received before. You pay for new jobs, not for the same listings again.

### What you get

| Field | Example |
|---|---|
| `job_id` | `remoteok:1137545` (stable: `<board>:<id>`) |
| `source`, `source_name` | `weworkremotely`, `We Work Remotely` |
| `title`, `company`, `company_logo` | `Senior Software Engineer`, `Sotheby’s`, logo URL |
| `location` | `Worldwide`, `USA Only`, `Europe`, `Berlin` — as the board writes it |
| `remote` | `true` |
| `category`, `tags` | `Engineering`, `["python", "backend", "senior"]` |
| `employment_type`, `seniority` | `Full-Time`, `Senior` |
| `salary_min`, `salary_max`, `salary_currency`, `salary_period` | `80000`, `120000`, `USD`, `year` (when the board publishes it) |
| `posted_at`, `expires_at` | ISO 8601 |
| `description_text`, `description_html` | full posting as plain text and as HTML |
| `url` | the listing on the board — use it as the apply link |
| `attribution` | `Source: Remote OK — https://remoteok.com/remote-jobs/…` |
| `scraped_at` | ISO 8601 |

**Not included, on purpose:** recruiter names, e-mail addresses, phone numbers or any other personal data. This is a job-data API, not a lead list.

### Boards

| Board | What we read | Coverage | Notes |
|---|---|---|---|
| Remote OK | public JSON API | newest ~100 jobs | worldwide, tech-heavy |
| Jobicy | public JSON API (cursor pagination) | all jobs from the last 7 days | many categories, salary when given |
| We Work Remotely | public RSS feeds (main + 11 categories) | whole board (~500) | region restrictions, expiry dates |
| 4 Day Week | public JSON API v2 | all **remote** 4-day-week jobs (thousands) | structured locations, salaries, stack |
| Arbeitnow | public JSON API | **remote** jobs from the newest pages | Europe / Germany focus |

### Use cases

- **Job boards and newsletters**: one feed instead of five integrations, deduplicated across boards
- **Daily alerts**: `monitorMode: true` on a schedule → only new matches, pushed to Slack, e-mail or a sheet via Apify integrations
- **Market research**: salaries, seniority and stack across boards; filter by `postedWithinDays`
- **AI agents**: a cheap, structured "find remote jobs about X" tool

### Input

```json
{
  "sources": ["remoteok", "jobicy", "weworkremotely", "4dayweek"],
  "keywords": ["python", "data engineer"],
  "excludeKeywords": ["intern"],
  "searchIn": "title_tags",
  "location": "USA",
  "postedWithinDays": 14,
  "maxItems": 500,
  "monitorMode": true
}
```

- `sources` — boards to read (all five by default)
- `keywords` / `excludeKeywords` — case-insensitive, any keyword matches; `searchIn` picks title only, title + tags + category + company (default), or everything incl. description
- `location` — substring of the board's location text (`USA`, `Europe`, `Worldwide`, `Germany`…); common variants are understood (`USA` also matches "United States" and "North America Only", `Worldwide` also matches "Anywhere")
- `postedWithinDays` — drop older jobs (jobs without a date are kept)
- `maxItems` — total cap. Every board first gets an equal share, then the rest is filled from boards with more matches, so a default run always mixes all boards; `maxItemsPerSource` sets a hard per-board cap instead
- `includeDescription` — turn off for a lighter dataset
- `dedupeAcrossSources` — the same posting often appears on several boards; keep only the first copy (default on)
- `monitorMode`, `monitorStateName` — remember delivered jobs in a named key-value store and output only new ones; use a different name per task
- `requestDelaySecs` — pause between requests (default 2 s)

The run also stores a `SUMMARY` record in the key-value store with per-board counts (listed, output, filtered, already seen, duplicates, requests).

### Pricing

Pay per job: **$1.50 per 1,000 jobs** plus a $0.001 start fee per run. No monthly fee. With monitor mode a daily run typically delivers a few dozen new jobs, i.e. cents per day.

### Using the data correctly

The boards publish these APIs and feeds for exactly this kind of integration, on simple conditions that this Actor makes easy to meet:

- **Link back and name the source.** Use `url` as the apply link and show `attribution` (or at least the board name with a link). Remote OK asks for a follow link; Jobicy asks that apply buttons lead to the Jobicy listing.
- **Don't re-post to other boards or job search engines** without the source's permission; use the data in your own product, dashboard, newsletter or agent.
- Keep request volume reasonable: this Actor fetches sequentially with a pause, well inside every board's published limits.

Boards whose terms don't allow aggregation or commercial reuse (for example Himalayas, Remotive and Working Nomads) or whose robots.txt disallows their API path are deliberately **not** included.

### Limits

- Coverage is what each board exposes publicly: Remote OK gives the newest ~100 jobs; Jobicy covers the last 7 days
- Salary fields are filled only when the board publishes them (Jobicy, 4 Day Week, some Remote OK jobs)
- `location` is free text and differs between boards; filter with short words

# Actor input Schema

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

Which boards to read. All five by default. Every board is read through its official public API or RSS feed.

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

Keep a job when ANY keyword appears (case-insensitive) in the fields chosen under "Search in". Leave empty for all jobs.

## `excludeKeywords` (type: `array`):

Drop a job when ANY of these appears in the same fields.

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

Where keywords are matched. "Title and tags" also covers category and company name.

## `location` (type: `string`):

Keep jobs whose location text contains this, e.g. "USA", "Europe", "Worldwide", "Germany". Boards write locations differently, so prefer short words.

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

Drop jobs older than this many days. Jobs without a date are kept.

## `maxItems` (type: `integer`):

Stop after this many jobs across all boards.

## `maxItemsPerSource` (type: `integer`):

Hard cap per board. By default every board first gets an equal share of the total and the rest is filled from boards with more matches; setting this turns that top-up off.

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

Turn off for a lighter dataset (description_text and description_html become null).

## `dedupeAcrossSources` (type: `boolean`):

The same posting often appears on several boards. When on, only the first copy (in board order) is output.

## `monitorMode` (type: `boolean`):

Remembers every job already delivered (per board) and outputs only jobs you have not received before. The first run outputs all matching jobs. Ideal for a daily schedule — you only pay for new jobs.

## `monitorStateName` (type: `string`):

Name of the key-value store that keeps the list of delivered jobs. Use a different name per task if you run several independent monitors.

## `requestDelaySecs` (type: `integer`):

Requests are made one at a time with this pause in between, to stay well inside every board's rate limits.

## Actor input object example

```json
{
  "sources": [
    "remoteok",
    "jobicy",
    "weworkremotely",
    "4dayweek",
    "arbeitnow"
  ],
  "keywords": [
    "engineer",
    "developer"
  ],
  "searchIn": "title_tags",
  "maxItems": 500,
  "includeDescription": true,
  "dedupeAcrossSources": true,
  "monitorMode": false,
  "monitorStateName": "remote-jobs-monitor",
  "requestDelaySecs": 2
}
```

# Actor output Schema

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

All remote job postings collected in this run, one row per job.

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

// Run the Actor and wait for it to finish
const run = await client.actor("steadyrow/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 = { "keywords": [
        "engineer",
        "developer",
    ] }

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,steadyrow/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/HhjBFAJp9iZahznj3/builds/IWv6E4uLDx2OgIeat/openapi.json