Skip to content
GitmoapAPIBeta
Planissue-comments
GET/repositories/{repo_id}/issues/{issue_id}/discussions

List a work item's discussion threads

list_issue_discussions
  • issue_comment:read
    A token needs the issue_comment:read scope: View work-item comments and timelinesGranted by mcp_agent, mcp_agent_write, read_api, read_repository, write_api, write_repository.Every operation this scope unlocks
  • Single-resource

    x-gitmoap-isolation: {"kind":"single_or_self_scoped"}

Returns every thread on the work item in one response — each top-level comment with all of its replies — threads and replies oldest first. Anyone who can see the work item may list them — on a public repository, without signing in.

Parameters

Path
  • repo_idRepositoryId (string · uuid)Repository ID
  • issue_idIssueId (integer · int64)The per-scope iid

Responses

200The threadsapplication/json
  • repliesarray of CommentThe replies, oldest first.
  • rootCommentThe comment that starts the thread, general or inline.
200 exampleSynthesized example
[
{
"replies": [
{
"author": {},
"body": "Renders each region as density contours of its operations.",
"comment_id": "23e2498a-2d24-4bcc-8110-a264b6779acd",
"created_at": "2026-10-10T07:18:27Z",
"edited": false,
"merge_request_id": 42,
"reply_count": 7,
"repository_id": "5b0e7c2a-9d14-4e8b-a6f1-2c3d4e5f6a70",
"thread_id": "7132d566-4840-4439-a915-2e07e33fa683",
"updated_at": "2026-10-15T20:46:49Z"
}
],
"root": {
"author": {
"email": "tomas@acme.example",
"id": "id-5bfe",
"username": "lin"
},
"body": "Renders each region as density contours of its operations.",
"comment_id": "dbbf0136-4528-45b2-bfcd-17370022e2b5",
"created_at": "2026-10-09T04:15:25Z",
"edited": false,
"merge_request_id": 42,
"reply_count": 2,
"repository_id": "5b0e7c2a-9d14-4e8b-a6f1-2c3d4e5f6a70",
"thread_id": "0d88c845-fdc0-4d65-b125-ffd2dd7d137a",
"updated_at": "2026-10-14T08:58:11Z"
}
},
{
"replies": [
{
"author": {},
"body": "Renders each region as density contours of its operations.",
"comment_id": "4ba26e02-a327-42af-8da2-66ce58a8e08f",
"created_at": "2026-10-17T04:10:41Z",
"edited": false,
"merge_request_id": 42,
"reply_count": 1,
"repository_id": "5b0e7c2a-9d14-4e8b-a6f1-2c3d4e5f6a70",
"thread_id": "06de1284-76be-4574-8950-892a888ea42d",
"updated_at": "2026-10-17T00:05:57Z"
},
{
"author": {},
"body": "Renders each region as density contours of its operations.",
"comment_id": "c88b7f16-8a14-4406-b33b-82a4bd79acef",
"created_at": "2026-10-09T15:10:08Z",
"edited": false,
"merge_request_id": 42,
"reply_count": 6,
"repository_id": "5b0e7c2a-9d14-4e8b-a6f1-2c3d4e5f6a70",
"thread_id": "6b7d00ae-c22e-472f-a4cf-59e4cf421c17",
"updated_at": "2026-10-16T10:41:57Z"
}
],
"root": {
"author": {
"email": "lin@acme.example",
"id": "id-3287",
"username": "tomas"
},
"body": "Renders each region as density contours of its operations.",
"comment_id": "2df6c898-c230-4916-b2db-7480acc2d508",
"created_at": "2026-10-11T03:51:09Z",
"edited": false,
"merge_request_id": 42,
"reply_count": 7,
"repository_id": "5b0e7c2a-9d14-4e8b-a6f1-2c3d4e5f6a70",
"thread_id": "06141a97-cdd0-4790-90b7-be93b944f330",
"updated_at": "2026-10-16T06:59:44Z"
}
}
]
400Bad request — a path parameter is not a well-formed value of its typeapplication/json
Error codes
  • BAD_REQUESTThe request is malformed: a parameter or a body field is not a well-formed value of its type
  • errorErrorBody
    • The ErrorBody schema
    • codestringThe coarse category, tied to the status: NOT_FOUND, CONFLICT, INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all.
    • messagestringWhat went wrong, for a person. Written to be read, not parsed: match on reason or code.
    • fieldstring or nulloptionalOn a 400 that refused one field's value, the field, as its JSON path: email, items[0].name. Put the message under that input. Absent on every other error.
    • reasonstring or nulloptionalThe specific code, when the error has one: LAST_ORGANIZATION_OWNER, BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and on code otherwise.
    • required_scopestring or nulloptionalThe scope the access token was missing, on INSUFFICIENT_SCOPE.
    • violationsanyoptionalPresent on the structured-validation errors (PROVIDER_VALIDATION_FAILED per-node, PIPELINE_VALIDATION_FAILED DAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.
400 exampleSynthesized example
{
"error": {
"code": "code-8697",
"message": "Inline scalar newtypes but keep their brand"
}
}
401Unauthenticated — no credential, or an invalid oneapplication/json
Error codes
  • UNAUTHORIZEDNo credential was sent, or the one sent is invalid, expired or revoked
  • errorErrorBody
    • The ErrorBody schema
    • codestringThe coarse category, tied to the status: NOT_FOUND, CONFLICT, INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all.
    • messagestringWhat went wrong, for a person. Written to be read, not parsed: match on reason or code.
    • fieldstring or nulloptionalOn a 400 that refused one field's value, the field, as its JSON path: email, items[0].name. Put the message under that input. Absent on every other error.
    • reasonstring or nulloptionalThe specific code, when the error has one: LAST_ORGANIZATION_OWNER, BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and on code otherwise.
    • required_scopestring or nulloptionalThe scope the access token was missing, on INSUFFICIENT_SCOPE.
    • violationsanyoptionalPresent on the structured-validation errors (PROVIDER_VALIDATION_FAILED per-node, PIPELINE_VALIDATION_FAILED DAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.
401 exampleSynthesized example
{
"error": {
"code": "code-2983",
"message": "Label every synthesized example"
}
}
403Forbidden — the caller's access level or token scope is insufficientapplication/json
Error codes
  • FORBIDDENYou are signed in but may not do this here; reason names the permission or the rule that refused it
  • INSUFFICIENT_SCOPEThe access token lacks the scope this operation needs; required_scope names it
  • PERMISSION_REQUIREDYou need a permission you do not hold here; the message names it
  • errorErrorBody
    • The ErrorBody schema
    • codestringThe coarse category, tied to the status: NOT_FOUND, CONFLICT, INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all.
    • messagestringWhat went wrong, for a person. Written to be read, not parsed: match on reason or code.
    • fieldstring or nulloptionalOn a 400 that refused one field's value, the field, as its JSON path: email, items[0].name. Put the message under that input. Absent on every other error.
    • reasonstring or nulloptionalThe specific code, when the error has one: LAST_ORGANIZATION_OWNER, BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and on code otherwise.
    • required_scopestring or nulloptionalThe scope the access token was missing, on INSUFFICIENT_SCOPE.
    • violationsanyoptionalPresent on the structured-validation errors (PROVIDER_VALIDATION_FAILED per-node, PIPELINE_VALIDATION_FAILED DAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.
403 exampleSynthesized example
{
"error": {
"code": "code-e1c0",
"message": "Draw the region map from operation density"
}
}
404Work item not foundapplication/json
Error codes
  • NOT_FOUNDThe resource does not exist — or exists and you cannot see it: a private resource you have no access to answers exactly as an absent one does
  • errorErrorBody
    • The ErrorBody schema
    • codestringThe coarse category, tied to the status: NOT_FOUND, CONFLICT, INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all.
    • messagestringWhat went wrong, for a person. Written to be read, not parsed: match on reason or code.
    • fieldstring or nulloptionalOn a 400 that refused one field's value, the field, as its JSON path: email, items[0].name. Put the message under that input. Absent on every other error.
    • reasonstring or nulloptionalThe specific code, when the error has one: LAST_ORGANIZATION_OWNER, BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and on code otherwise.
    • required_scopestring or nulloptionalThe scope the access token was missing, on INSUFFICIENT_SCOPE.
    • violationsanyoptionalPresent on the structured-validation errors (PROVIDER_VALIDATION_FAILED per-node, PIPELINE_VALIDATION_FAILED DAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.
404 exampleSynthesized example
{
"error": {
"code": "code-feae",
"message": "Pin a page's payload to the build that rendered it"
}
}

CLI

gitmoap issue-comments list-issue-discussions

  • --repo-ididRepository ID (id or owner/repo path)
  • --issue-ididThe per-scope iid

Used in these guides