# Job Scraper — Greenhouse, Ashby, Lever ATS Career Sites (`viridian_layout_ea2/company-career-site-jobs`) Actor

Scrape jobs from 3,584 company career sites via Greenhouse, Ashby and Lever. Reads their public JSON APIs instead of HTML, so it doesn't break. 125,000+ open roles, remote and keyword filters.

- **URL**: https://apify.com/viridian\_layout\_ea2/company-career-site-jobs.md
- **Developed by:** [Dave Hughes](https://apify.com/viridian_layout_ea2) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.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

## Job Scraper — Greenhouse, Ashby, Lever ATS Career Sites

Scrape open roles from **3,584 company career sites** running Greenhouse, Ashby,
or Lever.

Unlike other job scrapers, this one reads the **public JSON APIs** those
systems publish for syndication rather than parsing HTML — so it does not
break when a page changes.

### Why this one

Most job scrapers parse HTML from job boards. HTML changes, so they break — which
is why the category's ratings sit between 3.6 and 4.0 stars.

This reads **documented JSON APIs**. There is no markup to change, no anti-bot
arms race, and no proxy bill. When a company posts a role, it appears here.

- **Straight from the source** — the company's own board, not a third-party aggregator
- **One schema across three ATSs** — Greenhouse, Ashby, and Lever normalized identically
- **Curated registry included** — 3,584 verified companies, 125,000+ open roles, or name your own
- **You pay per job returned** — capped by `maxJobs`, and never charged past your budget

### Output

| Field | Description |
|---|---|
| `id` | Stable identifier: `{ats}:{company}:{nativeId}` |
| `title` | Role title |
| `company` / `companySlug` | Company |
| `location` | Location as published |
| `remote` | The location text itself says remote — precise |
| `remoteEligible` | The company's own ATS flag — broader, less precise (see note) |
| `department` | Team or department |
| `postedAt` | ISO 8601 posting date |
| `url` | Canonical apply link on the company's own board |
| `description` | Full description as plain text (optional) |
| `employmentType` | Full-time, contract, etc. where published |
| `ats` | Which system it came from |

### Examples

**Every remote engineering role across the curated list**

```json
{ "useCuratedList": true, "remoteOnly": true, "titleKeywords": ["engineer"], "maxJobs": 500 }
```

**Specific companies, recent postings only**

```json
{ "companies": [{ "slug": "stripe" }, { "slug": "ramp" }], "postedWithinDays": 14 }
```

**Fast and cheap — titles and links only**

```json
{ "useCuratedList": true, "includeDescription": false, "maxJobs": 2000 }
```

### A note on `remote`

Applicant tracking systems disagree about what "remote" means. Ashby flagged 112
of Ramp's 123 roles as remote while listing every one at "New York, NY (HQ)" —
that field means *remote-eligible*, not *remote*.

So we publish both signals rather than picking one and hiding the ambiguity:

- **`remote`** — the location text actually says remote. Trust this one.
- **`remoteEligible`** — what the company declared. Broader, noisier.

`remoteOnly` matches either. Filter on `remote` alone if you want only
genuinely location-independent roles.

### Notes

Slugs are usually just the company name in lowercase (`stripe`, `figma`, `ramp`).
Leave `ats` blank and we'll work out which system a company uses.

Companies that are unreachable or have no open roles are skipped — one bad
company never sinks a run.

# Actor input Schema

## `useCuratedList` (type: `boolean`):

Fetch every company in our verified registry (166+ companies, ~14,000 open roles). Turn this off if you want to name specific companies below.

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

Company job-board slugs, e.g. "stripe" or "ramp". Usually the company name in lowercase. Leave the ATS blank and we'll work out which system they use. Overrides the curated list.

## `maxJobs` (type: `integer`):

Hard cap on results. This is your main cost control — you are charged per job returned.

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

Only return roles that are remote or remote-eligible. Note: some ATSs (notably Ashby) flag most roles 'remote-eligible' while still listing an office location. Every record carries both `remote` (the location text actually says remote) and `remoteEligible` (the company's own flag), so you can filter more strictly yourself.

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

Only roles whose title contains one of these (case-insensitive). e.g. "engineer", "designer".

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

Only roles whose location contains one of these (case-insensitive). e.g. "London", "New York".

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

Only roles posted in the last N days. Roles with no posting date are kept.

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

Turn off for a much smaller, faster dataset when you only need titles, locations, and links.

## Actor input object example

```json
{
  "useCuratedList": true,
  "companies": [
    {
      "slug": "stripe"
    },
    {
      "slug": "ramp",
      "ats": "ashby"
    }
  ],
  "maxJobs": 1000,
  "remoteOnly": false,
  "titleKeywords": [],
  "locationKeywords": [],
  "includeDescription": true
}
```

# 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": [
        {
            "slug": "stripe"
        },
        {
            "slug": "ramp",
            "ats": "ashby"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("viridian_layout_ea2/company-career-site-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": [
        { "slug": "stripe" },
        {
            "slug": "ramp",
            "ats": "ashby",
        },
    ] }

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,viridian_layout_ea2/company-career-site-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/z8bXLsZLfOGquXA0U/builds/qlt6pBIuSA0b2EyjN/openapi.json