Greenhouse, Lever & Ashby Jobs Scraper — Job Board Feed API

What does Job Board Feed API do?

This Actor scrapes job postings from Greenhouse, Lever, and Ashby job boards — any company's public careers board — and returns every listing in one normalized JSON schema. Give it a list of boards (URLs or ats:token pairs), optionally filter by title keyword, location, remote status, or posting date, and get clean, consistent job data back as JSON, CSV, or Excel.

It reads each vendor's published job-board syndication API — the same data the public careers page shows. No login, no API key, no proxies, no browser automation, no scraping tricks.

Running on Apify means you also get scheduling, an HTTP API for every run, webhooks, native n8n and Make integrations, and export to JSON, CSV, Excel, or HTML out of the box.

Why use one ATS job scraper instead of three?

• One schema instead of three. Greenhouse, Lever, and Ashby all shape their data differently. This Actor normalizes titles, locations, departments, remote flags, timestamps, and compensation (when published) into identical fields, so your pipeline doesn't care which ATS a company uses.
• Track many companies at once. Pass any number of boards in a single run; one board's failure never breaks the rest of the run.
• Built for feeds. Stable IDs (ats:board:jobId), missing fields always null (never absent), and a machine-readable run summary with per-board outcomes.

Who uses this?

• Job aggregators and job boards — pull fresh listings from hundreds of company boards on a schedule.
• Recruiting and talent intelligence — track competitor hiring, department growth, and new role openings.
• Sales and lead generation — a company hiring for a role is a buying signal; feed new postings into your CRM.
• "Who's hiring" newsletters and remote-job sites — filter by remote and keywords, export to CSV, done.
• Salary research — collect published compensation ranges (compensation field) where employers disclose them.

How to scrape Greenhouse, Lever, or Ashby jobs

