# ATS Jobs Search: Greenhouse, Lever, Ashby & Workday Jobs (`agents001/ats-jobs-search`) Actor

Returns open jobs from thousands of company career sites on Greenhouse, Lever, Ashby and Workday, searched by keyword, location, remote and posted date with no company list needed. Each job has full description, salary where published, department, locations and apply link.

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

## Pricing

from $1.00 / 1,000 job results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 Jobs Search: Greenhouse, Lever, Ashby & Workday Jobs

**Returns open jobs from 12,500+ company career sites on Greenhouse, Lever, Ashby and Workday**, searched by keyword, location, remote and posting date, with no company list to supply. Each job comes with the full description as plain text, salary where the employer publishes it, department, team, locations, country, workplace type, employment type, posted date, job page and apply link.

- **Search every company at once.** A built-in directory of 12,500+ live job boards (4,500 Greenhouse, 1,200 Lever, 2,900 Ashby and 3,800 Workday career sites) holds over 450,000 open jobs. Type "data analyst" and "Germany" and get matching jobs from all of them in seconds.
- **Full job descriptions** read live from each company's own board, which also confirms the job is still open. Email addresses and phone numbers are removed.
- **Salary ranges** where published: min, max, currency and period (Greenhouse pay transparency ranges, Lever salary ranges, Ashby compensation).
- **One clean record shape** for all four systems, so Greenhouse jobs, Lever jobs, Ashby jobs and Workday jobs sit in one table.
- **Daily new-jobs feed.** Turn on "Only jobs not seen in previous runs" and schedule it: each run returns only jobs it has not returned before.
- **No login, no API key, no proxies to configure.**

### What you get

One record per job:

```json
{
  "title": "Senior Backend Engineer",
  "company": "Ramp",
  "ats": "ashby",
  "department": "Engineering",
  "team": "Backend",
  "location": "New York, NY (HQ)",
  "locations": ["New York, NY (HQ)", "Remote (US)"],
  "country": "United States",
  "countries": ["United States"],
  "remote": false,
  "workplaceType": "hybrid",
  "employmentType": "full-time",
  "postedAt": "2026-11-07T15:02:11Z",
  "salaryMin": 211400,
  "salaryMax": 290600,
  "salaryCurrency": "USD",
  "salaryInterval": "year",
  "salaryText": "USD 211,400 - 290,600 per year",
  "jobUrl": "https://jobs.ashbyhq.com/ramp/...",
  "applyUrl": "https://jobs.ashbyhq.com/ramp/.../application",
  "description": "About Ramp\n\nRamp is the financial operations platform...",
  "descriptionHtml": null,
  "isNew": true,
  "jobId": "34413f8d-26bf-4bbc-8ade-eb309a0e2245",
  "companyKey": "ashby:ramp",
  "boardToken": "ramp",
  "source": "api.ashbyhq.com",
  "indexedAt": "2026-11-08T03:41:00Z",
  "scrapedAt": "2026-11-08T10:07:56Z"
}
```

Fields a board does not publish are `null`. Company data only: there are no recruiter or hiring manager fields.

### Who uses it

- **Job boards and aggregators:** a steady feed of fresh jobs with full descriptions and apply links, straight from company career sites.
- **Recruiters and sourcers:** see which companies are hiring for a role, where, and at what pay.
- **Sales and market intelligence:** hiring signals by department, country and company.
- **Job seekers and career coaches:** a daily list of new roles that match a title, a place and remote preferences.
- **Salary research:** published pay bands by role, company and country.

### Input examples

**Remote product managers posted in the last 3 days**

```json
{ "keywords": ["product manager"], "remote": "remoteOnly", "postedWithinDays": 3, "maxItems": 200 }
```

**Data jobs in Germany or the Netherlands, skills matched in the description**

```json
{ "keywords": ["data engineer", "snowflake"], "searchDescription": true, "locations": ["Germany", "Netherlands"] }
```

**Daily feed of new sales jobs in London (schedule once a day)**

```json
{ "keywords": ["account executive", "sales"], "locations": ["London"], "onlyNew": true, "postedWithinDays": 7 }
```

