# gitlab.issues

**stable** **Advanced**

Recent issues of a GitLab.com project.

`GET /v1/gitlab/issues`

## What you get

A list of GitLab results in Onekey's unified shape, in `data` (an array). An empty array is a normal, successful answer and is charged like any other; a source that reports "nothing found" as an error returns a free `404 not_found` instead.

## What it costs

- **Advanced · 5 credits** for a fresh fetch, charged only when it succeeds.
- **Free when served from cache (0.2 credit for a cached response over 100 KB).**
- **Free** if the request is invalid (never charged) or the source fails or reports not found (refunded).

## Parameters

| Name | Type | Required | Default | What it is | Constraints |
| --- | --- | --- | --- | --- | --- |
| `project` | string | yes | (required) | Project path (group/project) or numeric id | max 200 chars; must match `[A-Za-z0-9_][A-Za-z0-9_.-]*(?:/[A-Za-z0-9_][A-Za-z0-9_.-]*)*`; trimmed, lowercased |

## Request

```bash
curl "https://api.onekey.dev/v1/gitlab/issues?project=gitlab-org%2Fgitlab" \
  -H "x-api-key: YOUR_API_KEY"
```

```python
import requests

res = requests.get(
    "https://api.onekey.dev/v1/gitlab/issues",
    params={"project": "gitlab-org/gitlab"},
    headers={"x-api-key": "YOUR_API_KEY"},
)
body = res.json()

if body["success"]:
    print(body["data"])
else:
    print(body["error"]["code"], body["error"]["message"])
```

```javascript
const params = new URLSearchParams({ project: "gitlab-org/gitlab" });
const res = await fetch(`https://api.onekey.dev/v1/gitlab/issues?${params}`, {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const body = await res.json();

