Feedback

Get Feedbacks

Changed on

Paginated list of feedbacks, newest first. total counts the feedbacks matching the filters, not the page.

get/admin/feedbacks

Request

  • Base URL: https://api.excellence-ai.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.excellence-ai.com/admin/feedbacks
  • Auth: OAuth 2 (password, token URL api/login)

Query parameters

status'new' | 'in-progress' | 'waiting-user' | 'done' | 'todo' nullable

A status, or "todo" for what is on us (new + in-progress)

searchstring nullable

Free text on the author: name or email

role'student' | 'teacher' | 'admin' nullable
school_idstring nullable

B2B school: its teachers and their students

sourcestring

Channel the feedback came in through. Defaults to what users wrote themselves; pass an empty value (or "all") for every source.

nature'misunderstanding' | 'bug' | 'suggestion'

What kind of feedback it is, which is also how it gets triaged.

A dysfunction of what exists is a bug and goes down the fast lane; everything that changes or adds behaviour waits for the weekly review.

theme'DEVOIR' | 'EVAL' | 'COURS' | 'COR_COPIES' | 'CONTENU' | 'UX' | 'CHAT' | 'CLASSES' | 'SETTINGS'

The part of the product a feedback is about.

origin'widget' | 'chat_answer_report' | 'rating_prompt'

Which door of the app a user feedback came through.

Both are written by the person they belong to, so they share the user source and the inbox; what differs is what the team has to read. A widget message is the user's own words. A chat answer report is one click under a chat answer (EXC-796): the text is ours, the question and the answer are what to look at.

Door of the app: the widget (also every feedback with no origin), a chat answer report, or the store-rating question (EXC-1642).

skipinteger
limitinteger

Response

Successful Response

totalinteger required

Changes

  • 1d6009058248Revision changes
    • warning

      added the new rating_prompt enum value to the /// response property for the response status

    • info

      added the new optional query request parameter origin

  • eb0ac355046cRevision changes
    • warning

      added the new waiting-user enum value to the // response property for the response status

    • info

      added the enum value todo to the property anyOf[subschema #1]/ of the query request parameter status

    • info

      added the enum value waiting-user to the property anyOf[subschema #1]/ of the query request parameter status

    • info

      added the optional property // to the response with the status

    • info

      added the optional property // to the response with the status