Per-dashboard content "tray" (usage, pages, revisions, elements, viewers, schedules).
A per-dashboard drill-down (DVT-1499) backing the command-center Content page's row-expansion tray: usage KPIs and trend, page-grain popularity, a revision timeline, element performance, top viewers, and export-schedule health. Admin or owner only (audit:read). The data object shape is frozen — field names are a client contract. Lazily fetched per dashboard (e.g. on Content-tab row expansion) rather than inlined onto GET .../analytics/content, since these queries aren't bounded to that endpoint's top-50 leaderboard — same pattern as GET .../analytics/content/{dashboardId}/effort. Only the days filter applies here — connectionId/actorType have no bearing on a single already-identified dashboard.
revisions[].method is exact (DVT-1522): dashboard_revisions.actor_type alone determines human/agent/system, so no correlation with audit_logs is needed.
Request
- Base URL: http://localhost:8080
- URL: http://localhost:8080/v1/orgs/{orgId}/analytics/content/dashboards/{dashboardId}
- Auth: one of:
- API key in cookie dvt_session
- HTTP bearer
Query parameters
Rolling window in calendar days, applied to every section except kpis.favorites/kpis.openComments (all-time signals) and revisions (all-time, capped to the latest 20). Default 30; clamped to [1, 365]. Out-of-range or non-integer values are silently clamped/defaulted.
Response
Per-dashboard content tray.
Changes
No recorded changes to this operation across all 1 revision of this API.