Skip to content
GitmoapAPIBeta
Reviewmerge-requests
GET/groups/{group_id}/merge-requests/cards

List merge requests across a group's subtree as rich cards

list_group_merge_request_cards
  • merge_request:read
    A token needs the merge_request:read scope: View merge requestsGranted by mcp_agent, mcp_agent_write, read_api, read_repository, write_api, write_repository.Every operation this scope unlocks
  • Filtered across resources

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

  • Paginated
    Pass the next_token a page returns to get the next one.

The card form of the group listing: each merge request with its author, reviewers, approvals, commit and comment counts, open threads and diff size, most recently updated first. Merge requests in repositories you cannot read are left out, and cards here carry no merge-readiness badge. Pages hold up to 25 cards, 10 by default.

Parameters

Path
  • group_idGroupId (string · uuid)Group ID
Query
  • statusstringoptionalFilter by status: open, merged, closed
  • searchstringoptionalSearch the title and description by word or phrase, or the title by any part of it
  • limitinteger · int32optionalPage size (1-25, default 10)
  • next_tokenstringoptionalPagination cursor

Responses

200Group merge request cards listedapplication/json
  • itemsarray of MergeRequestCard
    • The MergeRequestCard schema
    • approvalsApprovalSummary
    • authorActorSummary
    • comments_countinteger · int320–∞
    • commits_countinteger · int320–∞
    • created_atstring
    • diffDiffSummary
    • is_draftboolean
    • merge_request_idMergeRequestId (integer · int64)
    • repository_idRepositoryId (string · uuid)
    • reviewersarray of CardReviewer
      • The CardReviewer schema
      • emailstring
      • idstring
      • review_statusReviewStatuspendingapprovedrejected
      • stalebooleanWhether this reviewer's approval predates the current source-branch tip (approved an older revision). Computed at read time; always present.
      • usernamestring
      • avatar_urlstring or nulloptional
    • source_branchBranchName (string)
    • statusMergeRequestStatusopenmergedclosed
    • target_branchBranchName (string)
    • threadsThreadSummary
    • titleMrTitle (string)
    • updated_atstring
    • author_can_pushboolean or nulloptionalWhether the author can push to the repository — false for a drive-by contributor's merge request. Absent where it was not computed.
    • is_stackedbooleanoptionalTrue when the merge request is part of a stack: an open merge request is based on it, or it is based on one.
    • mergeMergeStatusSummary or nulloptional
    • my_review_statusReviewStatuspendingapprovedrejectedor nulloptionalYour own review status on the merge request. Present only in the listing of merge requests awaiting your review.
    • pipeline_stateMrPipelineStatependingrunningfailedpassedemptyor nulloptionalWhere the merge request's pipelines stand at its head: pending, running, failed, passed, or empty when no pipeline applies. Present only in a repository's own listing, whether or not the repository requires the pipelines to pass.
  • next_tokenstring or nulloptional
200 exampleSynthesized example
{
"items": [
{
"approvals": {
"given": 73,
"required": 38
},
"author": {
"email": "lin@acme.example",
"id": "id-6c60",
"username": "lin"
},
"comments_count": 4,
"commits_count": 2,
"created_at": "2026-10-13T03:58:17Z",
"diff": {
"additions": 62,
"deletions": 49
},
"is_draft": false,
"merge_request_id": 42,
"repository_id": "5b0e7c2a-9d14-4e8b-a6f1-2c3d4e5f6a70",
"reviewers": [],
"source_branch": "feature/region-legend",
"status": "open",
"target_branch": "main",
"threads": {
"resolved": 40,
"total": 1
},
"title": "Stream pipeline status into the run header",
"updated_at": "2026-10-09T09:59:07Z"
},
{
"approvals": {
"given": 24,
"required": 10
},
"author": {
"email": "mara@acme.example",
"id": "id-31c5",
"username": "mara"
},
"comments_count": 7,
"commits_count": 2,
"created_at": "2026-10-09T14:07:08Z",
"diff": {
"additions": 62,
"deletions": 31
},
"is_draft": false,
"merge_request_id": 42,
"repository_id": "5b0e7c2a-9d14-4e8b-a6f1-2c3d4e5f6a70",
"reviewers": [],
"source_branch": "fix/payload-build-pin",
"status": "open",
"target_branch": "main",
"threads": {
"resolved": 5,
"total": 4
},
"title": "Inline scalar newtypes but keep their brand",
"updated_at": "2026-10-15T11:18:25Z"
}
],
"next_token": "next-token-eb05"
}
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-fa49",
"message": "Pin a page's payload to the build that rendered it"
}
}
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-b9f3",
"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-c395",
"message": "Stream pipeline status into the run header"
}
}
404Not found — or found and private, which is masked as absentapplication/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-bee6",
"message": "Draw the region map from operation density"
}
}

CLI

gitmoap mr list-group-cards

  • --group-ididGroup ID (id or group path)
  • --limitnumberoptionalPage size (1-25, default 10)
  • --next-tokenstringoptionalPagination cursor
  • --searchstringoptionalSearch the title and description by word or phrase, or the title by any part of it
  • --statusstringoptionalFilter by status: open, merged, closed

Used in these guides