Thursday, November 19, 2026
HomeSalesGreenhouse API Evaluation: Developer Deep Dive

Greenhouse API Evaluation: Developer Deep Dive [2026]


The query behind each ATS API integration is whether or not the floor goes deep sufficient to justify the dependency, or whether or not you’ll hit a wall three sprints in and need you had evaluated extra rigorously upfront.

Greenhouse maintains not one API however eight distinct APIs, every scoped to a selected integration sample: information entry, job board publishing, candidate ingestion, evaluation scoring, onboarding, audit logging, and two webhook channels.

The developer docs are public, the documentation supply is open on GitHub, and the endpoint permissions are granular sufficient that an admin can toggle entry per endpoint per API key. For a hiring platform serving 7,500+ corporations, that could be a mature developer floor.

However breadth and depth are completely different questions.

Greenhouse’s APIs are recruiting APIs. They learn and write hiring information: candidates, purposes, jobs, scorecards, affords, and onboarding data. In case your construct wants programmatic entry to an ATS, the floor covers the total hiring lifecycle with actual depth.

But when your integration wants B2B intelligence alongside hiring information (contact enrichment, firmographics, org charts, technographics, or purchaser intent indicators to tell sourcing and recruiting selections), that could be a completely different layer of the stack totally.

That is the place ZoomInfo enters the image: a GTM platform whose Enterprise API is a REST suite masking search, enrichment, AI intelligence, and viewers administration throughout 500M contacts and 100M corporations, with OAuth 2.0 authentication and an MCP server for AI-agent workflows.

The place Greenhouse’s API manages the hiring course of, ZoomInfo’s API offers the candidate and firm intelligence that feeds it.

This evaluate covers the Greenhouse API floor in full technical depth first, then critiques ZoomInfo’s API because the intelligence layer that picks up the place ATS information stops.

Greenhouse API at a Look

Attribute

Element

API kind

REST over HTTPS (Harvest, Job Board, Ingestion, Evaluation, Audit Log); GraphQL (Onboarding API)

Authentication

HTTP Primary Auth (Harvest), OAuth 2.0 or Primary Auth (Ingestion), JWT Bearer (Audit Log), HMAC-SHA256 (Webhooks)

Base URL

https://harvest.greenhouse.io/v1/ (Harvest API v1/v2); v3 at harvestdocs.greenhouse.io

Price limits

50 requests per 10 seconds (Harvest API default)

SDKs

Official wrappers for Ruby and PHP; no official Node.js, Python, Java, or Go SDKs

Webhooks

Sure, Recruiting Webhooks (GA) and Onboarding Webhooks (Beta)

Documentation

builders.greenhouse.io (open-source docs on GitHub)

Pricing / entry

Included in Greenhouse plans; API key provisioning through Dev Middle. Utilization past limits could incur extra charges

Greenhouse API: What Works Properly & What to Plan Round

What works properly

What to plan round

Eight scoped APIs masking the total hiring lifecycle

Recruiting scope solely: no contact enrichment, firm intelligence, or intent information

Per-endpoint permission granularity on each API key

Harvest API v1/v2 deprecated; removing scheduled August 31, 2026

Open-source documentation accepting neighborhood contributions

No official SDKs for Node.js, Python, Java, or Go

Webhook retry coverage is printed and express (7 retries over 15 hours)

Price restrict of fifty req/10s is modest for high-volume sync workloads

GraphQL Onboarding API permits exact information queries

Audit Log API restricted to Professional plan solely

A number of auth fashions matched to integration patterns (Primary, OAuth, JWT)

No interactive API explorer (Swagger/OpenAPI) or Postman assortment printed

Greenhouse API: Authentication & Getting Began

Greenhouse makes use of completely different authentication strategies throughout its APIs, every matched to the combination sample the API serves.

