Greenhouse
Read and write Greenhouse candidates, applications, stage moves, rejections and notes, and read jobs, posts, offers, scorecards and interviews (Harvest v3).
Move candidates through hiring and hand hires to HRIS and onboarding without duplicate data entry.
Source actions
18
Destination actions
7
Data types
18
Validation status
Implemented · fixture tested.
Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.
What you can map
application rejection
- Reject applicationDestinationDuplicate protected
Rejects an application with a rejection reason and optional internal notes. No email is sent.
application stage
- Move applicationDestinationDuplicate protected
Advances an application to the next stage, moves it to a chosen stage, or transfers it to another job. Requires the current stage ID.
application stages
- List application stage historySourceIncremental
Stages an application has entered, with entry, exit and days in stage.
applications
- Add candidate to jobDestinationNot retried automatically
Creates an application for an existing candidate on a job.
- Get applicationSource
One application by ID.
- List applicationsSourceIncremental
Applications with stage, status, source and owners, filterable by job, candidate or status.
- Update applicationDestinationDuplicate protected
Updates source, referrer, recruiter, coordinator or custom fields.
candidates
- Create candidateDestinationNot retried automatically
Creates a candidate, optionally with an application on a job.
- Get candidateSource
One candidate by ID.
- List candidatesSourceIncremental
Candidates and prospects, optionally updated since a timestamp or filtered by email or tag.
- Update candidateDestinationDuplicate protected
Updates profile fields, contact lists, tags or custom fields. Lists replace existing values.
custom fields
- List custom fieldsSourceIncremental
Custom field definitions with object type and value type.
departments
- List departmentsSourceIncremental
Departments with parent and external IDs.
interviews
- List interviewsSourceIncremental
Scheduled interviews with times, location, organizer and video link.
job interview stages
- List job stagesSourceIncremental
Interview stages of jobs in order; use their IDs as move targets.
job posts
- List job postsSourceIncremental
Job board posts with title, live state, URL and content.
jobs
- List jobsSourceIncremental
Jobs with status, requisition ID, department and offices.
notes
- Add noteDestinationNot retried automatically
Adds a note to a candidate (and optionally an application).
- List notesSourceIncremental
Notes and activity on candidates and applications.
offers
- List offersSourceIncremental
Offers with status, version and dates (read-only; compensation custom fields are not returned).
offices
- List officesSourceIncremental
Offices with location, parent and external IDs.
rejection reasons
- List rejection reasonsSourceIncremental
Rejection reasons for rejecting applications.
scorecards
- List scorecardsSourceIncremental
Interview scorecards with overall rating and notes.
sources
- List sourcesSourceIncremental
Candidate sources.
users
- List usersSourceIncremental
Greenhouse users with emails, offices, departments and status.
Authentication
Harvest v3 (OAuth) client ID and secret
Plans and access
Harvest API access is available on all Greenhouse Recruiting plans. Harvest v3 credentials grant only the scopes selected in Greenhouse. Offers and private fields require the integration user to hold the private-data permission. Harvest v1/v2 were removed on 31 August 2026.
Test environment
Greenhouse provides sandbox sites to customers and partners on request.
Rate limits
Fixed 30-second windows per credential (see X-RateLimit-Limit); HTTP 429 includes Retry-After. Token requests have a separate 60-second window.
Provider events
Greenhouse web hooks for candidate, application, offer and job events. Nexra event triggers are not yet available; flows run on demand or on a schedule.
Before you build a flow
- Uses Harvest v3. Requests act as the credential's integration user; acting as a specific Greenhouse user (the token sub claim) is not configurable.
- Offers are read-only and their custom fields (which commonly hold compensation) are not returned.
- Rejecting applications never sends a rejection email; candidate merges, anonymisation, deletes, attachments and hires are not implemented.
- Moving and rejecting applications return no body; Nexra returns the application ID with the requested change.
- Candidate, application and note creates have no idempotency key; uncertain writes are not repeated automatically.