# Ashby Jobs Scraper (`fetch_cat/ashby-jobs-scraper`) Actor

Extract live job postings from public Ashby company job boards.

- **URL**: https://apify.com/fetch_cat/ashby-jobs-scraper.md
- **Developed by:** [Fetch Cat](https://apify.com/fetch_cat) (community)
- **Categories:** Jobs, Lead generation, Developer tools
- **Features:** Limited permissions
- **Stats:** 3 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.02 / 1,000 result extracteds

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

Export job postings from public Ashby company career boards into a structured dataset. Ashby Jobs Scraper accepts company slugs or hosted board URLs and returns job titles, teams, locations, compensation summaries when available, and job URLs, with optional descriptions.

Use it for recruiting research, hiring-signal analysis, and job-board feeds. Only public `jobs.ashbyhq.com` boards are supported. Fields and results depend on what each company publishes.

### Quick start

Add one public board and keep the first run small:

```json
{
  "companySlugsOrUrls": ["openai"],
  "maxItems": 10,
  "includeDescriptions": false
}
```

Click **Start**, then export the dataset as JSON, CSV or Excel. The result cap applies across all boards, not separately to each company.

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

https://youtu.be/1OW8gOqlZbY?t=25

### Ready-to-run examples

Choose a public example to see its settings before starting a run:

- [Ashby Remote Jobs with Descriptions](https://apify.com/fetch_cat/ashby-jobs-scraper/examples/ashby-remote-jobs-descriptions)
- [Find Engineering Roles on Ashby Boards](https://apify.com/fetch_cat/ashby-jobs-scraper/examples/ashby-engineering-roles)
- [Track AI Startup Jobs on Ashby](https://apify.com/fetch_cat/ashby-jobs-scraper/examples/ashby-ai-startup-jobs)

### What you get

- **Public job listings:** titles, company and board identifiers, teams, departments and posting links.
- **Location and employment details:** primary and secondary locations, workplace labels and employment types when the company provides them.
- **Optional detail:** public compensation summaries and source dates, plus full descriptions when you enable them. Missing values stay empty rather than being inferred.

### Who is it for?

- **Recruiters and job seekers** reviewing openings at a known set of companies.
- **Job-board editors and data teams** building feeds from public Ashby postings.
- **Hiring-market and account researchers** comparing published teams, locations and compensation information.

### Hiring research workflows

- **Review a target company's engineering roles.** Add its public Ashby board and use `teamFilter` to narrow the sample. Review titles, locations and job links in a spreadsheet, then open the original postings for application details. Team matching uses a substring rather than a shared taxonomy.
- **Prepare a job-board feed.** Collect your selected boards and retain `companySlug`, `jobId` and `jobUrl` with each posting. Enable descriptions if your feed needs them. Compare saved exports in your own system to decide which jobs to add or update, because the Actor does not detect new or closed jobs.
- **Compare published workplace and pay information.** Export location labels and compensation summaries from a small group of boards. Keep missing values visible and check each posting's terms. A location containing “Remote” does not establish worldwide applicant eligibility.

### Input settings

| Setting | API key | Summary |
| --- | --- | --- |
| Company slugs or board URLs | `companySlugsOrUrls` | Required list of public Ashby boards |
| Maximum jobs | `maxItems` | Global saved-result cap. Set it explicitly for predictable calls |
| Team filter | `teamFilter` | Case-insensitive substring match on team names |
| Title keywords | `titleFilter` | Comma-separated keywords; the title must contain any of them |
| Department filter | `departmentFilter` | Case-insensitive substring match on department names |
| Location filter | `locationFilter` | Case-insensitive substring match on primary or secondary locations, city, region or country |
| Employment types | `employmentTypes` | FullTime, PartTime, Intern, Contract, Temporary |
| Workplace types | `workplaceTypes` | OnSite, Hybrid, Remote |
| Remote jobs only | `remoteOnly` | Only postings marked remote |
| Posted within days | `postedWithinDays` | Only postings published in the last N days |
| Minimum yearly salary | `minSalary` | Only postings whose published yearly salary range reaches this amount, in the posting's currency |
| Include full descriptions | `includeDescriptions` | Adds description fields. Off by default |

Detailed defaults and limits are in the input-field help. All supplied filters must match. Jobs follow board order rather than a guaranteed newest-first sort.

#### Example inputs

Use the Quick start input as a small first run. Adjust the fields described above for your own data.

### Output data

One dataset row represents one job posting. This is an illustrative shape, not an observed vacancy. Optional board values may be `null`.

```json
{
  "companySlug": "example-company",
  "companyName": "Example Company",
  "jobId": "example-job-id",
  "postingId": "example-posting-id",
  "title": "Example role",
  "team": null,
  "locationName": null,
  "secondaryLocations": [],
  "compensationTierSummary": null,
  "jobUrl": "https://jobs.ashbyhq.com/example-company/example-posting-id",
  "scrapedAt": "2026-10-24T00:00:00.000Z"
}
```

| Fields | Meaning |
| --- | --- |
| `companySlug`, `companyName` | Board slug and company name. The slug is used if the name is unavailable |
| `jobId`, `postingId`, `jobUrl` | Job identifier, public posting identifier and posting URL |
| `title` | Job title |
| `team`, `teamId`, `department`, `departmentId` | Team and department |
| `locationName`, `secondaryLocations` | Primary location and an array of additional location names |
| `employmentType`, `workplaceType`, `isRemote` | Employment type, workplace type and remote flag |
| `addressLocality`, `addressRegion`, `addressCountry` | City, region and country of the job address |
| `publishedDate`, `updatedAt` | Published date and, when available, last update; not inferred closing dates |
| `compensationTierSummary`, `compensationSummary` | Public pay summary and salary range text when published |
| `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryInterval`, `hasEquity`, `compensationComponents` | Salary range as numbers with currency and pay period, equity flag and every published pay component |
| `applyUrl` | Direct application form link |
| `descriptionHtml`, `descriptionText` | Description fields, added only when enabled. Content can be missing |
| `scrapedAt` | Run timestamp shared by saved postings |

#### Download your results

Open your run's dataset, choose **Export** and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See [Apify's download and export guide](https://docs.apify.com/storage/dataset#apify-console) for the available formats and field options.

### Pricing

The `start` event is charged once after the input is validated.

The `result` event is charged for each job posting saved to the dataset. A run with no saved jobs has no result charge, but the start charge still applies.

A small `maxItems` bounds saved results, rather than total page size or run duration. Descriptions come with the job list, so enabling them adds no extra page per job. Apify platform usage depends on your plan.

See the [live Pricing tab](https://apify.com/fetch_cat/ashby-jobs-scraper/pricing) for current rates and plan discounts.

If you set a maximum cost per run or a run timeout, the run stops cleanly before it, keeps the jobs saved so far and says why in the status message.

### Tips for best results

- **Start with one board.** Enter a plain slug such as `openai` or its full public Ashby board URL, then set a small explicit `maxItems`.
- **Try the board without filters first.** Check the actual team and location wording in its results before adding substring filters. Both filters must match when you supply both.
- **Plan the cap across your boards.** `maxItems` applies to the whole run. Earlier boards can use the allowance before later boards are visited, so use separate runs when you need a sample from each.
- **Enable descriptions only when you need them.** Leave them off for a compact listing export, or turn them on when you need to read the role requirements.
- **Check status before using an export.** A failed run can retain rows already saved. Treat them as partial rather than a complete snapshot.

### Limits and caveats

- **Public Ashby boards only.** Arbitrary company websites, other recruiting platforms and private applicant or candidate records are outside the scope.
- **Empty results and failed runs mean different things.** A valid board with no postings, or filters matching no postings, can return an empty dataset. Invalid boards, unavailable pages or description-fetch errors can fail a run, even after some rows have been saved.
- **Company-provided fields can be missing.** Names, dates, compensation and descriptions are not inferred. A “Remote” label does not establish where someone is eligible to apply.
- **Repeated board inputs are not deduplicated.** Avoid entering the same board more than once if you do not want repeated collection.
- **No built-in history or alerts.** The Actor does not identify newly opened or closed jobs. It follows board order rather than a guaranteed newest-first order. There are no title, date, employment-type or workplace-type input filters, so apply those checks to your export.

### Automation and integrations

#### Save your settings for next time

Once you have an input that works for you, [save it as an Apify task](https://docs.apify.com/actors/running/tasks). This keeps your settings together so you can use them again without filling in the form from scratch.

#### Run on a schedule

Need fresh results regularly? You can [schedule the Actor or a saved task](https://docs.apify.com/actors/running/schedules) to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

#### Send results to your other tools

Use **n8n, Make or Zapier** to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the [Apify integration guides](https://docs.apify.com/integrations) for your chosen tool.

For a custom connection, an [Apify webhook](https://docs.apify.com/integrations/webhooks) can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

### API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its `defaultDatasetId` to fetch the results.

For setup instructions, see Apify's [JavaScript client guide](https://docs.apify.com/api/client/js), [Python client guide](https://docs.apify.com/api/client/python) and [Actor runs API reference](https://docs.apify.com/api/v2/acts-runs-post).

#### cURL

```bash
curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~ashby-jobs-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "companySlugsOrUrls": [
    "openai"
  ],
  "maxItems": 10,
  "includeDescriptions": false
}
JSON
```

#### Node.js

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

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/ashby-jobs-scraper').call({
  "companySlugsOrUrls": [
    "openai"
  ],
  "maxItems": 10,
  "includeDescriptions": false
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);
```

#### Python

```python
import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/ashby-jobs-scraper').call(run_input={'companySlugsOrUrls': ['openai'], 'maxItems': 10, 'includeDescriptions': False})
print(client.dataset(run['defaultDatasetId']).list_items().items)
```

#### API usage notes

The asynchronous API returns a run record, not job rows. Wait for terminal status, then use its `defaultDatasetId` with the [dataset items API](https://docs.apify.com/api/v2/dataset-items-get). Paginate dataset reads for larger exports.

### MCP and AI agents

You can ask your AI assistant to collect data with **Ashby Jobs Scraper** and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the [Apify MCP server](https://mcp.apify.com/). MCP gives your assistant a way to find this scraper, run it and read the results. Follow the [official setup and sign-in guide](https://docs.apify.com/mcp) for your app.

#### Easier setup with an Apify plugin

If you use a supported coding assistant, the [official Apify plugin](https://docs.apify.com/agents/plugins) can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

#### Use Apify AI in Console

Prefer to keep everything in Apify? Open [Apify AI in Console](https://docs.apify.com/account/apify-ai) and ask it to find Fetch Cat's **Ashby Jobs Scraper**. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

#### Choose your assistant

- **Claude and Claude Code (Anthropic):** [Apify setup guide](https://docs.apify.com/integrations/claude).
- **ChatGPT and Codex (OpenAI):** [Apify setup guides](https://docs.apify.com/integrations/openai).
- **Grok Bot (xAI):** [Apify plugin guide](https://docs.apify.com/integrations/grok-bot).
- **Gemini CLI (Google):** [MCP server setup guide](https://geminicli.com/docs/tools/mcp-server/). Use the server URL below with the HTTP configuration supported by Gemini CLI.

#### Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

```json
{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/ashby-jobs-scraper"
    }
  }
}
```

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

#### Use Apify's general server

Already connected to the general Apify MCP server at `https://mcp.apify.com`? You can use it to find this scraper without adding another server. Ask your assistant to use **Ashby Jobs Scraper** by Fetch Cat, or give it the identifier `fetch_cat/ashby-jobs-scraper`.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

#### Example requests

Give your assistant the inputs it needs along with a request like one of these:

- “Use Fetch Cat's Ashby Jobs Scraper to collect up to ten engineering jobs from OpenAI's public Ashby board. Show me titles, teams, locations and application links.”
- “Get a sample of up to ten jobs whose location contains Remote from OpenAI's public Ashby board. Include descriptions and help me check the actual location restrictions in the returned text.”
- “Collect up to twenty public jobs across the Ashby boards I provide. Make a table of company, title, location, published compensation and job link, and leave unavailable compensation blank.”

Normal Apify charges apply. Check the [live Pricing tab](https://apify.com/fetch_cat/ashby-jobs-scraper/pricing) before asking your assistant to run a larger batch.

### Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through [x402](https://docs.apify.com/integrations/x402). This experimental option lets an agent use Apify without a conventional account.

[Apify AGI](https://agi.apify.com/) provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

#### Other ways for agents to pay

Apify also supports **MPP** for prepaid access through AGI and **Skyfire** for eligible Actors. If your agent already uses one of these, see the [agentic payment guide](https://docs.apify.com/agents/payments) to choose the right setup.

### FAQ

#### Can I export Ashby jobs to CSV or use an API?

Yes. Export the dataset from Apify or retrieve it through the API. This Actor is not an official Ashby API and only supports public hosted boards.

#### Can I filter remote jobs or specific teams?

Use `locationFilter: "Remote"` or `teamFilter: "Engineering"`. Matching uses substrings, not a standardized remote-work classification or team taxonomy.

#### Why are descriptions missing?

Set `includeDescriptions` to `true`. It is off by default, and a posting may still lack description content.

#### Why did I get fewer jobs than expected?

The global `maxItems`, filters, missing posting IDs or titles, and board availability affect results. Check the final run status. A failed run may contain only partial output.

#### Can I use this for hiring alerts?

You can build your own workflow to compare exports over time. The Actor itself does not retain history or identify newly opened and closed jobs.

#### Do I need an Ashby account?

No. Public boards are supported without an Ashby login. Private applicant data is outside the product scope.

### Related Actors

For other public hiring sources and adjacent company research:

- [Greenhouse Jobs Scraper](https://apify.com/fetch_cat/greenhouse-jobs-scraper) — Collect public job openings and available details from known Greenhouse company boards.
- [Lever Jobs Scraper & Hiring Signals](https://apify.com/fetch_cat/lever-jobs-scraper) — Collect public Lever company-board jobs with locations, application URLs and available descriptions.
- [Workday Jobs Scraper](https://apify.com/fetch_cat/workday-jobs-scraper) — Collect public job postings and available employment metadata from known Workday-hosted career sites.
- [LinkedIn Jobs Scraper - Search & Export](https://apify.com/fetch_cat/linkedin-jobs-scraper) — Collect public LinkedIn job search or known-posting records with available employer and location details.
- [Y Combinator Companies Scraper](https://apify.com/fetch_cat/y-combinator-companies-scraper) — Collect public Y Combinator company-directory records and available company-profile metadata.

### Support and feedback

For custom additions or integrations, email <hello@fetchcat.dev>.

Found an error or have a feature request? [Open an issue](https://apify.com/fetch_cat/ashby-jobs-scraper/issues) with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See [Apify’s guide to sharing a run when reporting an issue](https://docs.apify.com/account/collaboration/general-resource-access#automatically-sharing-runs-via-actor-issues). Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. [Leave a review](https://apify.com/fetch_cat/ashby-jobs-scraper/reviews) to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥

# Changelog

This Actor's version history is a separate document: https://apify.com/fetch_cat/ashby-jobs-scraper/changelog.md

# Actor input Schema

## `companySlugsOrUrls` (type: `array`):

Required list of public Ashby hosted board slugs or URLs, such as openai or https://jobs.ashbyhq.com/openai. The form prefills openai and ramp; API calls must supply this list. Boards are visited in input order and repeated boards are not deduplicated. Other company websites are not supported.

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

Maximum job postings saved across all boards together, from 1 to 10000. The form/schema default is 20; a raw input reaching the runtime without this key uses 100. Set an explicit value for consistent calls. Earlier boards may fill the cap before later boards are visited; results retain board order, not a guaranteed newest-first sort.

## `teamFilter` (type: `string`):

Optional case-insensitive substring match on the team name, for example Engineering or Sales. Blank means no team filter. When locationFilter is also supplied, both filters must match. This does not search job titles or department names.

## `locationFilter` (type: `string`):

Optional case-insensitive substring match on primary or secondary location names, for example Remote, London, or San Francisco. Blank means no location filter. Remote matches location text, not applicant eligibility or workplaceType. When teamFilter is also supplied, both filters must match.

## `titleFilter` (type: `string`):

Optional comma-separated keywords; a job matches when its title contains any of them (case-insensitive), for example engineer, designer.

## `departmentFilter` (type: `string`):

Optional case-insensitive substring match on the department name, for example Engineering.

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

Keep only these employment types. Empty means all.

## `workplaceTypes` (type: `array`):

Keep only these workplace types. Empty means all.

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

Keep only postings marked remote.

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

Keep only postings published in the last N days. Postings without a published date are skipped when set.

## `minSalary` (type: `integer`):

Keep only postings with a published yearly salary range whose top reaches this amount, in the posting's own currency. Postings without a published yearly salary are skipped when set.

## `includeDescriptions` (type: `boolean`):

Off by default. Enable to add descriptionHtml and descriptionText. Descriptions come with the job list from Ashby, so this adds no extra page per job (only boards read through the page fallback need one request per matching job). Content may be unavailable.

## Actor input object example

```json
{
  "companySlugsOrUrls": [
    "openai",
    "ramp"
  ],
  "maxItems": 20,
  "remoteOnly": false,
  "includeDescriptions": false
}
```

# Actor output Schema

## `overview` (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 = {
    "companySlugsOrUrls": [
        "openai",
        "ramp"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("fetch_cat/ashby-jobs-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 = { "companySlugsOrUrls": [
        "openai",
        "ramp",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("fetch_cat/ashby-jobs-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 '{
  "companySlugsOrUrls": [
    "openai",
    "ramp"
  ]
}' |
apify call fetch_cat/ashby-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,fetch_cat/ashby-jobs-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/rdIRadieVZvG4e58c/builds/E9HI10Bd6Wz8aZ1Nj/openapi.json