Bullhorn ATS Integration

Bullhorn connector for Kombo’s ATS API

The Bullhorn ATS integration allows you to sync ATS data between Bullhorn and your application through Kombo’s unified API. The tool slug for this connector is bullhorn.

Guides and Resources

Connection Setup Guide

Step-by-step instructions to connect your Bullhorn account to Kombo.

View Candidate Sources

How to view and manage candidate sources in Bullhorn.

How to setup screening questions in Bullhorn

Additional documentation and guides for Bullhorn.

Supported Features & Coverage

Models

Users

Field	Notes
id
remote_id
changed_at
remote_deleted_at
first_name
last_name
email
remote_data

Jobs

Field	Notes
id
remote_id
changed_at
remote_deleted_at
name
description
weekly_hours
employment_type
status
visibility
category
experience_level
salary_amount
salary_period
location
custom_fields
integration_fields
closed_at
remote_created_at
remote_updated_at
remote_data

Candidates

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

Application Stages

Field	Notes
id
remote_id
changed_at
remote_deleted_at
name

Applications

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

Screening questions

Field	Notes
id
remote_id
changed_at
remote_deleted_at
title
description
format

Rejection reasons

Field	Notes
id
remote_id
changed_at
remote_deleted_at
name

Roles

Field	Notes
id
remote_id
changed_at
remote_deleted_at
remote_label
scope
unified_type

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

Bullhorn exposes two user relations per job.

• clientContact (shown as “Contact” in the UI) maps to HIRING_MANAGER
• owner (shown as “Consultant” in the UI) maps to RECRUITER

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

Bullhorn assigns each CorporateUser a userType object with an id and name. ClientContact users are external contacts and have no system role synced.

• Administrator maps to unified type ADMIN
• All other userType names sync without a unified type.

Field	Notes
user_id
role_id
id
changed_at
remote_deleted_at

Actions

Create candidate

Screening question answers are stored on the candidate, not the submission. Therefore, if a candidate applies to multiple jobs it will not be apparent in the UI which screening question answer set belongs to which submission.

Input Field	Notes
candidate.first_name
candidate.last_name
candidate.email_address
candidate.company
candidate.title
candidate.phone_number
candidate.location.city
candidate.location.country
candidate.location.zip_code
candidate.gender
candidate.availability_date
candidate.salary_expectations.period
candidate.salary_expectations.amount
candidate.social_links.url
application.job_id
application.stage_id
screening_question_answers.question_id
screening_question_answers.answer
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

Screening question answers are stored on the candidate, not the submission. Therefore, if a candidate applies to multiple jobs it will not be apparent in the UI which screening question answer set belongs to which submission.

Input Field	Notes
candidate.first_name
candidate.last_name
candidate.email_address
candidate.company
candidate.title
candidate.phone_number
candidate.location.city
candidate.location.country
candidate.location.zip_code
candidate.gender
candidate.availability_date
candidate.salary_expectations.period
candidate.salary_expectations.amount
candidate.social_links.url
application.job_id
application.stage_id
screening_question_answers.question_id
screening_question_answers.answer
attachments.name
attachments.content_type
attachments.data_url
attachments.data
attachments.type
source.name
source.unified_key
source.id
sourced_by.user_id

Add attachment to application

This action will fall back to the “Add attachment to candidate” action. Therefore, there could be cases where the attachment may not be added to the application but rather to the candidate.

Input Field	Notes
application_id
attachment.name
attachment.content_type
attachment.data_url
attachment.data
attachment.type

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

In Bullhorn an applications may be deleted when a position is filled. Consider calling get candidate attachments instead, because it will return attachments related to a candidate, including all attachments from all of their applications.

Input Field	Notes
application_id

Get candidate attachments

Input Field	Notes
candidate_id

Add attachment to candidate

Input Field	Notes
candidate_id
attachment.name
attachment.content_type
attachment.data_url
attachment.data
attachment.type

Add result link to candidate

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

Features

Feature	Notes
Source Writing
Sync Only Created Applications
Connection Guide
Prerequisites
Create credentials
Candidate Cutoff Filtering
Roles
System roles (e.g. Admin)	Bullhorn assigns each CorporateUser a userType object with an id and name. ClientContact users are external contacts and have no system role synced.

• Administrator maps to unified type ADMIN
• All other userType names sync without a unified type. | | Job roles (e.g. Hiring Manager) | Bullhorn exposes two user relations per job.
• clientContact (shown as “Contact” in the UI) maps to HIRING_MANAGER
• owner (shown as “Consultant” in the UI) maps to RECRUITER | | OAuth | | | API Passthrough | | | Delta Syncs | |

Integration Variants

Current connector: Choose this variant to use OAuth-based authentication (recommended)

For Bullhorn, we also offer the following other connector variants:

Bullhorn Login

Legacy login-based variant. This variant is deprecated and merged into the regular Bullhorn integration

Bullhorn Assessment

Bullhorn for the Assessment category

You can only use one variant at a time.