Feedback
Submit product feedback and follow comment threads on your reports.
User feedback routes let org members submit reports from the dashboard or shared canvas and track replies. Operator triage uses /admin/feedback and /api/v1/admin/feedback — see Feedback concept.
Endpoints
| Method | Path | Description |
|---|---|---|
GET | /api/v1/feedback | List the caller's submitted feedback (limit, offset). |
POST | /api/v1/feedback | Submit feedback (message, optional metadata, idempotencyKey). |
PATCH | /api/v1/feedback | Edit an open submission the caller still owns (id, message). |
GET | /api/v1/feedback/:id/comments | List the comment thread on a feedback item. |
POST | /api/v1/feedback/:id/comments | Add a comment (submitter, org admin, or platform admin). |
Submitting
POST /api/v1/feedback accepts a required message and optional structured metadata (route, session, viewport, canvas context). The dashboard feedback button and shared-canvas popover attach this context automatically.
Rate limit: 10 requests/minute per user or IP. Duplicate idempotency keys return the existing row with 200.
Listing and edits
GET /api/v1/feedback returns only feedback the authenticated user submitted in the current org, with comment counts and a public workflow status.
PATCH /api/v1/feedback allows message edits while the item is still open and has not been triaged, linked to a task, or handed off. After triage begins, edits are rejected.
Comments
Org admins and the original submitter can read and post on the thread. Use comments for clarifications — status changes and triage happen in the admin queue.
Dashboard
Org members review their submissions at /<orgSlug>/feedback. The top-bar feedback button opens the submit popover from any org page.