# Jobs API — All Sources (`apifmcpfactory/jobs-api-all-sources`) Actor

Open roles from every supported job platform in one run, as structured JSON or CSV, at $1.50 per 1,000 jobs. Paste careers URLs or company names and it works out which platform each is on. One schema, de-duplicated, with change detection and a white-label hiring report.

- **URL**: https://apify.com/apifmcpfactory/jobs-api-all-sources.md
- **Developed by:** [Howth Technology Factory](https://apify.com/apifmcpfactory) (community)
- **Categories:** Jobs, Developer tools, Agents
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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/platform/actors/running/actors-in-store#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

## Jobs API — All Sources

Open roles from every supported job platform in one run. Paste careers URLs or company names and it works out which platform each one is on.

**Unofficial. Not affiliated with or endorsed by any of the platforms it reads.**

***

### What it does

Reads seven public sources — five applicant-tracking systems and two global remote-job feeds — normalises them all to the same schema, merges, de-duplicates and returns one row per role: company, title, department, team, location, country, remote flag, workplace type, employment type, seniority, salary where published, posted date and the apply link.

You do not have to know which ATS a company uses. Paste `airbnb`, a `jobs.lever.co` URL and a Recruitee subdomain in the same list; each input is tried against every platform and lands wherever it belongs.

**Platforms read:** Greenhouse · Lever · Ashby · Recruitee · SmartRecruiters · Remote OK · Jobicy

### Who it's for

- **Aggregators and job boards** that want one integration instead of seven.
- **Talent researchers** measuring hiring across a portfolio of companies on mixed platforms.
- **AI agents** needing open roles as structured JSON without first working out which ATS an employer uses.

### Sample output

From a real run, 2026-08-01: three inputs across three different platforms — **53 roles from 7 sources and 14 boards in about 22 seconds**, no failures, 4 repost groups flagged.

```json
{
  "source": "greenhouse",
  "board": "airbnb",
  "company": "Airbnb",
  "title": "Software Engineer, Community Support Engineering",
  "department": "Software Engineering",
  "location": "San Francisco, CA",
  "isRemote": false,
  "workplaceType": "hybrid",
  "employmentType": null,
  "salary": null,
  "postedAt": "2026-07-31T11:14:30-04:00",
  "applyUrl": "https://careers.airbnb.com/positions/8097917?gh_jid=8097917"
}
```

Every row carries `source` and `board`, so you always know where a role came from.

#### "Not on this platform" is not a failure

Each input is tried against every platform, so a Greenhouse company legitimately "fails" on Lever, Ashby and the rest. Those are counted separately as `notOnThisPlatform`, not as errors: an input that succeeded **anywhere** was simply not on the platforms that could not find it. Only an input no source could read is reported as a real failure. On the run above that meant **0 failures** and 7 not-on-this-platform, rather than a scary-looking 7 errors.

#### What each platform publishes differs, and is never invented

Salary is in the public feed for Lever, Ashby, Recruitee and Jobicy, and absent from Greenhouse and SmartRecruiters. Department is everywhere except Remote OK. SmartRecruiters carries no advert body at all. Where a platform does not publish a field it is `null` — never guessed, never inferred from the job title. Each single-platform listing in this family documents its own coverage measured on a real run.

### The three rules this product is built on

1. **Job descriptions belong to the employer.** `includeDescription` is **off by default**.
2. **No personal data, ever.** No recruiter names, no hiring-manager contacts, no emails, no phone numbers. There is nowhere in this schema to put one, and a test fails the build if a personal-data field appears.
3. **Unofficial, reading public feeds.** No key, no login, no browser automation, no anti-bot circumvention. Where a source licences its data on condition of credit and a link back, that attribution travels with every run and the apply link is never rewritten.

### Pricing

| Event | Price |
|---|---|
| Actor start | $0.00005 |
| Job returned | $0.0015 |

**$1.50 per 1,000 jobs**, charged on the final de-duplicated set — not on the sum of the sources. A company on two platforms is charged once. A board that could not be read returns nothing and is not charged. The 53-job run above cost **$0.08**.

Use `maxJobsPerSource` and the title/location filters to cap what a run can cost: you are charged for what comes back, so filtering in the input costs less than filtering afterwards.

### Monitoring

Set `onlyNewSinceLastRun` and schedule it. The first run stores a baseline per board and returns everything — nothing is reported as a change, because everything being new the first time is not news. Add a `webhookUrl` for a JSON summary when anything moves.

### FAQ

**Do I need any API keys?** No. Every source is a public feed.

**Do I need to know which ATS a company uses?** No. That is the point of this listing.

**Can I limit it to certain platforms?** Yes — set `sources`, e.g. `["greenhouse","lever"]`.

**Why did a company return nothing?** Either it has nothing open, or it is on a platform not in this list. SmartRecruiters in particular cannot distinguish an unknown company from an empty board; its result says so.

**If a role appears on two platforms, do I pay twice?** No. De-duplication runs before charging.

**Which platforms are not included?** Several were evaluated and excluded — some because their terms prohibit commercial redistribution, one because its feed could only be read for one board in four. A source that cannot be read reliably or republished lawfully is not in here.

### MCP — for AI agents

```json
{ "mcpServers": { "jobs": { "url": "https://jobs-api.mcpize.run" } } }
```

`search_jobs` $0.01 · `get_company_jobs` $0.01 · `monitor_jobs` $0.02 · `generate_report` $0.10

***

*Unofficial. Not affiliated with or endorsed by any platform named here. Job adverts are the property of the employers who published them.*

# Actor input Schema

## `companies` (type: `array`):

One per line. Paste a careers URL, a board identifier or a company name and this listing works out which platform it belongs to. The global remote-job feeds inside it are read whether or not you name anything, so leaving this empty is valid.

## `dataPreset` (type: `string`):

All jobs is right for most uses. New only is for scheduled runs. With descriptions returns the advert body as well — see the note below before switching it on.

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

Off by default, and deliberately. A job advert is the employer's copyrighted text; the structured fields are not. Leaving it off means smaller payloads, faster runs and a cleaner licence position. Switch it on when your use needs the body text.

## `onlyNewSinceLastRun` (type: `boolean`):

For scheduled runs. The first run on a board always returns everything and stores the baseline; after that you get only what appeared since. Removed and edited postings are still reported in the summary and the report.

## `titleIncludes` (type: `array`):

For example engineer, designer, product. Leave empty for every role.

## `titleExcludes` (type: `array`):

For example intern, contract. Applied after the include list.

## `locationIncludes` (type: `array`):

For example Dublin, Germany, Remote.

## `departmentIncludes` (type: `array`):

Only useful where every supported platform publishes one — see the platform notes in the README.

## `employmentTypes` (type: `array`):

Normalised across every platform in this family. A platform that does not publish one leaves it empty, and those jobs are excluded when you set a filter here.

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

Uses the platform's own remote flag where there is one, and the location text where there is not.

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

Leave empty for all. Jobs with no published date are kept rather than silently dropped.

## `maxJobsPerCompany` (type: `integer`):

Caps what each board can return, and therefore what it can cost. Leave empty for all of them.

## `sortBy` (type: `string`):

Undated postings always sort last rather than pretending to be the oldest.

## `generateReport` (type: `boolean`):

A client-ready review of the whole run: where the hiring is by department and location, what changed since the last run, and every open role in one table. Costs nothing extra.

## `reportFormat` (type: `string`):

HTML opens in any browser and prints cleanly to A4. PDF is ready to send to a client.

## `reportCompanyName` (type: `string`):

Appears on the report. Setting this (or a logo) puts it in white-label mode and takes our name off.

## `reportLogoUrl` (type: `string`):

A direct link to a PNG, JPG or SVG.

## `reportAccentColor` (type: `string`):

Hex colour used for headings, for example #1E3A8A.

## `reportFooterText` (type: `string`):

Appears at the bottom of every page — usually your company name or a client reference.

## `exportFormat` (type: `string`):

The dataset is always JSON. This additionally writes flat comma-separated files you can open in a spreadsheet — the jobs, the boards, and what changed.

## `webhookUrl` (type: `string`):

Called with a JSON summary when a board gains, loses or changes a posting. Nothing fires on the first run, because everything is new the first time and that is not news.

## `userAgent` (type: `string`):

Every request declares who is making it and how to reach them. The default identifies this actor. If you are running at volume, put your own company name and email here.

## `requestsPerSecond` (type: `integer`):

Shared across the whole run. The default is deliberately gentle: these are free public feeds and staying welcome on them matters more than finishing half a second sooner.

## Actor input object example

```json
{
  "companies": [
    "airbnb",
    "https://jobs.lever.co/leverdemo",
    "https://jobs.ashbyhq.com/ashby"
  ],
  "dataPreset": "all-jobs",
  "includeDescription": false,
  "onlyNewSinceLastRun": false,
  "remoteOnly": false,
  "sortBy": "newest",
  "generateReport": false,
  "reportFormat": "both",
  "reportAccentColor": "#1E3A8A",
  "exportFormat": "none",
  "userAgent": "Howth Technology Factory jobs-api apifymcpfactory@gmail.com",
  "requestsPerSecond": 4
}
```

# Actor output Schema

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

No description

## `report` (type: `string`):

No description

## `reportPdf` (type: `string`):

No description

## `summary` (type: `string`):

No description

## `csv` (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 = {
    "companies": [
        "airbnb",
        "https://jobs.lever.co/leverdemo",
        "https://jobs.ashbyhq.com/ashby"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("apifmcpfactory/jobs-api-all-sources").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 = { "companies": [
        "airbnb",
        "https://jobs.lever.co/leverdemo",
        "https://jobs.ashbyhq.com/ashby",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("apifmcpfactory/jobs-api-all-sources").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "companies": [
    "airbnb",
    "https://jobs.lever.co/leverdemo",
    "https://jobs.ashbyhq.com/ashby"
  ]
}' |
apify call apifmcpfactory/jobs-api-all-sources --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=apifmcpfactory/jobs-api-all-sources",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/0sXHTZPbI71FIO2Gg/builds/8AghzZHFlKX7Yx1Cy/openapi.json