# Read and manage feedback events > List inbox feedback, page through results, update its status and link external issues. Canonical URL: https://pollenate.dev/docs/api/feedback/ ## Scope and base path These endpoints manage inbox events from widgets and the collection API. Survey answers use the [forms API](/docs/api/forms/). Base path: `/organizations/ORG_ID/feedback`. Server integrations use an **organization-wide organization API key** with `read` for reads. Personal keys and MCP OAuth sign-ins are not accepted on these REST routes; use the [MCP tools](/docs/integrations/mcp-tools/) instead. ## List and paginate ```bash curl "https://api.pollenate.dev/organizations/ORG_ID/feedback?limit=25&status=new" \ -H "X-Pollenate-Key: $POLLENATE_READ_KEY" ``` Supported query parameters are `brandId`, `inboxId`, `type`, `status`, `startDate`, `endDate`, `limit` and `cursor`. The default page size is 50; the maximum is 100. Older clients may send `offset`; prefer the returned cursor. ```json { "data": [], "total": 0, "hasMore": false, "cursor": null } ``` For another page, send the returned `cursor` unchanged with the same filters. Stop when `hasMore` is false. Rows include `id`, inbox and brand names, `type`, `score`, `comment`, parsed `context`, `pageUrl`, `source`, `status` and timestamps. The query returns most recent events first. Use `GET /organizations/ORG_ID/feedback/FEEDBACK_ID` for one event, `GET /organizations/ORG_ID/feedback/stats` for aggregates and `GET /organizations/ORG_ID/feedback/status-counts` for workflow totals. ## Update status and issue links Machine callers need an organization key with `admin` for feedback updates and deletes. A signed-in person's role must separately allow the operation. ```bash curl -X PATCH https://api.pollenate.dev/organizations/ORG_ID/feedback/FEEDBACK_ID \ -H "X-Pollenate-Key: $POLLENATE_ADMIN_KEY" \ -H "Content-Type: application/json" \ --data '{ "status": "planned", "externalTrackerType": "github", "externalTrackerId": "123", "externalTrackerUrl": "https://github.com/OWNER/REPO/issues/123" }' ``` Statuses are `new`, `reviewing`, `planned`, `resolved` and `archived`. Tracker types are `github`, `jira`, `redmine`, `linear` and `asana`. Send the complete tracker trio when changing a link: omitted tracker fields are cleared when any tracker field is updated. This records a link; it does not create an issue in that service. `DELETE /feedback/FEEDBACK_ID` permanently deletes the event and returns 204. Archive with a status update when you want to retain its content. A 403 can indicate an insufficient scope or a brand-scoped key on this organization-level API. A missing or inaccessible event returns 404. Use [semantic search](/docs/ai/semantic-search/) to discover relevant comments and [AI reports](/docs/ai/overview/) to summarize a selected period.