Namely API

Integrate Namely with your product—along with any other
 HR & Payroll

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

Your Product
Your customers' data
Async Passthroughs
Audit Trails
Bank Info
Employee Payroll Runs
Employer Benefits
Field Mappings

Top integration use cases for Namely

Keep employee information up to date

Assuming your product needs to store clients’ employees and their associated information, the last thing you’ll want is to force clients to add, edit, or remove employees from your application manually. 

The task is not only time-intensive to perform but can also lead to significant human errors that compromise your clients’ security. For instance, a client can forget to deprovision former employees or input the wrong role for a new employee—giving them more permissions than the client intended.

By connecting your product with the clients’ systems of record for employees—which is often an HRIS, like Namely—, your clients don’t have to worry about managing their users in your product; employee information can be updated automatically and accurately in your application, as the changes will be based on the corresponding activities in the clients’ instances of Namely. 

In addition, you can trigger timely in-app automations based on the employee data your clients sync (e.g. issuing corporate cards to new hires based on their role and location). This lets your clients realize more value from your product and, as a result, increases their chances of staying on longer and spending more with your business.

Learn more about onboarding and offboarding employees in your product via Merge.

Assign trainings to employees with ease

Say your product allows organizations to offer learning and development courses to their employees (i.e. you provide a learning management system, or LMS).

Left to their own devices, your users would need to manually assign courses to various team members, which can be extremely time consuming (especially for bigger teams) and lead to critical mistakes. For instance, a user can accidentally forget to assign a course to a specific employee, or they can assign employees the wrong training.

You can streamline the task of assigning courses over time and minimize errors by integrating your product with Namely. More specifically, as new employees get added and/or relevant fields for longer-tenured employees change in Namely, the information can be reflected in your product. 

Based on the logic your clients set within your product, courses can then be assigned to the appropriate set of employees automatically.

Analyze employee data effectively

Imagine your product allows clients to analyze various types of data, including employee insights, to help them make strategic business decisions.

Having clients manually export files from Namely and import them to your product is cumbersome; and having them manually copy fields and objects from Namely and paste them to the associated places in your product is even worse. Also, if your clients don’t perform either of these activities on a frequent enough cadence, their analysis can be suboptimal, as it could rely on outdated, incomplete information. 

You can address these issues by integrating your product with Namely. 

Doing so lets you sync all of the objects and fields (that you want to include in your analysis) from Namely with your product in, or near, real-time. You can even let clients add additional steps in your product that streamlines the data sync further; for example, if certain fields or objects get added or updated in Namely, they can automatically get included in the clients’ reports that use it.

Read more

Sync Namely Data

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.

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
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) => {
import (
  merge ""
  mergeclient ""

client := mergeclient.NewClient(
employee, err := client.Hris().Employees().List(
    IncludeRemoteData: merge.Bool(true),
if err != nil {
  return err
fmt.Printf("Retrieved employee with ID %q\n", *employee.Id)
ApiClient client = Configuration.getDefaultApiClient();
ApiKeyAuth tokenAuth = client.getAuthentication('tokenAuth');
CandidatesApi apiInstance = new CandidatesApi(client);
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()
Employee employee = mergeClient.hris().employees().list(
"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": [
"work_email": "",
"personal_email": "",
"mobile_phone_number": "+1234567890",
"employments": [
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 Posts
A guide to integrating multiple APIs
A guide to integrating multiple APIs
Blog Posts
The top challenges of normalizing multiple API integrations
The top challenges of normalizing multiple API integrations
Blog Posts
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.
Read more