Manually change an Incident's Impact on a Business Service.
Change Impact of an Incident on a Business Service.
Scoped OAuth requires: incidents.write
Authorization
api_key The API Key with format Token token=<API_KEY>
In: header
Path Parameters
The ID of the resource.
The business service ID.
Header Parameters
The Accept header is used as a versioning header.
"application/vnd.pagerduty+json;version=2"Request Body
application/json
The impacted relation will cause the Business Service and any Services that it supports to become impacted by this incident.
The not_impacted relation will remove the Incident's Impact from the specified Business Service.
The effect of adding or removing Impact to a Business Service in this way will also change the propagation of Impact to other Services supported by that Business Service.
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
Merge incidents PUT
Merge a list of source incidents into the target [incident](https://developer.pagerduty.com/api-reference/a47605517c19a-api-concepts#incidents). After the merge is performed the target incident will contain the source incidents' [alerts](https://developer.pagerduty.com/api-reference/a47605517c19a-api-concepts#alerts), and the source incidents will be resolved. Only incidents that have alerts or incidents that were created manually in the UI can be merged. Open incidents cannot be merged into a resolved incident. The target incident must be open. An incident cannot have more than 1000 alerts. The server will return an error if merging the source incidents will result in the target incident having more than 1000 alerts. Scoped OAuth requires: `incidents.write`
Remove Notification Subscriber POST
Unsubscribes the matching Subscribers from Incident Status Update Notifications. Scoped OAuth requires: `subscribers.write`