Can AI agents automate Greenhouse?

Greenhouse Harvest is automatable today through the Harvest v3 REST API. This record is Greenhouse Recruiting Harvest, not Teamtailor, Webcruiter, EasyCruit, Jobbnorge, the Job Board API, or Greenhouse Onboarding. Custom integrations mint a Bearer JWT at https://auth.greenhouse.io/token with OAuth 2.0 client credentials (Client ID and secret created as Harvest V3 (OAuth) credentials; an integration service user is attached unless sub names another user). Partners must use the authorization-code grant after a signed partnership agreement; partner access tokens last one hour and refresh tokens last 24 hours. Calls go to https://harvest.greenhouse.io/v3 with Authorization Bearer. Documented write coverage includes creating jobs from a template and creating, updating, hiring, rejecting, moving, and deleting applications. List endpoints require a Site Admin authorizing user. Private notes, salary, and offers need the matching advanced permission. Harvest is available on Core, Plus, and Pro. Harvest v1/v2 Basic auth was scheduled for removal after 2026-08-31; opened v1 docs still carry that deprecation banner, and Greenhouse states OAuth is the lasting Harvest method. Official PHP tools (grnhse/greenhouse-tools-php v3) wrap Harvest v3 OAuth. Recruiting webhooks POST signed JSON over HTTPS. Greenhouse also documents a first-party remote MCP server (Open Beta) at https://mcp.greenhouse.io/mcp and https://mcp.us.greenhouse.io/mcp. It is a permissioned subset of Harvest v3 for Core, Plus, and Pro, with Site Admin scopes in Dev Center, OAuth 2.0 PKCE, default read-only scopes, writes when admins enable them, DELETE permanently blocked, and US-only hosting. A Greenhouse CLI was not established. iPaaS connectors were not opened. Computer-use viability is unassessed. API scores 8 and MCP scores 6. API is the best path because it is the complete Harvest control plane and does not depend on the MCP beta or a signed-in user session.

Best path today: api · Overall automatability: 8/10