How to Scrape Jobs from Greenhouse, Lever, Ashby and Workable
How to Scrape Jobs from Greenhouse, Lever, Ashby and Workable A large share of tech and growth-stage hiring still runs through a handful of applicant tracking systems: Greenhouse, Lever, Ash...
Résumé
How to Scrape Jobs from Greenhouse, Lever, Ashby and Workable A large share of tech and growth-stage hiring still runs through a handful of applicant tracking systems: Greenhouse, Lever, Ashby, Workable and SmartRecruiters. Each company gets a public board URL, and those boards are the most reliable place to see current openings — better than a stale aggregate job site. If you want those jobs in one spreadsheet, you should not have to write a parser per ATS. This guide shows how to scrape them in a single run. You will use the ATS Job Scraper on Apify. Paste career-board URLs; the Actor detects the ATS automatically and returns a normalized schema: title, location, remote flag, department, salary (when the board publishes it), dates and the full description. By the end of this article you will have a CSV or JSON file on your machine, and a short Python snippet you can rerun or schedule. The same Actor is also callable from JavaScript and from AI agents through the Apify MCP server. What you need An Apify account. The Free plan is enough to try a small run. A list of inputs for the Actor (URLs, IDs or search terms — details in the steps below). Optional: Python 3 with the apify-client package if you want to automate the run. You do not need an ATS API key or a login. Public board URLs are enough. How to run it in the Apify Console Step 1: Open the Actor Go to https://apify.com/veenkes/veenkes-ats-jobs and click Try for free. Step 2: Paste board URLs Examples: https://boards.greenhouse.io/stripe or https://jobs.ashbyhq.com/ramp. Mix Greenhouse, Lever, Ashby, Workable and SmartRecruiters in the same run if you want. Step 3: Optional filters Add keywords, a location string, remote-only, or a posted since date if you are building a daily new-jobs alert. Set a modest max jobs per company for the first run. Step 4: Run and export Start the run and export the dataset as CSV or JSON. Full descriptions are included as plain text and HTML at no extra charge. If a URL is not a supported board, the run will skip or report it rather than silently inventing jobs. You pay only for jobs that are actually saved. How to run it from Python Install the official client and call the Actor by its Store id veenkes/veenkes-ats-jobs. Replace YOUR_APIFY_TOKEN with a token from Apify Console > Integrations. Do not commit the token to a public repository. pip install apify-client from apify_client import ApifyClient client = ApifyClient("YOUR_APIFY_TOKEN") run = client.actor("veenkes/veenkes-ats-jobs").call(run_input={ "companies": [ "https://boards.greenhouse.io/stripe" ], "maxJobsPerCompany": 50, "includeDescription": True }) # Write every dataset item, then export from the Console or keep going in code. for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) The JavaScript client (apify-client on npm) uses the same Actor id and the same input object. You can also start the run with a plain HTTP POST to the Apify API if you prefer. Sample output Here is a shortened example of one dataset record (field values are illustrative of the schema, taken from a real sample run shape): { "platform": "ashby", "company": "ramp", "companyName": null, "jobId": "b7fd55f4-6c5a-42f5-be04-aa09a4d5b7a9", "title": "Senior Design Engineer", "url": "https://jobs.ashbyhq.com/ramp/b7fd55f4-6c5a-42f5-be04-aa09a4d5b7a9", "applyUrl": "https://jobs.ashbyhq.com/ramp/b7fd55f4-6c5a-42f5-be04-aa09a4d5b7a9/application", "location": "Remote (US)", "allLocations": [ "Remote (US)", "San Francisco, CA", "New York, NY (HQ)" ], "country": "United States", "remote": true, "workplaceType": "Remote", "employmentType": "FullTime", "department": "Engineering", "team": "Engineering", "salaryText": "$188,000 - $259,250", "salaryMin": 188000, "salaryMax": 259250, "salaryCurrency": "USD", "salaryInterval": "1 YEAR", "publishedAt": "2026-11-12T20:01:54.072Z", "updatedAt": null, "descriptionText": "ABOUT RAMP\n\nRamp is building the smart infrastructure for finance teams, embedded in the transaction flow of every dollar a business spends. We automate how over $275B in annualize…", "descriptionHtml": "<h1><strong>About Ramp</strong></h1><p style=\"min-height:1.5em\">Ramp is building the smart infrastructure for finance teams, embedded in the transaction flow of every dollar a busi…", "scrapedAt": "2026-11-12T20:38:24.077Z" } Once the run has finished, open the dataset in the Console and use Export > CSV if a spreadsheet is your destination. JSON is usually better for code and for language models. What to use the data for Recruiters watch a list of target companies and get new roles the day they go live. Founders and compensation researchers compare titles, locations and published salaries. Lead-generation teams treat a burst of hiring in a department as a buying signal. Job-board products use a normalized schema so Greenhouse and Ashby jobs can live in the same table. Pricing Pay-per-result pricing starts at $2.00 per 1,000 saved jobs on the Apify Free plan, with lower unit prices on paid Apify plans. Full descriptions are included. There is also a small per-run start fee. Always check the live pricing on the Actor page, because plans and unit prices can change. For a first test, keep the input tiny so you can inspect the schema before you scale up. Scheduling and automations In the Apify Console you can schedule the Actor (daily or hourly) and leave the same input in place. For incremental jobs, prefer a "since" or "posted after" style filter when the Actor offers one, so you are not paying to re-collect old rows. When a run finishes you can send a webhook, or connect the Actor in Zapier, Make or n8n. AI agents can discover and call veenkes/veenkes-ats-jobs through Apify's MCP server using the same input. Good practices and limits Job descriptions are written by the employer and may be copyrighted; use them for search, analysis or application workflows, not to republish a competing board wholesale. Always follow the company's and the ATS vendor's terms. The Actor is not affiliated with Greenhouse, Lever, Ashby, Workable or SmartRecruiters. If a run returns fewer rows than you expected, check the input caps, language or country filters, and the Actor log. A zero-row run is usually a filter or an unavailable source, not a silent crash — read the log before you increase limits. Next step Open the Actor and run a small job: ATS Job Scraper: Greenhouse, Lever, Ashby & Workable. If you later want this on a schedule, save the input that worked, add a date filter where it applies, and export CSV automatically from the dataset or from the API snippet above.