/apify-ashby-jobs-scraper

name: apify-ashby-jobs-scraper
description: "Scrape Ashby jobs or discover companies using Ashby with the Apify Ashby Job Board API Actor (johnvc/ashby-job-board-scraper). Job mode returns live job rows with title, company, location, remote and employment fields, publish date, apply URL, employer-published salary columns, equity flag, and Markdown descriptions. Company mode finds Ashby boards from a bundled directory or checks a prospect list, returning company name, board slug and URL, live open-job count, and verification fields. Takes company names, board slugs, or board URLs; supports pre-billing job filters and publishedAfter feeds. Use for Ashby jobs data or API requests, salary and remote-role collection, job-board pipelines, companies using Ashby/Ashby customers, ATS market maps, prospect checks, and recruiting or sales target lists. Billed per delivered result with no start fee, and MCP-ready for Claude and other AI agents."
author: John Cole
author_url: https://github.com/johnisanerd
license: MIT
metadata:
  version: "1.0"
  keywords: "ashby, jobs, job-board, salary, remote-work, company-discovery, prospect-check"

Ashby Companies and Jobs, as Structured Rows

Find companies using Ashby, check a prospect list, or retrieve their job postings with employer-published salary data. Choose the output mode for the requested result.

When to use this skill

• Someone wants Ashby jobs and does not want to read jobs.ashbyhq.com boards by hand.
• You are filling a job board, a market-intel dashboard, or a sourcing tool with roles from Ashby-hosted careers pages.
• You need salary as numbers the employer actually published, not a string a human has to read or a model has to guess.
• You went looking for an Ashby jobs API and found only the employer-side APIs you cannot sign up for.
• Someone asks which companies use Ashby, wants an ATS market map, or needs to check a prospect list for Ashby boards.
• You need live open-role counts before choosing which boards to feed into a jobs pipeline.

Choose `outputMode` for the question: `jobs` for postings, `companiesOnly` for company discovery or verification, and `urlsOnly` for a cheap board index. See `references/actor-index.md`.

What you get

In `jobs` mode, one dataset row per job. `resultType` separates `job` rows from `error` rows.

Core fields:

• `id`, `url` (canonical, safe as a dedupe key), `applyUrl`, `title`
• `companyName`, `boardToken`, `boardUrl`
• `department`, `team`, `departments`, `employmentType`, `workplaceType`, `isRemote`
• `location`, `secondaryLocations`, `locationsDerived`, `countriesDerived`, `address`
• `datePublished`, `isListed`
• `compensationSummary` (the employer's own pay line), `salaryRaw` (structured, verbatim), `salaryDerived`, and flat `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryPeriod`, `salaryTiers`, `offersEquity`
• `descriptionMarkdown` (default add-on), `descriptionHtml`, `descriptionText` (opt-in add-ons)
• `source` (always `ashby`), `sourceType`, `scrapedAt`

With `includeCompanyData` on, each row also carries `companyWebsite`, `companyLogo`, `remoteEligibility` (the countries remote applicants may live in, as the employer declared them), `applicationDeadline`, and `directApply`.

The Actor ships dataset views for the console: `overview`, `salaries` (sortable pay columns), `companies`, and `newPostings`.

Company rows

With `outputMode: "companiesOnly"`, the dataset has one row per company. `resultType` separates `company` rows from `error` rows.

• `companyName`, `boardToken`, `boardUrl`
• `jobCount`: live open roles at verification time
• `live`: whether the board answered the probe (`null` when verification is off)
• `verifiedAt`, `scrapedAt`

A failed prospect check returns an error row with `errorCode: board_not_found`, `errorMessage`, and optional `didYouMean` suggestions. The `companies` dataset view presents company name, slug, open jobs, live flag, and board link.

Prerequisites

• Apify account (sign up at https://apify.com?fpr=9n7kx3&fp_sid=awesomeskills).
• Authentication via `apify login`, or an `APIFY_TOKEN` environment variable (Apify Console, Settings, Integrations).

The Actor

• Store page: https://apify.com/johnvc/ashby-job-board-scraper?fpr=9n7kx3&fp_sid=awesomeskills
• Actor ID: `johnvc/ashby-job-board-scraper`
• Pricing: pay per event, no start fee. See the cost section below and `references/gotchas.md` for the live-price command.

Run it with the Apify CLI

Engineering roles from two boards, capped at 25:

apify actors call "johnvc/ashby-job-board-scraper" -i '{"companies":["cerebras","ramp"],"titleKeywords":["engineer"],"maxJobs":25}' \
  --json \
  --user-agent apify-awesome-skills/apify-ashby-jobs-scraper \
  2>/dev/null

Remote full-time roles with pay, descriptions off for cheaper metadata rows:

apify actors call "johnvc/ashby-job-board-scraper" -i '{"companies":["openai","ramp","deel"],"remoteOnly":true,"employmentTypes":["FullTime"],"includeDescriptionMarkdown":false,"maxJobs":100}' \
  --json \
  --user-agent apify-awesome-skills/apify-ashby-jobs-scraper \
  2>/dev/null

Only postings added in the last day, the shape to put on a daily schedule:

apify actors call "johnvc/ashby-job-board-scraper" -i '{"companies":["openai","notion","linear"],"publishedAfter":"25h","maxJobs":200}' \
  --json \
  --user-agent apify-awesome-skills/apify-ashby-jobs-scraper \
  2>/dev/null

Confirm the live schema and prices before a large batch:

apify actors info "johnvc/ashby-job-board-scraper" --json \
  --user-agent apify-awesome-skills/apify-ashby-jobs-scraper \
  2>/dev/null

Read the rows back from a finished run:

apify datasets get-items <DATASET_ID> --format json \
  --user-agent apify-awesome-skills/apify-ashby-jobs-scraper \
  2>/dev/null

Discover up to 100 Ashby boards from the directory and verify them live:

apify actors call "johnvc/ashby-job-board-scraper" -i '{"outputMode"