if (body.success) console.log(body.data);
else console.error(body.error.code, body.error.message);
```

## Recorded response

A real GitLab response, recorded and returned in Onekey's shape. Fields the platform does not provide are `null`.

```json
{
  "success": true,
  "data": [
    {
      "content": {
        "id": "631178",
        "title": "Remove temporary index tmp_idx_group_audit_events_on_group_id_created_at_mcp_enabled",
        "text": "## Summary\n\nRemove the temporary index `tmp_idx_group_audit_events_on_group_id_created_at_mcp_enabled` from `group_audit_events`.\n\nThe index only supports the `McpServerDefaultTrueForGroups` batched background migration (https://gitlab.com/gitlab-org/gitlab/-/merge_requests/257102). Nothing else reads MCP audit events by name, so it can be dropped once that migration is finalized.\n\n- Index scheduled in: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/257148\n- Index added synchronously in: https://gitlab.com/gitlab-org/gitlab/-/work_items/631175\n- The batched migration is queued in 19.5 (a required stop), so it can be finalized in 19.6 and the index removed in 19.7.\n\n## Steps\n\n1. Confirm `McpServerDefaultTrueForGroups` has been finalized.\n1. Add a post-deployment migration that drops the index with `remove_concurrent_partitioned_index_by_name`.\n\nRelated to https://gitlab.com/gitlab-org/gitlab/-/work_items/630175",
        "url": "https://gitlab.com/gitlab-org/gitlab/-/work_items/631178",
        "createdAt": "2026-09-28T19:45:56Z",
        "updatedAt": "2026-09-28T19:45:56Z",
        "state": "opened"
      },
      "author": {
        "username": "jessieay",
        "displayName": "Jessie Young"
      },
      "engagement": {
        "comments": 0,
        "likes": 0
      },
      "ext": {
        "labels": [
          "backend",
          "category:agent tools",
          "database"
        ]
      }
    },
    {
      "content": {
        "id": "631177",
        "title": "Spike: Microsoft Teams as a second GitLab Duo messaging surface, capability parity with Slack and reuse analysis",
        "text": "<!--IssueSummary start-->\n\n<details>\n<summary>\n\nEveryone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/engineering/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.\n\n</summary>\n\n- [Label this issue](https://contributors.gitlab.com/manage-issue?action=label&projectId=278964&issueIid=631177)\n\n</details>\n\n<!--IssueSummary end-->\n\n## Context\n\nGitLab Duo in Slack (&22305) is heading to GA. Its backend is split into a platform-neutral messaging adapter layer (`Ai::Messaging::Adapters::Base`, `AdapterRegistry`, `CallbackWorker`/`ProgressDeliveryWorker`, the `slack_assistant/v1` flow from &23521) and a Slack-specific shell (`Slack::API`, `Slack::Manifest`, `SlackIntegration`, `Integrations::SlackEvents::*`, `Integrations::SlackInteractions::*`, `Ai::Messaging::Adapters::Slack`). &23521 set the principle \"nothing Slack-specific below the adapter\", and #607447 already asks for a messaging API that could serve Microsoft Teams.\n\nReliable numbers on which chat tool our customers live in are hard to get: we have no Teams app, so there is no usage to measure, and integration data only shows who wired a notification webhook to a project. Our working assumption is roughly 60% of users on Slack and 40% on Microsoft Teams, with Teams skewing towards larger, Microsoft-first enterprises on self-managed and Dedicated. Those customers are asking for Duo in Teams directly ",
        "url": "https://gitlab.com/gitlab-org/gitlab/-/work_items/631177",
        "createdAt": "2026-09-28T19:36:43Z",
        "updatedAt": "2026-09-28T19:46:05Z",
        "state": "opened"
      },
      "author": {
        "username": "jannik_lehmann",
        "displayName": "Jannik Lehmann"
      },
      "engagement": {
        "comments": 1,
        "likes": 0
      },
      "ext": {
        "labels": [
          "backend",
          "category:external agents",
          "devops::agent foundations"
        ]
      }
    }
  ],
  "metadata": {
    "platform": "gitlab",
    "endpoint": "issues",
    "cached": false,
    "stale": false,
    "age_s": 0,
    "fetched_at": "2026-01-01T12:00:00+00:00",
    "credits_charged": 5,
    "request_id": "7f3a9c2e5b1d4c8fa2e6d0b9c4f18e37"
  },
  "error": null
}
```

## Field mapping

How this endpoint's source fields become Onekey's [unified schema](https://onekey.dev/docs/schema.md). Fields the source lacks come back as `null`.

| Source path | Onekey field | Transform |
| --- | --- | --- |
| `iid` | `content.id` | `toString` |
| `title` | `content.title` | - |
| `description` | `content.text` | - |
| `web_url` | `content.url` | `safeUrl` |
| `created_at` | `content.createdAt` | `toIsoDate` |
| `updated_at` | `content.updatedAt` | `toIsoDate` |
| `state` | `content.state` | - |
| `author.username` | `author.username` | - |
| `author.name` | `author.displayName` | - |
| `user_notes_count` | `engagement.comments` | `toNumber` |
| `upvotes` | `engagement.likes` | `toNumber` |
| `labels` | `ext.labels` | - |

## Caching and freshness

- Fresh for about 2 minutes. Repeat calls in that window are served from cache and are free.
- Between 2 minutes and 15 minutes the cached copy is still served instantly and marked `stale: true` while Onekey refreshes it in the background.
- If the source is down when a refresh is needed, the last copy can be served for up to 1 hour more (marked stale).
- A "not found" is remembered for 1 minute and is free.
- The cache is shared across all customers, which is what keeps repeat calls cheap.

## What can go wrong

| Status | Code | What to do |
| --- | --- | --- |
| 401 | `unauthorized` | Check the `x-api-key` header. |
| 402 | `insufficient_credits` | [Add credits](https://onekey.dev/pricing); your balance must cover the price. |
| 404 | `not_found` | Unknown endpoint path. |
| 422 | `invalid_params` | Fix the parameters using the table above. Free. |
| 429 | `rate_limited` | Wait `Retry-After` seconds, then retry. |
| 502 | `upstream_error` | The source failed. Refunded; retry with backoff. |

See [Errors](https://onekey.dev/docs/errors.md) for the full list and retry guidance.

Status: stable (verified against the live source).