admin

Update Feedback

patch/api/admin/feedback/{note_id}

Request

  • Base URL: https://api.heymetra.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.heymetra.com/api/admin/feedback/{note_id}
  • Auth: none declared

Path parameters

note_idstring uuid required

Headers

authorizationstring nullable
x-workspace-idstring nullable

Request body

state'new' | 'triaged' | 'resolved' required

Where a note is in our own triage.

Three, because a fourth ("declined") would be a second way of saying the note is finished with, and a state nobody can tell from its neighbour is a state nobody sets.

Response

Successful Response

idstring uuid required
workspacestring required
emailstring nullable required
kind'connector_request' | 'data_dispute' | 'other' required

What a customer is telling us (ZEISO-218).

One mechanism carries two moments, and the difference between them is who reads the row rather than how it is stored: a connector we do not have is a product decision, a number the customer does not believe is a bug hunt. Collapsing them into one bucket would lose that, and splitting them into two tables would duplicate every column to record it.

state'new' | 'triaged' | 'resolved' required

Where a note is in our own triage.

Three, because a fourth ("declined") would be a second way of saying the note is finished with, and a state nobody can tell from its neighbour is a state nobody sets.

messagestring required
about_toolstring nullable required
clientstring nullable required
created_atstring date-time required

Changes

No recorded changes to this operation across all 3 revisions of this API.