Skip to main content
POST
/
v2
/
alerts
/
Create Alert (OpsGenie)
curl --request POST \
  --url https://api.warrn.io/v2/alerts/ \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "message": "<string>",
  "alias": "<string>",
  "description": "<string>",
  "priority": "P3",
  "responders": [
    {
      "name": "<string>"
    }
  ],
  "tags": [
    "<string>"
  ],
  "details": {},
  "entity": "<string>",
  "source": "<string>"
}
'
{
  "result": "Request will be processed",
  "took": 0,
  "requestId": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
}
Create an alert using the OpsGenie request format. Warrn transforms the payload to its native shape, so existing OpsGenie integrations work without code changes. A few mappings worth knowing:
  • message → alert name (truncated past 255 chars; the full string lands in metadata).
  • priority → severity: P1 → critical, P2 → high, P3 → medium, P4/P5 → low.
  • responders[0] (where type: "team") → resolved to a Warrn team by name.
  • entity → resolved to a service by name match.
  • details → alert metadata.
  • An opsgenie-migrated tag is added automatically.

Authorizations

​
Authorization
string
header
required

Bearer token using your Warrn API key.

Body

application/json
​
message
string
required

Alert message. Maps to alert name in Warrn.

Maximum string length: 255
​
alias
string

Stable alias for deduplication and later lookup.

​
description
string
​
priority
enum<string>
default:P3

P1→critical, P2→high, P3→medium, P4/P5→low.

Available options:
P1,
P2,
P3,
P4,
P5
​
responders
object[]
​
tags
string[]
​
details
object
​
entity
string

Resolved to a service by name match.

​
source
string

Response

Accepted

​
result
string
Example:

"Request will be processed"

​
took
number
Example:

0

​
requestId
string<uuid>