Create and manage alerts in Opsgenie using the REST API
domain: support.atlassian.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain an Opsgenie API key from Settings > API key management with the appropriate integration type (API integration for programmatic access)
Create an alert via POST to 'https://api.opsgenie.com/v2/alerts' with 'Authorization: GenieKey YOUR_KEY' header and JSON body containing 'message' (required, max 130 chars), 'alias' (dedup key), 'description', 'priority', and 'tags'
Acknowledge an alert by POST to '/v2/alerts/{identifier}/acknowledge' with body '{"user": "system", "note": "Ack reason"}' where identifier is the alert ID or alias with '?identifierType=alias'
Close an alert via POST to '/v2/alerts/{identifier}/close' with a note body; this marks the alert resolved and stops escalations
List active alerts via GET '/v2/alerts' with query parameters 'query' (Opsgenie query syntax), 'limit', and 'sort' to retrieve open alerts programmatically
Known gotchas
The 'alias' field is used for deduplication; alerts with the same alias are deduplicated within a two-minute window — outside that window a new alert is created with the same alias
Opsgenie has two API endpoint regions (US: api.opsgenie.com, EU: api.eu.opsgenie.com); using the wrong regional endpoint returns 401 even with a valid key
Alert 'message' has a 130-character hard limit; exceeding it silently truncates the message rather than returning a validation error in some API versions
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?