<p>PD has a lot of native integrations that can do auto-resolve but for those that don't you can use the API and/or rulesets to do that.</p>
<p>Here is a link to the ruleset documentation: <a href="https://support.pagerduty.com/docs/rulesets" rel="nofollow noreferrer">https://support.pagerduty.com/docs/rulesets</a></p>
<p>And here is documentation on the incident resolution API:
<a href="https://developer.pagerduty.com/api-reference/reference/REST/openapiv3.json/paths/%7E1incidents%7E1%7Bid%7D/put" rel="nofollow noreferrer">https://developer.pagerduty.com/api-reference/reference/REST/openapiv3.json/paths/~1incidents~1%7Bid%7D/put</a></p>
<p>In the API call you would pass the following json body to resolve it:
{
&quot;incident&quot;: {
&quot;type&quot;: &quot;incident_reference&quot;,
&quot;status&quot;: &quot;resolved&quot;
}
}</p>

CC BY-SA 4.0
2021-05-07T12:55:33.997Z
2021-05-07T12:55:33.997Z
Joe Calcada
<p>It is possible to implement auto-resolution with Pagerduty API integration. When a monitoring system detects an issue based on some metric and a threshold, it would create a Pagerduty incident through the API integration. Later, if the metric falls below the threshold, it could automatically resolve the incident, in case it is still open.</p>
<p>This feature could be very useful for several reasons:</p>
<h3>Cases where a large number of incidents get triggered due to a common root cause</h3>
<p>In this case, the on call person is spared from having to ack/resolve so many incidents and instead focus on troubleshooting and fixing the problem.</p>
<h3>Auto-resolution would capture the incident duration more accurately</h3>
<p>Humans are not good in doing things on a timely basis. If we are computing MTTR based on manual resolution of incidents, it may lead to inaccurate measurements.</p>
<p>Has anyone implemented auto-resolution with Pagerduty? If so, would you be able to talk about the pros and cons?</p>

CC BY-SA 4.0
2021-07-21T21:27:36.423Z
Related: [Advantages of API versus Email Integration](https://community.pagerduty.com/forum/t/advantages-of-api-versus-email-integration/1439).
codeforester
<monitoring><pagerduty>
Pagerduty API integration and auto-resolution
codeforester
# Pagerduty API integration and auto-resolution

(Asked by: username_0 on 2021-05-04)

It is possible to implement auto-resolution with Pagerduty API integration. When a monitoring system detects an issue based on some metric and a threshold, it would create a Pagerduty incident through the API integration. Later, if the metric falls below the threshold, it could automatically resolve the incident, in case it is still open.

This feature could be very useful for several reasons:

### Cases where a large number of incidents get triggered due to a common root cause

In this case, the on call person is spared from having to ack/resolve so many incidents and instead focus on troubleshooting and fixing the problem.

### Auto-resolution would capture the incident duration more accurately

Humans are not good in doing things on a timely basis. If we are computing MTTR based on manual resolution of incidents, it may lead to inaccurate measurements.

Has anyone implemented auto-resolution with Pagerduty? If so, would you be able to talk about the pros and cons?

**Tags:** monitoring, pagerduty

> **Comments:**
> **username_0**: Related: [Advantages of API versus Email Integration](https://community.pagerduty.com/forum/t/advantages-of-api-versus-email-integration/1439).  

---

## 1 answers

### Answer by username_1 on 2021-05-07. Score: 2

PD has a lot of native integrations that can do auto-resolve but for those that don't you can use the API and/or rulesets to do that.

Here is a link to the ruleset documentation: <https://support.pagerduty.com/docs/rulesets>

And here is documentation on the incident resolution API:
[https://developer.pagerduty.com/api-reference/reference/REST/openapiv3.json/paths/~1incidents~1%7Bid%7D/put](https://developer.pagerduty.com/api-reference/reference/REST/openapiv3.json/paths/%7E1incidents%7E1%7Bid%7D/put)

In the API call you would pass the following json body to resolve it:
{
"incident": {
"type": "incident\_reference",
"status": "resolved"
}
}


---

