Delete collection ticket in GitLab
Issue Tracking API · write, waits for approval · 10% field coverage
Your agent can delete collection ticket in GitLab through Apideck's Issue Tracking API, the same call it makes for every Issue Tracking app. It changes data in the customer's GitLab account, so it stops with the exact request until a person approves it. Apideck adds the customer's GitLab credentials, so no token ever reaches the agent.
The call
DELETE https://unify.apideck.com/issue-tracking/collections/{collection_id}/tickets/{ticket_id}
Headers: x-apideck-service-id: gitlab, plus your app id and the customer's consumer id. Apideck MCP tool: issue-tracking-collection-tickets-delete. Agent operation id: unified.issue-tracking.collectionTicketsDelete.
| Parameter | In | Description |
|---|---|---|
| ticket_id · required | path | ID of the ticket you are acting upon. |
| collection_id · required | path | The collection ID |
More for collection tickets in GitLab
list_collection_ticketscreate_collection_ticketget_collection_ticketupdate_collection_ticket
Delete collection ticket in other Issue Tracking apps
The same call works for each of these; only the service id changes.