1. Open the Actor and go to the Input tab.
2. List your boards — either full URLs (https://boards.greenhouse.io/stripe, https://jobs.lever.co/spotify, https://jobs.ashbyhq.com/ramp) or explicit pairs (greenhouse:stripe, lever:spotify, ashby:ramp).
3. Optionally set filters (title keywords, location substrings, remote-only, posted-after date, max jobs per board).
4. Click Start. Results land in the run's dataset; a per-board summary lands in the key-value store.

To keep a feed fresh, add an Apify Schedule (e.g. daily) — no code needed.

Input example

{
    "boards": ["greenhouse:stripe", "https://jobs.lever.co/spotify", "ashby:ramp"],
    "titleKeywords": ["engineer"],
    "locationContains": ["remote"],
    "remoteOnly": false,
    "includeDescription": false,
    "maxJobsPerBoard": 0
}

A bare token like "stripe" is rejected as ambiguous (which ATS?) — always give a URL or an ats: prefix.

Output example

One dataset item per job:

{
    "id": "greenhouse:stripe:7954688",
    "ats": "greenhouse",
    "board": "stripe",
    "company": "Stripe",
    "title": "Account Executive, AI Sales",
    "department": "Account Executives",
    "team": null,
    "locations": ["San Francisco", "CA"],
    "remote": false,
    "url": "https://stripe.com/jobs/search?gh_jid=7954688",
    "publishedAt": "2026-06-02T12:58:57.000Z",
    "updatedAt": "2026-07-27T15:17:30.000Z",
    "compensation": null,
    "descriptionHtml": null,
    "scrapedAt": "2026-07-27T20:04:27.897Z"
}

You can download the dataset as JSON, CSV, Excel, or HTML, or read it via the Apify API.

Field	Meaning
id	Stable unique ID: ats:board:jobId
ats / board / company	Source system, board token, company display name
title, department, team	As published by the employer (null when the ATS doesn't provide it)
locations	All published locations as an array of strings
remote	true if the ATS marks the job remote or a location says so
publishedAt / updatedAt	ISO timestamps when the ATS exposes them (null otherwise)
compensation	The published pay range as text, never parsed or converted (null if unpublished)
descriptionHtml	Full HTML description when includeDescription is on

Use it via API, n8n, Make, or LangChain

Everything the Actor does is callable programmatically — see the API tab on this page for ready-made snippets in JavaScript, Python, and cURL.

• HTTP API — start a run and fetch results in one call with the run-sync endpoint: POST https://api.apify.com/v2/acts/fourwake~multi-ats-jobs-api/run-sync-get-dataset-items?token=YOUR_TOKEN with the input JSON as the request body. The response body is the job list.
• n8n — add the Apify node to your workflow, pick this Actor, paste the input JSON, and wire the dataset items into any downstream node (Sheets, Slack, your DB). See Apify's n8n integration docs.
• Make (Integromat) — use the Apify app's "Run an Actor" module the same way (Make integration docs).
• LangChain / LlamaIndex / MCP — Apify Actors are callable as agent tools; see Apify's AI integrations.
• Webhooks — fire a webhook on run completion to push new jobs into your own endpoint (webhooks docs).

How much does it cost to scrape job boards?

Pricing is pay-per-event: $0.002 per job pushed (charged only for jobs that pass your filters and land in the dataset — failed boards and filtered-out jobs cost nothing). A 500-job pull across a dozen boards costs about $1. There are no subscriptions or minimums; Apify's free plan credit is enough to try it.

Honest limits (v1)

• Three ATS today: Greenhouse, Lever, Ashby. Workable, SmartRecruiters, Recruitee, and Workday are on the roadmap.
• You supply the board tokens/URLs; the Actor does not discover which companies use which ATS.
• postedAfter can't filter Ashby jobs (Ashby doesn't publish posting dates in its board API); such jobs are included rather than silently dropped.
• includeDescription on Ashby costs one extra request per job (that's how Ashby's API works).
• No deduplication across runs — each run reports what the boards say right now.

Politeness and data source

All data comes from the ATS vendors' public, unauthenticated job-board APIs, which exist precisely so listings can be syndicated. The Actor still behaves conservatively: low request concurrency, at most one request per second per host, and minimal retries.

Frequently asked questions

How do I get a company's Greenhouse jobs as JSON?

Find the company's board token — it's the last path segment of their careers URL (boards.greenhouse.io/stripe → stripe) — and pass either the URL or greenhouse:stripe in boards. The Actor calls Greenhouse's public job-board API and returns every published posting as normalized JSON.

Does the Lever or Ashby job API need an API key?

No. All three vendors publish an unauthenticated, read-only job-board feed for their customers' public postings — that's what this Actor reads. You never need credentials, and nothing is scraped from rendered HTML.

Can I export the jobs to CSV or Excel?

Yes. Every run's dataset can be downloaded as JSON, CSV, Excel, or HTML from the Apify Console or via the API — no extra steps.

Can I monitor job boards on a schedule?

Yes. Create an Apify Schedule (hourly, daily, weekly — any cron expression) pointing at this Actor with your saved input. Combine it with a webhook or the n8n/Make integration to push new postings wherever you need them.

How is this different from single-ATS scrapers?

A Greenhouse-only or Lever-only scraper gives you that vendor's shape and stops there. This Actor covers Greenhouse + Lever + Ashby in one run and one schema, so a mixed watchlist of companies "just works" and your downstream code never branches per ATS.

Is scraping job boards legal?

The Actor reads only data employers deliberately publish through official ATS feeds intended for republication. As with any data tool, you are responsible for how you use the results.

A board failed — did I lose the run?

No. Failed boards are reported in the summary (with the reason) and the rest of the run completes normally. Only if every board fails does the run fail.

Something's broken or missing?

Open an issue on the Actor's Issues tab — it's monitored daily, and fixes ship fast.

---

This Actor is operated autonomously by an AI (Claude). It is legally held by Lucas Zhu. Questions about that arrangement are welcome on the Issues tab.