Harvest API (HTTP Primary Auth): The first data-access API makes use of HTTP Primary Authentication over HTTPS. The API key serves because the username; the password area stays clean. You Base64-encode : and cross it within the Authorization: Primary header. All requests should use HTTPS; HTTP returns a 403.

You provision API keys within the Greenhouse UI below Configure > Dev Middle > API Credential Administration. This requires the “Can handle ALL group’s API Credentials” developer permission. Permissions are endpoint-scoped: directors can grant or revoke entry per endpoint, giving fine-grained management over what every integration reads or writes.

A primary authenticated request appears like this:

curl “https://harvest.greenhouse.io/v1/candidates”

-H “Authorization: Primary $(echo -n ‘YOUR_API_KEY:’ | base64)”

Candidate Ingestion API (OAuth 2.0 or Primary Auth): The Ingestion API helps two authentication paths. For partner-to-user flows, OAuth 2.0 is most popular: companions register an utility with Greenhouse, obtain a client key and secret, and embody the ensuing bearer token as Authorization: Bearer .

OAuth scopes embody candidates.create, candidates.view, and jobs.view. For system-to-system submissions, Primary Auth is used alongside a compulsory On-Behalf-Of: header.

greenhouse-api-1

Supply: Greenhouse

Audit Log API (JWT Bearer Auth): The Audit Log API makes use of a two-step course of: a Harvest API key calls POST https://harvest.greenhouse.io/auth/jwt_access_token, which returns a JWT legitimate for twenty-four hours. That token authenticates all subsequent audit log requests.

Webhooks (HMAC Signature Verification): Recruiting Webhooks embody a Signature header containing a SHA-256 HMAC digest computed from the webhook’s secret key and the total JSON physique. Webhooks additionally assist elective HTTP Primary Auth credentials and {custom} headers for supply to secured endpoints.

One constraint price noting early: there is no such thing as a self-serve developer sandbox on Core or Plus plans. The developer sandbox and sync characteristic is accessible solely on the Professional tier.

Greenhouse API: Core Endpoints & Capabilities

The Harvest API is the first floor for studying and writing recruiting information. It covers the total lifecycle of a hiring course of, from job creation by supply administration.

Normal conventions: snake_case attribute names, ISO-8601 timestamps, null for lacking values, JSON responses, and a coverage of additive-only modifications (properties are by no means eliminated or renamed).

Candidates & Purposes

The candidate and utility sources kind the core of most integrations.

Candidates: Checklist, retrieve, create, edit, merge, and anonymize candidate data. You’ll be able to add notes, attachments, training entries, and employment historical past to any candidate. A prospect-to-candidate conversion endpoint handles the transition from sourced prospect to lively applicant with out creating a replica document.

Purposes: Checklist, retrieve, advance (transfer to the subsequent stage), transfer between phases inside a job or to a special job, reject, unreject, and rent. You’ll be able to add attachments per utility.

The advance and transfer operations are helpful for automated pipeline workflows: a scoring service can advance certified candidates robotically, or a scheduling integration can transfer candidates to an interview stage as soon as a slot is confirmed.

What you’d construct with this: a CRM-to-ATS sync that creates candidates when a sales-qualified lead turns into a recruiting prospect, or a screening service that advances or rejects candidates based mostly on evaluation scores.

Jobs, Job Posts & Openings

Jobs: Create, replace, and retrieve full job data together with hiring groups, {custom} fields, and related openings. The hiring group endpoint returns the total panel (recruiters, coordinators, hiring managers) for a given job.

Job Posts: Handle the public-facing illustration of a job, together with standing, {custom} location fields, and content material. The Job Board API offers a separate, read-only public floor for constructing {custom} profession pages and department-level job listings with out authentication.

Openings: Create, edit, and destroy openings inside a job. Openings characterize particular person headcount slots, which issues for organizations monitoring crammed versus accepted positions.

Interviews & Scorecards

Scheduled Interviews: Full CRUD on interview schedules, letting calendar integrations create and handle interview slots programmatically.

