# Company Jobs Feed (Greenhouse, Lever, Ashby) (`checkbase/ats-jobs-feed`) Actor

Live job postings straight from companies' own applicant tracking systems. Official public feeds, so no scraping, no proxies and no blocking. Filter by title, location, remote and recency across every tracked company.

- **URL**: https://apify.com/checkbase/ats-jobs-feed.md
- **Developed by:** [Checkbase](https://apify.com/checkbase) (community)
- **Categories:** Jobs, Agents
- **Stats:** 2 total users, 1 monthly users, 50.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/actors/running/actors-in-store.md#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

## Company Jobs Feed: Greenhouse, Lever & Ashby

Live job postings taken **straight from companies' own applicant tracking systems**, not
scraped from a job board.

Most job scrapers hit Indeed, LinkedIn or Glassdoor. That means anti-bot defences, proxies,
breakage, and terms nobody enjoys reading. Companies already publish their vacancies through
ATS platforms with **official public APIs meant for aggregators**. This reads those instead.

The practical result: no proxies, no blocking, no stale cache of a scraped page. The data is
what the company itself published, in the format it published it.

### What it covers

- **Greenhouse**, **Lever** and **Ashby**
- Tracked companies including Stripe, OpenAI, Databricks, Anthropic, Datadog, MongoDB, Notion,
  Snowflake, GitLab, Airbnb, Coinbase, Pinterest, Elastic, Plaid, Deliveroo and more
- Roughly **8,000 open postings** at any time, about a third of them remote

### Input

```json
{
  "titleKeywords": ["engineer", "designer"],
  "locationKeywords": ["london", "remote"],
  "remoteOnly": true,
  "postedWithinDays": 7,
  "maxPerCompany": 200
}
```

Leave `companies` empty and it searches every tracked company at once. That is usually what
you want.

To target specific employers, pass them as `ats:slug`:

```json
{ "companies": ["greenhouse:stripe", "ashby:openai", "lever:spotify"] }
```

- **titleKeywords**, **locationKeywords**: case-insensitive, match any
- **remoteOnly**: keep only postings the company flags as remote
- **postedWithinDays**: 0 means no recency filter
- **includeDescription**: adds full description text. Much larger output
- **maxPerCompany**: cap per employer

### Output

```json
{
  "company": "Notion",
  "companySlug": "notion",
  "ats": "ashby",
  "jobId": "8fb1615c-34bf-47c4-a1d1-b7b2f836bbd3",
  "title": "Software Engineer, Developer Platform",
  "department": "Engineering",
  "location": "San Francisco, California",
  "isRemote": false,
  "employmentType": "FullTime",
  "url": "https://jobs.ashbyhq.com/notion/8fb1615c-...",
  "applyUrl": "https://jobs.ashbyhq.com/notion/8fb1615c-.../application",
  "publishedAt": "2026-08-19T14:02:07Z",
  "checkedAt": "2026-08-24T19:40:00Z"
}
```

All three systems are normalised to one shape, so you never write per-provider parsing.

**`isRemote` can be absent.** Not every ATS states it, and guessing would be worse than saying
nothing. Absent means unknown, not false.

### Good for

- **Job boards and aggregators**: a clean feed that does not break when a site changes markup
- **Recruiting and market research**: who is hiring, for what, where, and since when
- **Tracking a company or a competitor**: pass their slug and schedule it
- **Feeding an AI agent**: one consistent schema across employers

### Scheduling

Schedule it and diff the results. `publishedAt` and `checkedAt` on every row make it easy to
spot what is new since the last run.

### Limitations, stated plainly

- **Coverage is the tracked company list**, not the whole job market. If an employer does not
  use Greenhouse, Lever or Ashby, or is not yet in the list, it will not appear. The list grows.
- **Locations are free text**, exactly as the employer wrote them. "London", "London, UK" and
  "UK Remote" are all possible and are not normalised.
- **No deduplication across companies.** The same role posted by an agency and by the employer
  appears twice.
- **No salary data.** Most of these feeds do not carry it.
- A posting appearing here means the company published it. It does not guarantee the role is
  still open at the moment you read it.

### Disclaimer

This is an **unofficial** tool. It is not affiliated with, endorsed by, or sponsored by
Greenhouse Software, Lever, Ashby, or any of the employers whose postings it returns. It reads
their public job board APIs. Job adverts are company-published content and the output contains
no personal data.

# Actor input Schema

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

One per line as 'ats:slug', e.g. 'greenhouse:stripe' or 'ashby:openai'. Leave empty to use the built-in verified list.

## `useBuiltInList` (type: `boolean`):

Query every company shipped with this Actor. Ignores the Companies field when on.

## `titleKeywords` (type: `array`):

Case-insensitive. Empty means no title filter.

## `locationKeywords` (type: `array`):

Case-insensitive, e.g. 'London', 'Remote'. Empty means no location filter.

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

Keep only postings the company flags as remote.

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

0 means no recency filter.

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

Adds the description text. Much larger output.

## `maxPerCompany` (type: `integer`):

Cap per company, applied before filters.

## Actor input object example

```json
{
  "companies": [
    "greenhouse:stripe",
    "ashby:openai"
  ],
  "useBuiltInList": false,
  "titleKeywords": [],
  "locationKeywords": [],
  "remoteOnly": false,
  "postedWithinDays": 0,
  "includeDescription": false,
  "maxPerCompany": 200
}
```

# Actor output Schema

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

One row per open posting, normalised across Greenhouse, Lever and Ashby.

## `remoteJobs` (type: `string`):

The same run filtered to postings the company flags as remote.

# 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": [
        "greenhouse:stripe",
        "ashby:openai"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("checkbase/ats-jobs-feed").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": [
        "greenhouse:stripe",
        "ashby:openai",
    ] }

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

```

## MCP server setup

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

```

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/7Jf839sDeR0qMCakq/builds/Or59Gh7gPGc0ftxo4/openapi.json