Greenhouse, Lever, Ashby & Workday Jobs API — Verified Fresh Directory | $1/1K

Every coverage and freshness claim on this page is verifiable: our full company directory with per-company last-validated timestamps is public — live coverage & freshness stats. No other jobs actor lets you check whether a company is covered before you pay.

Normalized job postings straight from the public JSON endpoints of Greenhouse, Lever, Ashby and Workday — the same data employers publish for distribution. No browser, no proxies, no login, no LLM guesses. One clean schema across all four ATS.

Why this actor

	This actor	bovi	memo23 (multi-ATS)	fantastic-jobs (flagship)
Price per 1,000 jobs	$1.00	$1.50	$2.00	$4.00
Actor-start fee	none	none	$0.03/GB per run	$0.01+ per start
Empty run cost	$0 in events (seconds of platform usage only)	$0	start fee still charged	start fee still charged
Company directory	19,700+ verified-live boards / 1.25M open jobs — public, timestamped	4 static preset lists	none (bring your own slugs)	200k claimed — not verifiable, not public
Freshness proof	public per-company timestamps	none	none	marketing claims only
Delta mode (new/closed jobs)	yes	new only	no	time-window filters
Workday coverage	yes	no	yes	yes ($4/1k)
Salary fields	structured ATS data only (no AI guesses)	passthrough	regex	AI-extracted ("might have some errors" — their words)
Recruiter emails / person data	never (GDPR-clean by design)	no	"emails" = info@ addresses	hiring-manager names+emails

Scheduled monitoring runs are where start fees hurt: 30 daily runs/month of a 50-company watchlist cost $0 extra here.

Quick start (zero config)

Run with defaults: the top-tech preset fetches verified-live boards, capped at 50 jobs per company — a first run costs under $0.10. Then bring your own companies:

{
  "companies": ["stripe", "lever:netflix", "https://jobs.ashbyhq.com/linear"],
  "titleKeyword": "devops",
  "remoteOnly": true
}

Bare slugs are looked up across Greenhouse/Lever/Ashby automatically. Board URLs work as-is — including Workday career sites (https://acme.wd5.myworkdayjobs.com/careers or explicit workday:acme|wd5|careers).

Workday notes (v0.2): postings come from the same JSON endpoint the career site itself uses. posted_at is approximated from Workday's relative dates (flagged in parse_warnings); descriptions are not available at list level; per-tenant scans are capped (max 300 jobs) to keep runs fast — see parse_warnings for details.

Output (one schema for all three ATS)

{
  "global_id": "greenhouse:anthropic:5222180008",
  "ats": "greenhouse",
  "company_slug": "anthropic",
  "company_name": "Anthropic",
  "title": "DevOps Engineer",
  "department": "Platform",
  "team": null,
  "location_raw": "Madrid, Spain",
  "remote_type": "remote",
  "employment_type": "full_time",
  "salary": {"min": 60000, "max": 80000, "currency": "EUR", "period": "per-year-salary"},
  "posted_at": "2026-06-20T12:00:00+00:00",
  "updated_at": "2026-07-01T14:00:00+00:00",
  "absolute_url": "https://job-boards.greenhouse.io/anthropic/jobs/5222180008",
  "source_url": "https://boards.greenhouse.io/anthropic",
  "parse_warnings": []
}

• salary is filled only from structured ATS fields (Lever salaryRange, Ashby compensation tiers). We never invent numbers with AI.
• remote_type comes from the ATS's own flags where available (Lever workplaceType, Ashby isRemote), with a conservative location fallback.
• Descriptions (description_text/description_html) are off by default — enable includeDescriptions when you need them.
• Something unparseable? It lands in parse_warnings, never silently dropped.

Delta mode — monitor hiring, don't re-buy the firehose

Set onlyNewSinceLastRun: true and the actor remembers what it has seen (per your account): you get only new postings, plus delta_status: "closed" records when a previously seen job disappears. Hiring-signal data at job-scraper prices.

Honest failure modes

• A run that returns 0 jobs always tells you why in the status message (dead slugs? filters too narrow? nothing new since last run?) — and charges nothing.
• Per-board failures are listed in RUN_SUMMARY.failedTargets with reasons.
• Dead companies get pruned from the public directory daily — check it before running.

Legal & fair use

This actor reads officially public, unauthenticated job-board endpoints (Greenhouse Job Board API, Lever Postings API, Ashby Posting API) — data employers publish precisely so it spreads. Workday postings are read from the same public JSON endpoint the employer's career site itself uses — unauthenticated, conservative ≤1 req/s per tenant, and any block is treated as a hard stop for that tenant. Polite rate limits are enforced per host (Lever's robots.txt Crawl-delay honored). Output contains no personal data — no recruiter names, no emails. Takedown/opt-out: open an issue.

Use with AI agents (MCP) — dedicated endpoint

This actor is an MCP server (standby mode, streamable HTTP):

https://zon4a--ats-jobs-api.apify.actor/mcp

Authenticate with your Apify token (Authorization: Bearer <APIFY_TOKEN>). Tools:

• search_jobs — companies + filters → normalized postings (charged at the same $1/1K as batch runs; results also land in your dataset)
• check_company — free live coverage check: which boards a company has right now and how many open jobs on each

Alternatively, use the official Apify MCP server and call zon4a/ats-jobs-api as a generic actor tool.

Roadmap

• Directory-wide monitoring mode: one scheduled run watching the whole directory
• SmartRecruiters / Personio / Recruitee filters (already in our catalog)