PUT /incidents/{id}/alerts
Resolve multiple alerts or associate them with different incidents.
An incident represents a problem or an issue that needs to be addressed and resolved. An alert represents a digital signal that was emitted to PagerDuty by the monitoring systems that detected or identified the issue.
A maximum of 250 alerts may be updated at a time. If more than this number of alerts are given, the API will respond with status 413 (Request Entity Too Large).
For more information see the API Concepts Document
Scoped OAuth requires: incidents.write
Servers
- https://api.pagerduty.com
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
id |
String | Yes |
The ID of the resource. |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Accept |
String | Yes |
The Default value: "application/vnd.pagerduty+json;version=2" |
Content-Type |
String | Yes |
Possible values:
Default value: "application/json" |
From |
String | Yes |
The email address of a valid user associated with the account making the request. |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
limit |
Integer | No |
The number of results per page. |
offset |
Integer | No |
Offset to start pagination search results. |
total |
Boolean | No |
By default the See our Pagination Docs for more information. Default value: false |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
alerts[] |
Array | Yes |
An array of alerts, including the parameters to update for each alert. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.