Skip to content
GitmoapAPIBeta
Coderepositories
GET/user/starred

List the repositories the caller has starred, most recently starred first

list_my_starred_repositories
  • repo:read
    A token needs the repo:read scope: View repositories and metadataGranted 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"}

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

Every repository you starred that you can still see. A service account stars nothing, so it gets an empty list. Page with next_token.

Parameters

Query
  • limitinteger · int32optionalMaximum number of items to return
  • next_tokenstringoptionalPagination token

Responses

200Starred repositories listedapplication/json
  • itemsarray of Repository
    • The Repository schema
    • created_atstring
    • created_byUserId (string · uuid)
    • default_branchBranchName (string)
    • full_pathFullPath (string)
    • group_idGroupId (string · uuid)
    • repository_idRepositoryId (string · uuid)
    • repository_nameEntityName (string)
    • starsinteger · int32
    • updated_atstring
    • visibilityVisibilitypublicinternalprivate
    • ancestor_group_idsarray of GroupId (string · uuid)optional
    • avatarstring or nulloptional
    • descriptionstring or nulloptional
    • display_namestring or nulloptional
    • size_bytesinteger · int64optional0–∞Cached on-disk git object size in bytes, refreshed after each push. Rolls up to the namespace (root group) storage quota.
  • next_tokenstring or nulloptional
200 exampleSynthesized example
{
"items": [
{
"created_at": "2026-10-10T10:05:34Z",
"created_by": "b7e2d1c0-9f8e-4d7c-a6b5-c4d3e2f1a0b9",
"default_branch": "main",
"full_path": "acme/payments-api",
"group_id": "4c1d8e2f-6a3b-4f90-b7c5-1e2d3c4b5a69",
"repository_id": "5b0e7c2a-9d14-4e8b-a6f1-2c3d4e5f6a70",
"repository_name": "payments-api",
"stars": 83,
"updated_at": "2026-10-14T18:20:57Z",
"visibility": "public"
},
{
"created_at": "2026-10-12T06:29:17Z",
"created_by": "c9d8e7f6-a5b4-4c3d-9e2f-1a0b9c8d7e6f",
"default_branch": "main",
"full_path": "acme/payments-api",
"group_id": "4c1d8e2f-6a3b-4f90-b7c5-1e2d3c4b5a69",
"repository_id": "5b0e7c2a-9d14-4e8b-a6f1-2c3d4e5f6a70",
"repository_name": "payments-api",
"stars": 40,
"updated_at": "2026-10-12T20:58:39Z",
"visibility": "public"
}
],
"next_token": "next-token-1cbb"
}
401Unauthenticatedapplication/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-0b11",
"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-d996",
"message": "Label every synthesized example"
}
}

CLI

gitmoap repos list-my-starred

  • --limitnumberoptionalMaximum number of items to return
  • --next-tokenstringoptionalPagination token

Used in these guides