Skip to content
GitmoapAPIBeta
Organizeactivity
GET/user/activity

List the caller's own activity across every namespace they reach

list_my_activity
  • 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.

What you did — merge requests, work items, repositories, releases and pipelines — newest first, leaving out anything in a group or repository you can no longer see. The window defaults to the last 30 days and may span at most 366; domain narrows the kinds, and an unknown one is refused rather than ignored. Pages hold 1 to 50 entries (20 by default); other sizes are clamped.

Parameters

Query
  • domainstringoptionalComma-separated: merge_request, issue, repository, release, pipeline, member
  • fromstringoptionalRFC-3339 start of the window (default: 30 days ago)
  • tostringoptionalRFC-3339 end of the window (default: now)
  • limitinteger · int32optionalPage size (1-50, default 20; out-of-range values clamp)
  • next_tokenstringoptionalPagination cursor
  • actorstringoptionalIgnored here: this feed is already one person's activity

Responses

200The caller's activity, newest firstapplication/json
  • itemsarray of object
    • domainActivityDomain (string)
    • event_idActivityEventId (string · uuid)
    • kindActivityKind (string)
    • metadataobjectBounded free-form detail; the shape varies by kind and is documented per event.
    • occurred_atstringWhen it happened. A feed is ordered by this.
    • scopeActivityScope
    • actorActorSummary or nulloptionalWho did it. Absent when the platform did — a pipeline nobody triggered, a scheduled action.
    • subjectActivitySubject or nulloptional
      • The ActivitySubject schema
      • iidinteger · int64 or nulloptionalThe subject's number, as it is now — a work item that has moved since shows its new number.
      • titlestring or nulloptionalThe subject's title: its current title while it exists, the title it had at the time once it has been deleted. Absent when neither is known.
      • uidIssueUid (string · uuid) or nulloptionalThe subject's permanent identifier, for a work item.
  • next_tokenstring or nulloptional
200 exampleSynthesized example
{
"items": [
{
"domain": "domain-4560",
"event_id": "b8f202d6-e596-4ae8-9aa5-51f5842179ff",
"kind": "kind-861a",
"metadata": {},
"occurred_at": "2026-10-14T12:41:00Z",
"scope": {
"full_path": "acme/payments-api",
"id": "id-3171",
"type": "group"
}
}
],
"next_token": "next-token-045b"
}
400Unknown domain, malformed window, or bad 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-bf20",
"message": "Stream pipeline status into the run header"
}
}
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-4d36",
"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-891c",
"message": "Draw the region map from operation density"
}
}

CLI

gitmoap activity list-my-activity

  • --actorstringoptionalIgnored here: this feed is already one person's activity
  • --domainstringoptionalComma-separated: merge_request, issue, repository, release, pipeline, member
  • --fromstringoptionalRFC-3339 start of the window (default: 30 days ago)
  • --limitnumberoptionalPage size (1-50, default 20; out-of-range values clamp)
  • --next-tokenstringoptionalPagination cursor
  • --tostringoptionalRFC-3339 end of the window (default: now)

Used in these guides