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

# Get raw responses from a single incident

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

Provides enriched responder data for a single incident.

Example metrics include Time to Respond, Responder Type, and Response Status. See metric definitions below.

<!-- 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

## Request body

- object
  - `limit` integer — Number of results to include in each batch. Limits between 1 to 1000 are accepted.
  - `order` 'asc' | 'desc' — The order in which to display the results; asc for ascending, desc for descending. Defaults to `desc`.
  - `order_by` 'requested_at' — The column to use for ordering the results.
  - `time_zone` string — The time zone to use for the results.

## Response `200`

- object
  - `incident_id` string — The Incident 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` 'requested_at' — The column that was used for ordering the results.
  - `time_zone` string — The time zone that the results are in.
  - `responses` AnalyticsRawIncidentResponses[]
    - `responder_name` string — Name of the user associated with the Incident Response.
    - `responder_id` string — ID of the user associated with the Incident Response.
    - `response_status` 'joined' | 'pending' | 'declined' — Status of the user's interaction with the Incident notification.
    - `responder_type` 'assigned' | 'reassigned' | 'escalated' | 'added_responder' — Type of responder, where `assigned` means the user was added to the Incident via Assignment at Incident creation, `reassigned` means the user was added to the Incident via Reassignment, `escalated` means the user was added via Escalation, and `added_responder` means the user was added via Responder Reqeuest.
    - `requested_at` string — Timestamp of when the user was requested.
    - `responded_at` string — Timestamp of when the user responded to the request.
    - `time_to_respond_seconds` integer — Measures the time it took for the user to respond to the Incident request. In other words, `responded_at - requested_at`.

## 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)