STstatusstack

List incidents

Incidents on every service the API key's team can see, newest first, with their updates and affected components. Without page or per_page the response is a bare JSON array of at most the 100 newest; with either it is a paginated {data, links, meta} envelope. A key with no team scope receives an empty list.

get/v1/incidents

Request

  • Base URL
    https://statusstack.com/api
  • Auth
    HTTP bearer

Query parameters

status'investigating' | 'identified' | 'monitoring' | 'resolved' | 'postmortem' | 'scheduled' | 'completed' | 'clear'

scheduled and completed bound a maintenance window; clear is a provider's all-clear. resolved, postmortem, completed and clear are terminal.

impact'none' | 'minor' | 'major' | 'critical' | 'maintenance'
phase'ongoing' | 'resolved' | 'scheduled'

ongoing is unresolved and, for maintenance, inside its window; resolved has a resolved_at; scheduled is maintenance that has not started yet.

source_idstring uuid
created_afterstring date-time

Earliest started_at to include.

created_beforestring date-time

Latest started_at to include; must not precede created_after.

pageinteger

Switches the response to the paginated envelope.

per_pageinteger

Page size; also switches the response to the paginated envelope.

Response

Incidents

OR

Changes

No recorded changes to this operation across all 1 revision of this API.