PAGERDUTY_FETCH_INCIDENT_LIST

Retrieves a list of incidents from PagerDuty based on specified criteria. This endpoint allows users to fetch multiple incidents, making it useful for incident management, reporting, and analysis. It supports filtering by status and date range, as well as pagination for handling large result sets. The endpoint is particularly valuable for obtaining an overview of recent or ongoing incidents, tracking incident trends, or integrating PagerDuty incident data into external systems or dashboards. Note that while this endpoint provides a summary of incidents, it may not include full details for each incident; separate API calls might be necessary to fetch comprehensive information for individual incidents.

Available from 1 provider (1 remote)

Input Schema

            {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "description": "The number of results per page. Maximum of 100."
    },
    "since": {
      "type": "string",
      "title": "Since",
      "description": "The start of the date range over which you want to search. Maximum range is 6 months and default is 1 month. "
    },
    "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.  "
    },
    "until": {
      "type": "string",
      "title": "Until",
      "description": "The end of the date range over which you want to search. Maximum range is 6 months and default is 1 month. "
    },
    "offset": {
      "type": "integer",
      "title": "Offset",
      "description": "Offset to start pagination search results."
    },
    "include": {
      "enum": [
        "acknowledgers",
        "agents",
        "assignees",
        "conference_bridge",
        "escalation_policies",
        "first_trigger_log_entries",
        "priorities",
        "services",
        "teams",
        "users"
      ],
      "type": "string",
      "title": "Include",
      "description": "Array of additional details to include."
    },
    "sort_by": {
      "type": "array",
      "items": {
        "type": "string",
        "properties": {}
      },
      "title": "Sort By",
      "description": "Used to specify both the field you wish to sort the results on (incident_number/created_at/resolved_at/urgency), 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. The account must have the `urgencies` ability to sort by the urgency. "
    },
    "statuses": {
      "enum": [
        "triggered",
        "acknowledged",
        "resolved"
      ],
      "type": "string",
      "title": "Statuses",
      "description": "Return only incidents with the given statuses. To query multiple statuses, pass `statuses[]` more than once, for example: `https://api.pagerduty.com/incidents?statuses[]=triggered&statuses[]=acknowledged`. (More status codes may be introduced in the future.) "
    },
    "team__ids": {
      "type": "array",
      "items": {
        "type": "string",
        "properties": {}
      },
      "title": "Team  Ids",
      "description": "An array of team IDs. Only results related to these teams will be returned. Account must have the `teams` ability to use this parameter. "
    },
    "time_zone": {
      "type": "string",
      "title": "Time Zone",
      "description": "Time zone in which results will be rendered. This will default to the account time zone. "
    },
    "urgencies": {
      "enum": [
        "high",
        "low"
      ],
      "type": "string",
      "title": "Urgencies",
      "description": "Array of the urgencies of the incidents to be returned. Defaults to all urgencies. Account must have the `urgencies` ability to do this. "
    },
    "user__ids": {
      "type": "array",
      "items": {
        "type": "string",
        "properties": {}
      },
      "title": "User  Ids",
      "description": "Returns only the incidents currently assigned to the passed user(s). This expects one or more user IDs. Note: When using the assigned_to_user filter, you will only receive incidents with statuses of triggered or acknowledged. This is because resolved incidents are not assigned to any user. "
    },
    "date_range": {
      "enum": [
        "all"
      ],
      "type": "string",
      "title": "Date Range",
      "description": "When set to all, the since and until parameters and defaults are ignored. "
    },
    "incident_key": {
      "type": "string",
      "title": "Incident Key",
      "description": "Incident de-duplication key. Incidents with child alerts do not have an incident key; querying by incident key will return incidents whose alerts have alert_key matching the given incident key. "
    },
    "service__ids": {
      "type": "array",
      "items": {
        "type": "string",
        "properties": {}
      },
      "title": "Service  Ids",
      "description": "Returns only the incidents associated with the passed service(s). This expects one or more service IDs. "
    }
  }
}