Greenhouse (V3) ATS Integration

This connector is in open beta. You can freely enable it in your account.

This connector requires a partnership with Greenhouse (V3). Please contact us to get access.

The Greenhouse (V3) ATS integration allows you to sync ATS data between Greenhouse (V3) and your application through Kombo’s unified API. The tool slug for this connector is greenhousev3.

Guides and Resources

Source Setup Guide

Learn how to set up candidate sources in Greenhouse (V3).

Supported Features & Coverage

Models
Actions
Features

Users

Field	Notes
id
remote_id
changed_at
remote_deleted_at
first_name
last_name
email
status
remote_data

Jobs

Field	Notes
id
remote_id
changed_at
remote_deleted_at
name
job_code
description
confidential
employment_type
status
visibility
department
post_url
salary_amount_from
salary_amount_to
salary_currency
location
custom_fields
integration_fields
remote_url
opened_at
closed_at
remote_created_at
remote_updated_at
remote_data

Job postings

Field	Notes
id
remote_id
changed_at
remote_deleted_at
title
description_html
status
visibility
url
job_id
remote_data
remote_created_at
remote_updated_at

Candidates

Field	Notes
id
remote_id
changed_at
remote_deleted_at
first_name
last_name
company
title
confidential
source
phone_numbers
email_addresses
social_media
location
custom_fields
integration_fields
remote_url
remote_created_at
remote_updated_at
remote_data

Application Stages

Field	Notes
id
remote_id
changed_at
remote_deleted_at
name
remote_data

Applications

Field	Notes
id
remote_id
changed_at
remote_deleted_at
outcome
rejection_reason_name
rejected_at
current_stage_id
job_id
candidate_id
screening_question_answers
custom_fields
integration_fields
remote_url
remote_created_at
remote_updated_at
remote_data

Screening questions

Field	Notes
id
remote_id
changed_at
remote_deleted_at
title
description
format

Tags

Field	Notes
id
remote_id
changed_at
remote_deleted_at
name
remote_data

Interviews

Field	Notes
id
remote_id
changed_at
remote_deleted_at
title
starting_at
ending_at
location
video_conferencing_url
application_id
stage_id
canceled	If all interviewers decline the interview, it is considered canceled
remote_created_at
remote_updated_at
remote_data

Offers

Field	Notes
id
remote_id
changed_at
remote_deleted_at
status
employment_start_date
application_id
custom_fields
integration_fields
remote_created_at
remote_updated_at
remote_data

Rejection reasons

Field	Notes
id
remote_id
changed_at
remote_deleted_at
name
remote_data

Roles

Field	Notes
id
remote_id
changed_at
remote_deleted_at
remote_label
scope
unified_type

Notes

Greenhouse provides a wide variety of notes. We expose only those that provide direct signal about a candidate: NOTE, INTERVIEW, FORM, FEEDBACK

Field	Notes
id
remote_id
changed_at
remote_deleted_at
candidate_id
application_id
author_id
title
content_html
is_private
remote_created_at
remote_updated_at
remote_data

Scorecards

Greenhouse exposes submitted (complete) scorecards only; a draft is never returned.

The overall rating, summary, public notes, and private notes are the first four responses (remote_id: null). Harvest does not identify those fields.
author_id is the interviewer (interviewer_id), not the submitter.
interview_id is set only when /interviewers attaches the scorecard to a scheduled panel member; a manual scorecard is null.
Harvest wraps some interview-kit question labels in HTML (<p>…</p>) and leaves others bare, and publishes no plain variant of the field. The value is passed through as returned, so a label can contain markup.

Field	Notes
id
remote_id
changed_at
remote_deleted_at
candidate_id
application_id
interview_id
author_id
responses
remote_created_at
remote_updated_at
remote_data

Candidate tags

Field	Notes
candidate_id
tag_id
id
changed_at
remote_deleted_at

Job-specific application stages

Field	Notes
index
job_id
stage_id
id
changed_at
remote_deleted_at

Job-specific screening questions

Field	Notes
index
required
precondition_question_id
precondition_options
job_id
question_id
id
changed_at
remote_deleted_at

Job user role assignments

Greenhouse V3 exposes hiring team data via three flat endpoints plus per-user job admin permissions.

job_hiring_managers maps to HIRING_MANAGER
job_owners with type recruiter maps to RECRUITER
job_owners with type coordinator maps to COORDINATOR
job_owners with type sourcer maps to SOURCER
user_job_permissions role names (e.g. “Standard”, “Private”) sync without a unified role type, and only when the “Enable custom roles” integration setting is enabled (disabled by default).

Field	Notes
job_user_id
role_id
id
changed_at
remote_deleted_at

Job hiring team members

Field	Notes
roles
job_id
user_id
id
changed_at
remote_deleted_at

User roles

Greenhouse assigns each user a single role at the system level from the site_admin flag.

Site Admin maps to ADMIN
All other users map to Basic, which has no unified type.

Field	Notes
user_id
role_id
id
changed_at
remote_deleted_at

Interviewing team members

Field	Notes
interview_id
user_id
id
changed_at
remote_deleted_at

