# 🚀 Ashby Job Scraper: Startup Jobs with Compensation (`findata/ashby-job-scraper`) Actor

Scrape every open job from any Ashby board, the ATS behind many startups and AI companies. Title, team, location, remote flag, compensation range, published date, description and apply link as clean JSON. Only-new mode. No login, no proxies.

- **URL**: https://apify.com/findata/ashby-job-scraper.md
- **Developed by:** [Fin Data](https://apify.com/findata) (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 $2.10 / 1,000 job records

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

## Ashby Job Scraper

Every open job from any Ashby job board, as clean JSON. Paste a `jobs.ashbyhq.com` URL or just the board name and get title, department, team, location, remote flag, employment type, structured compensation range, published date, the full description and the apply link for every posting.

Built for recruiters sourcing from startups and AI companies (Ashby is the ATS behind many of them), sales teams that use hiring as a buying signal, job boards that need a direct feed, and AI agents that need job data in one shape.

### Why a dedicated Ashby scraper

Ashby publishes a public job-board API with the richest data of any ATS: a real remote flag, an employment type, and structured compensation tiers. This actor does the part that takes a day to get right:

- One request per board returns every listed job with its full description and compensation; no per-job calls.
- Compensation tiers are reduced to one `salaryMin` / `salaryMax` / `salaryCurrency` / `salaryPeriod` set (the salary component of the first tier), with the full tier list kept under `extra` for anyone who wants equity and bonus components.
- Secondary locations are flattened into `locations`, and Ashby's `isRemote` becomes the same `remote` flag every other FinData job scraper uses.
- Only-new mode, filters that run before billing, and a fail-soft run that finishes even when one board has been renamed or closed.

### Finding an Ashby board

Open the company's careers page and click any job. If the address bar shows `ashbyhq.com`, the first path segment is the board name. Any of these work as a source:

| Shape | Example |
| --- | --- |
| Board URL | https://jobs.ashbyhq.com/notion |
| A job page | https://jobs.ashbyhq.com/openai/2b7e5c1d-... |
| Just the board name | ramp |

Companies that embed Ashby on their own domain still have a board name; it is in the apply link (`jobs.ashbyhq.com/{board}/{id}/application`).

### Input

```json
{
  "sources": ["notion", "https://jobs.ashbyhq.com/openai"],
  "keywords": ["product manager", "designer"],
  "remoteOnly": true,
  "postedWithinDays": 7,
  "onlyNew": true
}
```

| Field | Type | Default | What it does |
| --- | --- | --- | --- |
| preset | string | custom | Employer list: `custom` (default), `sample`. `custom` runs the sites you list and falls back to the sample boards when the list is empty |
| sources | string\[] | \[] | Ashby board URLs or board names |
| keywords | string\[] | \[] | Keep jobs whose title contains any of these (case-insensitive) |
| excludeKeywords | string\[] | \[] | Drop jobs whose title contains any of these |
| locations | string\[] | \[] | Keep jobs whose location text contains any of these |
| departments | string\[] | \[] | Keep jobs whose department or team contains any of these |
| remoteOnly | boolean | false | Keep only jobs Ashby flags as remote |
| postedWithinDays | integer | 0 | Keep only jobs published in the last N days; 0 disables |
| includeDescriptionHtml | boolean | false | Add the original HTML description next to the plain text |
| onlyNew | boolean | false | Output only jobs not seen on a previous run of this board |
| seenStoreName | string | ashby-job-scraper-seen | Key-value store that remembers seen job IDs; use one name per monitor |
| maxJobsPerSource | integer | 0 | Stop after N jobs per board; 0 means the whole board |
| maxConcurrency | integer | 5 | Boards pulled in parallel |

Descriptions and compensation come with the list call, so there is no "fetch details" switch.

### Output

One record per job.

```json
{
  "vendor": "ashby",
  "source": "https://jobs.ashbyhq.com/notion",
  "company": "notion",
  "jobId": "2b7e5c1d-8a3f-4d60-b1c9-7e4a2f9d0c55",
  "title": "Product Manager, Growth",
  "department": "Product",
  "team": "Growth",
  "location": "San Francisco, CA",
  "locations": ["San Francisco, CA", "New York, NY"],
  "country": "US",
  "remote": false,
  "employmentType": "Full time",
  "postedAt": "2026-10-30T18:21:07.000Z",
  "updatedAt": "2026-10-30T18:21:07.000Z",
  "url": "https://jobs.ashbyhq.com/notion/2b7e5c1d-8a3f-4d60-b1c9-7e4a2f9d0c55",
  "applyUrl": "https://jobs.ashbyhq.com/notion/2b7e5c1d-8a3f-4d60-b1c9-7e4a2f9d0c55/application",
  "descriptionText": "About Us...",
  "salaryMin": 180000,
  "salaryMax": 240000,
  "salaryCurrency": "USD",
  "salaryPeriod": "year",
  "salaryText": "$180K - $240K",
  "extra": { "compensationTiers": [ { "title": "SF / NYC", "components": [ { "compensationType": "Salary", "minValue": 180000, "maxValue": 240000, "currencyCode": "USD", "interval": "1 YEAR" } ] } ] },
  "scrapedAt": "2026-11-05T01:47:38.912Z"
}
```

| Field | Meaning |
| --- | --- |
| company | The Ashby board name (Ashby's public API does not carry a display name) |
| jobId | Ashby job UUID. Stable; use it as the key |
| department, team | Ashby's department and team |
| location, locations | Ashby's primary location, then every secondary location |
| country | From the job's postal address when Ashby provides one |
| remote | Ashby's `isRemote` flag; false jobs whose location says remote are still true |
| employmentType | Ashby employment type, humanized (Full time, Part time, Contract, Intern) |
| postedAt, updatedAt | Ashby `publishedAt`, ISO 8601 |
| salaryMin, salaryMax, salaryCurrency, salaryPeriod, salaryText | The salary component of the first compensation tier when published; otherwise null |
| extra.compensationTiers | Every compensation tier and component Ashby returns, including equity and bonus |

A `RUN_SUMMARY` record in the default key-value store reports boards processed, jobs fetched, filtered, de-duplicated, skipped as already seen, and any board failures with the error text.

### Pricing

Pay per event. You are charged per job record written to the dataset, plus a small actor-start event. Filtered-out jobs and already-seen jobs in only-new mode are not charged. One request per board and no proxies, so platform usage is a fraction of a cent per run.

### Monitoring new postings

1. Set `onlyNew` to true and give `seenStoreName` a name for this monitor.
2. Add your filters.
3. Schedule the actor (daily, or hourly for boards you care about).
4. Connect the dataset to Google Sheets, Slack, Make, Zapier or a webhook from the Integrations tab.

The first run outputs everything on the boards and remembers it. Each later run outputs only what is new.

### Limits and notes

- Public job-board API only. No login, no proxies, no candidate or private data.
- Unlisted jobs (`isListed: false`) are skipped, matching what the public board shows.
- Boards that are closed or renamed return an error for that board only; the run continues.
- This actor reads Ashby boards only. For Workday, Greenhouse, Lever or SmartRecruiters, or for a mixed list where you do not know the ATS, use the FinData Career Site Job Scraper.

### Related FinData job scrapers

Same engine, same output fields, so records from any of them can be combined.

- [Workday Job Scraper](https://apify.com/findata/workday-job-scraper)
- [Greenhouse Job Scraper](https://apify.com/findata/greenhouse-job-scraper)
- [Lever Job Scraper](https://apify.com/findata/lever-job-scraper)
- [Career Site Job Scraper (any company, ATS auto-detected)](https://apify.com/findata/career-site-job-scraper)
- [Workday, Greenhouse, Lever, Ashby, SmartRecruiters Job Scraper (all five in one actor)](https://apify.com/findata/ats-jobs-feed)

### For AI agents

Every field is optional: an empty input `{}` runs the sample boards and returns jobs, so a first call never fails. Pick `"preset": "sample"` to say so explicitly. Minimal call: `{ "sources": ["notion"] }`. Add `"keywords"` and `"locations"` arrays to narrow, `"remoteOnly": true` for remote roles. Every record has the same fields and includes the description and compensation; `jobId` is the stable key.

### Using it from code

```js
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('findata/ashby-job-scraper').call({
    sources: ['notion', 'openai'],
    keywords: ['engineer'],
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
```

Works the same through the Apify API, MCP server and the Python client.

# Actor input Schema

## `preset` (type: `string`):

Pick a ready-made list or use your own. "The career sites I list below" runs exactly the sites in the next field, and if that field is empty it falls back to the sample boards so a run never fails for lack of input. The other choices add a curated list on top of anything you paste.

## `sources` (type: `array`):

Ashby job-board URLs or board names, one per line. The board name is the last part of the URL: for https://jobs.ashbyhq.com/notion it is notion. Examples: https://jobs.ashbyhq.com/notion, https://jobs.ashbyhq.com/openai, or just ramp. Optional when an Employer list is chosen above.

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

Keep jobs whose title contains at least one of these words or phrases. Case-insensitive. Leave empty to keep all.

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

Drop jobs whose title contains any of these words or phrases. Case-insensitive.

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

Keep jobs whose location text contains at least one of these, e.g. Atlanta, Georgia, GA, United States. Case-insensitive. Leave empty to keep all. With the Georgia and upstate SC list chosen and this left empty, the list's own Georgia and South Carolina locations are used.

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

Keep jobs whose department or team contains at least one of these, e.g. Finance, Engineering, People.

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

Keep only jobs the ATS marks as remote or whose location says remote.

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

Keep only jobs posted or updated within this many days. 0 means no limit. Workday list pages only give relative dates, so this is applied to the parsed value.

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

Add the raw HTML description to each record alongside the plain text. Makes datasets larger.

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

Remember every job ID seen per source in a named key-value store and output only jobs not seen before. Use with a schedule to get a feed of new postings. You are charged only for jobs that are output.

## `seenStoreName` (type: `string`):

Name of the key-value store used by only-new mode. Use a different name per monitor if you run several configurations.

## `maxJobsPerSource` (type: `integer`):

Stop paging a source after this many jobs. 0 means no limit. Workday boards cap at 2,000 per query; the actor splits large boards by facet automatically so you still get the whole board.

## `maxConcurrency` (type: `integer`):

How many career sites to pull at the same time.

## Actor input object example

```json
{
  "preset": "custom",
  "sources": [
    "https://jobs.ashbyhq.com/notion",
    "https://jobs.ashbyhq.com/openai",
    "https://jobs.ashbyhq.com/ramp",
    "https://jobs.ashbyhq.com/linear",
    "https://jobs.ashbyhq.com/elevenlabs"
  ],
  "keywords": [],
  "excludeKeywords": [],
  "locations": [],
  "departments": [],
  "remoteOnly": false,
  "postedWithinDays": 0,
  "includeDescriptionHtml": false,
  "onlyNew": false,
  "seenStoreName": "ashby-job-scraper-seen",
  "maxJobsPerSource": 0,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

One record per job posting, normalized across Workday, Greenhouse, Lever, Ashby and SmartRecruiters.

## `jobsTable` (type: `string`):

Same records in the Console table view.

## `runSummary` (type: `string`):

Sources processed, jobs fetched, filtered, de-duplicated, already seen, and any source failures.

# 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 = {
    "sources": [
        "https://jobs.ashbyhq.com/notion",
        "https://jobs.ashbyhq.com/openai",
        "https://jobs.ashbyhq.com/ramp",
        "https://jobs.ashbyhq.com/linear",
        "https://jobs.ashbyhq.com/elevenlabs"
    ],
    "keywords": [],
    "excludeKeywords": [],
    "locations": [],
    "departments": [],
    "seenStoreName": "ashby-job-scraper-seen"
};

// Run the Actor and wait for it to finish
const run = await client.actor("findata/ashby-job-scraper").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 = {
    "sources": [
        "https://jobs.ashbyhq.com/notion",
        "https://jobs.ashbyhq.com/openai",
        "https://jobs.ashbyhq.com/ramp",
        "https://jobs.ashbyhq.com/linear",
        "https://jobs.ashbyhq.com/elevenlabs",
    ],
    "keywords": [],
    "excludeKeywords": [],
    "locations": [],
    "departments": [],
    "seenStoreName": "ashby-job-scraper-seen",
}

# Run the Actor and wait for it to finish
run = client.actor("findata/ashby-job-scraper").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 '{
  "sources": [
    "https://jobs.ashbyhq.com/notion",
    "https://jobs.ashbyhq.com/openai",
    "https://jobs.ashbyhq.com/ramp",
    "https://jobs.ashbyhq.com/linear",
    "https://jobs.ashbyhq.com/elevenlabs"
  ],
  "keywords": [],
  "excludeKeywords": [],
  "locations": [],
  "departments": [],
  "seenStoreName": "ashby-job-scraper-seen"
}' |
apify call findata/ashby-job-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,findata/ashby-job-scraper"
        }
    }
}
```

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/p8C9ti5CfIC4m5akZ/builds/xdUbeohaUdSt5Ooao/openapi.json