# Company Jobs Scraper: Greenhouse, Lever, Ashby, Workday (`brightgro/any-ats-jobs`) Actor

Company names or career page URLs in, open jobs out. Finds each company's Greenhouse, Lever or Ashby board by name, reads Workday by URL, and returns every job in one shape: title, location, remote, department, dates, salary where published, link and description.

- **URL**: https://apify.com/brightgro/any-ats-jobs.md
- **Developed by:** [Brightgro LLC](https://apify.com/brightgro) (community)
- **Categories:** Jobs, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 jobs

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

## Company Jobs Scraper: Greenhouse, Lever, Ashby, Workday

Give a list of company names and get each company's open jobs, without first working out which applicant tracking system it uses. The actor looks the name up on Greenhouse, Lever and Ashby, picks the board with the most open jobs, and returns every job in one format. Workday career sites work by URL. The data comes from each system's public job board API, so a run does not depend on page layouts.

### Why use it

- One input for four job board systems: names like `figma`, `notion` or `Linear Inc`, or any Greenhouse, Lever, Ashby or Workday career page URL.
- One output shape across all four, so a sales list or a job feed needs no per-system cleanup.
- Salary where the company publishes it (Lever and Ashby).
- You pay only for jobs returned. A name with no board, a bad line or a duplicate gets a free row that says why.

### Input

- Companies: company names or career page URLs, up to 300. A name is tried as written without spaces (`Linear Inc` becomes `linearinc`), with hyphens (`linear-inc`), and without a trailing word such as Inc, Labs or AI (`linear`). Workday needs the career site URL, for example `https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite`.
- Jobs per company: the most jobs to return for each company, newest first. The default is 1,000.
- Title keyword: only jobs whose title contains this text.
- Location: only jobs whose location contains this text, for example `London` or `remote`.
- Remote only: only jobs marked remote.
- Posted within days: only jobs published in the last N days. Use it to watch for new roles on a schedule.
- Include description: add the description as plain text (on by default).

### Output

One row per job:

| Field | What it holds |
|---|---|
| status | `ok` for a job |
| input | The line you gave |
| ats, board | The system found (`greenhouse`, `lever`, `ashby` or `workday`) and the board name |
| boards_also_found | Other boards found for the same name, which you can give as URLs in another run |
| company, job_id, title | The company, the job's id and its title |
| location, all_locations, remote | The main location, every location listed, and whether the job is remote |
| department, employment_type | As the company set them |
| published_at | When the job was published (Workday gives the day only) |
| salary_min, salary_max, salary_currency, salary_interval | Salary where the company publishes it |
| url, apply_url | The job page and the application page |
| description | The description as plain text |

A line that is not a name or a career page URL, a name with no public board, a board with no job that matches the filters, and a second line for the same board each get one row with `status` set to `invalid_input`, `board_not_found`, `no_matching_jobs` or `duplicate` and a message. Those rows are free. A Workday site whose robots.txt disallows reading is skipped with a free `robots_disallowed` row.

### Price

$0.002 for each job returned. There is no start fee.

### Limits

- A name finds a board only when the company's board name matches it. If a name returns `board_not_found`, give the career page URL instead.
- Workday is read by URL only, because a Workday address cannot be guessed from a name. On Workday the title keyword is also sent to the site's own search, so large employers are searched in full.
- Lever asks for one request a second, so names are checked on Lever one at a time.

# Actor input Schema

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

Company names (for example Figma or Notion) or career page URLs on Greenhouse, Lever, Ashby or Workday, up to 300. Workday needs the career site URL.

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

The most jobs to return for each company, newest first.

## `titleKeyword` (type: `string`):

Return only jobs whose title contains this text, for example engineer. Not case sensitive.

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

Return only jobs whose location contains this text, for example London or remote.

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

Return only jobs marked remote.

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

Return only jobs published in this many days. Leave empty for every open job.

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

Add the full job description as plain text. Workday descriptions need one extra request per job.

## Actor input object example

```json
{
  "companies": [
    "figma",
    "notion"
  ],
  "maxJobsPerCompany": 5,
  "remoteOnly": false,
  "includeDescription": true
}
```

# Actor output Schema

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

Company names or career page URLs in, open jobs out. Finds each company's Greenhouse, Lever or Ashby board by name, reads Workday by URL, and returns every job in one shape: title, location, remote, department, dates, salary where published, link and 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": [
        "figma",
        "notion"
    ],
    "maxJobsPerCompany": 5
};

// Run the Actor and wait for it to finish
const run = await client.actor("brightgro/any-ats-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": [
        "figma",
        "notion",
    ],
    "maxJobsPerCompany": 5,
}

# Run the Actor and wait for it to finish
run = client.actor("brightgro/any-ats-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": [
    "figma",
    "notion"
  ],
  "maxJobsPerCompany": 5
}' |
apify call brightgro/any-ats-jobs --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,brightgro/any-ats-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/mLWpBdWH0hWSTjcSb/builds/c5gjBykW1ATlVGf4A/openapi.json