Opsgenie integration: API key, teams, and routing
Owner Theo Hayashi · Last updated 2026-03-19 · v3.0
opsgenieintegrationoncallteam-routing
Opsgenie integration
Opsgenie is structurally similar to PagerDuty — DevFlow speaks Opsgenie's REST API directly.
install
In Opsgenie, create an API integration under Settings → API key management, copy the API key.
In DevFlow:
bash
devflow channels add payments-oncall --type opsgenie --api-key og_abcdef --team payments-oncallteam routing
The --team flag is the Opsgenie team name to route to. DevFlow alerts target teams, not individuals — handoffs stay inside Opsgenie.
priority mapping
| DevFlow severity | Opsgenie priority |
|---|---|
| critical | P1 |
| error | P2 |
| warning | P3 |
| info | P5 |
dedup
Opsgenie alert dedup uses our alias field, set to devflow:incident:<incident-id>. Same approach as pagerduty-integration.
bidirectional ack
/devflow ack and Opsgenie ack stay in sync via the bidirectional webhook. Same shape as PD.
removing
Opsgenie admins can revoke the API key. DevFlow surfaces the failure on the next delivery.