Greenhouse Harvest API
Browse all Greenhouse APIsAgent-ready OpenAPI document · curated by JenticHR recruitingRecruiting Atsbasic11 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Read Greenhouse candidates, applications, jobs, departments, offices, users, and scheduled interviews for ATS automation.
Use for: List every candidate that applied to a specific job, Retrieve a candidate by id from Greenhouse, Find all applications attached to a candidate, List currently open jobs in our Greenhouse account
Not supported: Does not run payroll, store onboarding documents, or send interview invitations directly - use for reading recruiting data from Greenhouse only.
Jentic publishes the only available OpenAPI specification for Greenhouse Harvest API, keeping it validated and agent-ready. The Harvest API exposes the recruiting data model of a Greenhouse account - candidates, applications, jobs, departments, offices, scheduled interviews, and users - across 11 endpoints under harvest.greenhouse.io/v1. Authentication is HTTP basic, where the user portion is the Harvest API key and the password portion is left empty.
Install Jentic One Beta
Connect the Greenhouse Harvest API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Greenhouse Harvest API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgreenhouse.io%2Fgreenhouse-greenhouse" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgreenhouse.io%2Fgreenhouse-greenhouse" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Greenhouse Harvest API.
List and retrieve candidates from /candidates and /candidates/{id}
Read applications associated with candidates and jobs via /applications
Inspect open and archived jobs via /jobs
List the recruiters and hiring managers via /users
Retrieve the upcoming scheduled interviews via /scheduled_interviews
Map the company's departments and offices via /departments and /offices
Use Cases
Patterns agents use Greenhouse Harvest API for, with concrete tasks.
★ ATS Data Sync into a Data Warehouse
People analytics teams pull Harvest data on a schedule into a data warehouse to build hiring funnel dashboards, time-to-hire reports, and diversity analyses. The /candidates, /applications, and /jobs endpoints together provide the canonical data set for funnel reporting.
Iterate /candidates with pagination over the last 30 days and load the records into a warehouse table
Interview Scheduling Notifications
Recruiting coordinators run automation that polls /scheduled_interviews to detect newly booked interviews and post reminders into a chat tool with the candidate name, role, and panel. The endpoint returns interview times and panellist information needed to compose the message.
GET /scheduled_interviews for the next 24 hours and post each one to the recruiting chat channel
Job and Department Reference Data Refresh
HRIS integrations refresh local mirrors of Greenhouse jobs, departments, and offices on a daily cadence so that downstream tools stay accurate. Each endpoint accepts pagination so that large catalogues can be retrieved in batches.
Page through /jobs, /departments, and /offices and replace the local reference tables with the latest Greenhouse data
Agent-Driven Recruiting Assistant via Jentic
An AI recruiting assistant uses Jentic to discover the right Harvest endpoint when a recruiter asks 'who applied to the senior backend role?' or 'what interviews are tomorrow?'. Jentic injects the basic auth credentials from the vault and the agent works against structured Greenhouse data.
Search Jentic for 'list greenhouse candidates by job', load the schema, and execute /candidates filtered by job_id
Key Endpoints
11 endpoints — jentic publishes the only available openapi specification for greenhouse harvest api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/candidates
List candidates
GET
/candidates/{id}
Retrieve a candidate by id
GET
/applications
List applications
GET
/jobs
List jobs
GET
/users
List recruiter users
GET
/scheduled_interviews
List scheduled interviews
GET
/departments
List departments
GET
/offices
List offices
GET
/candidates
List candidates
GET
/candidates/{id}
Retrieve a candidate by id
GET
/applications
List applications
GET
/jobs
List jobs
GET
/users
List recruiter users
GET
/scheduled_interviews
List scheduled interviews
GET
/departments
List departments
GET
/offices
List offices
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Greenhouse Harvest API by hand means base64-encoding its basic-auth key, pointing at the harvest.greenhouse.io host, and mapping the candidate, application, job, and interview endpoints yourself. Through Jentic you install once, import the Greenhouse Harvest API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Greenhouse Harvest puts the candidate id in the URL path (/candidates/{id}), so a rule can pin your agent to one candidate: it can read that candidate's record and nothing else. You choose the operations it may call, and since this scope is read-only recruiting data, it stays within the reads you allow.
Credential isolation
Your Greenhouse Harvest key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get a candidate's applications' or 'list open jobs', and Jentic returns the matching Greenhouse Harvest operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Greenhouse Harvest API through Jentic.
Why is there no official OpenAPI spec for Greenhouse Harvest API?
Greenhouse documents the Harvest API in their developer portal but does not publish a maintained OpenAPI 3 file for tooling. Jentic generates and maintains this spec so that AI agents and developers can call Greenhouse Harvest API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Greenhouse Harvest API use?
The Harvest API uses HTTP basic authentication. The username portion is the Harvest API key issued from the Greenhouse account settings, and the password portion is left empty. Through Jentic the API key is held in the encrypted vault and the basic auth header is built per call.
Can I list every application associated with a candidate?
Yes. GET /candidates/{id} returns the candidate including their applications, and GET /applications can be filtered by candidate_id or job_id to retrieve the application list directly. Pagination uses the standard Harvest per_page and page query parameters.
What are the rate limits for the Greenhouse Harvest API?
Greenhouse enforces a default Harvest rate limit of 50 requests per 10 seconds per API key, with burst behaviour. Exceeding the limit returns HTTP 429 with a Retry-After header. Jentic propagates the 429 so the agent can back off rather than hammer the limit.
How do I retrieve upcoming scheduled interviews through Jentic?
Search Jentic for 'list greenhouse scheduled interviews', load the operation that maps to GET /scheduled_interviews, and execute it with optional starts_after and ends_before filters. The response lists interview times and panellists which the agent can render into a chat reminder.
Does the API let me post a new candidate or schedule an interview?
The 11 endpoints in this spec are read-style operations. Greenhouse provides a separate Ingestion API for creating candidates from sourcing tools and the Harvest API itself supports additional write endpoints under specific permissions. Confirm with your Greenhouse account admin which scopes are enabled before relying on writes.
Can I limit what my agent is allowed to do with the Greenhouse Harvest API?
Yes. Because you run Jentic One yourself, your own rules decide which Harvest operations and which stored key the agent may use, so you can allow only reads like GET /candidates, GET /applications, or GET /scheduled_interviews and block the rest. Since the candidate id sits in the URL path at /candidates/{id}, a rule can pin the agent to a single candidate, letting it read that record and nothing else. The scope you grant covers read-only recruiting data such as candidates, jobs, departments, offices, and users, so the agent stays within the endpoints you have permitted.
GET STARTED