v2.2.0

Merge Node SDK Release Notes - Version [2.2.0]

This release includes support for all of the latest updates for the Merge API. For more information, see https://www.merge.dev/changelog

v2.1.3

Merge Node SDK Release Notes - Version [2.1.3]

Improvements

This release contains an update to correctly use the account token configured in category specific client initializations by default. See the below code snippet for an example:

import { ATS } from `@mergeapi/merge-node-client/api/resources/ats/clientClient';

const mergeClient = new ATS({
  apiKey: 'YOUR_API_KEY',
  accountToken: 'YOUR_ACCOUNT_TOKEN',
});

// now uses the account token specified in the client initialization
mergeclient.accountDetails.retrieve();

v2.1.2

Merge Node SDK Release Notes - Version [2.1.2]

Improvements

This release contains an update to add is_common_model_field to RemoteFieldClass in Accounting, CRM and Ticketing.

v2.1.1

Merge Node SDK Release Notes - Version [2.1.1]

Updates

This release contains updates to address CVE-2025-7783.

v2.1.0

Merge Node SDK Release Notes - Version [2.1.0]

This release includes support for all of the latest Accounting updates for the Merge API. For more information, see https://www.merge.dev/changelog

v2.0.1

Merge Node SDK Release Notes - Version [2.0.1]

Improvements

The release contains the following accounting updates:

• added company id as a query param to the GET /accounting/v1/employees and GET /accounting/v1/project endpoints

v2.0.0

Merge Node SDK Release Notes - Version [2.0.0]

This release includes support for all of the latest updates to the Merge API. For more information, see https://www.merge.dev/changelog

Breaking Changes

• AccessLevelEnum was renamed
  Usages of AccessLevelEnum need to be updated to TicketAccessLevelEnum in code. If you were importing AccessLevelEnum directly that would also need to be updated.

---

v1.1.9

Merge Node SDK Release Notes - Version [1.1.9]

Improvements

This release contains updates for the Accounting category

• Project endpoint
  Surface the GET /projects and GET /projects{id} endpoints. See the docs for more information and the code snippet below for usage.

import { MergeClient } from '@mergeapi/merge-node-client';
const merge = new MergeClient({
    apiKey: 'your api key',
    accountToken: 'your account token',
  });
const projects = await merge.accounting.projects.list();

• Add project field to related models
  Can now POST to /expenses with a specified project, as per the snippet below

import { MergeClient } from '@mergeapi/merge-node-client';
const merge = new MergeClient({
    apiKey: 'your api key',
    accountToken: 'your account token',
  });

const expense = await merge.accounting.expenses.create({
  "model": {
        "lines": [
            {
                "netAmount": -1,
                "description": "test projects",
                "account": "account id",
                "project": "project id",
            }
        ],
        "account": "account id",
        "memo": "testing projects - 1",
        "contact": "contact id",
        "currency": "USD",
        "exchangeRate": "1",
        "transactionDate": new Date("2025-06-05T00:00:00Z"),
        "integrationParams": {
            "PaymentType": "CreditCard"
        }
    }
  })

v.1.1.8

This change impacts only the Accounting Category.

• Added category_type and status query params on the /tracking-categories endpoint
• Added status query param on the /accounts endpoint
• Added status query param on the /contacts endpoint

v1.1.7

Note this change touches ALL categories, however it only impacts File Storage usage.

• Lots of code cleanup and improvements across all categories
• The Permission object in File Storage was incorrectly using the PermissionRequest object for RETRIEVE File and Folder endpoints. The request version of the object does not include the id, created_at, or modified_at fields given they are automatically generated by Merge. They should be returned however, when getting Permission objects.