Errors - Warrn

Error Response Format

When a request fails, the API returns a JSON object with an error message:

{
  "message": "Alert not found with alias: my-alert-alias"
}

For OpsGenie-compatible endpoints, errors include a requestId for tracing:

{
  "message": "Failed to create alert. Please try again.",
  "took": 0.0,
  "requestId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
}

Code	Meaning
`200`	Request succeeded
`201`	Resource created
`400`	Bad request — invalid JSON, missing required fields, or integration disabled
`401`	Unauthorized — missing or invalid API key
`403`	Forbidden — API key lacks required permission, or IP not in allowlist
`404`	Not found — alert, team, or service does not exist
`422`	Validation error — field value out of range (e.g. invalid severity)
`429`	Rate limit exceeded — wait and retry

HTTP 401 Unauthorized

Check that you’re passing the key as Authorization: Bearer warrn_xxx. The key must start with warrn_.

HTTP 403 Forbidden

Your API key has read permission but the endpoint requires write. Create a new key with the correct permission level.

HTTP 422 Unprocessable Entity

The severity field must be one of: low, medium, high, critical.