Get collection ticket in GitHub
Issue Tracking API · read · 81% field coverage
Your agent can get collection ticket in GitHub 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 GitHub returns is screened before the agent sees it. Apideck adds the customer's GitHub credentials, so no token ever reaches the agent.
The call
GET https://unify.apideck.com/issue-tracking/collections/{collection_id}/tickets/{ticket_id}
Headers: x-apideck-service-id: github, plus your app id and the customer's consumer id. Apideck MCP tool: issue-tracking-collection-tickets-one. Agent operation id: unified.issue-tracking.collectionTicketsOne.
| 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 GitHub
list_collection_ticketscreate_collection_ticketupdate_collection_ticket
Get collection ticket in other Issue Tracking apps
The same call works for each of these; only the service id changes.
GitHub Enterprise Server (on-prem)GitLabGitLab server (on-prem)JiraLinearLinear Multiworkspace