Greenhouse, Lever, Ashby, Workday & Workable Jobs API

Search jobs from thousands of companies' own career sites by title, location, remote and posting date. You don't need a company list. Type "data engineer", "Remote" and "last 7 days", and get every matching opening from companies hiring on Greenhouse, Lever, Ashby and Workday.

Jobs come straight from employers' applicant tracking systems (ATS), not from aggregators. That means no reposts, no expired listings, and direct links to the company's application page.

How to use

1. Sign up for Apify — the free plan's monthly credit is enough to try this Actor.
2. Open Greenhouse & Lever Jobs Scraper, fill in the input (the form is pre-filled with a working example) and click Start.
3. Watch results stream into the dataset table while the run is going.
4. Export as JSON, CSV, Excel, XML, HTML or RSS — or pull the results from your own code with the Apify API.

Why use this Greenhouse and Lever jobs tool?

• Search across companies. A continuously refreshed index covers thousands of company job boards. Most ATS scrapers make you supply company slugs first; this one searches all of them.
• Four ATS in one schema. Greenhouse, Lever, Ashby and Workday results share the same fields.
• Fast and cheap. A search scans the whole index in seconds instead of crawling thousands of career pages at run time.
• Salary ranges. Returned when the employer publishes them (common on Ashby and Lever). Use Only jobs with salary to keep just those.
• Full descriptions on demand. Turn on Include full job description to fetch the live description, as plain text and HTML, for each result.
• Monitoring mode. Only new jobs since last run remembers your search and returns only newly posted roles. Schedule it and send alerts to Slack, email or Google Sheets.
• Smart matching.
  • Whole-word keywords, so "java" doesn't match "javascript".
  • Exclude keywords.
  • Location text match, e.g. "London", "Germany" or "Remote".
  • Workplace type (remote, hybrid, on-site).
  • Company filter.

How to scrape Greenhouse and Lever jobs

{
  "keywords": ["data engineer", "analytics engineer"],
  "excludeKeywords": ["intern", "principal"],
  "locations": ["Remote", "United States"],
  "workplaceTypes": ["remote"],
  "postedWithinDays": 3,
  "onlyWithSalary": false,
  "includeDescription": true,
  "onlyNewJobs": false,
  "maxResults": 500
}

Field	What it does
keywords	Title must contain one of these (whole words, case-insensitive)
excludeKeywords	Drop titles containing any of these
locations	Location contains any of these (city, state, country, "Remote")
workplaceTypes	remote, hybrid, onsite
postedWithinDays	Only jobs posted in the last N days
companies	Optional company names or slugs
sources	Limit to greenhouse, lever, ashby, workday
onlyWithSalary	Keep only jobs with a published salary
includeDescription	Fetch the full description for each result
onlyNewJobs	Monitoring: only jobs that appeared since the previous run of the same search
searchDepartment	Also match keywords against department/team
maxResults	Newest first; you pay per job returned

Input reference

Every option at a glance. A minimal input that works as-is:

{
  "keywords": [
    "data engineer"
  ],
  "locations": [
    "Remote"
  ],
  "postedWithinDays": 7,
  "maxResults": 1000
}

All fields:

• keywords (Job title keywords) — Return jobs whose title contains any of these (whole-word match, case-insensitive). Example: “data engineer”, “product designer”, “SRE”. Leave empty to match all titles (combine with other filters).
• excludeKeywords (Exclude title keywords) — Drop jobs whose title contains any of these, e.g. “senior”, “intern”, “manager”.
• locations (Locations) — Keep jobs whose location contains any of these (city, state, country or “Remote”). Example: “London”, “Germany”, “CA”, “Remote”.
• workplaceTypes (Workplace type) — Keep only these workplace types. Jobs where the company didn't say are excluded when this is set. Any of: remote, hybrid, onsite.
• postedWithinDays (Posted within (days)) — Only jobs posted (or first seen by the index) in the last N days.
• companies (Companies (optional)) — Limit to these companies — name or career-page slug, partial match (e.g. “stripe”, “openai”).
• sources (Job boards) — Which applicant tracking systems to search. Empty = all. Any of: greenhouse, lever, ashby, workday, workable.
• onlyWithSalary (Only jobs with salary) — Keep only jobs that publish a salary range (mostly Ashby and Lever). Default false.
• includeDescription (Include full job description) — Fetch the full description (plain text and HTML) live from the company's job board for every result. Slower, same price. Default false.
• onlyNewJobs (Only new jobs since last run (monitoring)) — Remembers this exact search and returns only jobs that appeared after the previous run. Schedule it hourly or daily and connect Slack, email or Google Sheets. Default false.
• searchDepartment (Also match keywords in department) — Match keywords against the department/team too, e.g. “Engineering” returns every engineering role. Default false.
• maxResults (Max results) — Newest jobs first. You are charged per job returned. Default 1000.

