This issue is being created by OpenAI Codex on behalf of @billyvg while implementing [billyvg/sentry-tui#188](https://github.com/billyvg/sentry-tui/issues/188). ## Context sentry-tui initially adopted `@sentry/api` 0.272.0 for API requests where the generated surface matched the runtime API. The initial integration used generated operations for schema-covered Discover datasets, organization reads, project and environment lists, and replay detail. It retained a small flexible request path for the gaps below. This is an inventory from real sentry-tui call sites, not a claim that the overall API gap list is exhaustive. The generated query-type and pagination gaps originally tracked here are resolved in `@sentry/api` 0.286.0. sentry-tui migrated those call sites in [billyvg/sentry-tui#241](https://github.com/billyvg/sentry-tui/pull/241). ## Routes not represented by generated operations sentry-tui currently calls these Sentry API routes, but 0.286.0 has no corresponding operation: - `GET /api/0/users/me/` - `GET /api/0/organizations/{org}/users/` - `GET /api/0/organizations/{org}/events-stats/` (the package exposes `/events-timeseries/`; guidance on response/query compatibility or replacement would also unblock this) - `GET /api/0/organizations/{org}/issues-stats/` - `GET /api/0/organizations/{org}/ai-conversations/` - `GET /api/0/organizations/{org}/open-periods/` - `GET /api/0/organizations/{org}/group-search-views/` - `GET /api/0/organizations/{org}/monitors-stats/` - `GET /api/0/organizations/{org}/uptime-stats/` - `GET /api/0/organizations/{org}/dashboards/starred/` - `GET /api/0/organizations/{org}/explore/saved/` - Seer Explorer chat/run/update and agent approval routes under `/api/0/organizations/{org}/seer/` and `/agent/approve/` ## Remaining work to unblock migration - Add operations and response types for the missing routes that are intended as supported API surface. - Clarify whether `/events-timeseries/` is intended to replace `/events-stats/` and, if so, document the query and response migration. sentry-tui now uses the generated operations for Discover queries, replay lists, dashboards, detectors, workflows, and trace-item attributes. The routes above still require the flexible request path.