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

Beta

Integrate GitLab with your product—along with any other
Ticketing
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 GitLab data

Collection

The Collection object is used to represent one or more Tickets. There can be a hierarchy of Collections, in which a sub-collection belongs to a parent-collection.

Comment

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

Project

Please use the Collection model. This model will be fully deprecated on 3/30/2024.

Role

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

Tag

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

Team

The Team object is used to represent one or more Users within the company receiving the ticket.

Ticket

The Ticket object is used to represent a ticket, issue, task or case.

User

The User object is used to represent a user with a login to the ticketing system. Users are either assignees who are directly responsible or a viewer on a Ticket/ Collection.

FAQ on integrating with GitLab API

What GitLab API endpoints does Merge interact with?

Merge interacts with several GitLab API endpoints to access and manage data. Here are just a few examples:

Comments: Accessed via POST /projects/{project_id}/issues/{issue_iid}/notes and GET /projects/{project_id}/issues/{issue_id}/notes
Tickets: Accessed via POST /projects/{project_id}/issues and GET /projects/{projects_id}/issues
Tags: Accessed via GET /projects/{project_id}/labels
Projects and Collections: Accessed via GET /groups/{group_id}/projects and GET /groups
Users: Accessed via GET /groups/{group_id}/members and GET /users/{user_id}

Learn more about the GitLab endpoints Merge can access and sync.

How frequently does Merge sync data with GitLab?

Merge requests data from GitLab at intervals determined by your sync plan:

Manual: Syncs are initiated manually
Daily: Data syncs every 24 hours
Standard: Syncs occur at standard intervals set by Merge. This is typically every 6 hours
High: More frequent syncs than the standard plan, and they are typically every 3 hours
Highest: Data syncs at the highest frequency supported by Merge, and they are typically every hour

For syncing outside of these intervals, you can use the Force Resync endpoint or the Automatic Webhooks feature.

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

Aside from GitLab, what ticketing platforms can I integrate with using Merge?

Merge offers integrations with dozens of ticketing platforms, including:

Jira (including Jira Data Center and Jira Service Management)
Zendesk
Asana
Freshdesk
GitHub Issues
GitLab
ServiceNow
Trello
Linear
Azure DevOps
ClickUp
HubSpot Ticketing
Basecamp

See the full list of ticketing integrations Merge supports.

What organizations use Merge’s GitLab integration?

A wide range of businesses use it, including Thoropass and Drata.

Learn more about how Merge’s customers use the GitLab integration—along with Merge’s other ticketing integrations—here.

How long does it take developers to set up a GitLab integration?

Developers can typically integrate with Merge's Ticketing Unified API within a few days. Once the connection is established, you can not only add the GitLab integration to your product but also 30+ additional ticketing integrations.

How does Merge log GitLab data and how long does it retain data?

Merge retains logs based on your plan:

Launch Plan: Logs are searchable and retained for 3 days
Professional Plan: Logs are searchable for 10 days and retained for 30 days
Enterprise Plan: Logs are searchable for 10 days and retained for 90+ days

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

The cost of integrating with GitLab depends on your Merge plan:

Launch Plan: Free for the first three Production Linked Accounts, $650/month for up to 10 Linked Accounts, and $65 per account after that
Professional and Enterprise Plans: Include additional features like Field Mapping, Remote Data, and Passthrough Requests at customized pricing

Learn more about Merge’s pricing plans by visiting this page.

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