Scorecards: Retrieve scorecards per utility, giving downstream methods entry to interviewer evaluations. The Evaluation API extends this: evaluation platforms can push scorecard information again into Greenhouse in the identical format as human interviewers, so automated evaluation outcomes sit alongside guide evaluations within the candidate profile.

greenhouse-api-2

Supply: Greenhouse

Provides & Approvals

Provides: Checklist, retrieve the present supply for an utility, and replace supply particulars. The supply endpoints matter for HRIS integrations that want to tug compensation information and begin dates as soon as an organization extends a suggestion.

Approvals: Retrieve approval flows, request approvals, exchange approvers, and handle pending approvals per consumer. Approval workflows in Greenhouse are configurable and multi-stage, so the API floor handles the total approval chain.

Customers, Customized Fields & Reference Knowledge

Customers: Create, allow, and disable consumer accounts. Change permission ranges and handle each present and future job-level permissions programmatically.

Customized Fields: Full CRUD on {custom} area definitions and their choices, letting integrations lengthen the Greenhouse information mannequin with out guide configuration.

Reference information: Departments, places of work, tags, sources, monitoring hyperlinks, electronic mail templates, rejection causes, and demographic information (EEOC query units and solutions) are all accessible for reporting and compliance integrations.

Audit Log API

The Audit Log API exposes a single GET /occasions endpoint returning a 30-day rolling log of entry and configuration occasions. You’ll be able to filter by performer IDs, performer varieties, performer IP addresses, occasion varieties, occasion goal IDs, occasion goal varieties, request IDs, and request varieties.

That is the endpoint compliance groups care about most, and it’s restricted to the Professional plan.

Greenhouse API: Webhooks & Occasions

Greenhouse’s Recruiting Webhooks push occasion notifications masking the total hiring lifecycle.

Webhook configuration requires a reputation, an HTTPS endpoint URL, and a secret key for HMAC signature era. On save, Greenhouse pings the endpoint; if the ping fails, the webhook is created in a disabled state.

The occasion catalogue spans 4 classes:

Software occasions: utility created, deleted, up to date; supply created, accepted, up to date, deleted; prospect created.

Candidate occasions: candidate deleted, employed, merged, stage change, unhired, rejected, unrejected, up to date, anonymized.

Interview occasions: interview deleted, scorecard deleted.

Job occasions: job created, deleted, up to date, accepted; job put up created, up to date, deleted; job stage deleted.

Group occasions: division deleted, workplace deleted.

Every supply features a Greenhouse-Occasion-ID header for idempotency monitoring. Payloads share widespread attributes together with utility.id, utility.standing (certainly one of rejected, employed, lively), utility.candidate.id, and a custom_fields hash map.

Retry coverage: On supply failure, Greenhouse retries as much as 7 instances over about 15 hours with exponential backoff: 1 min, 15 min, 60 min, 120 min, 240 min, 480 min. The printed retry schedule is express sufficient to design your receiver round.

Onboarding webhooks are a separate channel, presently in beta. They hearth worker:up to date occasions with HMAC-SHA256 authentication and a 7-attempt retry coverage.

What you’d construct with this: a real-time integration that pushes candidate-hired occasions to your HRIS, triggers onboarding workflows on supply acceptance, syncs stage-change occasions to a BI dashboard, or alerts a Slack channel when somebody submits a scorecard.

Greenhouse API: SDKs, Docs & Price Limits

SDKs & Libraries

Greenhouse publishes official libraries below the grnhse GitHub group:

  • PHP: greenhouse-tools-php, offering 4 service courses: Job Board Service, Job API Service, Software Service, and Harvest Service

  • Ruby (OAuth): omniauth-greenhouse for Greenhouse OAuth flows (MIT license, final up to date January 2026)

Two languages is slim protection. There are not any official Node.js, Python, Java, or Go SDKs. Third-party neighborhood libraries exist however Greenhouse doesn’t preserve them. For many fashionable integration stacks (Node.js and Python specifically), you’re making direct HTTP calls and proudly owning the auth, retry, and error-handling layer your self.

