Compatibility
Close or acknowledge an alert with the Opsgenie Alert API
POST/v1/integrations/opsgenie/{configurationId}/{escalationPolicyId}/v2/alerts/{identifier}/{action}requires incidents:write
Opsgenie-compatible close and acknowledge. identifier is the alert alias and identifierType=alias is required. Closing resolves the active incident for that alias and cancels pending escalation; an alias with no active incident is accepted without effect. The request body is not read.
Requestcurl -X POST https://api.transmit.dev/v1/integrations/opsgenie/{configurationId}/{escalationPolicyId}/v2/alerts/{identifier}/{action} \
-H "Authorization: Bearer tr_v2_…"Parameters
| Name | In | Notes |
|---|---|---|
configurationId required | path | Routing resource UUID in the API key's workspace. |
escalationPolicyId required | path | Routing resource UUID in the API key's workspace. |
identifier required | path | The alias the alert was created with, URL-encoded. |
action required | path | close or acknowledge. |
identifierType required | query | Must be alias. |
Responses
| Status | Meaning |
|---|---|
202 | Transition committed |
401 | The API key is missing, malformed, expired or revoked |
403 | The API key lacks the incidents:write scope |
404 | Unsupported action |
422 | identifierType is not alias, or the alias is invalid |
Every response body is described in the OpenAPI spec, which this page is generated from.