Skip to content
GitmoapAPIBeta
Identity & platformfeedback
POST/feedback

Send feedback about Gitmoap itself: a bug, a missing capability, a confusing result, an unhelpful error

create_feedback
  • feedback:create
    A token needs the feedback:create scope: Send feedback about Gitmoap itselfGranted by mcp_agent, mcp_agent_write, write_api.Every operation this scope unlocks
  • Audited · mutation

    x-gitmoap-audit: {"kind":"audited","arg":"mutation"}

  • Quota · feedback per day

    x-gitmoap-quota: {"kind":"enforced","arg":"feedback_per_day"}

A short summary of at most 500 characters, with optional details of up to 5000, the path of the page it is about, the MCP tool it is about or the reference an error gave. It is about the platform, never about a group or repository, so it changes nothing you own and stays allowed on a read-only connection; it is read only by platform administrators and kept for 90 days. Each sender may send up to 50 in any 24 hours. How it arrived — from the web app, through an MCP tool or directly over the API — is recorded from the request itself, never from its body.

Request body

application/json
  • kindFeedbackKindbugmissing_capabilityconfusing_resulterrorwrong_toolotherWhat the report is about: something broken, something missing, or something confusing.
  • summaryFeedbackSummary (string)What happened and what would have helped, in at most 500 characters. Never repository content, code, secrets or anything personal.
  • aboutFeedbackRequestRef (string) or nulloptionalThe reference an error gave, when the report is about one.
  • detailsFeedbackDetails (string) or nulloptionalMore about it, in at most 5000 characters: what you did, what you expected, what happened instead. The same rule as the summary: the problem, never the data.
  • pageFeedbackPage (string) or nulloptionalThe path of the page the report is about, such as /acme/api/-/merge_requests/87. The path alone: a query string or a fragment is refused.
  • toolFeedbackToolName (string) or nulloptionalThe MCP tool the report is about, when it is about one.
Request body exampleSynthesized example
{
"kind": "bug",
"summary": "summary-1022"
}

Responses

201Receivedapplication/json
  • created_atstringWhen the report arrived.
  • feedback_idFeedbackId (string · uuid)The report's reference — quote it if you write again about the same thing.
201 exampleSynthesized example
{
"created_at": "2026-10-08T22:16:44Z",
"feedback_id": "fe5d32db-455c-42ec-a3fd-c28b231cccf3"
}
400The report 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-5115",
"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-2338",
"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-10c5",
"message": "Draw the region map from operation density"
}
}
429You have sent as much feedback as you may in a dayapplication/json
Error codes
  • TOO_MANY_REQUESTSRetryableA quota, a rate limit or a transfer budget is spent. When the response carries Retry-After, retry after that many seconds
  • 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.
429 exampleSynthesized example
{
"error": {
"code": "code-2579",
"message": "Draw the region map from operation density"
}
}

CLI

gitmoap feedback create-feedback

  • --aboutstringoptional
  • --detailsstringoptional
  • --kindbug | missing_capability | confusing_result | error | wrong_tool | otherWhat the report is about: something broken, something missing, or something confusing.
  • --pagestringoptional
  • --summarystringWhat happened and what would have helped, in at most 500 characters. Never repository content, code, secrets or anything personal.
  • --toolstringoptional