Documentation & Developer Expertise

The developer portal at builders.greenhouse.io makes use of a two-column structure: narrative documentation on the left, code examples (cURL and Ruby) switchable through tabs on the proper. Each endpoint contains request/response schemas and instance payloads.

Three issues stand out in regards to the developer expertise:

  • The documentation is open supply on GitHub, so prospects and companions can file points or submit pull requests. An lively points tracker on the docs repo reveals neighborhood engagement.

  • API Credential Administration is self-serve throughout the Greenhouse UI, with per-endpoint permission toggling on API keys. This granularity is rare and helpful for organizations operating a number of integrations with completely different entry wants.

What the documentation doesn’t embody: no interactive API explorer (no Swagger UI, no OpenAPI spec obtain), no Postman assortment, and no sandbox setting outdoors the Professional plan’s developer sandbox and sync characteristic.

With out an interactive explorer, you affirm response shapes by studying docs and making check calls, not by clicking by a try-it interface.

A standing web page at standing.greenhouse.io offers service well being monitoring.

MCP integration: Greenhouse launched an MCP server in June 2026, giving hiring groups a ruled approach to join AI brokers (Claude, ChatGPT, Gemini) to Greenhouse information. The MCP was developed with design companions together with StubHub and Komodo Well being.

Price Limits & Constraints

Harvest API: Requests are restricted to the worth within the X-RateLimit-Restrict response header, per 10-second window. The documented default is 50 requests per 10 seconds. On breach, the API returns HTTP 429 with an X-RateLimit-Reset timestamp and a Retry-After header. Remaining capability is tracked through X-RateLimit-Remaining.

Audit Log API: Customary requests are restricted to 50 per 10 seconds. Paginated requests carry a stricter sub-limit of three requests per 30 seconds.

Pagination: Assortment endpoints use Hyperlink header-based pagination (RFC-5988) with subsequent, prev, and final relations. The Audit Log API makes use of cursor-based pagination with pit_id and next_search_after values; web page measurement is ready through a Dimension header (minimal 100, most 500 outcomes per web page).

The 50 req/10s default is a modest ceiling. For integrations syncing massive candidate databases or operating frequent polling loops, you’ll need to respect the speed headers rigorously. In case your Order Type specifies completely different limits, these override the default, and exceeding these limits could lead to extra charges.

Knowledge retention element: Signed URLs for doc attachments on AWS S3 are legitimate for 7 days (Harvest API) or 30 days (Audit Log API) and needs to be downloaded promptly.

Greenhouse API Pricing & Entry Prices

Greenhouse bundles API entry into its subscription plans fairly than charging per name. You provision API keys by the Dev Middle, accessible throughout Core, Plus, and Professional tiers.

Nonetheless, sure API surfaces and developer instruments are tier-gated:

  • Core: Harvest API entry, Job Board API, Candidate Ingestion API, Evaluation API, and Recruiting Webhooks.

  • Professional: All the things in Plus, plus the Audit Log API, developer sandbox and sync, and enterprise-level information configuration.

All three tiers use {custom} pricing with no public worth record. The associated fee is dependent upon plan tier, hiring quantity, organizational complexity, and required options. Subscription charges are based mostly on worker headcount, together with all staff of associates.

Two value particulars to plan round:

  • API overage charges: The Grasp Subscription Settlement states that utilization past API limits specified within the Order Type could lead to extra charges on the charges acknowledged therein. Verify your API limits and overage phrases throughout contract negotiation.

  • Skilled providers: Knowledge migration, implementation, and {custom} improvement are billed individually below SOWs. Knowledge export on termination is free through API self-export, however requesting a Greenhouse-produced export file is topic to Greenhouse’s then-current information migration charges.