What the Greenhouse and Lever jobs output looks like

{
  "title": "Software Engineer, Compute Foundations",
  "company": "Openai",
  "companySlug": "openai",
  "hiringEntity": null,
  "source": "ashby",
  "location": "San Francisco",
  "locations": ["San Francisco"],
  "country": "United States",
  "workplaceType": "hybrid",
  "department": "Scaling",
  "employmentType": "FullTime",
  "salaryMin": 255000,
  "salaryMax": 490000,
  "salaryCurrency": "USD",
  "salaryInterval": "1 YEAR",
  "salaryText": "$255K - $490K",
  "postedAt": "2026-09-16T23:39:23Z",
  "firstSeenAt": "2026-09-17T07:21:37Z",
  "url": "https://jobs.ashbyhq.com/openai/…",
  "jobId": "ashby:openai:…",
  "description": "About the team …",
  "descriptionHtml": "<p>About the team …</p>",
  "indexUpdatedAt": "2026-09-17T09:00:00Z"
}

Field notes:

• postedAt is the employer's publish date.
  • Workday only shows relative dates such as "Posted 3 Days Ago", so its postedAt is a day, not a time.
  • Workday's "30+ days ago" is null.
• firstSeenAt is when this index first saw the job.
• company comes from the job board. For Lever, Ashby and Workday it is derived from the career-site slug.

What can you do with Greenhouse and Lever jobs data?

• Job seekers & career coaches: daily alerts for new roles that fit exact criteria.
• Recruiters & staffing agencies: find companies actively hiring for a skill set.
• Sales & lead generation: hiring signals, e.g. companies opening data or security teams.
• Market & salary research: track demand and published pay ranges by role and location.
• Job boards & AI agents: a clean, structured feed of direct employer postings.

How fresh is the data?

The index is rebuilt several times a day. Every result includes indexUpdatedAt. Descriptions requested with Include full job description are fetched live at run time.

How much does it cost?

Pay per job returned, plus a negligible start fee per run. Jobs that don't match your filters are never charged. Set Max results or a spending limit to cap cost.

Workable jobs

Workable was added in October 2026: companies are discovered from public web archives and their boards are read from Workable's public job widget, with full descriptions (including requirements and benefits) when you turn on includeDescription. Workable does not publish salary ranges, so onlyWithSalary skips them.

Limits you should know about

• Only public job postings are used. No login and no personal data.
• Coverage grows as new company job boards are discovered. Missing a company you care about? Open an issue with its careers page and it will be added.

Pricing — what you pay per job

This Actor uses pay-per-event pricing: no monthly rental, you pay for the results you get. Prices per 1,000 results by Apify plan:

Event	Free plan	Bronze	Silver	Gold+
job — One job posting saved to the dataset	$1.00	$0.90	$0.85	$0.80

There is also a small start fee of $0.00005 per GB of memory ($0.00005 per run at the default 1 GB). Platform compute is included in the price — you are not billed separately for run time. Set a maximum total charge on the run if you want a hard cap, and use the input limits to control how much is fetched. The current prices are always on the Pricing tab.

Tips

• You do not need a company list — search by title and the index covers thousands of companies.
• Use excludeKeywords (e.g. senior, intern) to cut noise before you pay.
• Turn on searchDepartment to get every role in a team, e.g. Engineering.
• Leave includeDescription off for quick scans; turn it on only for the jobs you will read.
• Start with a small maxResults (say 20) to check the output, then raise it — you only pay per result.
• For ongoing tracking, schedule the Actor and turn on onlyNewJobs so each run returns only what is new.
• Rows the Actor cannot read are logged and skipped, never charged — check the run log if a count looks low.

Automate & schedule

Run this Actor on autopilot and pull results into your own stack:

