Skip to main content
The Warrn API uses conventional HTTP status codes to indicate the success or failure of a request. Codes in the 2xx range indicate success, codes in the 4xx range indicate a problem with the request (a missing field, an invalid API key, a resource that doesn’t exist), and codes in the 5xx range indicate a problem with Warrn’s servers. Every error response includes a human-readable message describing what went wrong, so you can surface useful diagnostics in client integrations and CI logs without having to map status codes by hand.

Error Response Format

When a request fails, the API returns a JSON object with an error message:
For OpsGenie-compatible endpoints, errors include a requestId for tracing:

HTTP Status Codes

Common Errors

Invalid API key

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

Permission denied

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

Invalid severity

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