Greenhouse
Greenhouse is an applicant tracking system (ATS) and recruiting software platform. It exposes a family of APIs and webhooks that let partners and customers manage candidates, jobs, applications, onboarding, audit logs, and assessment integrations.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Greenhouse the way a machine reads it — 31 machine-readable artifacts across 16 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Greenhouse scores 41.3/100 (thin), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Greenhouse
Each block below is one kind of artifact we hold for Greenhouse. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 16
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Greenhouse Assessment API
The Assessment Partner API enables assessment platforms (code testing, video interviewing, personality testing) to seamlessly integrate with the Greenhouse interview workflow.
Greenhouse Audit Log API
The Audit Log API offers a record of important events, providing insight into who accessed or edited information in Greenhouse.
Greenhouse Recruiting Webhooks
Recruiting Webhooks deliver event notifications for Greenhouse Recruiting activities such as candidate updates, application stage changes, and offers.
Greenhouse Onboarding Webhooks
Onboarding Webhooks deliver event notifications for Greenhouse Onboarding activities such as new hires and employee updates.
Greenhouse Applications API
The Applications API from Greenhouse — 5 operation(s) for applications.
Greenhouse Candidates API
The Candidates API from Greenhouse — 2 operation(s) for candidates.
Greenhouse Departments API
The Departments API from Greenhouse — 2 operation(s) for departments.
Greenhouse Education API
The Education API from Greenhouse — 3 operation(s) for education.
Greenhouse Graphql API
The Graphql API from Greenhouse — 1 operation(s) for graphql.
Greenhouse Greenhouse Job Board API API
The Greenhouse Job Board API API from Greenhouse — 1 operation(s) for greenhouse job board api.
Greenhouse Jobs API
The Jobs API from Greenhouse — 3 operation(s) for jobs.
Greenhouse Offices API
The Offices API from Greenhouse — 3 operation(s) for offices.
Greenhouse Prospects API
The Prospects API from Greenhouse — 1 operation(s) for prospects.
Greenhouse Sections API
The Sections API from Greenhouse — 2 operation(s) for sections.
Greenhouse Tracking API
The Tracking API from Greenhouse — 1 operation(s) for tracking.
Greenhouse Users API
The Users API from Greenhouse — 3 operation(s) for users.
Scroll within the panel for all 16 ·
Open Collections 4
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Greenhouse Harvest API
OPEN COLLECTIONGreenhouse Candidate Ingestion API
OPEN COLLECTIONGreenhouse Job Board API
OPEN COLLECTIONGreenhouse Onboarding API
OPEN COLLECTIONGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Greenhouse GraphQL API
A GraphQL API for Greenhouse Onboarding. Provides queries and mutations for employees, departments, locations, custom fields, teams, and pending hires.
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Greenhouse Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Greenhouse Finops
FINOPSSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Greenhouse API Rules
SPECTRALJSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Greenhouse Structure
JSON STRUCTURESecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Greenhouse — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/greenhouse · machine-readable index on apis.io