• Apify API — start runs, fetch datasets and manage schedules over REST.
• apify-client for JavaScript and apify-client for Python — official SDKs.
• Schedules — run it on a cron to keep your data fresh.
• Webhooks — trigger downstream actions the moment a run finishes.

JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'MY_APIFY_TOKEN' });
const run = await client.actor('tindacloud/ats-job-search').call({
    "keywords": [
        "data engineer"
    ],
    "locations": [
        "Remote"
    ],
    "postedWithinDays": 7,
    "maxResults": 1000
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(`Got ${items.length} records`);

Python

from apify_client import ApifyClient

client = ApifyClient("MY_APIFY_TOKEN")
run = client.actor("tindacloud/ats-job-search").call(run_input={
    "keywords": [
        "data engineer"
    ],
    "locations": [
        "Remote"
    ],
    "postedWithinDays": 7,
    "maxResults": 1000
})

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

cURL — run and get the results in one request:

curl -X POST "https://api.apify.com/v2/acts/tindacloud~ats-job-search/run-sync-get-dataset-items?token=MY_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"keywords": ["data engineer"], "locations": ["Remote"], "postedWithinDays": 7, "maxResults": 1000}'

Integrate with any app

Connect the dataset to thousands of apps — no code required:

• Make — multi-step automation scenarios.
• Zapier — push new records straight into your CRM or sheet.
• n8n — self-hosted workflows.
• Slack — get notified when a run finishes or finds something new.
• Google Drive / Sheets — auto-export every run to a spreadsheet.
• Airbyte — pipe results into your data warehouse.
• GitHub — trigger runs from commits or releases.
• Webhooks — call your own endpoint when a run succeeds or fails.

Use with AI assistants (MCP)

The output is clean, LLM-ready JSON. Call this Actor from Claude, ChatGPT, Cursor or any agent framework through the Apify MCP server — ask your assistant to "find remote data engineer jobs posted this week on company career sites, only ones with a salary range" and let it run this Actor for you.

Agent-ready: autonomous payments (x402 & Skyfire)

This Actor is agent-ready — AI agents can discover it, run it and pay for it on their own. It uses pay-per-event pricing and limited permissions, so it qualifies for Apify's agentic payments:

• x402 — an open, HTTP-native payment protocol. Agents pay in USDC through the Apify MCP server — no Apify account needed.
• Skyfire — agent-to-service payments with pre-funded Skyfire tokens.

Building an AI agent, MCP tool or data pipeline? This Actor is ready to plug in and pay as it goes.

Ready-made examples

Open one, change the fields, press Start — nothing to configure:

• Search every Greenhouse and Lever job board
• Find jobs on Ashby and Workday by keyword
• Monitor company career pages for new roles
• Search remote startup jobs with salary

Frequently asked questions about scraping Greenhouse and Lever jobs

Do I need an API key or a login?

No. Paste your input, press Start. There is nothing to connect and no account on the target site to create.

How do I export the results?

Every run produces a dataset you can download as JSON, CSV, Excel, XML or HTML, or read through the Apify API from your own code. You can also connect it to Make, Zapier or n8n.

Can I run this on a schedule?

Yes. Apify schedules run it every hour, day or week without you being there. With the monitoring option on, you only get jobs that appeared since the last run.

Can I call it from Python or JavaScript?

Yes — the Apify API runs any Actor and returns the dataset, and the official Python and JavaScript clients wrap it in a few lines. AI agents can call it too, through Apify's MCP server.

What does it cost?

You pay per result, not per hour. Filters are applied before anything is charged, so narrowing the input directly lowers the bill. Pages that cannot be read are reported in the log and never charged.

Is this data public?

Everything collected here is what company career pages shows to anyone without logging in. Check the target site's terms and the rules that apply to you before using the data commercially.

Related scrapers

Other scrapers from the same maker, built the same way — no browser where it isn't needed, one flat price per result:

• LinkedIn Jobs Scraper
• SEEK Jobs Scraper
• Website Contact & Email Scraper

Disclaimer

This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by their respective owners. All trademarks mentioned are the property of their respective owners. "Greenhouse, Lever, Ashby and Workable" is named here only in a descriptive sense — to identify the publicly available website this Actor reads. It collects only publicly available information that anyone can see without logging in; you are responsible for making sure your use of the data complies with applicable laws, regulations and the terms of the source website.