List collection ticket comments in GitHub Enterprise Server (on-prem)
Issue Tracking API · read · 100% field coverage
Your agent can list collection ticket comments in GitHub Enterprise Server (on-prem) 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 Enterprise Server (on-prem) returns is screened before the agent sees it. Apideck adds the customer's GitHub Enterprise Server (on-prem) credentials, so no token ever reaches the agent.
The call
GET https://unify.apideck.com/issue-tracking/collections/{collection_id}/tickets/{ticket_id}/comments
Headers: x-apideck-service-id: github-server, plus your app id and the customer's consumer id. Apideck MCP tool: issue-tracking-collection-ticket-comments-all. Agent operation id: unified.issue-tracking.collectionTicketCommentsAll.
| 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 |
| ticket_id · required | path | ID of the ticket you are acting upon. |
| sort[by] | query | The field on which to sort the Comments |
| sort[direction] | query | The direction in which to sort the results |
More for collection ticket comments in GitHub Enterprise Server (on-prem)
create_collection_ticket_commentget_collection_ticket_commentupdate_collection_ticket_commentdelete_collection_ticket_comment
List collection ticket comments in other Issue Tracking apps
The same call works for each of these; only the service id changes.