Greenhouse Harvest API

Name: Greenhouse Harvest API
Brand: Greenhouse Harvest API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingRecruiting Atsbasic20 EndpointsREST

For Agents

Retrieve candidate profiles, advance or reject applications, access interview scorecards, and query job and department data from a Greenhouse account.

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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Search candidates by name, email, or application status across all jobs

Advance applications through interview stages or reject with configurable reasons

Retrieve structured interview scorecards with ratings and interviewer comments

GET STARTED

Start building with Greenhouse Harvest API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Greenhouse Harvest API for, with concrete tasks.

★ AI Agent Hiring Pipeline Automation

AI agents use the Greenhouse Harvest API through Jentic to automate hiring decisions without direct Greenhouse credentials. An agent searches for 'advance application to next stage', loads the schema for the advance endpoint, and moves qualified candidates forward based on scorecard ratings. The reject endpoint handles automated declinations with configurable reason codes.

Retrieve all applications for job ID J001 in the 'Technical Screen' stage, check their scorecard ratings, and advance those with average rating above 4 to 'On-Site'

Candidate Data Export

Export structured candidate data for analytics, compliance reporting, or syncing with downstream HRIS systems. The candidates endpoint returns profile information, application history, and current status across all jobs. Paginated responses support incremental sync patterns for large candidate databases without overwhelming system resources.

Retrieve all candidates who applied in the last 30 days and return their name, email, current application stage, and applied job title

Interview Scorecard Analysis

Access structured interview feedback through the scorecards endpoint to aggregate ratings, identify patterns in interviewer assessments, and generate hiring committee summaries. Each scorecard includes the interviewer, rating scales, attribute scores, and free-text comments tied to a specific interview for a candidate.

Retrieve all scorecards for candidate ID C001 and calculate the average overall rating across all interviewers

Job and Department Reporting

Build organizational hiring reports by querying jobs with their department and office associations. The jobs endpoint returns hiring team members, opening count, and status while departments and offices provide the org structure. Combined queries enable headcount planning dashboards and time-to-fill metrics by department.

List all open jobs grouped by department and return the job title, number of openings, and days since posting for each

Key Endpoints

20 endpoints — jentic publishes the only available openapi specification for greenhouse harvest api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/candidates

List all candidates

GET

/candidates/{id}

Get a specific candidate

GET

/applications

List all applications

POST

/applications/{id}/advance

Advance an application to next stage

POST

/applications/{id}/reject

Reject an application

GET

/jobs

List all jobs

GET

/scorecards

List interview scorecards

GET

/scheduled_interviews

List scheduled interviews

GET

/candidates

List all candidates

GET

/candidates/{id}

Get a specific candidate

GET

/applications

List all applications

POST

/applications/{id}/advance

Advance an application to next stage

POST

/applications/{id}/reject

Reject an application

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Greenhouse Harvest API tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw Harvest tokens never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'advance application to next interview stage') and Jentic returns matching Greenhouse Harvest operations with their input schemas, so the agent can call the right endpoint without reading Greenhouse's developer docs.

Time to first call

Direct Greenhouse integration: 2-3 days for token setup, pagination handling, and webhook configuration. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Greenhouse Harvest API through Jentic.

Why is there no official OpenAPI spec for Greenhouse Harvest API?

Greenhouse does not publish an OpenAPI specification for the Harvest API. 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 at https://app.jentic.com/sign-up.

What authentication does the Greenhouse Harvest API use?

The API uses HTTP Basic authentication with your Harvest API token as the username and an empty password. Tokens are generated per-user in Greenhouse settings with configurable permission scopes. Through Jentic, the Harvest API token is stored in the MAXsystem vault so agents authenticate without handling the raw token.

Can I advance or reject applications through the Greenhouse Harvest API?

Yes. POST /applications/{id}/advance moves an application to the next configured stage in the job's interview plan. POST /applications/{id}/reject marks an application as rejected with an optional rejection reason ID and email notification flag. Both operations require the application ID and appropriate API token permissions.

What are the rate limits for the Greenhouse Harvest API?

Greenhouse enforces a rate limit of 50 requests per 10 seconds for the Harvest API. Exceeding this returns HTTP 429 with a Retry-After header. List endpoints support pagination via the per_page parameter (max 500) and Link headers for cursor-based traversal of large result sets.

How do I retrieve interview scorecards through Jentic?

Search Jentic for 'get interview scorecards for candidate', load the schema for GET /scorecards with the application_id filter parameter, and execute. The response includes each scorecard's overall recommendation, attribute ratings, and interviewer comments. Install with pip install jentic and authenticate at https://app.jentic.com/sign-up.

What candidate data can I access through the Harvest API?

GET /candidates returns candidate profiles including name, email addresses, phone numbers, tags, and linked applications. GET /candidates/{id} provides full detail for a single candidate. The applications sub-resource shows which jobs they applied to, their current stage, and rejection status if applicable.

Greenhouse Harvest API

Connect the Greenhouse Harvest API to your agent

Capabilities

Start building with Greenhouse Harvest API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs