ATS Jobs Scraper: Greenhouse, Lever, Ashby Job Postings

Job postings from Greenhouse, Lever and Ashby (plus Workable, Recruitee and SmartRecruiters) by company domain. Get every open job with its apply link, and monitor new and closed postings between runs as hiring signals for lead enrichment.

Start with a verified example

Open the Python quickstart. Includes a runnable one-target input, actual owner-run output from October 28, 2026, Python with an explicit spending cap, and source limits. Owner tests are not customer outcomes.

{
  "companies": [
    "linear.app"
  ],
  "output_mode": "jobs_and_summary",
  "max_jobs_per_company": 3,
  "track_diff": false
}

The example cap is $0.06 in event charges, not a quoted run price. Review the live Pricing tab. The guide does not run the Actor or request your token.

Who is hiring, for what, and what changed since yesterday? Give this Actor a company domain and it returns the company's open jobs and a compact hiring summary, straight from the company's own job board.

It supports six applicant tracking systems (ATS) and detects the right one automatically:

Greenhouse · Lever · Ashby · Workable · Recruitee · SmartRecruiters

No browsers and no proxies. Data comes from the public ATS JSON APIs, so a typical company takes a few seconds.

What you can ask it

• "How many open jobs does stripe.com have, and in which departments?"
• "Which of these 50 companies opened new engineering roles since the last run?"
• "Does ramp.com hire for Kubernetes or LLM skills?"
• "List remote data-engineering jobs at these companies."
• "Which jobs did linear.app close this week?"

What it is good for

• Sales intelligence: new roles in a department are a buying signal.
• Recruiting and talent teams: watch competitors' hiring.
• Market and investment research: track hiring growth and tech-stack adoption.
• AI agents: small, filterable, well-described output that fits in a context window.

Input

Only companies is required.

Field	Type	Default	Description
companies	array of strings	required	Domains (stripe.com) or board slugs (stripe). Prefix to force an ATS: greenhouse:stripe, lever:spotify, ashby:linear, workable:huggingface, recruitee:bunq, smartrecruiters:BoschGroup.
output_mode	string	jobs_and_summary	jobs_and_summary, summary_only (smallest output) or jobs_only.
track_diff	boolean	true	Compare with the previous run and set status to NEW / EXISTING / CLOSED.
state_id	string	default_state	Name of the saved history. Runs sharing a state_id are compared with each other.
extract_tech_keywords	boolean	true	Detect technologies in job titles and descriptions.
only_changes	boolean	false	Return only NEW and CLOSED jobs.
title_keywords	array of strings		Keep jobs whose title contains any of these.
departments	array of strings		Keep jobs whose department contains any of these.
locations	array of strings		Keep jobs whose location contains any of these.
technologies	array of strings		Keep jobs that mention any of these technologies.
remote_only	boolean	false	Keep remote jobs only.
max_jobs_per_company	integer	0	Cap on job records per company. 0 = no limit. NEW jobs are kept first.

Filters only reduce which job records are returned. Change tracking and the company summary always cover all of the company's jobs.

Example: quick hiring signal for an agent

{
    "companies": ["stripe.com", "ramp.com", "linear.app"],
    "output_mode": "summary_only"
}

Example: daily monitor of new engineering jobs

{
    "companies": ["stripe.com", "ramp.com", "linear.app"],
    "only_changes": true,
    "title_keywords": ["engineer"],
    "state_id": "eng-watchlist"
}

Output

The dataset holds two kinds of records, told apart by record_type.

company_summary — one per company

{
    "record_type": "company_summary",
    "company_domain": "linear.app",
    "ats_type": "ashby",
    "board_slug": "linear",
    "total_active_jobs": 31,
    "remote_jobs": 31,
    "is_first_run": false,
    "new_jobs": 2,
    "closed_jobs": 1,
    "new_job_titles": ["Senior Product Engineer", "Enterprise Account Executive"],
    "closed_job_titles": ["Support Specialist"],
    "jobs_by_department": { "GTM": 15, "Product": 13, "Operations": 3 },
    "top_locations": { "North America": 19, "Europe": 8, "London": 2 },
    "top_technologies": { "React": 8, "TypeScript": 8, "GraphQL": 7 },
    "matching_jobs": 10,
    "scraped_at": "2026-10-13T13:17:26+00:00"
}

is_first_run: true means there was no saved history yet, so new_jobs equals all jobs and is a baseline, not a hiring spike.

job — one per job posting

{
    "record_type": "job",
    "company_domain": "stripe.com",
    "ats_type": "greenhouse",
    "job_id": "8172487",
    "title": "Abuse Investigator",
    "department": "Security Analytics",
    "location": "Dublin",
    "is_remote": false,
    "posted_date": "2026-09-03T13:30:34-04:00",
    "apply_url": "https://stripe.com/jobs/search?gh_jid=8172487",
    "detected_technologies": ["Databricks", "Pandas", "Python", "Spark", "SQL"],
    "status": "NEW",
    "scraped_at": "2026-10-13T12:08:14+00:00"
}

A human-readable report of the whole run is saved to the run's key-value store under OUTPUT_SUMMARY.md: companies processed, successes and failures, total active jobs, new and closed jobs, and a breakdown by ATS.

How change tracking works

• The first run for a company under a given state_id marks every job NEW.
• Later runs mark jobs EXISTING (seen before), NEW (first seen now) or CLOSED (seen before, gone now).
• A CLOSED job is reported once, then forgotten.
• If a company cannot be reached in a run, its history is left untouched, so nothing is falsely reported as closed.
• History lives in a named key-value store, ats-job-pulse-state, in your own Apify account.

To monitor continuously, put the Actor on an Apify Schedule (for example daily) and keep the same state_id.

How the job board is found

1. The slug (stripe from stripe.com) is checked against all six systems in parallel.
2. If nothing is found, the Actor fetches https://{domain}/careers (then /jobs) and follows any link or embed pointing to a supported system.

When several boards match, the one with the most open jobs is used.

Pricing

Pay per event: you are charged once per successfully processed company (event company-processed), whether it has 5 jobs or 5,000. Companies with no supported job board, invalid inputs and temporary failures receive no company-processed event. The listed Actor start event can still apply. Set a maximum cost per run and the Actor stops cleanly when it is reached.

Use from AI agents (MCP)

The Actor works with the Apify MCP server, so Claude, Cursor and other MCP clients can find it and call it as a tool:

https://mcp.apify.com/?actors=hirepulse/ats-job-pulse

Tips for agents:

• Start with "output_mode": "summary_only": one small record per company.
• When you need job records, narrow them with title_keywords, departments, technologies, remote_only and max_jobs_per_company.
• For "what changed" questions, reuse the same state_id and set only_changes to true.

Limitations

• Companies on other systems (Workday, iCIMS, Taleo, in-house career sites) are reported as not found and are not charged.
• SmartRecruiters publishes no job description in its listing, so technologies there are detected from the job title and job function only. At most 3,000 postings per company are read.
• SmartRecruiters slugs are case-sensitive and often not guessable (for example BoschGroup). Pass a domain whose careers page links to the board, or use the smartrecruiters: prefix.
• A bare slug can occasionally match a different company with the same name on another ATS. Use a prefix (lever:acme) when you need to be exact.
• Careers pages rendered entirely in JavaScript may not expose an ATS link to the fallback step; pass the slug directly in that case.
• Technology detection is keyword-based. A technology named in a company's standard "about us" text is counted for every job of that company.

Local development

pip install -r requirements-dev.txt
python -m pytest tests/test_local.py -v

Set ATS_LIVE_TESTS=1 to also run the tests that call the real ATS APIs.