Get collection user in GitHub
Issue Tracking API · read · 100% field coverage
Your agent can get collection user 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}/users/{id}
Headers: x-apideck-service-id: github, plus your app id and the customer's consumer id. Apideck MCP tool: issue-tracking-collection-users-one. Agent operation id: unified.issue-tracking.collectionUsersOne.
| Parameter | In | Description |
|---|---|---|
| collection_id · required | path | The collection ID |
| id · required | path | ID of the record you are acting upon. |
More for collection users in GitHub
Get collection user 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)Jira