Update collection ticket in GitHub
Issue Tracking API · write, waits for approval · 100% field coverage
Your agent can update collection ticket in GitHub through Apideck's Issue Tracking API, the same call it makes for every Issue Tracking app. It changes data in the customer's GitHub account, so it stops with the exact request until a person approves it. Apideck adds the customer's GitHub credentials, so no token ever reaches the agent.
The call
PATCH 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-update. Agent operation id: unified.issue-tracking.collectionTicketsUpdate.
| Parameter | In | Description |
|---|---|---|
| ticket_id · required | path | ID of the ticket you are acting upon. |
| collection_id · required | path | The collection ID |
Body fields
| Field | Type | Description |
|---|---|---|
| parent_id | string | The ticket's parent ID |
| type | string | The ticket's type |
| subject | string | Subject of the ticket |
| description | string | The ticket's description. HTML version of description is mapped if supported by the third-party platform |
| status | string | The current status of the ticket. Possible values include: open, in_progress, closed, or - in cases where there is no cl |
| priority | string | Priority of the ticket |
| assignees | array | |
| due_date | string | Due date of the ticket |
| tags | array |
More for collection tickets in GitHub
list_collection_ticketscreate_collection_ticketget_collection_ticket
Update 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