---
title: "Get raw data - single incident"
method: GET
path: "/analytics/raw/incidents/{id}"
tags: ["Analytics"]
---

# Get raw data - single incident

`GET /analytics/raw/incidents/{id}`

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](https://support.pagerduty.com/docs/insights#incidents-list).

<!-- theme: info -->
> **Note:** Data availability reflects [pipeline processing cycles](https://support.pagerduty.com/main/docs/insights#:~:text=Data%20Update%20Schedule) and is generally within 24 hours under normal conditions.

Scoped OAuth requires: `analytics.read`

## Headers

- `Accept` string, required
- `Content-Type` 'application/json', required

## Response `200`

- AnalyticsRawIncident
  - `acknowledged_user_ids` string[] — The IDs of the users who acknowledged the incident.
  - `acknowledged_user_names` string[] — The names of the users who acknowledged the incident.
  - `acknowledgement_count` integer — Total count of acknowledgements in the incident.
  - `active_user_count` integer — Total number of responders who either acknowledged the incident or accepted a responder request.
  - `assigned_user_ids` string[] — The IDs of the users who were assigned the incident.
  - `assigned_user_names` string[] — The names of the users who were assigned the incident.
  - `assignment_count` integer — Total count of instances where responders were assigned an incident (including through reassignment or escalation).
  - `auto_resolved` boolean — Whether or not the incident resolved automatically, either via an integration or [auto-resolved in PagerDuty](https://support.pagerduty.com/docs/configurable-service-settings#auto-resolution).
  - `business_hour_interruptions` integer — Total number of unique interruptions during business hours; 8am-6pm Mon-Fri, based on the user’s time zone.
  - `created_at` string — Timestamp of when the incident was created.
  - `updated_at` string — 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.
  - `description` string — The incident description
  - `engaged_seconds` integer — 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.
  - `engaged_user_count` integer — Total number of users who engaged (acknowledged, accepted responder request) in the incident.
  - `escalation_count` integer — Total count of instances where an incident is escalated between responders assigned to an escalation policy.
  - `escalation_policy_id` string — ID of the escalation policy the incident was assigned to.
  - `escalation_policy_name` string — Name of the escalation policy the incident was assigned to.
  - `id` string — Incident ID
  - `incident_number` integer — The PagerDuty incident number.
  - `incident_type_id` string — ID of the Incident Type.
  - `incident_type_name` string — The name of the Incident Type.
  - `joined_user_ids` string[] — The IDs of the users who either acknowledged the incident or accepted a responder request.
  - `joined_user_names` string[] — The names of the users who either acknowledged the incident or accepted a responder request.
  - `major` boolean — An incident is classified as a [major incident](https://support.pagerduty.com/docs/operational-reviews#major-incidents) if it has one of the two highest priorities, or if multiple responders are added and acknowledge the incident.
  - `manual_escalation_count` integer — Total count of manual escalations in the incident.
  - `off_hour_interruptions` integer — Total number of unique interruptions during off hours; 6pm-10pm Mon-Fri and all day Sat-Sun, based on the user’s time zone.
  - `priority_id` string, nullable — ID of the incident's priority level.
  - `priority_name` string, nullable — The user-provided short name of the priority.
  - `priority_order` integer, nullable — The numerical value used to sort priorities. Higher values are higher priority.
  - `reassignment_count` integer — Total count of reassignments in the incident.
  - `resolved_at` string — Timestamp of when the incident was resolved.
  - `resolved_by_user_id` string — ID of the user who resolved the incident.
  - `resolved_by_user_name` string — Name of the user who resolved the incident.
  - `seconds_to_engage` integer — 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.
  - `seconds_to_first_ack` integer — Time between the start of an incident, and the first responder to acknowledge.
  - `seconds_to_mobilize` integer — 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.
  - `seconds_to_resolve` integer — Time from when an incident was triggered until it was resolved.
  - `service_id` string — ID of the service that the incident triggered on.
  - `service_name` string — Name of the service that the incident triggered on.
  - `sleep_hour_interruptions` integer — Total number of unique interruptions during sleep hours; 10pm-8am every day, based on the user’s time zone.
  - `snoozed_seconds` integer — Total seconds the incident has been snoozed for.
  - `status` string — The incident status. Can be one of `triggered`, `acknowledged`, or `resolved`.
  - `team_id` string, nullable — ID of the team the incident was assigned to.
  - `team_name` string, nullable — Name of the team the incident was assigned to.
  - `timeout_escalation_count` integer — Total count of timeout escalations in the incident.
  - `total_interruptions` integer — Total number of unique interruptions in the incident.
  - `total_notifications` integer — Total number of notifications sent for the incident.
  - `urgency` string — Notification level
  - `user_defined_effort_seconds` integer, nullable — The total response effort in seconds, [as defined by the user](https://support.pagerduty.com/docs/editing-incidents#edit-incident-duration).

## Other responses

- `404` — The requested resource was not found.
- `429` — Too many requests have been made, the rate limit has been reached.

---

[API](https://skmtc.net/pagerduty/apis/rest-api.md) · [All operations](https://skmtc.net/pagerduty/apis/rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pagerduty/rest-api/revisions/b679a8f3f02c/schema)