Authorization: Bearer <accessToken> and live under /api/v1/dashboard.
GET /dashboard/metrics
Retrieve key performance metrics for the authenticated user’s workspace. Returns aggregate values for the current period — useful for summary cards and health indicators. Requeststring
ISO 8601 start date for the metrics window. Example:
"2025-05-01T00:00:00Z". Defaults to 30 days ago.string
ISO 8601 end date for the metrics window. Example:
"2025-05-31T23:59:59Z". Defaults to the current time.number
Total number of incidents created during the period.
number
Number of incidents currently open.
number
Number of incidents resolved during the period.
number
Mean time to resolution in seconds.
number
Mean time to detect in seconds (from signal ingestion to incident creation).
number
Number of incidents that exceeded their SLA threshold.
number
Percentage of incidents resolved within SLA. Range: 0–100.
number
Count of incidents with
CRITICAL severity.number
Count of incidents with
HIGH severity.number
Total number of signals ingested from all sources during the period.
object
The effective time range used to compute the metrics.
GET /dashboard/analytics
Retrieve detailed analytics data including time-series breakdowns, source distributions, and team performance statistics. Suitable for charting incident trends or building custom reporting pipelines. Requeststring
ISO 8601 start date. Defaults to 30 days ago.
string
ISO 8601 end date. Defaults to the current time.
string
default:"day"
Time bucket size for time-series data. One of:
"hour", "day", "week".object[]
Time-series array of incident creation and resolution counts, bucketed by
granularity.object
Count of incidents per severity level during the period.
object
Count of ingested signals per source during the period.
object[]
Per-user MTTR and resolved incident count, useful for understanding team performance distribution.
object[]
Ranked list of the sources generating the most signals, with counts and percentage share.
Both endpoints return data scoped to the authenticated user’s workspace. Users with the
VIEWER role can read analytics data but cannot modify incidents or configuration.