The dashboard API provides the data that powers the Scrubbe analytics interface. Use the metrics endpoint to fetch high-level KPIs for a summary view, or the analytics endpoint for time-series and breakdown data suitable for custom dashboards and reporting. Both endpoints requireDocumentation Index
Fetch the complete documentation index at: https://docs.scrubbe.com/llms.txt
Use this file to discover all available pages before exploring further.
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. RequestISO 8601 start date for the metrics window. Example:
"2025-05-01T00:00:00Z". Defaults to 30 days ago.ISO 8601 end date for the metrics window. Example:
"2025-05-31T23:59:59Z". Defaults to the current time.Total number of incidents created during the period.
Number of incidents currently open.
Number of incidents resolved during the period.
Mean time to resolution in seconds.
Mean time to detect in seconds (from signal ingestion to incident creation).
Number of incidents that exceeded their SLA threshold.
Percentage of incidents resolved within SLA. Range: 0–100.
Count of incidents with
CRITICAL severity.Count of incidents with
HIGH severity.Total number of signals ingested from all sources during the period.
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. RequestISO 8601 start date. Defaults to 30 days ago.
ISO 8601 end date. Defaults to the current time.
Time bucket size for time-series data. One of:
"hour", "day", "week".Time-series array of incident creation and resolution counts, bucketed by
granularity.Count of incidents per severity level during the period.
Count of ingested signals per source during the period.
Per-user MTTR and resolved incident count, useful for understanding team performance distribution.
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.