# RemoteOK remote jobs feed (public API, attribution) (`retrainmap/remoteok-jobs`) Actor

Newest remote job postings from Remote OK's public JSON API, one row per job: company, position, tags, location, salary range, date, URL and description text, plus the source attribution Remote OK's terms require. Filter by tag (one request each) and keyword. Default: the newest 100 postings.

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

## Pricing

from $5.00 / 1,000 records

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## RemoteOK remote jobs feed (public API, attribution)

One row per remote job posting from **Remote OK**'s public JSON API (https://remoteok.com/api):
id, company, position, tags, location, published salary range, date, Remote OK URL, apply URL,
description text (first 3,000 characters) — and, on every row, the source attribution the API's
terms ask for. Filter by Remote OK tags (one request per tag, merged) and a client-side keyword.

**The default input (the unfiltered newest feed, up to 200 rows) succeeds within 5 minutes and
returns rows** — Apify auto-tests it daily.

### Data source, terms and attribution

| | |
|---|---|
| Publisher | Remote OK (https://remoteok.com) |
| API | https://remoteok.com/api — public, no key; `?tags=a,b` filters server-side |
| Terms (from the API's own first element, read on every run and stored in `RUN_SUMMARY.source_terms`) | *"Please link back (with follow, and without nofollow!) to the URL on Remote OK and mention Remote OK as a source ... please don't use the Remote OK logo without written permission as it's a registered trademark, please DO use our name Remote OK though."* |
| How this Actor honours them | Every row carries `url` (the Remote OK posting page) and `source_attribution` = `Source: Remote OK - <url>`; no logo field is copied (`company_logo`/`logo` are dropped). **If you republish the rows, keep the link back to `url` as a follow link and name Remote OK as the source** — that is a condition of the API, not of this Actor |
| Refresh cadence | Live on every run; the API's `last_updated` epoch is stored in `RUN_SUMMARY.source_last_updated` |
| Known caveats | **No paging**: one request returns at most the newest ~100 postings (`page`/`offset`/`limit` are ignored — measured 2026-09-04); use tags to widen the pull (each tag = one request, ~100 newest postings carrying it). `salary_min`/`salary_max` are the API's integers (USD, 0 = not published → `null`); `location` is often empty for worldwide roles; `original`/`verified` are present on a few postings only |

Honesty note: the rows are the API's own fields — nothing is parsed out of the description, no
salary is estimated, no field is inferred. A body that is not `[legal notice, jobs...]` or a job
without `id`/`position` stops the run with an error rather than guess.

Identification: requests carry a product-token User-Agent and the operator's contact address in
the standard `From:` header; at most one request per second by default.

### Input

| Field | Type | Meaning |
|---|---|---|
| `tags` | array | Optional Remote OK tags (`python`, `devops`, `design`, `customer support`, `senior`, ...); one request per tag, at most 20 |
| `keyword` | string | Optional substring on position/company/tags/description (case-insensitive) |
| `min_salary` | integer | Optional; keep only postings with a published salary at least this (USD) |
| `max_records` | integer | Default 200, newest first |
| `request_interval_ms` | integer | Default 1000 (floor 500) |
| `contact_email` | string | Sent in the `From:` header |

Example — senior Python, DevOps or design roles:

```json
{ "tags": ["python", "devops", "design"], "keyword": "senior", "max_records": 150 }
```

### Output (dataset row)

`id`, `slug`, `company`, `position`, `tags`, `location`, `salary_min`, `salary_max`,
`salary_currency`, `date`, `url`, `apply_url`, `description`, `original`, `verified`,
`matched_tag`, `source_attribution`, `source_url`, `fetched_at`.

A run summary (the API's terms text, `last_updated`, per-tag counts, unique postings, requests,
whether the pay-per-event budget stopped the run) is stored as `RUN_SUMMARY` in the run's
key-value store.

### Pricing (pay per event)

| Event | Price |
|---|---|
| `run-start` — once per run | $0.10 |
| `record` — per row written | $0.005 |

The default pull (~100 rows) costs about $0.60; 1,000 rows across many tags cost $5.10. Rows
stop when your run's maximum charge is reached; the run summary says so.

### Operator

Steelyard Ventures LLC (RetrainMap) — info@steelyardclinical.com. Not affiliated with Remote OK.
The Actor writes only to its own dataset and key-value store; it stores no credentials and sends
nothing else.

# Actor input Schema

## `tags` (type: `array`):

Optional Remote OK tags, e.g. python, javascript, devops, design, marketing, customer support, senior. One request per tag (at most 20); a posting matches when it carries the tag. Empty = the unfiltered newest feed.

## `keyword` (type: `string`):

Optional, case-insensitive substring matched client-side against position, company, tags and description.

## `min_salary` (type: `integer`):

Optional. Keep only postings whose published salary\_max (or salary\_min) is at least this. Postings without a published salary are dropped when this is set.

## `max_records` (type: `integer`):

Stop after this many rows (newest first). Without tags at most ~100 rows exist; with N tags at most ~100 x N.

## `request_interval_ms` (type: `integer`):

Politeness delay towards remoteok.com; the floor is 500 ms.

## `contact_email` (type: `string`):

Sent in the standard From: request header so the data owner can reach the operator (RFC 9110 s10.1.2).

## Actor input object example

```json
{
  "max_records": 200,
  "request_interval_ms": 1000,
  "contact_email": "info@steelyardclinical.com"
}
```

# Actor output Schema

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

One row per remote job posting: id, company, position, tags, location, salary range, date, URL, description, source attribution.

## `results_csv` (type: `string`):

The same rows as a CSV file.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("retrainmap/remoteok-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("retrainmap/remoteok-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 '{}' |
apify call retrainmap/remoteok-jobs --silent --output-dataset

```

## MCP server setup

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