Skip to content
GitmoapAPIBeta
Organizenotifications
GET/user/notifications

List the notifications sent to you

list_my_notifications
  • notification:read
    A token needs the notification:read scope: Read your notification preferences and the notifications sent to youGranted 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 reached you, on which channel and when, newest first — and what was held for your quiet hours or your digest, or not sent and why. Kept for ninety days. A notification about something you can no longer read is left out. Pages hold 1 to 100 entries, 20 by default.

Parameters

Query
  • limitinteger · int32optionalPage size (1-100, default 20)
  • next_tokenstringoptionalPagination cursor

Responses

200Your notifications, newest firstapplication/json
  • itemsarray of object
    • categoryNotificationCategorygate_requestedgate_expiringescalationquestion_to_youmentiondigest_readybudget_thresholdritual_inviteWhat it is about, by kind.
    • channelNotificationChannelin_appemailWhere it was meant to reach you.
    • created_atstringWhen it was written.
    • digestbooleanWhether it was, or will be, sent in your email digest.
    • intent_idNotificationIntentId (string · uuid)The notification.
    • linkstringWhere in the web app it leads.
    • stateNotificationDeliveryStatependingsendingsentdeferredsuppressedfailedWhere its delivery is.
    • subjectNotificationSubjectWhat it is about.
    • titlestringWhat it says.
    • next_attempt_atstring or nulloptionalWhen it is next due, while it is still owed.
    • sent_atstring or nulloptionalWhen it reached your inbox or the mail service.
    • suppressionNotificationSuppressionlost_accesssubject_resolvedaddress_suppressedor nulloptionalWhy it was not sent, when it was not.
  • next_tokenstring or nulloptional
200 exampleSynthesized example
{
"items": [
{
"category": "gate_requested",
"channel": "in_app",
"created_at": "2026-10-13T20:40:06Z",
"digest": false,
"intent_id": "10dd1cc6-1da1-4cd7-a15c-6f9e91a1e0e7",
"link": "link-727a",
"state": "pending",
"subject": {
"gate_id": "53fce380-af34-4588-87cd-20a62851643d",
"kind": "ai_gate"
},
"title": "Pin a page's payload to the build that rendered it"
}
],
"next_token": "next-token-8fdc"
}
400A 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-f521",
"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-642c",
"message": "Pin a page's payload to the build that rendered it"
}
}
403The caller is not a personapplication/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-a349",
"message": "Pin a page's payload to the build that rendered it"
}
}

CLI

gitmoap notifications list-my-notifications

  • --limitnumberoptionalPage size (1-100, default 20)
  • --next-tokenstringoptionalPagination cursor