---
title: "List Event Views"
method: GET
path: "/v1/events/views"
---

# List Event Views

`GET /v1/events/views`

List views paginated from video_views (one row per completed view).

Using video_views instead of aggregating from events drops page-1 latency
from ~5s to ~0.45s and count from ~17s to ~0.5s for large orgs.

Pass count_only=true to get only the total count without fetching rows.
The frontend fires both in parallel so the table renders immediately while
the count resolves in the background.

Note: views where viewEnd never fired are omitted (no video_views row).
Tracked in SHO-63.

## Query parameters

- `event_type` string[], nullable
- `content_id` string, nullable
- `viewer_id` string, nullable
- `limit` integer
- `page` integer
- `count_only` boolean

## Response `200`

Successful Response

- unknown

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.net/shortkit/apis/shortkit-api.md) · [All operations](https://skmtc.net/shortkit/apis/shortkit-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/shortkit/shortkit-api/revisions/4ff6d068cf75/schema)