Resolve an Incident
Resolve an incident from your own system, for example when a failed check starts passing again. Resolving stops all paging for the incident, the same as clicking Resolve in Oppex.
Request
POST https://api.oppex.ai/api/v1/incident/resolve?incidentID=<incident-id>
There is no request body. Send the incident id as the incidentID query parameter, and your
API key in the X-API-KEY header.
curl -X POST "https://api.oppex.ai/api/v1/incident/resolve?incidentID=8GFB1ADE-1M3C-KJ2QX7PA" \
-H "X-API-KEY: <your-api-key>"
The incident id is the data value returned by Post an Incident. You can also
find it with List Incidents.
Response
{
"success": true,
"statusCode": 200,
"message": "Incident resolved successfully",
"data": "8GFB1ADE-1M3C-KJ2QX7PA"
}
A 200 means Oppex accepted the request. The incident is resolved a moment later. To confirm it,
check the incident's status with List Incidents.
Errors
| Status | When |
|---|---|
400 | incidentID is missing. Or your workspace requires an RCA before an incident can be resolved, and this incident has none: This workspace requires an RCA before resolving. Add an RCA first. Add one with Update RCA, then resolve again. |
401 | The API key is missing, wrong or disabled. See API Keys. |
500 | Something went wrong in Oppex. Retry. If it keeps happening, contact support with the message. |