Incidents APIs read and act on the incidents BigPanda creates by correlating alerts, plus the structures around them — environments, tags, change context, and outbound notifications.What you can achieve here:
Read incident state: Retrieve a single incident, or page through a BPQL-filtered search with related alerts expanded inline.
Automate the lifecycle: Comment, assign, snooze, resolve, merge, and split incidents from your runbooks and ticketing flows.
Carry triage state: Define incident tag types once, then read and write tags per incident — priority, owning team, SLA bucket.
Scope what teams see: Environments are saved BPQL queries that slice the incident stream per team; environment groups roll them up for reporting and access control.
Close the root-cause loop: Send change records from your CMDB and deployment tooling, and manage the relationships BigPanda draws between changes and incidents.
Push events out: Webhook v2 notifications deliver incident events to chat, ticketing, and paging tools.
Incidents only exist once alerts are flowing and correlation patterns are active — if this category returns empty results, start in Alerts.
