Get the incident-chart rows for an organization
const url = 'https://api.adversarial.com/api/v1/incidents/chart?start_date=2026-01-01T00%3A00%3A00Z&end_date=2026-12-31T23%3A59%3A59Z';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://api.adversarial.com/api/v1/incidents/chart?start_date=2026-01-01T00%3A00%3A00Z&end_date=2026-12-31T23%3A59%3A59Z'Returns the incidents visible in the requested window, unpaginated. The window may span at most two years, and each requested severity level’s rows are capped server-side so one severity cannot crowd out the others.
Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”Inclusive lower bound on the window. RFC 3339 timestamp or bare
YYYY-MM-DD (anchored at start-of-day UTC).
Example
2026-01-01T00:00:00ZInclusive upper bound on the window. RFC 3339 timestamp or bare
YYYY-MM-DD (anchored at end-of-day UTC).
Example
2026-12-31T23:59:59ZSeverity levels to plot. Absent means every level. Unscored incidents are never plotted, so there is no unscored bucket to select.
Filter on what an incident is linked under, using the same vocabulary
as the register: null (top-level), any (linked children only), or a
parent id as INC-<n> or a bare number. Repeat to union. Defaults to
null — parity with the register, so the chart plots bundle parents
only.
Responses
Section titled “Responses”Incident rows visible in the requested chart window
One incident row for the incident chart, as served by
GET /v1/incidents/chart: the incident’s identity, severity, and
lifecycle dates.
object
Example
[ { "id": "INC-00001", "severity": "SEV-5" }]