GitLab project issues API

Use the GitLab project issues API to retrieve public issue records with status, labels and project references. Provide project path or ID (path); refine the result with record state (state), search expression or keywords (q). Issue records retain the reported problem or task beside its state, labels, assignees and project references, helping callers follow triage and ownership without interpreting the list as a stream of code commits. Track reported defects or tasks, compare labels and assignees and organise project follow-up by state or milestone. The detail page provides the supported parameters, request examples, available response examples and usage pricing for this operation.

Selected price
$0.002 / billing creditPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Project path (namespace/project), its gitlab.com link, or the numeric project id.
Optional parameters (22)
`opened` (default), `closed` or `all`.
Search words in title and description.
Label names, comma-separated (all must match).
Milestone title.
Author's username.
Assignee's username.
ISO 8601 time.
ISO 8601 time.
ISO 8601 time.
ISO 8601 time.
Sort field (default `created_at`).
`desc` (default) or `asc`.
Work item type.
`true` or `false`.
Page number (default 1).
Results per page (default 20, max 100).
One issue by its number (the number in its URL). The answer then holds that issue in `items` and `item`, with its full reference, closed by, time tracking, blocking issues count, epic and iteration.
0 leaves out the bulky `raw` source blocks (often 10-30x smaller).
Comma-separated fields to return, e.g. `posts.id,posts.title`. Call metadata is always included.
1 skips the 24-hour cache and fetches live.
JSON only for this OpenAny product. Omit output or use json; CSV and NDJSON exports are not exposed.
Native CSV/NDJSON record selector; it has no effect on this JSON-only product.

Sample response

"cached": false
"count": 20
"credits_used": 1
items [3]
[0] {}
"assignees": []
"author": {
  "avatar": "https://gitlab.com/uploads/-/system/user/avatar/1388762/avatar.png?v=1793772205",
  "name": "Pedro Pombeiro",
  "url": "https://gitlab.com/pedropombeiro",
  "username": "pedropombeiro"
}
"closed_at": null
"confidential": false
"created_at": "2026-11-03T16:13:38.680Z"
descriptionString · text preview
items[0].description
## Summary

After #39573, #39574, and #39535, most configuration-caused failures on GitLab.com hosted runners report an accurate failure rea…
"downvotes": 0
"draft": null
"due_date": null
"id": 208998292
"iid": 40235
"labels": [
  "Category:Runner Core",
  "automation:quick-win-judged",
  "… 7 more"
]
"merge_requests_count": 0
"milestone": null
"severity": "UNKNOWN"
"state": "opened"
"task_completion": {
  "completed_count": 0,
  "count": 0
}
"title": "Container-start and pre-request secrets configuration errors are still reported as `runner_system_failure`"
"type": "issue"
"updated_at": "2026-11-04T00:09:19.404Z"
"upvotes": 0
"url": "https://gitlab.com/gitlab-org/gitlab-runner/-/work_items/40235"
"user_notes_count": 1
"weight": null
[1] {}
"assignees": []
"author": {
  "avatar": "https://secure.gravatar.com/avatar/afa743e48382b2e91a7668a4847acd0df4cae8bad2709b42e1075722f5e885d2?s=80&d=identicon",
  "name": "stampaaaron",
  "url": "https://gitlab.com/stampaaaron",
  "username": "stampaaaron"
}
"closed_at": null
"confidential": false
"created_at": "2026-11-02T16:12:09.341Z"
descriptionString · text preview
items[1].description

## Summary

On a Windows shell-executor runner, `step_script` hangs indefinitely after the job's script has visibly finished all its work (…
"downvotes": 0
"draft": null
"due_date": null
"id": 208860627
"iid": 40234
"labels": [
  "Category:Runner Core",
  "automation:ml",
  "… 8 more"
]
"merge_requests_count": 0
"milestone": null
"severity": "UNKNOWN"
"state": "opened"
"task_completion": {
  "completed_count": 0,
  "count": 0
}
"title": "Windows shell executor: step_script hangs forever - gitlab-runner.exe itself holds orphaned pipe handles after every child process is confir…"
"type": "issue"
"updated_at": "2026-11-03T09:09:05.108Z"
"upvotes": 0
"url": "https://gitlab.com/gitlab-org/gitlab-runner/-/work_items/40234"
"user_notes_count": 2
"weight": null
2: "… 18 more"
"next_page": 2
"page": 1
"project": "gitlab-org/gitlab-runner"
"state": "opened"
"total": 2583
"total_pages": 130

Response result

Response structure

Inferred from examples
  • cachedboolean
  • countinteger
  • credits_usedinteger
  • items(object | string)[]
    • assigneesunknown[]
    • authorobject
      • avatarstring
      • namestring
      • urlstring
      • usernamestring
    • closed_atnull
    • confidentialboolean
    • created_atstring
    • descriptionstring
    • downvotesinteger
    • draftnull
    • due_datenull
    • idinteger
    • iidinteger
    • labelsstring[]
    • merge_requests_countinteger
    • milestonenull
    • severitystring
    • statestring
    • task_completionobject
      • completed_countinteger
      • countinteger
    • titlestring
    • typestring
    • updated_atstring
    • upvotesinteger
    • urlstring
    • user_notes_countinteger
    • weightnull
  • next_pageinteger
  • pageinteger
  • projectstring
  • statestring
  • totalinteger
  • total_pagesinteger

Loading related APIs…

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use GitLab project issues API with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.