# ATS Job Listings: Greenhouse, Lever, Ashby, Personio, Recruitee (`datasetworks/company-jobs`) Actor

Get every open role at a list of companies in one clean table, from their official public Greenhouse, Lever, Ashby, Personio and Recruitee job boards. Same fields across platforms, keyword and remote filters, optional full descriptions. Built for spreadsheets and AI agents.

- **URL**: https://apify.com/datasetworks/company-jobs.md
- **Developed by:** [Dataset Works](https://apify.com/datasetworks) (community)
- **Categories:** Jobs, Lead generation, AI
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.50 / 1,000 job returneds

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

## ATS Job Listings: Greenhouse, Lever, Ashby, Personio, Recruitee

**Get every open role at a list of companies in one clean table, straight from their official public job boards.**

Give it company names or job-board links. It finds each company's board on Greenhouse, Lever, Ashby, Personio or Recruitee and returns every open job with the same fields every time, whichever platform the company uses.

### Sample output

| company | platform | title | location | department | employmentType | isRemote | compensation |
| --- | --- | --- | --- | --- | --- | --- | --- |
| stripe | greenhouse | AI Engineer | Chicago | SA Transformation | | false | |
| palantir | lever | Backend Software Engineer - Application Development | London, United Kingdom | Dev | Full-time | false | |
| ramp | ashby | Security Engineer, Cloud | New York, NY (HQ) | Engineering / Backend | Full-time | true | $211.4K – $290.6K • Offers Equity |
| notion | ashby | Software Engineer, AI Connections (Developer Platform) | San Francisco, California | Engineering | Full-time | true | |

Every row also has `jobId`, `url` (the apply link), `postedAt`, `updatedAt`, `scrapedAt` and, if you ask for it, `description` as clean plain text.

One record as JSON:

```json
{
  "company": "stripe",
  "platform": "greenhouse",
  "jobId": "8172508",
  "title": "Abuse Investigator",
  "location": "Dublin",
  "department": "Security Analytics",
  "employmentType": null,
  "isRemote": false,
  "url": "https://stripe.com/jobs/search?gh_jid=8172508",
  "postedAt": "2026-09-03T13:32:53-04:00",
  "updatedAt": "2026-10-29T10:42:09-04:00",
  "compensation": null,
  "scrapedAt": "2026-11-17T07:09:20.993Z"
}
```

### How to use

1. Add companies to **Companies**. Any of these work:
   - a board name: `stripe`
   - a board name with a platform: `lever:palantir`, `ashby:ramp`, `greenhouse:airbnb`, `personio:personio`, `recruitee:bunq`
   - a job-board link: `https://jobs.lever.co/palantir`, `https://jobs.ashbyhq.com/ramp`, `https://boards.greenhouse.io/stripe`, `https://bunq.recruitee.com`
2. Optional filters: **Title keywords** (comma-separated, e.g. `engineer, data`), **Remote jobs only**, **Max jobs per company**.
3. Tick **Include full job description** if you want the text of each posting.
4. Run. Results appear in the dataset; export to CSV, Excel or JSON, or read them via the API.

The default input works with no setup. A `SUMMARY` record in the key-value store lists how many jobs each company returned, and which companies had no board found.

**Tip:** the board name is the last part of a company's careers link, e.g. `jobs.lever.co/`**`palantir`**.

### Ready-made inputs

Copy one of these into the **JSON** tab of the input and run it.

**Engineering roles at a list of AI companies**

```json
{"companies": ["anthropic", "ashby:openai", "greenhouse:scaleai", "ashby:cohere"], "keyword": "engineer"}
```

**Remote-only jobs at fintechs, with full descriptions**

```json
{"companies": ["stripe", "ashby:ramp", "greenhouse:affirm", "greenhouse:brex"], "remoteOnly": true, "includeDescription": true}
```

**Sales hiring signals: who is hiring account executives**

```json
{"companies": ["greenhouse:datadog", "ashby:notion", "greenhouse:figma", "lever:palantir"], "keyword": "account executive, sales"}
```

Schedule any of these daily or weekly and compare runs to see new and closed roles.

### Use cases

- Track hiring at competitors, customers or portfolio companies.
- Spot companies hiring for a role you sell into (sales signals).
- Build job boards and job alerts for a niche.
- Feed AI agents and research tools with up-to-date hiring data.

### Pricing

**$1.50 per 1,000 jobs** ($0.0015 per job returned). No charge for companies with no jobs found. Platform usage is included. Example: 5 companies with 500 open roles in total costs $0.75.

### For AI agents

Call it through the Apify API or the Apify MCP server with `{"companies": ["stripe", "lever:palantir"]}`. It returns one JSON object per job with a fixed set of fields, so agents can rely on the shape. Use `keyword`, `remoteOnly` and `maxJobsPerCompany` to keep responses small.

### FAQ

**Is this a Greenhouse API or Lever API scraper?** Yes. It reads the public job-board APIs of Greenhouse, Lever, Ashby, Personio and Recruitee and gives you one table with the same columns for all five, so you don't need separate code for each.

**How do I find a company's board name?** It's the last part of their careers link, e.g. `boards.greenhouse.io/`**`stripe`** or `jobs.ashbyhq.com/`**`ramp`**. If you only give a name, the tool tries each platform for you.

**Does it work for LinkedIn or Indeed?** No. It only reads companies' own public job boards, which are the original source of most tech and startup jobs, and it never logs in anywhere.

**How do I track hiring changes over time?** Save your company list as a task, schedule it daily or weekly, and send results to Google Sheets or a webhook. Each job has a stable `jobId`, so new and removed roles are easy to spot.

**Can I use it with ChatGPT, Claude or Cursor?** Yes. Add the Apify MCP server with this tool (`https://mcp.apify.com/?tools=datasetworks/company-jobs`) and ask "what data roles is Ramp hiring for?".

### Data and responsibility

Data comes only from the public job-board APIs that Greenhouse, Lever, Ashby, Personio and Recruitee provide so companies can publish their jobs. The tool collects job postings, not people: no candidate or employee data, no logins, nothing behind access controls. It follows each site's robots.txt and rate limits.

### Support

Found a bug or need a field? Open an issue on this page and we'll reply within one working day.

Built and maintained by **Dataset Works**.

# Actor input Schema

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

Job-board names (e.g. 'stripe'), names with a platform prefix (e.g. 'lever:palantir', 'ashby:ramp', 'greenhouse:airbnb'), or job-board URLs (e.g. https://jobs.lever.co/palantir). Without a prefix, Greenhouse, Lever, Ashby, Personio and Recruitee are tried in turn.

## `keyword` (type: `string`):

Only keep jobs whose title contains any of these words. Separate several with commas, e.g. 'engineer, data'. Case-insensitive.

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

Only keep jobs marked remote by the job board, or with 'remote' in the location.

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

Adds the full job description as clean plain text. Useful for AI agents and analysis.

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

Cap on jobs returned for each company (after filters). Leave empty for all.

## Actor input object example

```json
{
  "companies": [
    "stripe",
    "lever:palantir",
    "ashby:ramp"
  ],
  "remoteOnly": false,
  "includeDescription": false
}
```

# Actor output Schema

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

No description

## `summary` (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": [
        "stripe",
        "lever:palantir",
        "ashby:ramp"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("datasetworks/company-jobs").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": [
        "stripe",
        "lever:palantir",
        "ashby:ramp",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("datasetworks/company-jobs").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": [
    "stripe",
    "lever:palantir",
    "ashby:ramp"
  ]
}' |
apify call datasetworks/company-jobs --silent --output-dataset

```

## MCP server setup

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

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/pMAT9nPJvCbDznr5F/builds/XI0nRylt3sQXVEiUF/openapi.json
