Greenhouse Harvest API
Browse all Greenhouse APIs40
AI ReadinessFoundational (D-)40/100
Agent-ready OpenAPI document · curated by JenticHR recruitingRecruiting Atsbasic20 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Retrieve candidate profiles, advance or reject applications, access interview scorecards, and query job and department data from a Greenhouse account.
Use for: I need to retrieve a candidate's application details, I want to advance an application to the next interview stage, List all open jobs in the Engineering department, Retrieve interview scorecards for a specific candidate
Not supported: Does not handle job board posting distribution, employee onboarding, payroll, or HRIS functions - use for recruiting data export and candidate pipeline management only.
Jentic publishes the only available OpenAPI specification for Greenhouse Harvest API, keeping it validated and agent-ready. Export and manage recruiting data across 20 endpoints covering candidates, applications, jobs, interviews, scorecards, and organizational structure. Advance or reject applications programmatically, retrieve structured interview scorecards, and access department and office hierarchies for reporting.
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-harvest" | 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-harvest" | 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.
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
Query open jobs with department, office, and hiring team associations
Access organizational hierarchy through departments and offices endpoints
Pull scheduled interview details including date, interviewers, and location
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
GET
/jobs
List all jobs
GET
/scorecards
List interview scorecards
GET
/scheduled_interviews
List scheduled interviews
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
G
Greenhouse Harvest API
- Foundational (D-)40/100
85
Foundational Compliance63
Developer Experience & Jentic Compatibility47
AI-Readiness & Agent Experience94
Agent Usability10
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
85
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
42%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
47
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
28%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
61%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
10
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
10%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>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, scorecard, 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 application id in the URL path (/applications/{id}/advance, /applications/{id}/reject), so a rule can pin your agent to one application: it can read that application's stage and nothing else. You choose the operations it may call, so ones like advancing or rejecting an application are not included unless you add them.
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 'export candidates in a pipeline' or 'read an application's scorecards', 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 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 with Jentic One, the self-hosted execution layer.
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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer.
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.
Can I limit what my agent is allowed to do with the Greenhouse Harvest API?
Yes. Jentic One is self-hosted, so you run it and your own rules decide which Greenhouse Harvest operations and credentials your agent may use. Because the application id sits in the URL path, such as /applications/{id}/advance and /applications/{id}/reject, a rule can pin the agent to a single application and let it read that application's stage and nothing else. Write operations like advancing or rejecting an application are only callable if you explicitly add them, so a read-only agent stays limited to endpoints like GET /candidates and GET /scorecards.
GET STARTED