---
title: "Get raw incidents for a single responder_id"
method: POST
path: "/analytics/raw/responders/{responder_id}/incidents"
tags: ["Analytics"]
---

# Get raw incidents for a single responder_id

`POST /analytics/raw/responders/{responder_id}/incidents`

Provides enriched incident data and metrics for a specific responder.

Example metrics include Mean Seconds to Resolve, Mean 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.write`

## Headers

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

## Request body

- object
  - `filters` object — Filters the result, only show incidents that match the conditions passed in the filter.
    - `created_at_start` string — Filters the result, showing only the incidents where the creation timestamp is greater than the filter value.
    - `created_at_end` string — Filters the result, showing only the incidents where the creation timestamp is less than the filter value.
    - `urgency` string — Filters the result, showing only the incidents where urgency matches the filter value.
    - `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.
    - `team_ids` string[] — An array of team IDs. Only incidents that are assigned to a member of these teams will be returned. Account must have the teams ability to use this parameter.
    - `service_ids` string[] — An array of service IDs. Only results related to these services will be returned.
    - `priority_ids` string[] — The priority_ids filter applied to the results.
    - `priority_names` string[] — The priority_names filter applied to the results.
    - `incident_type_ids` string[] — Filter incidents by specific incident type IDs. Only incidents matching the given IDs will be returned.
  - `starting_after` string — A cursor to indicate the reference point that the results should follow
  - `ending_before` string — A cursor to indicate the reference point that the results should precede
  - `order` 'asc' | 'desc' — The order in which to display the results; asc for ascending, desc for descending. Defaults to `desc`.
  - `order_by` 'incident_created_at' — The column to use for ordering the results. Defaults to `incident_created_at`.
  - `limit` integer — Number of results to include in each batch. Limits between 1 to 1000 are accepted.
  - `time_zone` string — The time zone to use for the results.

## Response `200`

- object
  - `first` string — Cursor to identify the first object in the response.
  - `last` string — Cursor to identify the last object in the response.
  - `responder_id` string — The Responder ID passed into the request.
  - `limit` integer — Number of results to include in the batch.
  - `order` 'asc' | 'desc' — The order in which the results were sorted; asc for ascending, desc for descending.
  - `order_by` 'incident_created_at' — The column that was used for ordering the results.
  - `time_zone` string — The time zone that the results are in.
  - `filters` object — A collection of filters that were applied to the results.
    - `created_at_start` string — The lower boundary for the created_at range filter applied to the results.
    - `created_at_end` string — The upper boundary for the created_at range filter applied to the results.
    - `urgency` 'high' | 'low' — The urgency filter applied to the results.
    - `major` boolean — The [major incident](https://support.pagerduty.com/docs/operational-reviews#major-incidents) filter applied to the results.
    - `team_ids` string[] — The team_ids filter applied to the results.
    - `service_ids` string[] — The service_ids filter applied to the results.
    - `priority_ids` string[] — The priority_ids filter applied to the results.
    - `priority_names` string[] — The priority_names filter applied to the results.
    - `incident_type_ids` string[] — The incident_type_ids filter applied to the results.
  - `data` AnalyticsRawResponderIncidents[]
    - `incident_created_at` string — Timestamp of when the incident was created.
    - `incident_description` string — The incident description.
    - `incident_id` string — Incident ID
    - `incident_number` integer — The PagerDuty incident number.
    - `incident_priority_id` string, nullable — ID of the incident's priority level.
    - `incident_priority_name` string, nullable — The user-provided short name of the priority.
    - `incident_priority_order` integer, nullable — The numerical value used to sort priorities. Higher values are higher priority.
    - `incident_urgency` string — Notification level
    - `mean_time_to_acknowledge_seconds` integer — Mean time from this user being assigned to an incident until this user acknowledges the incident.
    - `responder_id` string — ID of the responder.
    - `responder_name` string — Name of the responder.
    - `service_id` string — ID of the service that the incident triggered on.
    - `service_name` string — Name of the service that the incident triggered on.
    - `service_team_id` string, nullable — ID of the team that owns the related service.
    - `service_team_name` string, nullable — Name of the team that owns the related service.
    - `total_acknowledgements` integer — Total acknowledgements from the responder on the incident.
    - `total_business_hour_interruptions` integer — Total number of unique interruptions during business hours; 8am-6pm Mon-Fri, based on the user’s time zone.
    - `total_engaged_seconds` integer — Total engaged time across all responders for incidents. 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_interruptions` integer — Total number of unique interruptions for the responder during the incident.
    - `total_manual_escalations_from` integer — Total times the responder was manually escalated away from the incident.
    - `total_manual_escalations_to` integer — Total times the responder was manually escalated to the incident.
    - `total_off_hour_interruptions` string — Total number of unique interruptions during off hours; 6pm-10pm Mon-Fri and all day Sat-Sun, based on the user’s time zone.
    - `total_reassignments_from` integer — Total times the responder was reassigned away from the incident.
    - `total_reassignments_to` integer — Total times the responder was reassigned to the incident.
    - `total_sleep_hour_interruptions` integer — Total number of unique interruptions during sleep hours; 10pm-8am every day, based on the user’s time zone.
    - `total_timeout_escalations_from` integer — Total times the responder was escalated away from the incident due to timeout.
    - `total_timeout_escalations_to` integer — Total times the responder was escalated to the incident due to timeout.

## 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/versions/b679a8f3f02c/schema)