Greenhouse (V3) ATS Integration

Greenhouse (V3) connector for Kombo’s ATS API

This connector is in closed beta. 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

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
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

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.

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 derives roles from site_admin on the user and job-assignment state. If job-permission data cannot be fetched, no system role rows are created.

• When site_admin is true, Kombo maps to unified type ADMIN
• When site_admin is false, Kombo maps to either Job Admin or Basic depending on assignments; both have 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

Actions

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.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.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

Features

Feature	Notes
Source Writing
Sync Only Created Applications
Candidate Cutoff Filtering
Roles
System roles (e.g. Admin)	Greenhouse derives roles from site_admin on the user and job-assignment state. If job-permission data cannot be fetched, no system role rows are created.

• When site_admin is true, Kombo maps to unified type ADMIN
• When site_admin is false, Kombo maps to either Job Admin or Basic depending on assignments; both have 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. | | OAuth | | | API Passthrough | | | Scope Testing | | | Per Model Tests | | | Per Field Tests | | | Delta Syncs | | | Custom Field Explorer | | | Jobs | | | Candidates | | | Applications | | | Offers | |

Integration Variants

Current connector: Choose this variant if you want to use the Greenhouse Harvest API V3 with OAuth2 authentication

For Greenhouse (V3), we also offer the following other connector variants:

Greenhouse

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

Greenhouse Job Board

Choose this variant if you want to write Screening Questions 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.