|docs
Start Trial
REST APIIncidents

Merge incidents

Merge a list of source incidents into the target incident.

After the merge is performed the target incident will contain the source incidents' 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

Authorization

api_key
Authorization<token>

The API Key with format Token token=<API_KEY>

In: header

Path Parameters

id*string

The ID of the resource.

Header Parameters

Accept*string

The Accept header is used as a versioning header.

Default"application/vnd.pagerduty+json;version=2"
Content-Type*"application/json"
Default"application/json"

Value in

  • "application/json"
From*string

The email address of a valid user associated with the account making the request.

Formatemail

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

List incidents GET

List existing incidents. An incident represents a problem or an issue that needs to be addressed and resolved. For more information see the [API Concepts Document](https://developer.pagerduty.com/api-reference/a47605517c19a-api-concepts#incidents) Scoped OAuth requires: `incidents.read`

Manually change an Incident's Impact on a Business Service. PUT

Change Impact of an Incident on a Business Service. Scoped OAuth requires: `incidents.write`