GitLab Python API Docs | dltHub

Build a GitLab-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

GitLab REST API supports authentication via personal access tokens or OAuth tokens, and includes endpoints for projects, issues, merge requests, and more. OpenAPI documentation is available for interactive API usage. The API is used for automating GitLab operations. The REST API base URL is https://<gitlab_host>/api/v4 and all requests that require auth accept Personal/Project/Group access tokens or OAuth2; recommended header is PRIVATE-TOKEN or Authorization: Bearer.

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading GitLab data in under 10 minutes.


What data can I load from GitLab?

Here are some of the endpoints you can load from GitLab:

ResourceEndpointMethodData selectorDescription
projectsprojectsGETList projects
groupsgroupsGETList groups
usersusersGETList users
issuesprojects/:id/issues or groups/:id/issuesGETList issues for project or group
merge_requestsprojects/:id/merge_requestsGETList merge requests
commitsprojects/:id/repository/commitsGETList commits for project
pipelinesprojects/:id/pipelinesGETList pipelines

How do I authenticate with the GitLab API?

GitLab supports multiple auth methods; pass Personal/Project/Group access tokens in the PRIVATE-TOKEN header or use OAuth2 tokens via Authorization: Bearer. Some CI/job endpoints accept JOB-TOKEN headers.

1. Get your credentials

  1. Sign in to GitLab (gitlab.com or self-managed). 2) For a personal access token: User Settings > Access Tokens, choose scopes (api for full REST API), create token, copy value (only shown once). 3) For project/group tokens: Project/Group > Settings > Access Tokens (or Access Tokens menu), create and copy. 4) For OAuth: register an application in Settings > Applications to obtain client_id/client_secret and exchange for access token. 5) Store token securely.

2. Add them to .dlt/secrets.toml

[sources.gitlab_source] private_token = "your_personal_access_token_here"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

dlt ai toolkit rest-api-pipeline install

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the GitLab API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

python gitlab_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline gitlab_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset gitlab_data The duckdb destination used duckdb:/gitlab.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline gitlab_pipeline show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads projects and issues from the GitLab API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def gitlab_source(private_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<gitlab_host>/api/v4", "auth": { "type": "api_key", "private_token": private_token, }, }, "resources": [ {"name": "projects", "endpoint": {"path": "projects"}}, {"name": "issues", "endpoint": {"path": "projects/:id/issues"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="gitlab_pipeline", destination="duckdb", dataset_name="gitlab_data", ) load_info = pipeline.run(gitlab_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("gitlab_pipeline").dataset() sessions_df = data.projects.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM gitlab_data.projects LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("gitlab_pipeline").dataset() data.projects.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load GitLab data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install

Was this page helpful?

Community Hub

Need more dlt context for GitLab?

Request dlt skills, commands, AGENT.md files, and AI-native context.