Skip to content
GitmoapAPIBeta
Identity & platformfeedback
GET/admin/feedback

The feedback people and agents have sent, newest first (platform admin)

list_feedback
  • feedback:read
    A token needs the feedback:read scope: Read agents' feedback about Gitmoap (platform admins)Granted by read_api, write_api.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.

Filter by kind, by the MCP tool a report is about, or to reports sent after an instant. Each report shows who sent it, how it arrived, the client that sent it and, for a bug, whether the support desk was told. Only platform administrators, in a signed-in session, can read it.

Parameters

Query
  • kindFeedbackKindbugmissing_capabilityconfusing_resulterrorwrong_toolotheroptionalOnly reports of this kind
  • toolstringoptionalOnly reports about this MCP tool
  • sincestringoptionalOnly reports sent after this instant (RFC 3339)
  • limitinteger · int32optionalPage size (1-100)
  • next_tokenstringoptionalPagination cursor

Responses

200Feedback listedapplication/json
  • itemsarray of FeedbackView
    • The FeedbackView schema
    • channelFeedbackChannelwebmcprestHow it arrived: from the web app, through an MCP tool, or over the API.
    • created_atstringWhen it arrived.
    • feedback_idFeedbackId (string · uuid)The report's reference.
    • kindFeedbackKindbugmissing_capabilityconfusing_resulterrorwrong_toolotherWhat the report is about.
    • senderActorSummaryThe person or service account that sent it, as they are named now.
    • summaryFeedbackSummary (string)What happened and what would have helped, in the sender's words.
    • aboutFeedbackRequestRef (string) or nulloptionalThe reference an error gave, when it is about one.
    • clientstring or nulloptionalThe client application: the name an MCP client gave itself, or the User-Agent the request carried.
    • deliveryDeskMailStatependingsendingdeliveredfailedor nulloptionalWhere the support desk's notice of it is, for a report that owes one.
    • detailsFeedbackDetails (string) or nulloptionalMore about it, when the sender gave more.
    • oauth_client_idstring or nulloptionalThe app the person approved, when the token came from connecting it by signing in.
    • pageFeedbackPage (string) or nulloptionalThe path of the page it is about, when it came from the web app.
    • toolFeedbackToolName (string) or nulloptionalThe MCP tool it is about, when it is about one.
  • next_tokenstring or nulloptional
200 exampleSynthesized example
{
"items": [
{
"channel": "web",
"created_at": "2026-10-11T04:15:25Z",
"feedback_id": "bab9fa6c-c6a8-4b81-86f3-34b5276b2760",
"kind": "bug",
"sender": {
"email": "lin@acme.example",
"id": "id-ebf5",
"username": "mara"
},
"summary": "summary-a003"
}
],
"next_token": "next-token-e84c"
}
400A filter is not validapplication/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-3292",
"message": "Stream pipeline status into the run header"
}
}
401Unauthorizedapplication/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-3581",
"message": "Stream pipeline status into the run header"
}
}
403Platform administrators onlyapplication/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-54d9",
"message": "Draw the region map from operation density"
}
}

CLI

gitmoap feedback list-feedback

  • --kindbug | missing_capability | confusing_result | error | wrong_tool | otheroptionalOnly reports of this kind
  • --limitnumberoptionalPage size (1-100)
  • --next-tokenstringoptionalPagination cursor
  • --sincestringoptionalOnly reports sent after this instant (RFC 3339)
  • --toolstringoptionalOnly reports about this MCP tool