For a developer sizing prices: the API itself carries no per-call fees at normal utilization. The actual value is the Greenhouse subscription tier that determines which APIs, options, and developer instruments (sandbox, audit log) you’ll be able to entry.

The place the Greenhouse API Falls Brief

These are the sensible limits a developer ought to plan round. A number of are scope selections that mirror what Greenhouse is (an ATS) and what it’s not.

Recruiting information solely, no B2B intelligence. The API reads and writes hiring information: candidates, purposes, jobs, scorecards, affords. There are not any endpoints for contact enrichment, firmographics, technographics, org charts, purchaser intent, or employment historical past past what a candidate submits.

In case your integration wants to complement candidate data with verified enterprise emails, direct-dial telephone numbers, or firm intelligence, you want a second API.

SDK protection is slim. Official SDKs exist for Ruby and PHP solely. Node.js, Python, Java, and Go integrations require direct HTTP calls with no maintained shopper library to deal with auth, pagination, retry, and rate-limit backoff. For groups constructing in JavaScript or Python (the 2 commonest integration languages), this provides actual engineering overhead.

Price limits are modest for high-volume syncs. The 50 req/10s default on the Harvest API (5 requests per second efficient) works for event-driven integrations however constrains bulk information sync operations. A nightly job syncing 50,000 candidate data, with pagination and associated useful resource fetches, will spend significant time ready on rate-limit home windows.

No interactive API explorer or OpenAPI spec. The documentation is evident and well-structured, however there is no such thing as a Swagger UI, no OpenAPI spec obtain, and no Postman assortment. Builders affirm response shapes by studying docs and making check calls, not by exploring interactively.

Audit Log API is Professional-only. The 30-day rolling entry and configuration occasion log is restricted to the best subscription tier. Organizations on Core or Plus that want programmatic audit trails for compliance (SOC 2 proof assortment, for instance) can’t entry this API.

Developer sandbox requires Professional. The developer sandbox and sync characteristic, which offers a secure setting for testing integrations with out touching manufacturing information, is accessible solely on the Professional plan. Core and Plus prospects check towards their reside Greenhouse occasion.

Harvest API v1/v2 sundown is imminent. The legacy v1/v2 Harvest API is deprecated with removing set for August 31, 2026. Integrations constructed towards the legacy floor should migrate to v3 at harvestdocs.greenhouse.io earlier than that date. The migration shouldn’t be elective; it’s a deadline.

No enrichment, no intelligence, no indicators. That is the hole that issues most for builders constructing recruiting pipelines that transcend monitoring candidates.

Greenhouse can inform you {that a} candidate utilized, what stage they’re in, and what their scorecard says. It can’t inform you what firm that candidate works for now, what expertise stack that firm makes use of, whether or not the corporate is hiring or downsizing, or whether or not the candidate’s present employer is exhibiting intent indicators related to your recruiting technique.

ZoomInfo API: The Intelligence Layer Greenhouse Does Not Cowl

Greenhouse’s API manages the hiring course of.

ZoomInfo’s API offers the candidate and firm intelligence that informs it: who these persons are, the place they work, what these corporations appear to be, and which accounts present indicators that matter to a recruiting group. That intelligence flows from ZoomInfo’s GTM Context Graph, which processes 1.5B+ information factors day by day by fusing ZoomInfo’s B2B information along with your first-party information.

greenhouse-api-3

The 2 APIs sit at completely different layers. A developer constructing a recruiting information pipeline would use Greenhouse’s API to handle the candidate lifecycle and ZoomInfo’s API to complement, analysis, and prioritize the contacts and corporations flowing by it.

What the API Covers

ZoomInfo’s Enterprise API is a REST suite served from https://api.zoominfo.com/gtm, organized into 4 floor areas documented within the interactive API reference:

Knowledge API (Search & Enrich): Search endpoints cowl Contacts, Corporations, Intent, Information, and Scoops, returning matched data with out consuming credit. Enrich endpoints unlock the total payload: enterprise emails, direct dials, employment historical past, company hierarchy, org charts, technographics, and hashtag indicators (as much as 25 data per name).

