GitLab API: what you can do and how to use it with AI agents
The GitLab API covers projects, repositories, issues, merge requests, CI/CD pipelines, groups and users, in REST and GraphQL. Engineering and DevOps teams use it, on GitLab.com as well as on self-managed instances. Access is through a personal, project or group token, or OAuth.
What the GitLab API offers
Projects and repositories
Files, branches, commits, tags and comparisons.
Issues
Create issues, add labels, milestones, assignees and comments.
Merge requests
Open, discussions, approvals and merge.
Pipelines and jobs
CI/CD runs, logs, artifacts and retries.
Groups and members
Group structure, members and access levels.
Webhooks
Push, MR, issue and pipeline events.
How to access the GitLab API
- Public APIA personal, project or group access token with scopes (for example api or read_api), or OAuth 2.0. On self-managed instances, the base URL is your company's server.
- Request limits differ between GitLab.com and self-managed instances.
- Tokens with the api scope give broad access: prefer read_api when it is enough.
- CI variables and logs can contain secrets: the agent must not pass them on.
Official documentation: docs.gitlab.com/api
What an iTeam agent does with the GitLab API
Red pipeline explained
The agent reads the log of the failed job, summarizes the likely cause and comments on the merge request, tagging whoever made the commit.
Forgotten merge requests
The agent lists MRs with no review for days and nudges the reviewers in Slack or Teams.
A well-written support issue
Technical tickets from support become issues with reproduction steps, environment and priority, in the right project.
Sprint changelog
When the milestone closes, the agent gathers the merged MRs and drafts the changelog for review.
From the credential to the agent at work, with approval
Create a project or group token
Use minimum scopes and the lowest role that works. On self-managed, provide the instance URL.
Register it in the iTeam vault
The token stays in the vault and each agent has its own permissions. Triage does not merge.
Test with approval
Merges, deploy retries and configuration changes go through human approval.
Ready-made AI teams for this work
Questions about the GitLab API
Is the GitLab API free?
Generally yes: the API is available on all plans. Some features it exposes depend on the plan.
Do I need to code to use the GitLab API with iTeam?
Not necessarily. GitLab is in the app catalog, and the deployment team sets up the flows.
Does it work with self-managed GitLab?
Yes, as long as iTeam can reach the instance, over the network or a tunnel approved by IT.
