PAGERDUTY_GET_ALERTS_BY_INCIDENT_ID

Retrieves all alerts associated with a specific incident in PagerDuty. This endpoint allows users to fetch detailed information about the notifications and alerts that were triggered as part of an incident's lifecycle. It is particularly useful for incident postmortems, auditing purposes, or understanding the notification flow during an incident. The endpoint returns a list of alerts, which may include information such as alert creation time, alert status, and the targets (users or services) that received the notifications. It should be used when detailed alert information for a known incident is required, but it will not provide information about the incident itself beyond its associated alerts.

Available from 1 provider (1 remote)

Input Schema


            {
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "title": "Id",
      "description": "The ID of the resource."
    },
    "limit": {
      "type": "integer",
      "title": "Limit",
      "description": "The number of results per page."
    },
    "total": {
      "type": "boolean",
      "title": "Total",
      "default": false,
      "description": "By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated. See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information.  "
    },
    "offset": {
      "type": "integer",
      "title": "Offset",
      "description": "Offset to start pagination search results."
    },
    "include": {
      "enum": [
        "services",
        "first_trigger_log_entries",
        "incidents"
      ],
      "type": "string",
      "title": "Include",
      "description": "Array of additional details to include."
    },
    "sort_by": {
      "enum": [
        "created_at",
        "resolved_at",
        "created_at:asc",
        "created_at:desc",
        "resolved_at:asc",
        "resolved_at:desc"
      ],
      "type": "string",
      "title": "Sort By",
      "description": "Used to specify both the field you wish to sort the results on (created_at/resolved_at), as well as the direction (asc/desc) of the results. The sort_by field and direction should be separated by a colon. A maximum of two fields can be included, separated by a comma. Sort direction defaults to ascending. "
    },
    "statuses": {
      "enum": [
        "triggered",
        "resolved"
      ],
      "type": "string",
      "title": "Statuses",
      "description": "Return only alerts with the given statuses. (More status codes may be introduced in the future.) "
    },
    "alert_key": {
      "type": "string",
      "title": "Alert Key",
      "description": "Alert de-duplication key."
    }
  }
}
          

Remote Providers (1)

These servers are accessible over the network — no local installation needed.

PagerDuty

Remote

pagerduty

View product →