Update Unleash feedback

PUT /api/admin/feedback/:id

Updates the feedback with the provided ID. Only provided fields are updated. Fields left out are left untouched. Must be called with a token with an identifiable user (either from being sent from the UI or from using a PAT).

Request

Path Parameters

• id string required

application/json

Body

required

feedbackUpdateSchema

• userId integer

  The ID of the user that gave the feedback.

• neverShow boolean

  true if the user has asked never to see this feedback questionnaire again.

• given date-time nullable

  When this feedback was given

Responses

• 200
• 400
• 401
• 415

---

feedbackResponseSchema

application/json

Schema

Schema

• userId integer

  The ID of the user that gave the feedback.

• neverShow boolean

  true if the user has asked never to see this feedback questionnaire again.

• given date-time nullable

  When this feedback was given

• feedbackId string

  The name of the feedback session

Example (from schema)

{
  "userId": 2,
  "neverShow": false,
  "given": "2023-07-06T08:29:21.282Z",
  "feedbackId": "pnps"
}

The request data does not match what we expect.

application/json

Schema

Schema

• id string

  The ID of the error instance

• name string

  The name of the error kind

• message string

  A description of what went wrong.

Example (from schema)

{
  "id": "9c40958a-daac-400e-98fb-3bb438567008",
  "name": "ValidationError",
  "message": "The request payload you provided doesn't conform to the schema. The .parameters property should be object. You sent []."
}

Authorization information is missing or invalid. Provide a valid API token as the authorization header, e.g. authorization:*.*.my-admin-token.

application/json

Schema

Schema

• id string

  The ID of the error instance

• name string

  The name of the error kind

• message string

  A description of what went wrong.

Example (from schema)

{
  "id": "9c40958a-daac-400e-98fb-3bb438567008",
  "name": "AuthenticationRequired",
  "message": "You must log in to use Unleash. Your request had no authorization header, so we could not authorize you. Try logging in at /auth/simple/login."
}

The operation does not support request payloads of the provided type. Please ensure that you're using one of the listed payload types and that you have specified the right content type in the "content-type" header.

application/json

Schema

Schema

• id string

  The ID of the error instance

• name string

  The name of the error kind

• message string

  A description of what went wrong.

Example (from schema)

{
  "id": "9c40958a-daac-400e-98fb-3bb438567008",
  "name": "ContentTypeerror",
  "message": "We do not accept the content-type you provided (application/xml). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format."
}

Loading...