Merge Unified's JobAdder integration Merge Agent Handler's MCP server

Beta

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

Connect your product to all the applications your customers use via Merge's Unified API to close more deals, retain customers, and expand to new markets

Get a demo

Sync JobAdder data

Activity

The Activity object is used to represent an activity for a candidate performed by a user.

Application

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.

Candidate

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.

Job

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

JobInterviewStage

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.

RemoteUser

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

FAQ on integrating with JobAdder API

‍What JobAdder data can Merge sync?

Merge can sync core JobAdder data, such as candidate profiles, applications, jobs, and user information. This includes fields like candidate contact details, job statuses, and application stages, all normalized into a common model for simplified access. Additionally, Merge’s Field Mapping and Remote Data features allow you to retrieve and map custom data fields as needed.

Learn more about all of the Jobadder data Merge can sync.

How often does Merge sync JobAdder data?

The sync frequencies largely vary based on the Common Model you use and the frequency you set. That said, Merge can typically sync JobAdder data every hour, 3 hours, 6 hours, or 24 hours.

You can also sync data outside of these intervals via Merge’s Force Resync endpoint, and you can sync data in real-time by using Merge’s Automatic Webhooks feature.

Learn more about Merge’s sync frequencies for JobAdder.

What other ATS integrations does Merge support?

Merge supports dozens of additional applicant tracking system (ATS) integrations beyond JobAdder, including platforms like Greenhouse, Lever, iCIMS, SmartRecruiters, Workable, and Bullhorn.

With Merge's Unified API, you can integrate with any of these ATS solutions through a single API, making it easy to expand your ATS coverage and manage candidates, applications, and job data seamlessly across multiple platforms.

Learn about the other ATS integrations Merge supports.

What are some use cases for Merge’s integration with JobAdder?

While the use cases naturally depend on the type of application you provide, here are some common use cases:

If you provide a candidate sourcing solution, you can integrate with customers’ ATS solutions to seamlessly add recommended candidates

If you offer a candidate matchmaking platform, you can ingest the descriptions across open roles from customers’ ATS solutions and leverage them to match the best candidates with the different opportunities

If you have an AI solution that provides recommendations on your recruitment strategy, you can sync all of the customers’ data on candidates and feed it to your machine learning model. From there, your model can provide personalized and valuable outputs on the candidates that tend to receive offer letters and those that don’t

Learn more about Merge’s use cases with JobAdder—and any other ATS integration—here.

How long will it take you to add Merge’s JobAdder integration?

The process can be completed in just a few hours, and you’ll receive support from Merge’s team of solutions architects and customer success managers. In addition, once you’ve built to Merge’s Unified API, you can add dozens of other ATS integrations, saving your engineers countless time and effort.

Trusted to power integrations at

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

40+ Languages

Get Employee Data

1from merge import Merge
2
3client = Merge(
4    account_token="YOUR_ACCOUNT_TOKEN",
5    api_key="YOUR_API_KEY",
6)
7client.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>"),

1ApiClient client = Configuration.getDefaultApiClient();
2client.setBasePath('https://api.merge.dev/api/ats/v1');
3ApiKeyAuth tokenAuth = client.getAuthentication('tokenAuth');
4tokenAuth.setApiKey('API_KEY');
5CandidatesApi apiInstance = new CandidatesApi(client);
6apiInstance.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)

> {

"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": [

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