Bullhorn API

Integrate Bullhorn with your product—along with any other
ATS
 application

Connect your product to all the applications your customers use via Merge's

ATS

 

Unified API to close more deals, retain customers, and expand to new markets

Merge provides the infrastructure to enable customers to integrate to the Bullhorn system but there is no current affiliation or relationship between Merge API Inc. and Bullhorn Inc.

Get a demo
Your Product
Merge
Your customers' data
Activities
Applications
Async Passthroughs
Attachments
Audit Trails
Candidates
Departments
Eeocs
Field Mappings
Interviews
Job Interview Stages
Job Postings
Jobs

Top integration use cases for Bullhorn

Read more

Sync Bullhorn Data

Applications

The Application Object is used to represent a candidate's journey through a particular Job's recruiting process. If a Candidate applies for multiple Jobs, there will be a separate Application for each Job if the third-party integration allows it.

Docs
Attachments

The Attachment object is used to represent a file attached to a candidate.

Docs
Candidates

The Candidate object is used to represent profile information about a given Candidate. Because it is specific to a Candidate, this information stays constant across applications.

Docs
Jobs

The Job object can be used to track any jobs that are currently or will be open/closed for applications.

Docs
Job Interview Stages

The JobInterviewStage object is used to represent a particular recruiting stage for an Application. A given Application typically has the JobInterviewStage object represented in the current_stage field.

Docs
Users

The RemoteUser object is used to represent a user with a login to the ATS system.

Docs

FAQ on integrating with Bullhorn’s API

How does Merge interact with Bullhorn’s API?

Merge can create, retrieve and update a variety of data types via GET, PUT, and POST methods. This includes candidate information (e.g., name, title, and company), job orders, job submissions, and interview stages. 

You can learn more about the endpoints Merge supports here.

What are the sync frequencies for Bullhorn data in Merge?

The frequencies can vary, depending on the Bullhorn endpoints’ associated Common Models. That said, they typically range from 1 hour to daily syncs.

You can also leverage webhooks, which allow for real-time updates when key events occur, such as changes to candidates, job submissions, or job interview stages in Bullhorn.

What are some of the other ATS integrations Merge supports?

In addition to Bullhorn, Merge supports 50+ key ATS platforms via its ATS Unified API. This includes Greenhouse, Lever, Workable, JazzHR, and Jobvite.

You can see the full list of ATS integrations here.

How does Merge provide a secure Bullhorn integration?

Merge ensures that all data from Bullhorn is encrypted at rest and in transit using AES-256 encryption. Additionally, the integration supports multi-tenant and single-tenant environments, offering flexible security options based on customers' needs​.

How do my customers authorize a Bullhorn integration with Merge?

They would do so using Merge Link, a user-friendly, customizable UI component. Once embedded into your product, Merge Link guides users through the authorization process step-by-step. This involves logging into their Bullhorn account securely through Merge Link, which grants the necessary permissions to sync data between their instance of Bullhorn and your application. 

For more details on Merge Link, you can visit this page.

How does Merge log Bullhorn data and how long does it retain data?

Merge logs API requests and responses from Bullhorn and other integrations in real time. Data logs are stored based on your plan: Launch and Core plans have log retention of 3 to 7 days, while Professional and Enterprise plans extend retention to 30 to 90 days. During this period, logs are available for search and audit purposes​​.

How much does it cost to integrate with Bullhorn using Merge?

The cost of integrating with Bullhorn using Merge depends on the plan you choose. Merge offers various pricing options, including a Launch plan, which is free for up to 3 Production Linked Accounts and $650 per month for up to 10 accounts. For additional Linked Accounts, the cost is $65 per Linked Account.

If you need to support a high volume of Linked Accounts, your integration requirements are highly custom, and/or you'd like more strategic guidance and support in taking your integrations to market, you may want to explore Merge's Professional or Enterprise plans​​.

You can learn more about Merge's pricing plans here.

Are there any days you’ll be closed for the holidays in 2024?
Trusted to power integrations globally
Build Smarter

Make integrations your competitive advantage

More sales, less code, fewer headaches

Focus on your core product

Stop diverting your engineers to yet another integration and let them get back to work.

Give customer success a break

Manage your simplified integration issues in a single pane. No therapist required.

Stop losing sales due to integrations

Launch integrations in days, not quarters. Your sales team will thank you.

Seamless Account Linking

Integration authentication that feels like magic

Merge seamlessly manages authentication and authorization on behalf of your customers.

Offer account linking and permission controls to your users with Link for a customizable frontend or with Magic Link for URL-based authorization

View docs
APIs Made Simple

The toolkit for all your integration needs

We make integrations painless with accessible API design, dead-simple SDKs, and beautiful documentation that we agonize over.

