Skip to main content
POST
/
v2
/
alerts
/
{identifier}
/
close
Close Alert (OpsGenie)
curl --request POST \
  --url https://api.warrn.io/v2/alerts/{identifier}/close \
  --header 'Authorization: Bearer <token>'
{
  "result": "Request will be processed",
  "took": 0,
  "requestId": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
}
Close an alert, setting its status to resolved. The most common pattern is to close by alias - pass identifierType=alias and use the same alias you set when creating the alert.

​
Typical workflow

Create the alert with a stable alias, then close it by that alias when the issue resolves: 
# 1. Alert fires - create with alias
curl -X POST "https://api.warrn.io/v2/alerts/" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer warrn_k8sM2vL9xQ7nP4wR..." \
  -d '{"message": "Disk full on db-01", "alias": "disk-full-db-01", "priority": "P2"}'

# 2. Issue resolved - close by alias
curl -X POST "https://api.warrn.io/v2/alerts/disk-full-db-01/close?identifierType=alias" \
  -H "Authorization: Bearer warrn_k8sM2vL9xQ7nP4wR..."
Lookup by alias only matches alerts currently open or acknowledged (the same window during which a repeat create dedups). If the alias has no live alert, the endpoint returns an error response with the message "No open alert found with alias: {your-alias}".

Authorizations

​
Authorization
string
header
required

Bearer token using your Warrn API key.

Path Parameters

​
identifier
string
required

Query Parameters

​
identifierType
enum<string>
default:id
Available options:
id,
alias,
tiny

Response

Accepted

​
result
string
Example:

"Request will be processed"

​
took
number
Example:

0

​
requestId
string<uuid>