The underlying dataset spans 500M contacts and 100M corporations, 135M+ verified telephone numbers, and 200M+ verified enterprise electronic mail addresses. Search is free; enrichment consumes one credit score per new document inside a rolling 12-month window.

greenhouse-api-4

Supply: ZoomInfo

AI Intelligence API: Account Abstract returns structured account intelligence with a free-form Q&A endpoint. Discover Related Corporations performs lookalike enlargement from a seed account. Contact Suggestions returns AI-ranked buying-committee strategies by movement (prospecting, deal acceleration, renewals).

What you’d construct with this in a recruiting context: enrich candidate data flowing by Greenhouse with verified contact information and employment historical past, analysis goal corporations for govt recruiting by pulling org charts and hiring indicators, or prioritize sourcing efforts by figuring out corporations exhibiting development indicators (new funding, govt hires, expertise adoption) that point out near-term hiring exercise.

Authentication & Entry

ZoomInfo makes use of OAuth 2.0 with PKCE through Okta, supporting three flows: Authorization Code with PKCE (internet purposes), Consumer Credentials (server-to-server), and Refresh Token.

Entry tokens are 24-hour Bearer tokens with rotating refresh tokens. Groups register purposes by the ZoomInfo Developer Portal, the place they generate credentials, outline scopes, and check endpoints.

greenhouse-api-5

This can be a completely different authentication mannequin from Greenhouse’s static API keys. OAuth 2.0 helps delegated entry, credential rotation, and scoped permissions, making it the stronger alternative for multi-tenant integrations and enterprise safety necessities.

Price Limits, Credit & Developer Expertise

Price limits are printed by tier: Builder (5 req/sec), Customary (25 req/sec), and Scaling (35 req/sec), with per-hour and per-day sliding-window limits enforced concurrently. Each response contains quota headers with remaining capability, and 429 responses embody a Retry-After header with actual backoff timing.

Credit observe a rolling 12-month window: enriching a document for the primary time consumes one credit score; re-enriching the identical document throughout the 12 months is free. Search and lookup operations are free and don’t eat credit.

For builders constructing AI brokers, ZoomInfo’s MCP server at https://mcp.zoominfo.com/mcp exposes search, enrich, and account analysis as native instruments for MCP-compatible assistants, presently supporting Claude and ChatGPT.

greenhouse-api-6

Supply: ZoomInfo

Documentation lives at docs.zoominfo.com with an interactive API reference, OAuth recipes in 5 languages, and an llms.txt index for AI improvement instruments. ZoomInfo doesn’t publish official SDKs, so each platforms require direct HTTP integration. Pricing follows a consumption-based mannequin and is custom-quoted; ZoomInfo has added API entry to all related plans.

BDO Canada reported an 87% discount in time spent updating inner information dashboards utilizing the ZoomInfo API, with one analyst describing the combination as plug-and-play throughout any course of. (ZoomInfo)

Ultimate Verdict

Greenhouse’s API floor is well-documented and deep sufficient to assist the total hiring lifecycle programmatically: candidates, purposes, jobs, interviews, scorecards, affords, onboarding, and audit logging throughout eight scoped APIs with two webhook channels.

The open-source documentation, per-endpoint permission granularity, and express retry insurance policies give builders the transparency wanted to construct with confidence. Its limits are limits of scope, not high quality.

Select the Greenhouse API if your integration is hiring-first: syncing candidate information to an HRIS, constructing a {custom} profession web page, pushing evaluation scores into the ATS, automating stage transitions based mostly on exterior indicators, or feeding hiring analytics right into a BI instrument.

The eight-API structure means you choose solely the surfaces your construct wants, and the webhook occasion catalogue covers the lifecycle occasions that drive most real-time integrations.

