GitLab (via Apideck)

Access GitLab through Apideck's Issue Tracking unified API — one of 6 Issue Tracking connectors that share the same method surface. Code you write here ports to Jira, GitHub, Linear and 2 other Issue Tracking connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant GitLab plumbing.

Beta connector. GitLab is currently in beta on Apideck. Expect partial resource coverage and occasional mapping gaps. Always verify coverage (see below) and fall back to the Proxy API for unsupported operations.

Quick facts

• Apideck serviceId: gitlab
• Unified API: Issue Tracking
• Auth type: oauth2
• Status: beta
• GitLab docs: https://docs.gitlab.com/ee/api/
• Homepage: https://www.gitlab.com/

When to use this skill

Activate this skill when the user explicitly wants to work with GitLab — for example, "create a ticket in GitLab" or "comment on an issue in GitLab". This skill teaches the agent:

1. Which Apideck unified API covers GitLab (Issue Tracking)
2. The correct serviceId to pass on every call (gitlab)
3. GitLab-specific auth and coverage caveats

For the full method surface (parameters, pagination, filtering), use your language SDK skill:

• apideck-node, apideck-python, apideck-dotnet, apideck-java, apideck-go, apideck-php, or apideck-rest

For the raw OpenAPI spec:

• Issue Tracking: https://specs.apideck.com/issue-tracking.yml · API Explorer

Minimal example (TypeScript)

import { Apideck } from "@apideck/unify";

const apideck = new Apideck({
  apiKey: process.env.APIDECK_API_KEY,
  appId: process.env.APIDECK_APP_ID,
  consumerId: "your-consumer-id",
});

// List tickets in GitLab
const { data } = await apideck.issueTracking.tickets.list({
  serviceId: "gitlab",
});

Portable across 6 Issue Tracking connectors

The Apideck Issue Tracking unified API exposes the same methods for every connector in its catalog. Switching from GitLab to another Issue Tracking connector is a one-string change — no rewrite, no new SDK.

// Today — GitLab
await apideck.issueTracking.tickets.list({ serviceId: "gitlab" });

// Tomorrow — same code, different connector
await apideck.issueTracking.tickets.list({ serviceId: "jira" });
await apideck.issueTracking.tickets.list({ serviceId: "github" });

This is the compounding advantage of using Apideck over integrating GitLab directly: code against the unified Issue Tracking API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.

GitLab via Apideck Issue Tracking

GitLab Issues is mapped to Apideck's Issue Tracking unified API. Covers projects, issues, comments (notes), users, and labels.

Entity mapping

Coverage highlights

• ✅ CRUD on issues within projects
• ✅ Comments (notes)
• ✅ Labels as tags
• ❌ Merge requests — separate surface; use Proxy
• ❌ CI/CD pipelines, runners — use Proxy

Auth

• Type: OAuth 2.0, managed by Apideck Vault
• Self-hosted GitLab: the cloud gitlab connector targets gitlab.com. For self-hosted Data Center / CE, use the separate gitlab-server connector.
• Scopes: api scope for read/write access.

Example: list issues in a project

const { data } = await apideck.issueTracking.collectionTickets.list({
  serviceId: "gitlab",
  collectionId: "1234", // GitLab project ID
  filter: { status: "opened" },
});

Escape hatch: Proxy API

When an endpoint isn't covered by the Issue Tracking unified API, use Apideck's Proxy to call GitLab directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on GitLab's own API:

curl 'https://unify.apideck.com/proxy' \
  -H "Authorization: Bearer ${APIDECK_API_KEY}" \
  -H "x-apideck-app-id: ${APIDECK_APP_ID}" \
  -H "x-apideck-consumer-id: ${CONSUMER_ID}" \
  -H "x-apideck-service-id: gitlab" \
  -H "x-apideck-downstream-url: <target endpoint on GitLab>" \
  -H "x-apideck-downstream-method: GET"

See GitLab's API docs for available endpoints.

Sibling connectors

Other Issue Tracking connectors that share this unified API surface (same method signatures, just change serviceId):

jira (beta), github (beta), linear (beta), gitlab-server (beta), linear-multiworkspace (beta).

See also

• Issue Tracking OpenAPI spec · API Explorer
• apideck-connector-coverage — programmatic coverage checks
• apideck-best-practices — architecture, Vault, pagination, error handling
• apideck-node — TypeScript / Node SDK patterns
• GitLab official docs