---
title: "GET /api/analytics/views/"
method: GET
path: "/api/analytics/views/"
tags: ["Analytics"]
---

# GET /api/analytics/views/

`GET /api/analytics/views/`

CRUD endpoints for per-user analytics saved views.

All routes are gated behind the same ``should_check_analytics_permission``
helper used by the KPI endpoints, so a user who cannot access the analytics
dashboard cannot read view metadata even via a shared link.

Lookup uses ``uuid`` (not PK) so the primary key is never exposed.

Access rules
------------
* list / create   — scoped to requesting user + active org
* retrieve        — any org member who passes the analytics permission check
                    (enables shared-link UX: ``?view=<uuid>`` in the URL)
* update / destroy — owner-only

## Query parameters

- `ordering` string

## Response `200`

- AnalyticsView[]
  - `created_at` string, date-time, required
  - `dashboard_type` 'overview' | 'member_performance' — * `overview` - Overview * `member_performance` - Member Performance
  - `filters` unknown
  - `name` string, required
  - `owner_id` integer, required
  - `updated_at` string, date-time, required
  - `uuid` string, uuid, required

---

[API](https://skmtc.net/humansignal/apis/label-studio-api.md) · [All operations](https://skmtc.net/humansignal/apis/label-studio-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/humansignal/label-studio-api/revisions/1d13f90af57a/schema)