# RemoteOK Jobs — Multi-Tag Feed Export (`jpmarketdata/remoteok-multi-tag-job-feed-export`) Actor

Export RemoteOK public job feeds across a tag watchlist with descriptions, salary data and original links. Deduplicate jobs and report the source feed window. Unofficial.

- **URL**: https://apify.com/jpmarketdata/remoteok-multi-tag-job-feed-export.md
- **Developed by:** [h ichi](https://apify.com/jpmarketdata) (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

$0.50 / 1,000 job exporteds

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

## RemoteOK Multi-Tag Job Feed Export

> **Unofficial** — independent tool, **not affiliated with, endorsed by, or sponsored by Remote OK**. It reads only publicly visible pages. Support, reliability guarantees and the full disclaimer are at the bottom of this page.

Export RemoteOK public job feeds into one deduplicated dataset for a tag watchlist, scheduled job alerts or an existing job aggregator. Remote OK provides this JSON API free without authentication; the Actor adds Apify scheduling, storage, integration, strict filters and normalized fields.

### Input

`tags` accepts up to 10 lowercase public tags, default python and design. Fetch each tag separately and union exact tag matches. Empty tags selects the public base feed. `keywordFilter` is a case-insensitive phrase matched locally in the job title, employer, tags and description. `minSalary` is an optional local positive source salary bound, disabled by zero; exclude undisclosed salaries when active. `maxJobs` defaults to 200, maximum 1000. It limits delivered unique jobs and cannot increase the source feed window.

### Output

Each unique source ID includes title, employer, published location text, source tags, clean full description, posting timestamp, positive source salary bounds, original public job URL and HTTP(S) apply URL. Zero salary placeholders become null; salary currency/period remain null because this endpoint does not explicitly label them. Do not infer employment type, applicant country eligibility or worldwide status. `sourceWindowBounded` is always true. `sourceReturnedCount` is the observed feed count, not the site's total. `sourceDataIncomplete` flags a confirmed feed item with an empty slug and list-root URL/application, which is excluded with id/reason in SUMMARY. The sourceReturnedCount stays unchanged; no direct job URL is invented. Other malformed source fields still fail. `coverageComplete` means all observed selected-feed matches were delivered without such missing job links; `outputLimited` separately reports a user output cap. Uncharged SUMMARY gives each feed count/date window, matched/deduplicated/emitted counts, source update metadata and the explicit non-paginated source bound.

### Limits

RemoteOK's public API currently returns about 100 recent jobs per tag and 99 in the base feed. There is no documented archive pagination. Multiple tag feeds can extend the combined window, but this does not export the whole site's history. Current feed contents and order can change between requests. Process all requested feed responses even after a global output cap. Source tag feeds sometimes include unrelated recommendations; these are removed by exact tag membership. Maximum 10 tags, 1000 unique output rows, 40 requests including robots and retries, 90 seconds, 256 MB and 4 MiB per response. Identifying User-Agent, Accept application/json and at least one second between host requests. No browser, proxy, paid service, login or detail-page crawl. Invalid schema, auth/challenge, HTTP 429, timeout or an incomplete response fails before charged output. A verified zero-match selection records an uncharged SUMMARY and fails as no-matching-jobs.

### Privacy

Public employer and vacancy data only. Strip email and phone contacts from descriptions; no applicant profiles or external application destinations are fetched. Retain Remote OK attribution and a follow link to each original job when displaying these data, as required by its API terms. No use of the Remote OK logo. Independent tool, unaffiliated with Remote OK.

### Charging

One primary job-exported event costs $0.0005 per unique delivered job, including description. No start, request, summary or detail fees. Before any source query the allowance must cover the requested maxJobs; an insufficient allowance fails without silently lowering the requested scope. Initial price hypothesis; public usage counts do not establish paid revenue.

### If something goes wrong

- **Wrong number or a failed run?** Open a ticket on the **Issues** tab. I read every one and reply within 2 business days (Japan time).
- **You never get a fake "empty" result.** If the site can't be read, the run fails and says so.
- **Delivered rows only.** One validated unique row is one billable event. Duplicates, summaries, failed acquisition and undelivered rows are not charged.
- **Checked every week.** An automatic test runs this tool weekly; if the site changes, I fix it.
- **Public source data only.** No login or member/applicant records. Contact patterns are screened before delivery; prose may still name people.

### More tools by the same author

- [We Work Remotely Jobs — Search & Export](https://apify.com/jpmarketdata/weworkremotely-job-search-export)

All tools (Japan marketplaces, real estate, jobs, racing, prediction markets): <https://apify.com/jpmarketdata>

### Disclaimer

Unofficial, independent tool — **not affiliated with, endorsed by, or sponsored by Remote OK**. Product names and logos belong to their owners and only say where the data comes from. Data is read from public pages, for market research; check before you act on it.

# Actor input Schema

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

Union of up to 10 public single-tag feeds. Empty selects the unfiltered public feed. Each source feed currently returns about 100 postings; no historical pagination is offered.

## `keywordFilter` (type: `string`):

Case-insensitive phrase matched locally in position, employer, tags and clean description within the selected source feeds.

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

Optional local lower bound on source salary_max (or positive salary_min when max is absent). Zero disables it. Currency and period are unverified source context; no salary conversion or estimation.

## `maxJobs` (type: `integer`):

Unique output cap, 1–1000. A cap larger than a feed does not expand the source window.

## Actor input object example

```json
{
  "tags": [
    "python",
    "design"
  ],
  "keywordFilter": "",
  "minSalary": 0,
  "maxJobs": 200
}
```

# Actor output Schema

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

Validated job descriptions, salary facts and source coverage.

# 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("jpmarketdata/remoteok-multi-tag-job-feed-export").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("jpmarketdata/remoteok-multi-tag-job-feed-export").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 jpmarketdata/remoteok-multi-tag-job-feed-export --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpmarketdata/remoteok-multi-tag-job-feed-export"
        }
    }
}
```

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/1MbDHzbCEwfvgtY9W/builds/DJ9v7nzo3bHuhSPQ3/openapi.json