NovumOS · Schema

FeedbackResponse

One feedback row as its submitter sees it (spec §25.4). ``org_id`` / ``user_id`` are omitted for the same reason :class:`~app.schemas.notification.NotificationResponse` omits them: the caller IS the owner, so echoing the ownership keys back adds nothing and only widens the surface. **No ``jira_*`` field at all.** Not the issue key or URL (§25.9: the user never sees an internal issue id — it leaks backlog structure and means nothing to a customer), not ``jira_last_error`` (platform-admin-only, §25.10), and — since NOV-443 — not ``jira_status`` either. A submitter has no use for the state of an integration they cannot see, and every value it can take is either uninformative or actively misleading: ``pending`` reads as "not dealt with yet", ``skipped`` and ``failed`` describe OUR misconfiguration and OUR outage as though they were something that happened to the report. The report is durable in either case (§25.6), which is the only fact the submitter needs, and the ``FB-`` reference is how they quote it. The ``jira_*`` columns belong to the §25.7 admin schemas. ``context`` is likewise withheld — it is scrubbed diagnostic state for an operator, and re-serving it would hand a client back the server-side snapshot (plan, seat counts) it never supplied.

Work boardAI AssistantProject ManagementPricing

Properties

Name Type Description
object string
id string
reference string
type string
status string
surface string
severity object
category object
exit_reason object
rating object
content object
expected object
board_id object
card_id object
automation_run_id object
route string
screenshot_file_id object
app_version object
api_version object
created_time string
View JSON Schema on GitHub

JSON Schema

novumos-app-feedback-response-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://artifacts.apis.io/novumos-app/json-schema/novumos-app-feedback-response-schema.json",
  "title": "FeedbackResponse",
  "description": "One feedback row as its submitter sees it (spec §25.4).\n\n``org_id`` / ``user_id`` are omitted for the same reason\n:class:`~app.schemas.notification.NotificationResponse` omits them: the\ncaller IS the owner, so echoing the ownership keys back adds nothing and\nonly widens the surface.\n\n**No ``jira_*`` field at all.** Not the issue key or URL (§25.9: the user\nnever sees an internal issue id — it leaks backlog structure and means\nnothing to a customer), not ``jira_last_error`` (platform-admin-only,\n§25.10), and — since NOV-443 — not ``jira_status`` either. A submitter has\nno use for the state of an integration they cannot see, and every value it\ncan take is either uninformative or actively misleading: ``pending`` reads\nas \"not dealt with yet\", ``skipped`` and ``failed`` describe OUR\nmisconfiguration and OUR outage as though they were something that happened\nto the report. The report is durable in either case (§25.6), which is the\nonly fact the submitter needs, and the ``FB-`` reference is how they quote\nit. The ``jira_*`` columns belong to the §25.7 admin schemas.\n\n``context`` is likewise withheld — it is scrubbed diagnostic state for an\noperator, and re-serving it would hand a client back the server-side\nsnapshot (plan, seat counts) it never supplied.",
  "x-generated": "2026-11-19",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/novumos-app-openapi.json#/components/schemas/FeedbackResponse",
  "properties": {
    "object": {
      "type": "string",
      "title": "Object",
      "default": "feedback"
    },
    "id": {
      "type": "string",
      "format": "uuid",
      "title": "Id"
    },
    "reference": {
      "type": "string",
      "title": "Reference"
    },
    "type": {
      "type": "string",
      "title": "Type"
    },
    "status": {
      "type": "string",
      "title": "Status"
    },
    "surface": {
      "type": "string",
      "title": "Surface"
    },
    "severity": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Severity"
    },
    "category": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Category"
    },
    "exit_reason": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Exit Reason"
    },
    "rating": {
      "anyOf": [
        {
          "type": "integer"
        },
        {
          "type": "null"
        }
      ],
      "title": "Rating"
    },
    "content": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Content"
    },
    "expected": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Expected"
    },
    "board_id": {
      "anyOf": [
        {
          "type": "string",
          "format": "uuid"
        },
        {
          "type": "null"
        }
      ],
      "title": "Board Id"
    },
    "card_id": {
      "anyOf": [
        {
          "type": "string",
          "format": "uuid"
        },
        {
          "type": "null"
        }
      ],
      "title": "Card Id"
    },
    "automation_run_id": {
      "anyOf": [
        {
          "type": "string",
          "format": "uuid"
        },
        {
          "type": "null"
        }
      ],
      "title": "Automation Run Id"
    },
    "route": {
      "type": "string",
      "title": "Route"
    },
    "screenshot_file_id": {
      "anyOf": [
        {
          "type": "string",
          "format": "uuid"
        },
        {
          "type": "null"
        }
      ],
      "title": "Screenshot File Id"
    },
    "app_version": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "App Version"
    },
    "api_version": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Api Version"
    },
    "created_time": {
      "type": "string",
      "format": "date-time",
      "title": "Created Time"
    }
  },
  "additionalProperties": false,
  "type": "object",
  "required": [
    "id",
    "reference",
    "type",
    "status",
    "surface",
    "route",
    "created_time"
  ]
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/novumos-app-feedback-response"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.