List the account's incidents, newest first.
const url = 'https://api.siteqwality.com/incident?status=active';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
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.siteqwality.com/incident?status=active' \ --header 'Authorization: Bearer <token>'total is the size of the whole filtered set. The status filter is applied
in SQL: the dashboard used to fetch one page and filter it client-side, so
an open incident older than the newest 50 was never shown as active.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters ”Page size. Defaults to 50, clamped to 1..=100.
Row offset into the filtered list, newest first.
Which incidents GET /incident/ returns.
Keyed on the responder lifecycle (responder_status), which is what the
dashboard’s Active and Resolved tabs mean: an incident is active until a
responder resolves it, whatever its public status-page status says.
active (triggered or acknowledged), resolved, or all. Defaults to
all. Keyed on responder_status.
Responses
Section titled “ Responses ”One page of incidents in data, plus total: the number of incidents matching status
Invalid query parameters, including an unknown status
Missing or invalid authentication
Internal server error