v1
latestOpenAPI 3.0.22026-07-144652931.4 MBGet raw data - single incident
Provides enriched incident data and metrics for a single incident.
Example metrics include Seconds to Resolve, Seconds to Engage, Snoozed Seconds, and Sleep Hour Interruptions. Metric definitions can be found in our Knowledge Base.
<!-- theme: info -->Note: Data availability reflects pipeline processing cycles and is generally within 24 hours under normal conditions.
Scoped OAuth requires: analytics.read
Headers
The Accept header is used as a versioning header.
Response
The IDs of the users who acknowledged the incident.
The names of the users who acknowledged the incident.
Total count of acknowledgements in the incident.
Total number of responders who either acknowledged the incident or accepted a responder request.
The IDs of the users who were assigned the incident.
The names of the users who were assigned the incident.
Total count of instances where responders were assigned an incident (including through reassignment or escalation).
Whether or not the incident resolved automatically, either via an integration or auto-resolved in PagerDuty.
Total number of unique interruptions during business hours; 8am-6pm Mon-Fri, based on the user’s time zone.
Timestamp of when the incident was created.
Timestamp of when the incident was last updated by the analytics process. Does not match the updated_at for an incident returned by the standard REST api incidents endpoint.
The incident description
Total engaged time across all responders for this incident. Engaged time is measured from the time a user engages with an incident (by acknowledging or accepting a responder request) until the incident is resolved. This may include periods in which the incidents were snoozed.
Total number of users who engaged (acknowledged, accepted responder request) in the incident.
Total count of instances where an incident is escalated between responders assigned to an escalation policy.
ID of the escalation policy the incident was assigned to.
Name of the escalation policy the incident was assigned to.
Incident ID
The PagerDuty incident number.
ID of the Incident Type.
The name of the Incident Type.
The IDs of the users who either acknowledged the incident or accepted a responder request.
The names of the users who either acknowledged the incident or accepted a responder request.
An incident is classified as a major incident if it has one of the two highest priorities, or if multiple responders are added and acknowledge the incident.
Total count of manual escalations in the incident.
Total number of unique interruptions during off hours; 6pm-10pm Mon-Fri and all day Sat-Sun, based on the user’s time zone.
ID of the incident's priority level.
The user-provided short name of the priority.
The numerical value used to sort priorities. Higher values are higher priority.
Total count of reassignments in the incident.
Timestamp of when the incident was resolved.
ID of the user who resolved the incident.
Name of the user who resolved the incident.
A measure of people response time. This metric measures the time from the first user engagement (acknowledge or responder accept) to the last. This metric is only used for incidents with multiple responders; for incidents with one or no engaged users, this value is null.
Time between the start of an incident, and the first responder to acknowledge.
Time between the start of an incident, and the last additional responder to acknowledge. If an incident has one or no responders, the value will be null.
Time from when an incident was triggered until it was resolved.
ID of the service that the incident triggered on.
Name of the service that the incident triggered on.
Total number of unique interruptions during sleep hours; 10pm-8am every day, based on the user’s time zone.
Total seconds the incident has been snoozed for.
The incident status. Can be one of triggered, acknowledged, or resolved.
ID of the team the incident was assigned to.
Name of the team the incident was assigned to.
Total count of timeout escalations in the incident.
Total number of unique interruptions in the incident.
Total number of notifications sent for the incident.
Notification level
The total response effort in seconds, as defined by the user.