Opsgenie Alert API

Name: Opsgenie Alert API API
Brand: Opsgenie Alert API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring ObservabilityapiKey18 EndpointsREST

For Agents

Create, route, acknowledge, snooze, close, and escalate Opsgenie alerts across 18 endpoints, with API key authentication and async request tracking.

Quickstart

Get started with Opsgenie Alert API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create an opsgenie alert"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Opsgenie Alert API API.

Create an alert with priority, message, responders, and tags from a monitoring source

Acknowledge or close alerts to mark them as handled by the on-call responder

Snooze a noisy alert so it does not page again before a chosen time

Assign an alert to a specific responder or escalate it to the next on-call

GET STARTED

Start building with Opsgenie Alert API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Opsgenie Alert API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Opsgenie Alert API, keeping it validated and agent-ready. Opsgenie is Atlassian's alerting and on-call management platform used by SRE and DevOps teams to route incidents to the right responders. The Alert API exposes endpoints to create, list, count, acknowledge, snooze, close, escalate, and tag alerts, plus add notes, assign responders, and trigger custom actions. Asynchronous operations return a request ID that can be polled via the request status endpoint. Authentication uses a Genie key passed in the Authorization header.

Use Cases

Patterns agents use Opsgenie Alert API API for, with concrete tasks.

★ Routing monitoring alerts into on-call

When a monitoring system detects an outage, an automation agent calls POST /alerts with priority, message, responders, and tags so Opsgenie can fan the alert out to the right on-call schedule. Because alert creation is asynchronous, the agent retrieves the requestId from the response and polls GET /alerts/requests/{requestId} to confirm the alert was processed before moving on.

POST /alerts with priority=P1, message='Database master down', tags=['production','postgres'], then poll /alerts/requests/{requestId} until status is processed.

Auto-acknowledge from chat or ticket

Incident commanders running ChatOps can acknowledge an alert directly from a chat command by calling POST /alerts/{identifier}/acknowledge. The same flow extends to ticket systems where opening a Jira issue marks the originating Opsgenie alert as acknowledged so it stops paging the rotation.

POST /alerts/{identifier}/acknowledge with note='picked up by Sam in #incidents' to silence the page.

Suppressing flapping alerts

When a known-flaky service is generating repeated alerts, the on-call agent can call POST /alerts/{identifier}/snooze with an end time several hours out so the alert does not re-page during the silence window. The snooze record is visible to the rest of the rotation, which keeps the action transparent rather than hidden in a chat thread.

POST /alerts/{identifier}/snooze with endTime set 4 hours in the future and a note explaining why the alert is being suppressed.

Escalation policies and assignment

When an alert sits unacknowledged past a threshold, an automation agent can use POST /alerts/{identifier}/escalate to move it to the next escalation level, or POST /alerts/{identifier}/assign to assign it to a specific responder. This is well suited to deadline-aware bots that watch alert age and bump them when they go stale.

Read alerts via GET /alerts, identify any open longer than 30 minutes, and POST /alerts/{identifier}/escalate to move them up a level.

AI agent for incident triage

Through Jentic, an SRE assistant agent can answer 'what's open right now' by calling GET /alerts with a status=open filter, then offering to acknowledge or snooze specific alerts via the same toolset. The Opsgenie API key sits in the Jentic vault, so triage agents can run alongside existing PagerDuty or chat integrations without exposing it.

Search Jentic for 'list open opsgenie alerts', execute GET /alerts with status=open, and propose an action (ack, snooze, escalate) for each.

Key Endpoints

18 endpoints — jentic publishes the only available openapi specification for opsgenie alert api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/alerts

Create an alert

GET

/alerts

List alerts

POST

/alerts/{identifier}/acknowledge

Acknowledge an alert

POST

/alerts/{identifier}/close

Close an alert

POST

/alerts/{identifier}/snooze

Snooze an alert

POST

/alerts/{identifier}/escalate

Escalate an alert

GET

/alerts/requests/{requestId}

Get the status of an async alert request

POST

/alerts

Create an alert

GET

/alerts

List alerts

POST

/alerts/{identifier}/acknowledge

Acknowledge an alert

POST

/alerts/{identifier}/close

Close an alert

POST

/alerts/{identifier}/snooze

Snooze an alert

POST

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Opsgenie GenieKey API keys are stored encrypted in the Jentic vault. Agents receive a scoped execution context — Jentic prepends 'GenieKey ' and adds the Authorization header at request time, so the agent never sees or constructs the credential.

Intent-based discovery

Agents search Jentic with intents like 'create an opsgenie alert' or 'acknowledge an alert' and Jentic returns the matching operation under /alerts with its full input schema.

Time to first call

Direct integration: 1 day to read the docs, build a Genie key handling layer, and wire async request polling. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

PagerDuty

Incident response platform with on-call schedules and automation

Choose PagerDuty when the team is already standardised on PagerDuty schedules and wants its automation actions and analytics.

Complementary

Atlassian Jira

Issue tracker commonly paired with Opsgenie for postmortems and tickets

Use alongside Opsgenie when alerts should automatically open Jira incidents or postmortem tickets.

Complementary

New Relic

Observability platform that emits events Opsgenie turns into pages

Use alongside Opsgenie when an agent needs to read New Relic metrics before deciding whether to acknowledge or escalate an alert.

FAQs

Specific to using Opsgenie Alert API API through Jentic.

Why is there no official OpenAPI spec for Opsgenie Alert API?

Atlassian's Opsgenie does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Opsgenie Alert API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Opsgenie Alert API use?

Opsgenie uses an API key sent in the Authorization header in the format 'GenieKey {apiKey}'. Through Jentic the GenieKey is stored encrypted in the vault and prefixed correctly at execution, so the agent never sees or assembles the header itself.

Can I create an alert and add a note in a single call with this API?

Not in one call. POST /alerts creates the alert and POST /alerts/{identifier}/notes adds a note. Because alert creation is asynchronous, the agent waits for /alerts/requests/{requestId} to return the alert identifier before adding the note.

What are the rate limits for the Opsgenie Alert API?

Opsgenie applies per-customer and per-endpoint quotas; create-alert is the most heavily limited operation. Treat 429 responses as a signal to back off and keep an eye on the X-RateLimit headers Opsgenie returns alongside responses.

How do I acknowledge an alert through Jentic?

Search Jentic for 'acknowledge an opsgenie alert', load POST /alerts/{identifier}/acknowledge, and execute it with the alert ID. The vaulted GenieKey is supplied automatically and the response includes a request ID you can poll for confirmation.

Why does creating an alert return a request ID instead of the alert?

Alert creation is asynchronous in Opsgenie. POST /alerts returns a requestId and the alert is created shortly after; agents call GET /alerts/requests/{requestId} to retrieve the eventual alert ID and confirm successful processing.