**Every open engineering job at named companies**

```json
{ "companies": ["Stripe", "greenhouse:figma", "https://jobs.ashbyhq.com/openai", "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"], "departments": ["engineering"], "maxItems": 1000 }
```

### Input

| Field | What it does |
|---|---|
| Job title keywords | A job matches when its title matches any entry. All words of an entry must start a word of the title, in any order. Empty returns every job. |
| Also match keywords in the description | Adds jobs whose description contains all words of an entry (skills such as SQL or Kubernetes). Up to 3,000 extra jobs are checked per run. |
| Locations | Countries, states or cities. Country names also match city-only locations ("Austin, TX" counts as United States). "Remote" matches remote jobs. |
| Remote jobs | All jobs, remote only, or exclude remote. |
| Posted within (days) | Only jobs first published in the last N days. |
| Job board systems | Any of Greenhouse, Lever, Ashby, Workday. Empty means all. |
| Departments or teams | Words matched against the department and team. |
| Employment types | Full-time, part-time, contract, temporary, internship. |
| Exclude title keywords | Leave out titles such as senior, manager or intern. |
| Only these companies | Optional. Company names, `greenhouse:board`, `lever:site`, `ashby:name` or job board links. Boards named with a system or a link are read live even if the directory does not hold them. |
| Maximum jobs | Default 100, up to 50,000 per run. Newest jobs come first. |
| Maximum jobs per company | Stops one large employer filling the run. |
| Only jobs not seen in previous runs | New-jobs mode for scheduled runs. Each different input keeps its own memory. |
| Include full description | On by default. Turn off for a faster, lighter list. |
| Include description HTML | Adds `descriptionHtml` as well as the plain text. |

### How fresh is it?

The search runs against a job index that lists every open job on every board in the directory. It is rebuilt every day from each vendor's official public job board endpoint. With descriptions on, each description is read live from the company's board at run time, so a job that closed since the last rebuild is dropped and never charged. Workday career sites contribute their newest 100 jobs each. The board directory itself is refreshed every month. The run summary (key-value store record `RUN_SUMMARY`) shows when the index was built.

### Pricing

Pay per event, with platform usage included: you pay only for jobs saved to your dataset.

| Event | Price per 1,000 |
|---|---|
| `job-result` (one job saved to the dataset) | $1.00 on every plan (launch price) |

A first run with the prefilled input (50 jobs) costs about $0.13. Jobs that closed since indexing, duplicates and errors are free. Set a maximum charge per run in the run options to cap spend.

### Speed

The prefilled search (engineer jobs from the last 7 days, 50 jobs with descriptions) finishes in a few seconds. Large exports of thousands of jobs with descriptions take longer because each description is read from the company's own board at a polite rate.

### Data sources and terms

All data comes from public job board endpoints that each vendor documents for showing job listings on careers sites:

