# Career Site Jobs API — Greenhouse, Ashby, Workday & 8 more (`careersignal/career-site-jobs-api`) Actor

Live job postings straight from company career sites across Greenhouse, Ashby, Lever, Workday, Workable and Personio. No login, no proxies, no failed runs.

- **URL**: https://apify.com/careersignal/career-site-jobs-api.md
- **Developed by:** [สรสิช นีลวัชระ](https://apify.com/careersignal) (community)
- **Categories:** Jobs, Lead generation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$4.00 / 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?

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

## Career Site Jobs API — Greenhouse, Ashby, Lever, Workday & 7 more

Job postings taken **straight from the company's own career site**, not from a job board
that copied them three days ago. One run gives you a clean, deduplicated feed across
**25,900 employers and 460,000+ open roles**, with a direct apply link on every row.

Covers Greenhouse, Ashby, Lever, Workday, Workable, SmartRecruiters, Personio,
Teamtailor, Recruitee, Breezy HR and BambooHR.

### What people use it for

- **Recruiting and sourcing** — see who is hiring for a role before it reaches the aggregators.
- **Sales prospecting** — a company posting five backend roles is a company with budget.
  Job counts are one of the cleanest buying signals there is.
- **Market and salary research** — track hiring volume by function, city or industry over time.
- **Building a job board** — a live feed with apply links, no scraping stack to maintain.
- **Competitor tracking** — watch a named list of companies and get told when they open a role.

### Sample output

```json
{
  "platform": "greenhouse",
  "company": "Stripe",
  "companyToken": "stripe",
  "title": "Machine Learning Engineer, Fraud",
  "location": "Dublin",
  "department": "Engineering",
  "employmentType": "Full-time",
  "remote": false,
  "postedAt": "2026-09-02T11:04:18Z",
  "url": "https://job-boards.greenhouse.io/stripe/jobs/8172487",
  "scrapedAt": "2026-09-10T06:41:02.551Z"
}
```

Export as JSON, CSV, Excel or XML, hit it from the API, or put it on a schedule so a
fresh feed lands every morning.

### Why runs do not fail

Every platform here publishes an **official, public JSON endpoint** for its job boards —
the same one the employer's own careers page calls. So there is no HTML parsing that
breaks when a site is restyled, no login, no proxies, and no rate-limit roulette.

Two things keep the failure rate at zero rather than merely low:

- **Dead boards are pruned before publishing.** Every company in the index is contacted
  and confirmed answering; the ones that have moved off the platform never cost you a
  request. Employers with nothing open today are kept but sorted last.
- **Each platform gets its own request budget.** Workable starts refusing at any real
  concurrency, so it is throttled separately and retried with backoff instead of being
  allowed to fail. Measured over a 1,000-job run: 125 career sites polled, 0 failures.

Measured on the live index:

| run | time | employers covered | failures |
|---|---|---|---|
| 100 jobs, no filter | 1.4 s | 10 | 0 |
| 1,000 jobs, no filter | 2.2 s | 100 | 0 |
| 500 jobs posted in the last 7 days | 1.9 s | 58 | 0 |
| 1,000 remote engineering roles | 38 s | 312 | 0 |

### Options

Every field is optional — run it with the defaults and you get jobs straight away.

| Option | What it does |
|---|---|
| `keywords` | Keep jobs whose title or department matches, e.g. `["engineer", "data"]` |
| `locations` | Keep jobs whose location matches, e.g. `["London", "Berlin"]` |
| `remoteOnly` | Keep only postings the employer flagged remote |
| `postedWithinDays` | Drop anything older, e.g. `7` for this week's openings |
| `excludeKeywords` | Drop titles containing these, e.g. `["intern"]` |
| `platforms` | Restrict to certain applicant tracking systems |
| `maxJobsPerCompany` | Spread results across employers instead of filling the run from the largest one |
| `companies` | Watch a named list instead of the whole index, e.g. `["stripe", "ashby:ramp"]` |
| `maxItems` | Stop after this many matching jobs — this is what you pay for |
| `maxCompanies` | Cap how many career sites to contact |

#### Watching a specific set of companies

```json
{
  "companies": ["stripe", "airbnb", "ashby:ramp"],
  "postedWithinDays": 7,
  "maxItems": 500
}
```

#### This week's remote engineering roles

```json
{
  "keywords": ["engineer", "developer"],
  "remoteOnly": true,
  "postedWithinDays": 7,
  "maxItems": 1000
}
```

### Pricing

Pay per job returned. You are charged for rows you actually receive — a run that
matches nothing costs nothing beyond the start event. Set `maxItems` to cap the spend.

### Notes

Only publicly listed job postings are returned, from endpoints the employers publish for
exactly this purpose. No personal data of any applicant is collected.

# Actor input Schema

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

Keep only jobs whose title or department contains one of these. Leave empty for every job.

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

Keep only jobs whose location contains one of these, e.g. "London", "Germany", "New York".

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

Keep only postings flagged remote by the employer, or with remote in the title/location.

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

Drop postings older than this. 0 keeps everything.

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

Drop jobs whose title contains any of these, e.g. "intern", "senior".

## `withDepartments` (type: `boolean`):

Greenhouse serves department names from a separate, roughly twice-as-slow endpoint. Off by default; turn it on if you filter or group by department.

## `platforms` (type: `array`):

Which career-site platforms to pull from.

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

Board tokens to target instead of the whole index, e.g. "stripe" or "greenhouse:stripe". Leave empty to search every indexed company.

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

The run stops as soon as this many matching jobs are found. This is what you are charged for.

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

Spread the results across employers instead of filling the whole run from the largest one. 0 means no limit.

## `maxPagesPerCompany` (type: `integer`):

Workday returns 20 jobs per request; this caps how deep to page into a single enterprise career site.

## `maxCompanies` (type: `integer`):

Safety cap on how many career sites to contact. 0 means no cap.

## Actor input object example

```json
{
  "keywords": [
    "engineer"
  ],
  "locations": [],
  "remoteOnly": false,
  "postedWithinDays": 0,
  "excludeKeywords": [],
  "withDepartments": false,
  "platforms": [
    "greenhouse",
    "ashby",
    "lever",
    "workable",
    "recruitee",
    "smartrecruiters",
    "personio",
    "teamtailor",
    "workday",
    "breezy",
    "bamboohr"
  ],
  "companies": [],
  "maxItems": 100,
  "maxJobsPerCompany": 10,
  "maxPagesPerCompany": 5,
  "maxCompanies": 0
}
```

# Actor output Schema

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

Every posting the run matched, one row each, with a direct link to the real application page.

## `runStats` (type: `string`):

How many career sites were contacted, how many answered, and how many postings were seen.

# 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"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("careersignal/career-site-jobs-api").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"] }

# Run the Actor and wait for it to finish
run = client.actor("careersignal/career-site-jobs-api").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"
  ]
}' |
apify call careersignal/career-site-jobs-api --silent --output-dataset

```

## MCP server setup

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

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/ejdfLPVE3uldTDfkS/builds/TbIks4MHY33wmq2h3/openapi.json