> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usenotra.com/llms.txt
> Use this file to discover all available pages before exploring further.

# List feedback



## OpenAPI

````yaml https://api.usenotra.com/openapi.json get /v1/feedback
openapi: 3.1.1
info:
  title: Notra API
  version: 1.0.0
  description: >-
    OpenAPI schema for Notra content endpoints. Use GET /v1/status for public
    reachability. Error responses include recovery guidance.
servers:
  - url: https://api.usenotra.com
    description: Production
security:
  - BearerAuth: []
tags:
  - name: Discovery
    description: Public API status and authenticated workspace discovery.
  - name: Content
    description: >-
      Manage posts, brand identities, and GitHub or Linear integrations, and
      queue content generation. Organization is inferred from the API key
      (identity.externalId).
  - name: Schedules
    description: >-
      Manage scheduled content generation. Organization is inferred from the API
      key (identity.externalId).
  - name: Event Triggers
    description: >-
      Manage event-based content generation triggered by GitHub webhooks.
      Organization is inferred from the API key (identity.externalId).
  - name: Chats
    description: >-
      Manage chat sessions. Organization is inferred from the API key
      (identity.externalId).
  - name: Skills
    description: >-
      Manage reusable writing skills. Organization is inferred from the API key
      (identity.externalId).
  - name: Feedback
    description: >-
      Collect and triage feedback submitted by AI agents. Agents post to the
      organization's feedback URL without credentials; reading and triage
      require an API key with feedback.read or feedback.write.
  - name: GEO
    description: >-
      Manage generative engine optimization: projects, tracking settings,
      prompts, prompt sequences, competitors, scans, visibility reads, content
      gaps and briefs, agent readiness and AI traffic. Project-scoped endpoints
      require the GEO plan entitlement in addition to their scope;
      organization-level ingest endpoints require only the traffic scope.
paths:
  /v1/feedback:
    get:
      tags:
        - Feedback
      summary: List feedback
      operationId: listFeedback
      parameters:
        - schema:
            type: string
            enum:
              - new
              - triaged
              - resolved
              - archived
            description: Triage status.
            example: new
          required: false
          description: Triage status.
          name: status
          in: query
        - schema:
            type: string
            enum:
              - bug
              - feature
              - praise
              - question
              - other
            description: What kind of feedback this is.
            example: bug
          required: false
          description: What kind of feedback this is.
          name: kind
          in: query
        - schema:
            type: string
            minLength: 1
            pattern: ^[A-Za-z0-9_-]{1,100}$
          required: false
          name: projectId
          in: query
        - schema:
            type: integer
            minimum: 1
            maximum: 100
            default: 25
            description: Items per page
            example: 25
          required: false
          description: Items per page
          name: limit
          in: query
        - schema:
            type: integer
            minimum: 1
            default: 1
            description: Page number
            example: 1
          required: false
          description: Page number
          name: page
          in: query
      responses:
        '200':
          description: Feedback fetched successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ListFeedbackResponse'
        '400':
          description: Invalid query params
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Missing or invalid API key
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '503':
          description: Authentication service unavailable
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    ListFeedbackResponse:
      type: object
      properties:
        feedback:
          type: array
          items:
            $ref: '#/components/schemas/Feedback'
        pagination:
          type: object
          properties:
            limit:
              type: integer
              minimum: 1
            currentPage:
              type: integer
              minimum: 1
            nextPage:
              type:
                - integer
                - 'null'
              minimum: 1
            previousPage:
              type:
                - integer
                - 'null'
              minimum: 1
            totalPages:
              type: integer
              minimum: 1
            totalItems:
              type: integer
              minimum: 0
          required:
            - limit
            - currentPage
            - nextPage
            - previousPage
            - totalPages
            - totalItems
      required:
        - feedback
        - pagination
    ErrorResponse:
      type: object
      properties:
        error:
          type: string
        code:
          type: string
        recovery:
          type: string
      required:
        - error
    Feedback:
      type: object
      properties:
        id:
          type: string
        projectId:
          type:
            - string
            - 'null'
        source:
          type: string
          enum:
            - mcp
            - api
            - sdk
          description: Channel the feedback arrived through.
          example: mcp
        kind:
          type: string
          enum:
            - bug
            - feature
            - praise
            - question
            - other
          description: What kind of feedback this is.
          example: bug
        sentiment:
          type:
            - string
            - 'null'
          enum:
            - negative
            - neutral
            - positive
            - null
          description: Overall sentiment of the feedback.
          example: negative
        status:
          type: string
          enum:
            - new
            - triaged
            - resolved
            - archived
          description: Triage status.
          example: new
        title:
          type:
            - string
            - 'null'
        message:
          type: string
        agentClient:
          type:
            - string
            - 'null'
        agentModel:
          type:
            - string
            - 'null'
        toolVersion:
          type:
            - string
            - 'null'
        userAgent:
          type:
            - string
            - 'null'
        contextUrl:
          type:
            - string
            - 'null'
        externalId:
          type:
            - string
            - 'null'
        idempotencyKey:
          type:
            - string
            - 'null'
        metadata:
          type:
            - object
            - 'null'
          additionalProperties: {}
        resolvedAt:
          type:
            - string
            - 'null'
        createdAt:
          type: string
        updatedAt:
          type: string
      required:
        - id
        - projectId
        - source
        - kind
        - sentiment
        - status
        - title
        - message
        - agentClient
        - agentModel
        - toolVersion
        - userAgent
        - contextUrl
        - externalId
        - idempotencyKey
        - metadata
        - resolvedAt
        - createdAt
        - updatedAt
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: API Key
      description: Send your API key in the Authorization header as Bearer API_KEY.

````