POST /incidents

Create an incident synchronously without a corresponding event from a monitoring service.

An incident represents a problem or an issue that needs to be addressed and resolved.

For more information see the API Concepts Document

Scoped OAuth requires: incidents.write

This API operation has operation specific rate limits. See the Rate Limits page for more information.

Servers

Request headers

Name Type Required Description
Accept String Yes

The Accept header is used as a versioning header.

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

Content-Type String Yes

Possible values:

  • "application/json"

Default value: "application/json"

From String Yes

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

Request body fields

Name Type Required Description
incident Object Yes

Details of the incident to be created.

incident.priority No
incident.escalation_policy No
incident.urgency String No

The urgency of the incident

Possible values:

  • "high"
  • "low"
incident.type String Yes

Possible values:

  • "incident"
incident.title String Yes

A succinct description of the nature, symptoms, cause, or effect of the incident.

incident.service Yes
incident.body No
incident.incident_type No
incident.conference_bridge No
incident.incident_key String No

A string which identifies the incident. Sending subsequent requests referencing the same service and with the same incident_key will result in those requests being rejected if an open incident matches that incident_key.

incident.assignments[] Array No

Assign the incident to these assignees. Cannot be specified if an escalation policy is given.

incident.assignments[].assignee No

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. 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.
  3. Click Test request to test run your request to the API and see the API's response.