OpsGenie

Manage alerts, incidents, schedules, and on-call rotations.

Install

amodal connect opsgenie

Authentication

GenieKey authentication (not standard Bearer).

• OPSGENIE_API_KEY — OpsGenie API key

Format: Authorization: GenieKey <api_key>. API keys can be scoped to a team or global. EU customers must use api.eu.opsgenie.com instead of api.opsgenie.com.

Endpoints

Alerts

• GET /v2/alerts — List alerts
• GET /v2/alerts/{id} — Get alert details
• GET /v2/alerts/{id}/notes — Get alert notes
• POST /v2/alerts/{id}/acknowledge — Acknowledge alert (confirmation)
• POST /v2/alerts/{id}/close — Close alert (confirmation)
• POST /v2/alerts/{id}/assign — Assign alert (confirmation)
• POST /v2/alerts — Create alert (confirmation)
• DELETE /v2/alerts/{id} — Delete alert (confirmation)

Incidents

• GET /v2/incidents — List incidents
• GET /v2/incidents/{id} — Get incident details
• POST /v2/incidents — Create incident (confirmation)

Schedules

• GET /v2/schedules — List schedules
• GET /v2/schedules/{id} — Get schedule details
• GET /v2/schedules/{id}/on-calls — Get on-call participants

Entities

• alert, note, incident, schedule, on-call, acknowledge, close

Rules

• Rate limits vary by plan: Free (20/min), Essentials/Standard (60/min), Enterprise (120/min)
• Closing an alert is terminal — closed alerts cannot be reopened; acknowledging stops escalation but does not close
• Alert notes are a separate sub-resource (/alerts/{id}/notes) and are not included in the alert detail response
• Alerts with the same alias are de-duplicated — subsequent triggers increment count instead of creating new alerts