Skip to content
GitmoapAPIBeta
Planissues
GET/user/issues

List the work items assigned to the caller

list_my_issues
  • issue:read
    A token needs the issue:read scope: Read work items and their settingsGranted 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.

Returns the work items assigned to you in every repository and group, a page at a time, most recently updated first, with the status, type, label, milestone and search filters. Work items in places you can no longer see are left out, so a page can hold fewer than limit entries while next_token still leads to more. You must be signed in.

Parameters

Query
  • status_categorystringoptionalStatus category
  • status_idstringoptionalThe named status within its category
  • typestringoptionalWork-item type
  • labelstringoptionalLabel key
  • milestonestringoptionalMilestone ID
  • searchstringoptionalWords to find in the title or description, or part of the title
  • limitinteger · int32optionalPage size (default 20, max 100)
  • next_tokenstringoptionalPagination cursor

Responses

200The caller's assigned work itemsapplication/json
  • itemsarray of object
    • created_atstring
    • created_byActorSummaryWho created the work item, as they were when they created it.
    • iidIssueId (integer · int64)
    • root_scope_idGroupId (string · uuid)The top-level group the item's group or repository belongs to.
    • scope_idstring
    • scope_typeScopeTypegrouprepositoryWhether the item lives in a group or a repository. With scope_id and iid it forms the item's current address — the #412 a person types — which changes when the item moves.
    • status_categoryStatusCategorytriagetodoin_progressin_reviewblockeddonecancelledThe fixed category of the item's current status, which boards, filters and progress rollups work from.
    • status_idStatusId (string)
    • titleIssueTitle (string)
    • uidIssueUid (string · uuid)The work item's permanent identifier. Unlike its number, it never changes, even when the item moves to another group or repository.
    • updated_atstringWhen the work item last changed, ISO 8601. Listings order by it, newest first.
    • work_item_typeWorkItemTypeepicstorybugtaskspikechoreincidentsub_taskThe kind of work item. The type decides where an item may live (a group or a repository), which types it may have as children, and which fields it accepts.
    • ancestor_group_idsarray of GroupId (string · uuid)optionalThe groups the item sits beneath, nearest first.
    • ancestor_issue_uidsarray of IssueUid (string · uuid)optionalThe item's ancestors' permanent identifiers, nearest first, for display. It can briefly lag behind a change of parent higher up the chain.
    • assignee_idsarray of PrincipalId (string · uuid)optionalThe people assigned to the work item. Absent when nobody is.
    • author_can_pushboolean or nulloptionalWhether the author can push to where this work item lives — its repository, or a group work item's group. False for a drive-by contributor's text. Absent where it was not computed.
    • closed_atstring or nulloptional
    • closed_byPrincipalId (string · uuid) or nulloptional
    • descriptionMarkdownDoc (string) or nulloptional
    • labelsarray of LabelKey (string)optionalThe keys of the labels applied to the work item. Absent when it has none.
    • milestone_idMilestoneId (string · uuid) or nulloptional
    • milestone_scope_idstring or nulloptional
    • milestone_scope_typeScopeTypegrouprepositoryor nulloptionalWhether the item's milestone belongs to a group or a repository — not necessarily the item's own, since a group milestone can hold work items from several repositories.
    • parent_refIssueRef or nulloptionalThe parent's current address, for display. Absent when the item has no parent.
    • parent_uidIssueUid (string · uuid) or nulloptionalThe parent work item's permanent identifier, if the item has a parent.
    • pointsinteger · int32 or nulloptional0–∞
    • regressed_atstring or nulloptional
    • regressed_at_shaCommitHash (string) or nulloptionalThe commit whose evidence proved the regression — the first known bad commit, and the upper end of the range of suspect commits.
    • regressed_from_shaCommitHash (string) or nulloptionalThe commit at which the item was last verified, kept when it regresses — the last known good commit.
    • regressed_run_idPipelineRunId (string · uuid) or nulloptional
    • severitySeveritycriticalhighmediumlowor nulloptional
    • type_profileBlueprintRef or nulloptionalThe custom type this item was filed as, pointing at the group or repository where the blueprint is defined. work_item_type still decides where the item may live, its children and its fields; the blueprint adds a display label and facets. Absent for an item filed as a plain built-in type.
    • verificationVerificationStateunverifiedverifiedregressedoptionalWhether CI has proved the work item's acceptance criteria. unverified until a pipeline run proves them, verified once one has, and regressed when a later run shows that evidence no longer holds.
    • verified_atstring or nulloptional
    • verified_at_shaCommitHash (string) or nulloptionalThe commit at which CI proved the acceptance criteria. Absent until a pipeline run has.
    • verified_run_idPipelineRunId (string · uuid) or nulloptional
    • versioninteger · int64optional0–∞The work item's revision, incremented on every change. Send it back with an update; if the item has changed since you read it, the update is refused with a 409.
  • next_tokenstring or nulloptional
200 exampleSynthesized example
{
"items": [
{
"created_at": "2026-10-12T06:25:00Z",
"created_by": {
"email": "mara@acme.example",
"id": "id-4177",
"username": "lin"
},
"iid": 28,
"root_scope_id": "4c1d8e2f-6a3b-4f90-b7c5-1e2d3c4b5a69",
"scope_id": "6ed484e1-e25f-47a3-8250-6c08925a3bdc",
"scope_type": "group",
"status_category": "triage",
"status_id": "6b3e23c1-6b49-4790-af17-48e747b6f5a7",
"title": "Pin a page's payload to the build that rendered it",
"uid": "144f5657-a0c1-4934-930d-06c8e20ba813",
"updated_at": "2026-10-10T13:44:49Z",
"work_item_type": "epic"
},
{
"created_at": "2026-10-15T10:00:46Z",
"created_by": {
"email": "tomas@acme.example",
"id": "id-e4cf",
"username": "lin"
},
"iid": 63,
"root_scope_id": "4c1d8e2f-6a3b-4f90-b7c5-1e2d3c4b5a69",
"scope_id": "16f18564-838a-4d87-87a6-e7756fee83fe",
"scope_type": "group",
"status_category": "triage",
"status_id": "be12b5ec-5905-49fe-85f2-3acc4bbce9ad",
"title": "Draw the region map from operation density",
"uid": "db7737db-7336-4c91-b2bc-44708adba1d2",
"updated_at": "2026-10-16T15:16:05Z",
"work_item_type": "epic"
}
],
"next_token": "next-token-3665"
}
400Invalid filter or cursorapplication/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-2fd4",
"message": "Inline scalar newtypes but keep their brand"
}
}
401Not authenticatedapplication/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-c1d7",
"message": "Stream pipeline status into the run header"
}
}
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-5e2d",
"message": "Label every synthesized example"
}
}

CLI

gitmoap issues list-my

  • --labelstringoptionalLabel key
  • --limitnumberoptionalPage size (default 20, max 100)
  • --milestonestringoptionalMilestone ID
  • --next-tokenstringoptionalPagination cursor
  • --searchstringoptionalWords to find in the title or description, or part of the title
  • --status-categorystringoptionalStatus category
  • --status-idstringoptionalThe named status within its category
  • --typestringoptionalWork-item type

Used in these guides