Source connector

Greenhouse connector

Greenhouse integration for databases, warehouses and BI tools

Applicant tracking and structured hiring. Datrise captures Greenhouse entities such as candidates, applications, jobs, interviews, scorecards and offers, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Greenhouse Harvest API (current stable, unversioned in URL; Harvest v3 in rollout with a v3 endpoint prefix) authenticates with API key, incremental runs key on updated_after / updated_before query params (ISO-8601), and Greenhouse caps calls at 50 requests per 10 seconds per API key.

Of the 6 objects, 5 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `greenhouse_candidates`) with a schema derived from the Greenhouse API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Greenhouse pipeline page, and join the waitlist to get the Greenhouse connector (CRM) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Greenhouse data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
candidates	greenhouse_candidates	Upsert by primary key, incremental on updated-at
applications	greenhouse_applications	Upsert by primary key, incremental on updated-at
jobs	greenhouse_jobs	Append-only, incremental by timestamp
interviews	greenhouse_interviews	Upsert by primary key, incremental on updated-at
scorecards	greenhouse_scorecards	Upsert by primary key, incremental on updated-at
offers	greenhouse_offers	Upsert by primary key, incremental on updated-at

Greenhouse API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Greenhouse Harvest API (current stable, unversioned in URL; Harvest v3 in rollout with a v3 endpoint prefix)
Authentication	API key — HTTP Basic Auth with the API key as the username and a blank password; Harvest v3 additionally supports OAuth2 and JWT bearer tokens.
Pagination	link_header — RFC-5988 Link header with next/prev/last relations; per_page defaults to 100 with a maximum of 500.
Rate limit	50 requests per 10 seconds per API key
Incremental cursor	updated_after / updated_before query params (ISO-8601) — updated_after tracks a record's own last-modified timestamp only, so an application's stage change doesn't bump the parent Candidate's updated_after.
Webhooks	Yes — Recruiting Webhooks (HMAC-SHA256 signed payloads)
Bulk export	No
Deletes detectable	Yes — candidate_deleted / application_deleted / job_deleted webhook events; there is no REST endpoint that lists deleted IDs directly.

Official API reference

What bites when replicating Greenhouse

Default page size is 100 with a per_page cap of 500; you must follow the Link header's next relation instead of constructing offset URLs yourself.
Rate limit is 50 requests per 10 seconds per API key and Greenhouse sends no Retry-After header, only X-RateLimit-Reset, so backoff timing has to be computed manually.
updated_after filters on a resource's own timestamp only, so polling Candidates with updated_after misses Applications whose stage or status changed without touching the Candidate record itself.
All POST/PATCH write calls require an On-Behalf-Of header naming an active Site Admin user ID; omitting it returns a 403 even with a valid API key.

Compare this against every other documented API

Popular destinations for Greenhouse

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Greenhouse connector FAQ

What Greenhouse data does the connector extract?: 6 objects: candidates, applications, jobs, interviews, scorecards and offers. Each lands in its own table with types preserved; history-style objects (1: jobs) load as append-only streams.
Is the Greenhouse integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Greenhouse data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Greenhouse → destination pair has its own page with the object-to-table mapping.

Related CRM sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Greenhouse pipeline with guided onboarding

Join the waitlist to get priority access for Greenhouse integrations with guided setup, schema-aware mapping, and production-grade incremental sync.