# ATS Careers Scraper: Greenhouse, Lever, Ashby (`talcoe/ats-careers-multi`) Actor

Pull every open role, with location, department, employment type and description, from any public Greenhouse, Lever, Ashby, Workable or SmartRecruiters careers page. Filter by keyword, location or department. Priced per result.

- **URL**: https://apify.com/talcoe/ats-careers-multi.md
- **Developed by:** [M Usama](https://apify.com/talcoe) (community)
- **Categories:** Jobs
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.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

### What does ATS Careers Scraper: Greenhouse, Lever, Ashby, Workable & SmartRecruiters do?

Give it a company's public career page URL and it returns every open role posted there: title, company, location, department, employment type, remote flag, posted date, apply link and a plain text description. It reads the same public JSON APIs that power Greenhouse, Lever, Ashby, Workable and SmartRecruiters career pages, so results are current as of the run. Filters for keyword, location and department keep runs small, and you only pay for the results you keep.

### Data source

The Actor calls the public JSON API behind each career page (for example `boards-api.greenhouse.io` for Greenhouse, `api.lever.co` for Lever) rather than parsing HTML, so data is live and as current as the company's own careers page.

### Why use it?

- Lead generation and recruiting: pull open roles across many companies to spot who is hiring and for what.
- Market and hiring research: track headcount growth, new departments or new office locations by role postings.
- Sales signals: new engineering or GTM roles often precede a buying window.
- Job board or newsletter content: republish current openings without maintaining scrapers for five different ATS platforms yourself.

### How to use it

1. Open the Actor and paste one or more company career page URLs (Greenhouse, Lever, Ashby, Workable or SmartRecruiters), then set optional filters.
2. Click Start. Download results as JSON, CSV or Excel, or read them through the API.
3. Add a Schedule and an Integration (Slack, Google Sheets, webhook) to get new postings automatically.

### Input

| Field | Description |
|---|---|
| `startUrls` | Public company career page URLs. The ATS is detected automatically from the URL. |
| `keywords` | Comma separated keywords to match in the job title or description. Leave empty to keep every role. |
| `location` | Only keep roles whose location text contains this, for example Remote or New York. |
| `department` | Only keep roles whose department or team contains this, for example Engineering. |
| `maxResults` | Hard stop for the run. You are billed per result, so this caps the cost. |
| `proxyConfiguration` | Apify proxy is recommended for larger runs. |

Example input:

```json
{
    "startUrls": [
        { "url": "https://job-boards.greenhouse.io/gitlab" },
        { "url": "https://jobs.lever.co/angellist" },
        { "url": "https://jobs.ashbyhq.com/linear" },
        { "url": "https://apply.workable.com/zyte" },
        { "url": "https://jobs.smartrecruiters.com/Equinox" }
    ],
    "keywords": "",
    "location": "",
    "department": "",
    "maxResults": 60
}
```

### Output

Every record has the same shape regardless of the source ATS:

```json
{
    "id": "greenhouse:gitlab:8556658002",
    "title": "AI Engineer",
    "company": "GitLab",
    "location": "Remote, Bangalore",
    "department": "Enterprise Applications",
    "employmentType": null,
    "remote": true,
    "postedAt": "2026-09-14T20:01:39.000Z",
    "url": "https://job-boards.greenhouse.io/gitlab/jobs/8556658002",
    "description": "GitLab is the intelligent orchestration platform for DevSecOps...",
    "source": "greenhouse",
    "sourceUrl": "https://job-boards.greenhouse.io/gitlab",
    "scrapedAt": "2026-09-29T09:26:09.167Z"
}
```

| Field | Meaning |
|---|---|
| `id` | Stable key (`source:company:nativeId`), safe for deduplication between runs |
| `title` | Job title |
| `company` | Company name as published by the ATS |
| `location` | Location text as published, or null if not given |
| `department` | Department or team, when the ATS publishes one |
| `employmentType` | Full time, part time, contract, etc, when the ATS publishes one |
| `remote` | true, false or null when the source does not say |
| `postedAt` | ISO date the role was posted, when available |
| `url` | Public apply or posting page |
| `description` | Plain text job description, HTML stripped |
| `source` | Which ATS the role came from: greenhouse, lever, ashby, workable or smartrecruiters |
| `sourceUrl` | The career page URL you supplied that produced this record |
| `scrapedAt` | When this Actor run fetched the record |

### Pricing

Pay per event: a small fee when a run starts, then a fixed price per result returned. You only pay for records that pass your filters. Set `maxResults` to cap any run.

### Limitations

- Workday career pages are not supported. Workday's public job API intermittently rejects automated requests with a generic error even without any login wall, so results from it would not be reliable.
- Only fields the source ATS actually publishes are filled in; some boards omit department or employment type.
- SmartRecruiters results are read from the first 100 postings per company page; very large boards beyond that are not paginated further in a single run.

### FAQ

**Is this legal?** The Actor reads listings the company publishes for any visitor without a login and stores only the job posting information published for that purpose. You are responsible for how you use the data.

**Something is missing or broken?** Open an issue in the Issues tab; response time is usually under a day.

# Actor input Schema

## `startUrls` (type: `array`):

Public company career page URLs. Detected automatically: Greenhouse, Lever, Ashby, Workable or SmartRecruiters.

## `keywords` (type: `string`):

Comma separated keywords to match in the job title or description. Leave empty to keep every role.

## `location` (type: `string`):

Only keep roles whose location text contains this, for example Remote or New York. Leave empty to keep every location.

## `department` (type: `string`):

Only keep roles whose department or team contains this, for example Engineering. Leave empty to keep every department.

## `maxResults` (type: `integer`):

Hard stop for the run. You are billed per result, so this caps the cost.

## `proxyConfiguration` (type: `object`):

Apify proxy is recommended for larger runs.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://job-boards.greenhouse.io/gitlab"
    },
    {
      "url": "https://jobs.lever.co/angellist"
    },
    {
      "url": "https://jobs.ashbyhq.com/linear"
    },
    {
      "url": "https://apply.workable.com/zyte"
    },
    {
      "url": "https://jobs.smartrecruiters.com/Equinox"
    }
  ],
  "keywords": "",
  "location": "",
  "department": "",
  "maxResults": 60,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# 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 = {
    "startUrls": [
        {
            "url": "https://job-boards.greenhouse.io/gitlab"
        },
        {
            "url": "https://jobs.lever.co/angellist"
        },
        {
            "url": "https://jobs.ashbyhq.com/linear"
        },
        {
            "url": "https://apply.workable.com/zyte"
        },
        {
            "url": "https://jobs.smartrecruiters.com/Equinox"
        }
    ],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("talcoe/ats-careers-multi").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 = {
    "startUrls": [
        { "url": "https://job-boards.greenhouse.io/gitlab" },
        { "url": "https://jobs.lever.co/angellist" },
        { "url": "https://jobs.ashbyhq.com/linear" },
        { "url": "https://apply.workable.com/zyte" },
        { "url": "https://jobs.smartrecruiters.com/Equinox" },
    ],
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("talcoe/ats-careers-multi").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 '{
  "startUrls": [
    {
      "url": "https://job-boards.greenhouse.io/gitlab"
    },
    {
      "url": "https://jobs.lever.co/angellist"
    },
    {
      "url": "https://jobs.ashbyhq.com/linear"
    },
    {
      "url": "https://apply.workable.com/zyte"
    },
    {
      "url": "https://jobs.smartrecruiters.com/Equinox"
    }
  ],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call talcoe/ats-careers-multi --silent --output-dataset

```

## MCP server setup

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

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/mgj58yWeKTNNJhTk8/builds/DycC7iw8sqF7VV3f4/openapi.json