- **Greenhouse Job Board API**: "Job Board data is publicly available, so authentication is not required for any GET endpoints." https://developers.greenhouse.io/job-board.html
- **Lever Postings API**: "This API is designed to help you create a job site." https://github.com/lever/postings-api. The Actor keeps to the one request per second that api.lever.co asks for in its robots.txt.
- **Ashby Job Postings API**: "This API allows you to get data for all currently published Job Postings for your organization." https://developers.ashbyhq.com/docs/public-job-posting-api. Descriptions are also read from public Ashby job pages, which robots.txt allows.
- **Workday career sites**: the same public JSON the career site's own search page uses. Sites whose robots.txt disallows them are left out of the directory.
- **Board directory**: board names found in the Common Crawl URL index (https://commoncrawl.org/terms-of-use), each checked against the vendor's live API.

Only published job postings are read. Nothing behind a login is accessed, and no application forms are submitted.

This Actor is not affiliated with Greenhouse, Lever, Ashby, Workday or Common Crawl.

### Tips

- Combine title keywords with a location and `postedWithinDays` for the fastest, most relevant results.
- For a daily feed, schedule the Actor with `onlyNew` on and the same input every day.
- Looking for a company that is missing? Add it under "Only these companies" as `greenhouse:board`, `lever:site`, `ashby:name` or a Workday link and it is read live.

# Actor input Schema

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

A job matches when its title matches ANY entry. All words of one entry must appear, in any order, at the start of a word: "engineer" also finds "Engineering Manager" and "data analyst" finds "Analyst, Data". Leave empty for every job.

## `searchDescription` (type: `boolean`):

Also return jobs whose description contains all words of a keyword entry, for skills such as SQL or Kubernetes. Title matches come first. Up to 3,000 extra jobs are checked per run, so this is slower.

## `locations` (type: `array`):

Countries, states or cities, for example United States, Germany, London, California or Remote. A job matches when any of its locations matches any entry. Country names also match city-only locations such as "San Francisco, CA".

## `remote` (type: `string`):

Keep all jobs, only remote jobs, or only jobs that are not remote. Hybrid jobs count as not remote.

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

Only jobs first published in the last N days. Jobs without a posting date are left out when this is set. Empty or 0 means any age.

## `ats` (type: `array`):

Search only these applicant tracking systems. Empty means all four.

## `departments` (type: `array`):

Only jobs whose department or team contains any of these words, for example Engineering, Sales, Finance. Workday jobs carry no department, so they drop out when this is set.

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

Only these employment types. Jobs that do not state a type (most Greenhouse boards) drop out when this is set.

## `excludeKeywords` (type: `array`):

Leave out jobs whose title matches any of these, for example senior, manager, intern.

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

Leave empty to search every company. Otherwise company names (Stripe), board names with the system (greenhouse:stripe, lever:palantir, ashby:ramp) or job board links (https://jobs.ashbyhq.com/openai, https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite). Boards named with a system or link are read live even when they are not in the built-in directory.

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

Stop after this many jobs (newest first). 0 means up to 50,000.

## `maxItemsPerCompany` (type: `integer`):

Cap per company, so one large employer does not fill the whole run. 0 means no cap.

## `onlyNew` (type: `boolean`):

Remembers the jobs this search returned before and outputs only new ones. Schedule it daily for a new-jobs feed. Each different input keeps its own memory.

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

Adds the full job description as plain text, read live from the company's own board (email addresses and phone numbers are removed). It also confirms the job is still open and adds Greenhouse pay ranges. Turn off for a faster list.

## `includeDescriptionHtml` (type: `boolean`):

Also add the description as HTML (descriptionHtml). Needs 'Include full description'.

## `stateStoreName` (type: `string`):

Only used when 'Only jobs not seen in previous runs' is on. Name of the key-value store in your account that keeps the list of jobs already returned. Each different input gets its own record inside it. If a run reports that it cannot open the store, enter a different name here.

## Actor input object example

```json
{
  "keywords": [
    "engineer"
  ],
  "searchDescription": false,
  "locations": [],
  "remote": "any",
  "postedWithinDays": 7,
  "maxItems": 50,
  "maxItemsPerCompany": 5,
  "onlyNew": false,
  "includeDescription": true,
  "includeDescriptionHtml": false,
  "stateStoreName": "agents001-ats-jobs-search-state"
}
```

# Actor output Schema

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

No description

## `descriptions` (type: `string`):

No description

## `runSummary` (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 = {
    "keywords": [
        "engineer"
    ],
    "locations": [],
    "postedWithinDays": 7,
    "maxItems": 50,
    "maxItemsPerCompany": 5
};

// Run the Actor and wait for it to finish
const run = await client.actor("agents001/ats-jobs-search").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 = {
    "keywords": ["engineer"],
    "locations": [],
    "postedWithinDays": 7,
    "maxItems": 50,
    "maxItemsPerCompany": 5,
}

# Run the Actor and wait for it to finish
run = client.actor("agents001/ats-jobs-search").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 '{
  "keywords": [
    "engineer"
  ],
  "locations": [],
  "postedWithinDays": 7,
  "maxItems": 50,
  "maxItemsPerCompany": 5
}' |
apify call agents001/ats-jobs-search --silent --output-dataset

```

## MCP server setup

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

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/4hOEeqBQPa0dleByV/builds/SwTmrJcICHJVe7lBq/openapi.json
