ServiceNow API

Integrate ServiceNow with your product—along with any other
Ticketing
 application

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

Ticketing

 

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

Get a demo
Your Product
Merge
Your customers' data
Accounts
Async Passthroughs
Attachments
Audit Trails
Collections
Comments
Contacts
Field Mappings
Projects
Roles
Scopes
Tags
Teams

Top integration use cases for ServiceNow

Read more

Sync ServiceNow Data

Accounts

The Account object is used to represent the account that a ticket is associated with. The account is a company that may be a customer. This does not represent the company that is receiving the ticket.

Docs
Attachments

The Attachment object is used to represent an attachment for a ticket.

Docs
Comments

The Comment object is used to represent a comment on a ticket.

Docs
Contacts

The Contact object is used to represent the customer, lead, or external user that a ticket is associated with.

Docs
Roles

The Role object is used to represent the set of actions & access that a user with this role is allowed to perform.

Docs
Tags

The Tag object is used to represent a tag or label for a ticket.

Docs
Teams

The Team object is used to represent a team within the company receiving the ticket.

Docs
Tickets

The Ticket object is used to represent a ticket or a task within a system.

Docs
Users

The User object is used to represent an employee within a company.

Docs

FAQ on integrating with ServiceNow’s API

How often does Merge sync ServiceNow data?

The frequency depends on the Common Model and sync setting you choose (Daily, Standard, High, Highest). 

That said, the frequencies are typically every 10 minutes, every hour, every 3 hours, or daily.

You can also sync data beyond these intervals by using Merge’s Force Resync Endpoint (allowing you to sync data ad hoc) or via Merge’s Automatic Webhooks feature (enabling you to sync data in real-time).

Learn more about Merge’s sync frequencies for ServiceNow data.

Which ServiceNow data fields are accessible through Merge?

Merge provides access to a wide range of ServiceNow endpoints, allowing you to sync tickets, users, attachments, comments, and more. Data from these fields is normalized into Merge’s common data models, streamlining retrieval and management within your application.

More specifically, you can POST incidents, attachments, and cases; and you can fetch information on teams, users, incidents, tasks, attachments, and more. 

Learn more about the ServiceNow data you can access and sync.

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

Merge offers a variety of pricing plans based on your usage needs. The Launch Plan provides up to 10 Production Linked Accounts at $650 per month, while larger-scale integrations require Professional or Enterprise plans. 

For tailored pricing information, visit Merge’s Pricing Page​​.

Which other ticketing integrations does Merge support besides ServiceNow?

Merge supports dozens of additional ticketing integrations, enabling you to easily connect to these systems at scale. Some of the other ticketing integrations available include:

  • Zendesk
  • Jira
  • Asana
  • Trello
  • Freshdesk
  • GitHub Issues
  • Intercom
  • Salesforce Service Cloud
  • ClickUp
  • Wrike

See the full list of ticketing integrations Merge supports.

What organizations use Merge’s integration with ServiceNow?

A wide range of organizations use Merge’s ServiceNow integrations, such as Drata and Thoropass.

What security measures and regulations does Merge comply with?

Merge maintains comprehensive compliance certifications, including SOC 2 Type 2, HIPAA, GDPR, CCPA, and ISO 27001. 

In addition, Merge provides a range of features to help customers provide secure integrations that only access and sync the data that’s absolutely necessary. This includes features like Scopes, Audit Trails, role-based access control, and multi-tenant support.

Learn more about Merge’s approach to security.

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