--- title: GitLab API Integration on Truto slug: gitlab category: Ticketing canonical: "https://truto.one/integrations/detail/gitlab/" --- # GitLab API Integration on Truto **Category:** Ticketing **Status:** Generally available ## Unified APIs ### Unified CI/CD API - **Branches** — The branch represent a branch in the CI/CD. - **Pull-Requests** — - **Repos** — The repo represent a repository in the CI/CD. ### Unified User Directory API - **Groups** — Groups are a collection of users in the source application. In some applications, they might also be called Teams. - **Licenses** — Licenses represent concepts like user seats in apps that support them - **Me** — - **Roles** — The Role object represents a role of a User. - **Users** — The User object represents a User. - **Workspaces** — Workspaces represent concepts like teams, workspaces, projects in apps that support them ### Unified Ticketing API - **Comments** — Comments represent the communication happening on a Ticket, both between a User and a Contact and the internal things like notes, private comments, etc. A Ticket can have one or more Comments. - **Tags** — Tags represent a common classification approach used in various ticketing systems. A Ticket may have one or more Tags associated with them. - **Ticket Status** — Ticket Status represents the completion level of the Ticket. Some products provide customizing the Ticket Status. - **Ticket Types** — Ticket Types represent the classification system used by the underlying products for Tickets. Some examples are bugs, feature, incident, etc. - **Tickets** — Core resource which represents some work that needs to be carried out. Tickets are usually mapped to issues, tasks, work items, etc. depending on the underlying product. - **Workspaces** — Workspaces represent the top-level subdivision in a ticketing system. They usually have their own set of settings, tickets, statuses, priorities and users. Some of the usual terminologies used by the products for the top-level subdivision are projects, bases, spaces, workspace, etc. A Workspace could belong to an Organization. ## How it works 1. **Link your customer's GitLab account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach GitLab.** The Proxy API is a 1-to-1 mapping of the GitLab API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Sync customer-reported bugs to GitLab Issues** — Support and CRM platforms can let agents escalate bugs directly into GitLab as Issues, then track resolution status back in their own UI — so customers get notified the moment a fix ships. - **Ingest GitLab data for developer productivity analytics** — DevEx and DORA metrics platforms need read access to Merge Requests, Branches, and Repos across their customers' GitLab instances to calculate cycle time, review speed, and deployment frequency without building bespoke API integrations. - **Auto-create GitLab Issues from security or monitoring alerts** — Security posture and observability SaaS products can automatically open GitLab Issues tagged with severity labels and assigned to the right team, turning detected vulnerabilities or incidents into actionable engineering work. - **Mirror incident timelines into GitLab for engineering collaboration** — Incident management platforms can create GitLab Issues of type Incident and sync comments bi-directionally, letting engineers participate in incident response from whichever tool they prefer. - **Enrich Merge Request reviews with external context** — QA, testing, and code analysis tools can post comments directly on active GitLab Merge Requests with screenshots, test results, or compliance findings — giving developers feedback without leaving their workflow. ## What you can build - **Two-way ticket sync between your app and GitLab Issues** — Map your product's tasks or cases to GitLab Issues via the Unified Ticketing API so status changes, comments, and labels stay in sync across both platforms. - **Cross-platform comment mirroring** — Surface GitLab Issue and Merge Request comments inside your product so support agents, PMs, and engineers can collaborate without context-switching. - **Label-driven workflow automation** — React to GitLab label changes (e.g., 'Ready for QA' or 'Severity::High') via the Tags resource to trigger downstream actions like status updates or customer notifications in your app. - **Merge Request status dashboard for non-engineering stakeholders** — Pull Merge Request state and linked branch data through the Unified CI/CD API to give PMs and executives real-time visibility into code progress without GitLab access. - **Automated issue creation with smart assignment** — Combine the Unified Ticketing API and User Directory API to create GitLab Issues and assign them to the correct user or group based on repository ownership or team roles. - **User and group directory sync for access governance** — Read GitLab users, groups, roles, and licenses through the Unified User Directory API to power access reviews, onboarding workflows, or license optimization features in your product. ## FAQs ### What authentication methods does the GitLab integration support? GitLab supports OAuth 2.0 for SaaS (gitlab.com) instances and personal/project access tokens for both SaaS and self-managed deployments. Truto handles the OAuth flow and token refresh so your team doesn't manage auth state. ### How does GitLab terminology map to Truto's Unified APIs? GitLab Issues map to Tickets, Merge Requests map to Pull-Requests, Labels map to Tags, Notes/Discussions map to Comments, Projects map to both Repos and Workspaces, and Groups map to Groups in the User Directory API. ### Does Truto handle GitLab's API rate limits and pagination? Yes. Truto manages keyset and offset pagination across GitLab's REST API and respects rate-limit headers automatically, so your application receives consistent, complete result sets without building retry logic. ### Can I integrate with self-managed (on-premise) GitLab instances? Yes. Because Truto supports configurable base URLs and token-based auth, your end users can connect self-hosted GitLab instances — a common requirement in regulated industries like finance and government. ### Which Unified APIs cover GitLab today? GitLab is covered by three Unified APIs: the Unified Ticketing API (Tickets, Comments, Tags, Ticket Status, Ticket Types, Workspaces), the Unified CI/CD API (Branches, Pull-Requests, Repos), and the Unified User Directory API (Users, Groups, Roles, Licenses, Me, Workspaces). ### What if I need a GitLab endpoint that isn't in the Unified API? Truto builds custom tools on request. If you need access to GitLab-specific resources like Pipelines, Milestones, or Epics that aren't yet in the unified model, the Truto team can add support for your use case.