Ashby Jobs Scraper

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:

{
  "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.

Ready-to-run examples

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

• Ashby Remote Jobs with Descriptions
• Find Engineering Roles on Ashby Boards
• Track AI Startup Jobs on Ashby

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
Location filter	locationFilter	Case-insensitive substring match on primary or secondary locations
Include full descriptions	includeDescriptions	Adds description fields. Off by default

Detailed defaults and limits are in the input-field help. Both filters must match when both are supplied. There is no title, date, employment-type or workplace-type input filter. Filter those fields in your exported data. 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.

{
  "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 values when supplied
locationName, secondaryLocations	Primary location and an array of additional location names
employmentType, workplaceType	Employment and workplace labels when supplied
publishedDate, updatedAt	Source dates when supplied, not inferred opening or closing dates
compensationTierSummary	Public compensation summary when available
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 for the available formats and field options.

Pricing

The start event is charged once at run start, before input validation. Invalid input can still incur this charge.

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. Enabling descriptions requires extra work per matching job and can increase runtime. Apify platform usage depends on your plan.

See the live Pricing tab for current rates and plan discounts.

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. 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 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 for your chosen tool.

For a custom connection, an Apify webhook 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, Python client guide and Actor runs API reference.

cURL

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

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

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. 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. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin 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 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.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. 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:

{
  "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 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. This experimental option lets an agent use Apify without a conventional account.

Apify AGI 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 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 — Collect public job openings and available details from known Greenhouse company boards.
• Lever Jobs Scraper & Hiring Signals — Collect public Lever company-board jobs with locations, application URLs and available descriptions.
• Workday Jobs Scraper — Collect public job postings and available employment metadata from known Workday-hosted career sites.
• LinkedIn Jobs Scraper - Search & Export — Collect public LinkedIn job search or known-posting records with available employer and location details.
• 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 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. 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 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. ♥