# Remote Jobs Aggregator: Jobicy, RemoteOK & ATS Boards (`brioq/remote-jobs-ats-aggregator`) Actor

Remote job listings from sources whose API terms allow reuse (Jobicy, RemoteOK) plus any company's Greenhouse, Lever or Ashby job board, in one schema with salaries converted to USD per year.

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

## Pricing

$2.00 / 1,000 results

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 Aggregator: Jobicy, RemoteOK & ATS Boards

Collect **remote job listings** from public sources and from **any company's Greenhouse, Lever or Ashby job board**, in **one clean schema**, with salaries also converted to **USD per year**.

### What it does

- Pulls remote jobs from **Jobicy** and **Remote OK** through their public APIs.
- Pulls jobs from company career boards on **Greenhouse**, **Lever** and **Ashby** through their official public job-board APIs — add as many companies as you like, e.g. `greenhouse:stripe`, `lever:spotify`, `ashby:ramp`.
- Normalizes every job into the same fields, deduplicates the same job posted on several sources, and sorts by publication date.
- Converts published salaries to **USD per year** using daily ECB exchange rates, while keeping the original amount, currency and period.
- Filters by keywords, publication date and remote status.

### Sources and fair use

Only sources whose API terms allow reuse with attribution are included. Every result keeps the **original job URL** (applications go to the source) and an **`attribution`** line crediting the source — please keep that credit visible if you display the jobs. Remotive and Himalayas are intentionally not included, because their terms do not allow passing their jobs to other aggregators.

Email addresses and phone numbers are removed from descriptions, so results never carry recruiters' personal contacts.

### Input

| Field | Description |
| --- | --- |
| `sources` | `jobicy`, `remoteok` (default: both). |
| `atsBoards` | Company boards as `provider:company`. The company part is the board name from the board URL (`boards.greenhouse.io/stripe` → `greenhouse:stripe`). |
| `keywords` | Keep jobs whose title, tags or description contain any keyword. |
| `remoteOnly` | For company boards, keep only remote jobs (default `true`). |
| `postedWithinDays` | Keep jobs published in the last N days (default 30). |
| `maxItems` | Maximum jobs to return (default 100). |

### Output example

```json
{
  "id": "jobicy:156705",
  "source": "jobicy",
  "attribution": "Job listing via Jobicy (https://jobicy.com)",
  "title": "Senior Software Engineer",
  "company": "Veriff",
  "url": "https://jobicy.com/jobs/156705-senior-software-engineer-16",
  "location": "Spain",
  "remote": true,
  "employmentType": "Full-Time",
  "tags": ["Software Engineering"],
  "salaryMin": 65000,
  "salaryMax": 105000,
  "salaryCurrency": "EUR",
  "salaryPeriod": "year",
  "salaryMinUsdYear": 72754,
  "salaryMaxUsdYear": 117525,
  "description": "At Veriff's Biometric Solutions team, ...",
  "postedAt": "2026-10-24T09:52:43+00:00"
}
```

### Pricing

You pay per job returned. The price per result is shown on this page. Use `maxItems` or the run's maximum charge to cap spending; the Actor stops cleanly at the cap.

### Limitations

- Salaries appear only when the source publishes them; many jobs have none.
- Remote detection on company boards relies on what the board publishes (a remote flag or "Remote" in the location).
- Phone-number removal can also blank out number sequences that look like phone numbers.
- Jobicy's feed covers roughly the last week of postings.

# Actor input Schema

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

Public remote-job sources to include. Supported: jobicy, remoteok.

## `atsBoards` (type: `array`):

Company boards as provider:company, e.g. greenhouse:stripe, lever:spotify, ashby:ramp. The company part is the board name in the board's URL.

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

Keep jobs whose title, tags or description contain any of these words (case-insensitive). Leave empty to keep all.

## `remoteOnly` (type: `boolean`):

For company boards, keep only jobs marked remote. Jobicy and RemoteOK jobs are always remote.

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

Keep jobs published in the last N days.

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

Maximum number of jobs to return. Each job is one billed result.

## Actor input object example

```json
{
  "sources": [
    "jobicy",
    "remoteok"
  ],
  "atsBoards": [
    "greenhouse:stripe",
    "ashby:ramp"
  ],
  "keywords": [],
  "remoteOnly": true,
  "postedWithinDays": 30,
  "maxItems": 50
}
```

# Actor output Schema

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

No description

# 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 = {
    "atsBoards": [
        "greenhouse:stripe",
        "ashby:ramp"
    ],
    "maxItems": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("brioq/remote-jobs-ats-aggregator").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 = {
    "atsBoards": [
        "greenhouse:stripe",
        "ashby:ramp",
    ],
    "maxItems": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("brioq/remote-jobs-ats-aggregator").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 '{
  "atsBoards": [
    "greenhouse:stripe",
    "ashby:ramp"
  ],
  "maxItems": 50
}' |
apify call brioq/remote-jobs-ats-aggregator --silent --output-dataset

```

## MCP server setup

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

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/7pluUR2reb87l0Qzm/builds/HKEggWVO1x2raikg8/openapi.json