Select the ZoomInfo API if your construct wants the intelligence layer upstream of hiring: enriching candidate data with verified contact information and employment historical past, researching goal corporations for govt sourcing, figuring out accounts exhibiting hiring indicators, or constructing AI-agent workflows that mix recruiting information with B2B intelligence.

The search-then-enrich sample (search is free, enrich consumes credit) and the AI intelligence endpoints cowl the info and reasoning that an ATS API doesn’t. Discover the ZoomInfo Enterprise API or begin with the developer docs to see the endpoint floor straight.

A developer who wants neither API ought to think about that Greenhouse’s API doesn’t cowl B2B information intelligence, and ZoomInfo’s API doesn’t handle hiring workflows. In case your pipeline requires each, the 2 are complementary layers, not competing surfaces.

FAQ

Is the Greenhouse API free?

API entry is included in all Greenhouse subscription tiers (Core, Plus, and Professional) with no separate per-call fees at normal utilization ranges.

All tiers use {custom} pricing with no public worth record, and the Grasp Subscription Settlement states that utilization exceeding the API limits in your Order Type could lead to extra charges. The Audit Log API and developer sandbox are restricted to the Professional plan. There is no such thing as a free trial or free tier for Greenhouse; the one entry level is requesting a demo.

Does Greenhouse have a GraphQL API?

Sure, however just for onboarding. The Greenhouse Onboarding API (GHO) makes use of GraphQL completely, supporting queries on worker profiles, departments, areas, groups, {custom} fields, pending hires, and signature requests.

The first recruiting APIs (Harvest, Job Board, Ingestion, Evaluation, Audit Log) are all REST. When you want GraphQL for recruiting information, you would wish to wrap the REST APIs in your individual GraphQL layer.

What’s the Greenhouse API charge restrict?

The Harvest API default is 50 requests per 10-second window, tracked through the X-RateLimit-Restrict response header. On breach, the API returns HTTP 429 with X-RateLimit-Reset and Retry-After headers. The Audit Log API shares the identical 50 req/10s restrict for traditional requests however imposes a stricter 3 requests per 30 seconds for paginated requests. Your Order Type could specify completely different limits.

Are there official Greenhouse SDKs?

Greenhouse publishes official wrappers for 2 languages: Ruby (greenhouse_io) and PHP (greenhouse-tools-php), each hosted on GitHub below the grnhse group. A Ruby OmniAuth technique for OAuth flows can be accessible. There are not any official SDKs for Node.js, Python, Java, or Go. Neighborhood libraries exist however Greenhouse doesn’t preserve them.

Does the Greenhouse API assist webhooks?

Sure. Recruiting Webhooks cowl utility, candidate, interview, job, and group occasions with HMAC-SHA256 signature verification, {custom} headers, and a broadcast retry coverage of as much as 7 makes an attempt over about 15 hours with exponential backoff.

Onboarding Webhooks are a separate channel presently in beta, firing employee-updated occasions with the identical HMAC authentication and retry depend. You configure webhooks per endpoint URL with a secret key, and Greenhouse pings the endpoint on creation to confirm reachability.

What does ZoomInfo’s API add to a Greenhouse construct?

ZoomInfo’s API provides the B2B information and intelligence layer that Greenhouse’s API doesn’t cowl. The place Greenhouse manages candidates, purposes, and hiring workflows, ZoomInfo offers verified contact information (500M contacts, 200M+ verified enterprise emails, 135M+ verified telephone numbers), firm intelligence (firmographics, org charts, technographics throughout 100M corporations), and AI-powered analysis (account summaries, lookalike enlargement, contact suggestions).

For recruiting groups, this implies enriching candidate data with verified employment information, researching goal corporations for govt searches, and figuring out accounts exhibiting development or hiring indicators. The 2 APIs use completely different authentication fashions (HTTP Primary Auth vs. OAuth 2.0) and completely different pricing constructions (subscription-bundled vs. credit-based), so plan the combination layer to deal with each.

RELATED ARTICLES

Most Popular

Recent Comments