Skip to content
GitmoapAPIBeta
Identity & platformfeedback
GET/admin/feedback/{feedback_id}

One report (platform admin) — what the support desk's notice of a bug links to

get_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

Everything the report says and how it arrived. Only platform administrators, in a signed-in session, can read it.

Parameters

Path
  • feedback_idFeedbackId (string · uuid)The report's reference

Responses

200The reportapplication/json
  • 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.
200 exampleSynthesized example
{
"channel": "web",
"created_at": "2026-10-10T02:44:45Z",
"feedback_id": "5a43c7ed-e126-404b-a160-b06b327cb7a7",
"kind": "bug",
"sender": {
"email": "mara@acme.example",
"id": "id-66c7",
"username": "tomas",
"avatar_url": "https://gitmoap.example/acme/98024e98"
},
"summary": "summary-7dca",
"about": "about-e70f",
"client": "client-69c2",
"delivery": "pending",
"details": "details-abe2",
"oauth_client_id": "8d46826c-c3d2-4399-8014-93b310f72f6c",
"page": "page-c62c",
"tool": "tool-0302"
}
400Bad request — a path parameter is not a well-formed value of its typeapplication/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-660e",
"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-31f7",
"message": "Draw the region map from operation density"
}
}
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-f7b5",
"message": "Label every synthesized example"
}
}
404No such report: it may have been deletedapplication/json
Error codes
  • NOT_FOUNDThe resource does not exist — or exists and you cannot see it: a private resource you have no access to answers exactly as an absent one does
  • 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.
404 exampleSynthesized example
{
"error": {
"code": "code-b1c6",
"message": "Pin a page's payload to the build that rendered it"
}
}

CLI

gitmoap feedback get-feedback

  • --feedback-ididThe report's reference