---
title: "Get Paused Incident Reporting on Alerts"
method: GET
path: "/paused_incident_reports/alerts"
tags: ["Paused Incident Reports"]
---

# Get Paused Incident Reporting on Alerts

`GET /paused_incident_reports/alerts`

Returns the 5 most recent alerts that were triggered after being paused and the 5 most recent alerts that were resolved after being paused for a given reporting period (maximum 6 months lookback period).  Note: This feature is currently available as part of the Event Intelligence package or Digital Operations plan only.

For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#paused-incident-reports)

Scoped OAuth requires: `incidents.read`

## Query parameters

- `since` string, date-time
- `until` string, date-time
- `service_id` string
- `suspended_by` 'auto_pause' | 'rules'

## Headers

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

## Response `200`

Paused Incident Reporting on Alerts for the Account or scoped to a Service.

- object
  - `paused_incident_reporting_alerts` object — A list of the 5 most recent paused Alerts that weere triggered and 5 most recent Alerts that were reesolved before being triggerd.
    - `since` string — The start of the date range over which the report data is represented.
    - `until` string — The end of the date range over which the report data is represented.
    - `triggered_after_pause_alerts` object[] — An array of Alerts that were triggered after being paused.
      - `id` string — The Alert ID
      - `service_id` string — The Alert's Service ID
      - `created_at` string — The date/time the Alert was created
    - `resolved_after_pause_alerts` object[] — An array of Alerts that were resolved after being paused.
      - `id` string — The Alert ID
      - `service_id` string — The Alert's Service ID
      - `created_at` string — The date/time the Alert was created

## Other responses

- `400` — Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work.
- `403` — Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action.
- `404` — The requested resource was not found.
- `429` — Too many requests have been made, the rate limit has been reached.
- `500` — Internal Server Error the PagerDuty server experienced an error.

---

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