Create candidate

Input Field	Notes
candidate.first_name
candidate.last_name
candidate.email_address
candidate.additional_email_addresses.email_address
candidate.company
candidate.title
candidate.phone_number
candidate.additional_phone_numbers.phone_number
candidate.location.city
candidate.location.country
candidate.social_links.url
application.job_id
application.stage_id
attachments.name
attachments.content_type
attachments.data_url
attachments.data
attachments.type
source.name
source.unified_key
source.id
sourced_by.user_id

Create application

Input Field	Notes
candidate.first_name
candidate.last_name
candidate.email_address
candidate.additional_email_addresses.email_address
candidate.company
candidate.title
candidate.phone_number
candidate.additional_phone_numbers.phone_number
candidate.location.city
candidate.location.country
candidate.social_links.url
application.job_id
application.stage_id
attachments.name
attachments.content_type
attachments.data_url
attachments.data
attachments.type
source.name
source.unified_key
source.id
sourced_by.user_id

Add tag to candidate

Input Field	Notes
candidate_id
tag.name

Remove tag from candidate

Input Field	Notes
candidate_id
tag.name

Add attachment to application

Input Field	Notes
application_id
attachment.name
attachment.content_type
attachment.data_url
attachment.data
attachment.type	Attachments of type “OTHER” will only be visible to admins due to a limitation in Greenhouse’s API.

Move application to stage

Input Field	Notes
application_id
stage_id

Reject application

Input Field	Notes
application_id
rejection_reason_id
note

Add result link to application

Input Field	Notes
application_id
label
url
details.custom_field_name_prefix
details.attributes.key
details.attributes.value

Add note to application

Input Field	Notes
application_id
content

Get application attachments

Input Field	Notes
application_id

Get candidate attachments

Input Field	Notes
candidate_id

Feature	Notes
OAuth
API Passthrough
Upstream Webhooks	ping: triggered when a webhook was configured and the endpoint is checked to confirm it is working update_candidate: triggered when a candidate or prospect is updated, including when a tag is assigned or unassigned candidate_anonymized: triggered when a candidate or prospect is anonymized, scrubbing PII from the candidate and their applications delete_candidate: triggered when a candidate is deleted merge_candidate: triggered when two candidates are merged application_updated: triggered when an application is updated candidate_stage_change: triggered when an application’s stage is changed hire_candidate: triggered when a candidate is hired new_candidate_application: triggered when a new candidate application is created new_prospect_application: triggered when a new prospect application is created unhire_candidate: triggered when a candidate is unhired reject_candidate: triggered when a candidate or prospect is rejected unreject_candidate: triggered when a candidate or prospect is unrejected delete_application: triggered when an application is deleted job_approved: triggered when a job is approved job_created: triggered when a job is created job_updated: triggered when a job is updated job_deleted: triggered when a job is deleted job_post_created: triggered when a job post is created (a job is published) job_post_updated: triggered when a job post is updated job_post_deleted: triggered when a job post is deleted (a job is unpublished) interview_deleted: triggered when an interview is deleted offer_approved: triggered when an offer is approved offer_created: triggered when an offer is created offer_updated: triggered when an offer is updated offer_deleted: triggered when an offer is deleted Not covered: screening questions updated for a job Not covered: interview scheduled or updated
Automatic Setup
Scope Testing
Per Model Tests
Per Field Tests
Delta Syncs
Custom Field Explorer
Jobs
Candidates
Applications
Offers
Source Writing
Sync Only Created Applications
Candidate Cutoff Filtering
Roles
System roles (e.g. Admin)	Greenhouse assigns each user a single role at the system level from the site_admin flag.

Site Admin maps to ADMIN
All other users map to Basic, which has no unified type. | | Job roles (e.g. Hiring Manager) | Greenhouse V3 exposes hiring team data via three flat endpoints plus per-user job admin permissions.
job_hiring_managers maps to HIRING_MANAGER
job_owners with type recruiter maps to RECRUITER
job_owners with type coordinator maps to COORDINATOR
job_owners with type sourcer maps to SOURCER
user_job_permissions role names (e.g. “Standard”, “Private”) sync without a unified role type, and only when the “Enable custom roles” integration setting is enabled (disabled by default). |

Integration Variants

Current connector: This is the recommended Greenhouse integration For Greenhouse (V3), we also offer the following other connector variants:

Greenhouse (V1)

Choose this variant if you want to use the Greenhouse Harvest v1 API

Greenhouse Job Board

Choose this variant if you want to write Screening Question Answers with the Greenhouse Job Board API, this integration’s coverage is limited

Multiple variants can be used within your Kombo environment at the same time.

General

Features

Guides

ATS API Reference

General API Reference

Greenhouse (V3) ATS Integration

Guides and Resources

Source Setup Guide

Supported Features & Coverage

Integration Variants

Greenhouse (V1)

Greenhouse Job Board

​Guides and Resources

Source Setup Guide

​Supported Features & Coverage

​Integration Variants

Greenhouse (V1)

Greenhouse Job Board

Guides and Resources

Supported Features & Coverage

Integration Variants