View docs
Get Employee Data
Python
Ruby
Node
Go
Java
.NET
import merge
from merge.client import Merge
merge_client = Merge(api_key="<YOUR_API_KEY>", account_token="<YOUR_ACCOUNT_TOKEN>")
employee = merge_client.hris.employees.list()

import { MergeClient, Merge } from '@mergeapi/merge-node-client';
const merge = new MergeClient({
  apiKey: 'YOUR_API_KEY',
  accountToken: 'YOUR_ACCOUNT_TOKEN',
});
employee = await merge.hris.employees.list()

ApiClient.instance.authentications.tokenAuth = {
  type: 'bearer',
  accessToken: 'API_KEY',
};
new EmployeesApi().employeesList('ACCOUNT_TOKEN', {}, (data) => {
  console.log(data);
});

import (
  "context"
  "fmt"
  merge "github.com/fern-api/merge-go"
  mergeclient "github.com/fern-api/merge-go/client"
  "github.com/fern-api/merge-go/hris"
)

client := mergeclient.NewClient(
  mergeclient.ClientWithAuthApiKey("<YOUR_API_KEY>"),
  mergeclient.ClientWithHeaderAccountToken("<YOUR_ACCOUNT_TOKEN>"),
)
employee, err := client.Hris().Employees().List(
  context.TODO(),
  &hris.EmployeesRetrieveRequest{
    IncludeRemoteData: merge.Bool(true),
  },
)
if err != nil {
  return err
}
fmt.Printf("Retrieved employee with ID %q\n", *employee.Id)

ApiClient client = Configuration.getDefaultApiClient();
client.setBasePath('https://api.merge.dev/api/ats/v1');
ApiKeyAuth tokenAuth = client.getAuthentication('tokenAuth');
tokenAuth.setApiKey('API_KEY');
CandidatesApi apiInstance = new CandidatesApi(client);
apiInstance.candidatesList('ACCOUNT_TOKEN');

import com.merge.api.MergeApiClient;
import com.merge.api.resources.hris.employees.requests.EmployeesRetrieveRequest;
import com.merge.api.resources.hris.types.Employee;
MergeApiClient mergeClient = MergeApiClient.builder()
    .accountToken("ACCOUNT_TOKEN")
    .apiKey("API_KEY")
    .build();
Employee employee = mergeClient.hris().employees().list(
    EmployeesRetrieveRequest.builder()
        .includeRemoteData(true)
        .build());

{
"id": "0958cbc6-6040-430a-848e-aafacbadf4ae",
"remote_id": "19202938",
"employee_number": "2",
"company": "8d9fd929-436c-4fd4-a48b-0c61f68d6178",
"first_name": "Dirna",
"last_name": "Emanuel",
"display_full_name": "Dirna Emanuel",
"username": "dirnaemanuel",
"groups": [
  "21a54124-397f-494d-985e-3c5b330b8a68"
],
"work_email": "dirna@merge.dev",
"personal_email": "dirnaemanuel@gmail.com",
"mobile_phone_number": "+1234567890",
"employments": [
  "17a54124-287f-494d-965e-3c5b330c9a68"
+ More languages
Meta Endpoint

Programmatically access required schemas

Third-party providers require specific (and often different) fields to write data to their APIs, making your code a mess.

Dynamically fetch required data schemas from Merge’s /meta endpoint to make POST or PATCH requests that just work.

View Docs
Beyond Building

Rely on the best integration observability system

Let our logs, issue detection, and automated alerts save your customer success team time, money, and headaches.

Forget maintenance - let your developers focus on building!

Start for free

How Drata helps thousands streamline their SOC 2 with Merge

Read case study

​​”Working with Merge’s Unified API and beautiful React component took less than a sprint to integrate, test, and release.”

Daniel Marashlian of profile photo
Daniel Marashlian
Co-Founder & CTO

Read more about building and maintaining multiple integrations

A guide to maintaining your product integrations
A guide to maintaining your product integrations
Blog
Blog Posts
10/27/2023
A guide to integrating multiple APIs
A guide to integrating multiple APIs
Blog
Blog Posts
11/13/2023
The top challenges of normalizing multiple API integrations
The top challenges of normalizing multiple API integrations
Blog
Blog Posts
11/20/2023
One Step Ahead

We're the cheat code to your integrations strategy

Revolutionize your integrations strategy for HR, payroll, directory, ATS, project management, ticketing, accounting and CRM platforms.

Start for free or talk to our sales team and learn how Merge makes it easy to add all your integrations in days – not years.
Get a demo
Create free account

Merge provides the infrastructure to enable customers to integrate to the Bullhorn system but there is no current affiliation or relationship between Merge API Inc. and Bullhorn Inc.

ATS
ATS
Read more