analytics

Get Escalations

Reporting -> Escalations: one row per escalated alarm (Escalate - Voice Down or Escalate - Dispatch, Site Summary's own definition) with its full action timeline on one clock, and KPI medians over the FULL filtered set.

The window keys on the ESCALATION INSTANT (the operator close-out, else the AI announcement), like Site Summary, so an alarm created before the window start but escalated inside it appears; rows are ordered by when the alarm landed. Tenant scoping is /analytics/incidents': a forged parent/site/camera filter is 403, rows outside the caller's grants never appear. Operator names are returned only to owner / monitoring manager; everyone else sees "Operator". Customer-side logins also lose internal-only detail.

get/analytics/escalations

Request

  • Base URL
    https://api.verdun.ai (the document declares no server; this is the origin it was published from)
  • URL
    https://api.verdun.ai/analytics/escalations
  • Auth
    HTTP bearer

Query parameters

hoursinteger nullable

Rolling window ending now (default 168 = 7 days). start/end win when both are given.

startstring date-time nullable
endstring date-time nullable
parent_idstring[] nullable
site_idstring[] nullable
camera_idstring[] nullable
kind'voice_down' | 'dispatch' nullable
escalated_by'operator' | 'agent' nullable
limitinteger

Response

Successful Response

totalinteger required

Rows matching the filters, uncapped by limit.

returnedinteger required

Rows in this response.

limitinteger required

The applied limit.

kpi_truncatedboolean

True when the filtered set exceeded the server's candidate cap and the KPIs cover the newest rows only.

Changes

No recorded changes to this operation across all 2 revisions of this API.