Skip to content
GitmoapAPIBeta
Organizeattention
GET/user/attention

List the caller's attention inbox

list_my_attention_items
  • attention:read
    A token needs the attention:read scope: Read your attention inbox and activity feedGranted by read_api, write_api.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 merge requests, work items, pipeline runs and repositories waiting on you, most recently updated first. state picks pending items (the default, including snoozes whose time has passed), snoozed, done or all; reason and target_kind narrow further, and an unknown value is refused rather than ignored. Items about something you can no longer see are left out. Pages hold 1 to 50 items (20 by default).

Parameters

Query
  • statestringoptionalpending (default) | snoozed | done | all
  • reasonstringoptionalComma-separated attention reasons
  • target_kindstringoptionalmerge_request | issue | pipeline_run | repository
  • limitinteger · int32optionalPage size (1-50, default 20)
  • next_tokenstringoptionalPagination cursor

Responses

200The caller's inbox, newest firstapplication/json
  • itemsarray of object
    • attention_idAttentionId (string · uuid)
    • created_atstring
    • principal_idPrincipalId (string · uuid)
    • reasonAttentionReasonreview_requestedchanges_requestedreview_approvedmr_ready_to_mergemr_restack_requiredmr_unmergeablemr_commentedassignedissue_commentedcriterion_failedissue_regressedblocked_by_resolvedpipeline_failedpipeline_not_starteddeployment_approval_requestedmentionedaccess_grantedaccess_expiringmarkedWhy an item is in front of you.
    • stateAttentionStatependingsnoozeddoneWhere an item is in its life.
    • targetAttentionTargetRef
    • updated_atstring
    • actorActorSummary or nulloptionalWho caused the item, as they are now. Absent when nobody did, such as for a bookmark.
    • notestring or nulloptionalYour own note, on a bookmark only.
    • resolved_atstring or nulloptional
    • snoozed_untilstring or nulloptional
  • next_tokenstring or nulloptional
200 exampleSynthesized example
{
"items": [
{
"attention_id": "fbaac6d7-a6ce-4120-876c-889676519697",
"created_at": "2026-10-08T13:27:05Z",
"principal_id": "6bb79644-af03-4ed0-9865-2f616bdf3da6",
"reason": "review_requested",
"state": "pending",
"target": {
"kind": "merge_request",
"merge_request_iid": 42,
"repository_id": "5b0e7c2a-9d14-4e8b-a6f1-2c3d4e5f6a70"
},
"updated_at": "2026-10-11T06:57:13Z"
},
{
"attention_id": "fd958bdb-df91-4e90-85d9-0efe69bba036",
"created_at": "2026-10-14T11:43:46Z",
"principal_id": "b8956b77-1a6a-4813-a448-e98d9e9b0a8e",
"reason": "review_requested",
"state": "pending",
"target": {
"kind": "merge_request",
"merge_request_iid": 42,
"repository_id": "5b0e7c2a-9d14-4e8b-a6f1-2c3d4e5f6a70"
},
"updated_at": "2026-10-09T20:40:44Z"
}
],
"next_token": "next-token-a348"
}
400Unknown filter value or malformed 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-cf43",
"message": "Draw the region map from operation density"
}
}
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-c3e3",
"message": "Draw the region map from operation density"
}
}
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-aca3",
"message": "Inline scalar newtypes but keep their brand"
}
}

CLI

gitmoap attention list-my-attention-items

  • --limitnumberoptionalPage size (1-50, default 20)
  • --next-tokenstringoptionalPagination cursor
  • --reasonstringoptionalComma-separated attention reasons
  • --statestringoptionalpending (default) | snoozed | done | all
  • --target-kindstringoptionalmerge_request | issue | pipeline_run | repository

Used in these guides