Greenhouse Recruiting API
Enterprise ATS with multiple REST APIs (Harvest for data access, Job Board for public postings, Onboarding for new hire workflows) enabling deep recruiting process automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
SOC 2 Type II certified, GDPR compliant. Basic Auth with API key is functional but dated — no OAuth or token scoping. Separate API keys per API family reduces cross-API blast radius but adds credential management overhead.
⚡ Reliability
Best When
Your enterprise organization uses Greenhouse and you need deep, read-heavy integration into candidate data, structured interview feedback, or onboarding workflow automation.
Avoid When
You need a developer-friendly modern ATS with self-serve API access — Greenhouse's API surface is broad but enterprise-gated, and the multiple API families add integration complexity.
Use Cases
- • Extracting full candidate pipeline and interview feedback data for analytics
- • Syncing job postings to external boards and career pages via Job Board API
- • Automating new hire onboarding task assignment via the Onboarding API
- • Building HR agent workflows that track candidate status and trigger actions on stage changes
Not For
- • Companies not using Greenhouse ATS
- • Small companies needing a lightweight ATS — Greenhouse is enterprise-priced
- • Real-time streaming of candidate events (webhook-based, not streaming)
Interface
Authentication
Harvest API uses HTTP Basic Auth with API key as username and empty password. Job Board API is public (no auth). Onboarding API uses a separate API key. No OAuth or scoped tokens — each API key has full access to its respective API.
Pricing
No public pricing. All plans require a sales engagement and annual contract.
Agent Metadata
Known Gotchas
- ⚠ Three separate APIs (Harvest, Job Board, Onboarding) with different auth mechanisms require agents to manage multiple credentials and base URLs.
- ⚠ No idempotency — creating candidates or applications twice produces duplicates; external deduplication is required.
- ⚠ Pagination uses Link headers (RFC 5988) rather than a cursor in the response body — less common pattern that many agent frameworks don't handle out of the box.
- ⚠ Webhook payloads are not signed by default on all event types; agents should validate IP allowlisting or payload signatures where available.
- ⚠ Read-heavy API design — many write operations are not available via API and must be done in the Greenhouse UI.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Greenhouse Recruiting API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-06.