# Remote Jobs Monitor — Remotive + RemoteOK in one feed (`bitme/remote-jobs-monitor`) Actor

Remote job postings from Remotive and RemoteOK in one normalized, deduplicated feed. Filter by keywords and category; schedule with onlyNew for an automatic new-jobs radar. Official APIs, no scraping.

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

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

## 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

## Remote Jobs Monitor — Remotive + RemoteOK in one feed

Aggregates **remote job postings** from the **official public APIs** of
[Remotive](https://remotive.com) and [Remote OK](https://remoteok.com) into one
normalized, deduplicated feed — filtered by keywords, category and source.

Both boards publish these endpoints deliberately so developers can redistribute their
jobs. No scraping, no login, no API key — which means near-zero breakage and
maintenance compared to scraping job sites.

### What it does

- Pulls from the **official Remotive API** and the **official RemoteOK API**
- Normalizes both into one schema: title, company, tags, location, salary,
  publication date, description excerpt, direct link
- **Keyword filter** applied uniformly to both sources (title, company, tags,
  description) plus a **category filter** for Remotive jobs
- **Monitoring mode** (`onlyNew`): run on a schedule and each run emits *only jobs you
  haven't seen before* — connect the dataset to email/Slack/Sheets via any Apify
  integration and you have an automatic job radar

### Example: senior Python roles, monitored daily

```json
{
  "sources": ["remotive", "remoteok"],
  "keywords": ["python", "senior"],
  "onlyNew": true,
  "maxItems": 200
}
```

Typical output item:

```json
{
  "id": "remotive-1919266",
  "source": "Remotive",
  "title": "Senior Independent AI Engineer / Architect",
  "company": "A.Team",
  "category": "Software Development",
  "tags": ["go", "testing"],
  "jobType": "contract",
  "location": "Americas, Europe, Israel",
  "salary": "$120 - $170 /hour",
  "publicationDate": "2026-08-16T10:09:41",
  "url": "https://remotive.com/remote-jobs/software-development/senior-independent-ai-engineer-architect-1919266",
  "description": "A.Team is a network of senior product builders..."
}
```

### Input

| field | meaning |
|---|---|
| `sources` | `remotive`, `remoteok`, or both |
| `category` | Remotive category slug, e.g. `software-dev`, `design`, `marketing` (RemoteOK jobs carry no category, so setting this returns Remotive jobs only) |
| `keywords` | case-insensitive substrings matched against title, company, tags and description — filter both sources |
| `onlyNew` | dedup against previous runs (for schedules) |
| `maxItems` | cap per run |

### Scheduling a job radar

1. Set `onlyNew: true`
2. Create a Schedule (e.g. daily 08:00 — both boards advise a few pulls per day at most)
3. Add an integration on the dataset (email, Slack, Google Sheets, webhook)

New matching jobs land in your inbox; silence means nothing new — not a broken run.

### Attribution

Every item carries `source` and a direct `url` back to the original posting, as
required by both boards' API terms. Jobs are sourced from **Remotive** and
**Remote OK** — follow the links to apply.

# Actor input Schema

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

Which boards to pull from. Valid values: remotive, remoteok. Both are official public APIs — no scraping, no key.

## `category` (type: `string`):

Remotive category slug, e.g. software-dev, design, marketing, customer-support, sales, product, data, devops, finance-legal, hr, qa, writing, all-others. Enforced client-side against each job's category. NOTE: RemoteOK jobs carry no category, so setting this excludes RemoteOK items. Leave empty for all categories.

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

Case-insensitive substrings matched against title, company, tags and description — applied client-side to BOTH sources, e.g. rust, senior, django.

## `onlyNew` (type: `boolean`):

Deduplicate against previous runs — turn on when running on a schedule, so each run emits only fresh job postings.

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

Cap on results per run.

## Actor input object example

```json
{
  "sources": [
    "remotive",
    "remoteok"
  ],
  "category": "",
  "keywords": [],
  "onlyNew": false,
  "maxItems": 200
}
```

# Actor output Schema

## `jobs` (type: `string`):

All job postings matching the source/keyword filters, one item per posting.

# 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": [
        "remotive",
        "remoteok"
    ]
};

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

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

```

## MCP server setup

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

```

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/rOvbiw9sgobkh71fd/builds/TXyFJ2PaJdHB7sdOU/openapi.json