younifyd
Menu

List Incident Alerts

List alerts for an incident

GET/incidents/{id}/alerts

Use it in a workflow

  1. Add a step and choose the PagerDuty connector.
  2. Pick the List Incident Alerts action (under Incidents).
  3. Fill in the fields below, then reference the result from later steps as {{listIncidentAlerts.response.data}}.

Request

Path parameters

idstringrequired

The ID of the resource.

Query parameters

limitinteger

The number of results per page.

offsetinteger

Offset to start pagination search results.

totalboolean

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.

Default false

alert_keystring

Alert de-duplication key.

statuses[]string

Return only alerts with the given statuses. (More status codes may be introduced in the future.)

One oftriggeredresolved

sort_bystring

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.

One ofcreated_atresolved_atcreated_at:asccreated_at:descresolved_at:ascresolved_at:desc

include[]string

Array of additional details to include.

One ofservicesfirst_trigger_log_entriesincidents

Headers

Acceptstringrequired

The `Accept` header is used as a versioning header.

Default "application/vnd.pagerduty+json;version=2"

Content-Typestringrequired

One ofapplication/jsonDefault "application/json"

Response

Returns 200 with a any. Read it in later steps with {{listIncidentAlerts.response.data.<field>}}.

Need more? See the PagerDuty guide for connection setup and behaviour shared by every action.