|docs
Start Trial
REST APIIncidents

Create a responder request for an incident

Send a new responder request for the specified incident. This endpoint requires the account to have access to the responder requests feature.

Account Ability Requirement: The account must have the coordinated_responding ability. Returns 402 Payment Required if the ability is missing. You can use the List Abilities API to check account abilities.

A user or an escalation policy can be requested. The responder targets will be notified via their high urgency notification rules, until the target user has either accepted or declined the request. Previous responder requests for a given target can be cancelled (preventing them from further notifying or escalating), with the Cancel Responder Requests endpoint.

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"

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

Add Notification Subscribers POST

Subscribe the given entities to Incident Status Update Notifications. Scoped OAuth requires: `subscribers.write`

Snooze an incident POST

Snooze an incident. 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.write`