List collection tickets in GitLab
Issue Tracking API · read · 86% field coverage
Your agent can list collection tickets in GitLab through Apideck's Issue Tracking API, the same call it makes for every Issue Tracking app. It only reads, so it runs straight away; what GitLab returns is screened before the agent sees it. Apideck adds the customer's GitLab credentials, so no token ever reaches the agent.
The call
GET https://unify.apideck.com/issue-tracking/collections/{collection_id}/tickets
Headers: x-apideck-service-id: gitlab, plus your app id and the customer's consumer id. Apideck MCP tool: issue-tracking-collection-tickets-all. Agent operation id: unified.issue-tracking.collectionTicketsAll.
| Parameter | In | Description |
|---|---|---|
| cursor | query | Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response. |
| limit | query | Number of results to return. Minimum 1, Maximum 200, Default 20 |
| collection_id · required | path | The collection ID |
| sort[by] | query | The field on which to sort the Tickets |
| sort[direction] | query | The direction in which to sort the results |
| filter[status] | query | Filter by ticket status, can be `open`, `closed` or `all`. Will passthrough if none of the above match |
| filter[since] | query | Only return tickets since a specific date |
| filter[assignee_id] | query | Only return tickets assigned to a specific user |
More for collection tickets in GitLab
create_collection_ticketget_collection_ticketupdate_collection_ticketdelete_collection_ticket
List collection tickets in other Issue Tracking apps
The same call works for each of these; only the service id changes.
GitHubGitHub Enterprise Server (on-prem)GitLab server (on-prem)JiraLinearLinear Multiworkspace