get_incidents
Retrieve PagerDuty incidents by filters like status, service, team, or date range. Get details for a specific incident by ID or number.
Instructions
Get PagerDuty incidents by filters or get details for a specific incident ID or number.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| incident_id | No | The incident ID or number to retrieve (optional, cannot be used with any other filters). | |
| current_user_context | No | Filter by current user's context (default: True). Not used if `incident_id` is provided. | |
| service_ids | No | Filter by services (optional, excludes current_user_context). Not used if `incident_id` is provided. | |
| team_ids | No | Filter by teams (optional, excludes current_user_context). Not used if `incident_id` is provided. | |
| statuses | No | Filter by status (optional). Not used if `incident_id` is provided. Must be input as a list of strings, valid values are `["triggered", "acknowledged", "resolved"]`. | |
| since | No | Start of query range in ISO8601 format (default range: 1 month, max range: 6 months). Not used if `incident_id` is provided. | |
| until | No | End of query range in ISO8601 format (default range: 1 month, max range: 6 months). Not used if `incident_id` is provided. | |
| limit | No | Max results (optional). Not used if `incident_id` is provided. | |
| include_past_incidents | No | If True and `incident_id` is provided, includes similar past incidents in the response. Defaults to False. Cannot be used without `incident_id`. | |
| include_related_incidents | No | If True and `incident_id` is provided, includes related incidents impacting other services/responders in the response. Defaults to False. Cannot be used without `incident_id`. | |
| include_notes | No | If True, includes notes for each incident in the response. Defaults to False. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||