Greenhouse API
Greenhouse runs six first-party APIs, led by the Harvest REST API over the full ATS object model, plus Job Board, Onboarding, Ingestion, Assessment, and Audit Log surfaces. Keys are issued in-product; Harvest v3 moves to OAuth 2.0. Harvest v1 and v2 retire on August 31, 2026.
Frequently asked questions
Greenhouse scores A+ on Supergood's API Report Card. Greenhouse runs six first-party APIs, led by the Harvest REST API over the full ATS object model, plus Job Board, Onboarding, Ingestion, Assessment, and Audit Log surfaces. Keys are issued in-product; Harvest v3 moves to OAuth 2.0. Harvest v1 and v2 retire on August 31, 2026.
Greenhouse has a workable official integration path. Most engineering teams can build against it directly. Open API: self-serve, documented, with SDKs
Greenhouse is the modern structured-hiring applicant tracking system + talent acquisition suite, founded in 2011 in New York City by Daniel Chait (CEO) and Jon Stross (President), both serial founders out of the NYC enterprise-software scene, and built explicitly to operationalize Laszlo Bock-style 'structured hiring' (predefined scorecards, calibrated interview kits, interview-kit-driven evaluation, anti-bias workflow) at SaaS-era scale rather than retrofitting it onto a legacy applicant database.
Vertical: Enterprise / HR / ERP, specifically the applicant tracking / talent acquisition slice (Sanity vertical: Enterprise/HR/ERP; Airtable bucket: misc). Open requisitions, approval workflows, headcount tracking, job templates. Post jobs to a Greenhouse-hosted careers site + syndicate to LinkedIn, Indeed, Glassdoor, ZipRecruiter, Built In, and 200+ job boards.
Very high inside modern tech / SaaS / fintech / consumer internet talent-acquisition stacks; high in mid-market and lower-enterprise overall; the default ATS brand-name reference for 'modern structured-hiring ATS' the way Salesforce is for CRM.
Candidates: deduplicated person records, contact info, source, owner, tags, custom fields, attachments (resumes, cover letters). Applications: the formal application linking a Candidate to a Job, with status, current stage, rejection reason, source, EEO responses, custom fields.
Founded 2011 in NYC, ~14-15 years old as of 2026. Cloud-native multi-tenant SaaS from day one; built on a Ruby on Rails backend with a modern JSON REST API surface and a React-style frontend.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Greenhouse has partial MCP support. Greenhouse has not published an official MCP server. The community open-greenhouse-mcp project is actively maintained, ships on PyPI, and covers the Harvest API with read only and write profiles.
Partially. MCP support for Greenhouse exists but is incomplete, so what MCP clients like Claude, Cursor, and Codex can reach depends on what the available server covers.