Justworks API

Integrate Justworks with your product—along with any other
HR & Payroll
 application

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

HR & Payroll

 

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

Get a demo
Your Product
Merge
Your customers' data
Async Passthroughs
Audit Trails
Bank Info
Benefits
Companies
Dependents
Employee Payroll Runs
Employees
Employer Benefits
Employments
Field Mappings
Groups
Locations

Top integration use cases for Justworks

Read more

Sync Justworks Data

Companies

The Company object is used to represent a company within the HRIS / Payroll system.

Docs
Employees

The Employee object is used to represent any person who has been employed by a company.

Docs
Employments

The Employment object is used to represent a job position at a company. If an integration supports historical tracking of employments, it will be reflected in the data. If not, a new Employment object will be created whenever there is a change in job title or pay. The effective_date field should be used to order Employment objects, with the most recent date corresponding to the latest employment record for an employee.

Docs
Groups

The Group object is used to represent any subset of employees across, for example, DEPARTMENT or TEAM. Employees can be in multiple Groups.

Docs
Locations

The Location object is used to represent an address that can be associated with an employee.

Docs
Teams

The Team object is used to represent a subdivision of the company, usually a department. Each employee will be grouped into one specific Team.

Docs
Time Off

The TimeOff object is used to represent all employees' Time Off entries.

Docs
Time Off Balances

The TimeOffBalance object is used to represent current balances for an employee's Time Off plan.

Docs

FAQ on integrating with Justworks’s API

How frequently can Merge sync Justworks data?

The sync frequency depends on the Common Model(s) you use and the frequency setting you set (Daily, Standard, High, and Highest). That said, you can typically sync data every 24 hours.

You can also use Merge’s Force Resync endpoint to sync data ad hoc and you can use Merge’s Automatic Webhooks feature to sync data in real-time.

Learn more about Merge’s sync frequencies for Justworks.

What customers use Merge’s Justworks integration?

A wide range of organizations leverage it, including enterprise businesses like BILL, Electric, and AngelList.

You can learn more about the organizations that use it—along with Merge’s other HRIS and payroll integrations—here.

What other HRIS and payroll integrations does Merge support?

In addition to Justworks, Merge’s HRIS Unified API lets you add more than 70 integrations. This includes ADP Workforce Now, BambooHR, Gusto, UKG, Workday, and many others. 

Merge’s Common Models also standardize key data points across different providers, making it easy to extend integrations as your needs evolve. 

See the full list of supported HRIS and payroll integrations here.

Does Merge have a partnership with Justworks?

Yes, Merge not only has a formal partnership with Justworks but also has agreements with other HRIS providers, like Workday and Paylocity.

Can I map custom fields from Justworks into my application?

Yes, Merge’s Field Mapping feature allows you to map custom fields from Justworks to target fields within Merge’s Common Models, which simplifies data normalization and integration. Field Mapping can be accessed via the Merge dashboard for easy configuration​.

Can I directly access Justworks data endpoints not included in the Common Model?

With Merge's Authenticated Passthrough Request feature, which is available to customers on Professional and Enterprise plans, you can access Justworks data directly from endpoints outside of Merge’s Common Model, offering flexibility for specific data needs​.

How will Merge support our team?

Merge provides support across all stages of the partnership. This including technical support, onboarding, and guidance on using advanced features. Depending on your plan, you can also get a dedicated customer success manager, solutions architect, and solutions engineer, and have a dedicated Slack channel to get any of your questions or concerns addressed quickly.

How is your customers' Justworks data encrypted and where is it stored?

Merge encrypts all data at rest and in transit using AES-256 encryption. Data is also stored within Amazon Web Services (AWS) data centers, which provide enterprise-grade security. 

For users that need to meet specific data residency requirements, Merge offers both U.S. and EU multi-tenant storage options as well as a single-tenant option, which can host data in any AWS region of your choice​​.

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
HRIS
HRIS
Read more