---
title: Atlassian Opsgenie
description: ''
slug: /help/docs/platform-services/automation-service/app-central/integrations/atlassian-opsgenie/
canonical: https://www.sumologic.com/help/docs/platform-services/automation-service/app-central/integrations/atlassian-opsgenie/
---
import useBaseUrl from '@docusaurus/useBaseUrl';
})
***Version: 1.6
Updated: March 23, 2026***
OpsGenie, a service powered by Atlassian in the cloud, provides operational teams with robust alert management capabilities. It ensures efficient tracking of notifications triggered by various monitoring systems. The primary goal is to guarantee that alerts reach the appropriate team members and that issues are resolved swiftly. This service has been successfully incorporated and rigorously vetted in combination with OpsGenie's platform.
## Actions
* **Acknowledge Alert** *(Notification)* - Confirm receipt of alerts with OpsGenie.
* **Add Note to Alert** *(Notification)* - Append a remark to an alert within the OpsGenie system
* **Add Responder to Alert** *(Notification)* - Append a responder to an alert within OpsGenie.
* **Add Tag to Alert** *(Notification)* - Allocate an OpsGenie tag.
* **Assign Alert** *(Notification)* - Allocate an OpsGenie alert.
* **Close Alert** *(Containment)* - Close an alert within OpsGenie.
* **Create Alert** *(Notification)* - Generate a notification within OpsGenie.
* **Create Incident** *(Notification)* - Generate an incident within OpsGenie.
* **Delete Alert** *(Containment)* - Remove an alert from OpsGenie.
* **Escalate Alert Notification Analysis** *(Enrichment)* - Retrieve escalation policies from OpsGenie.
* **Get Alert** *(Enrichment)* - Retrieve the specified alert from OpsGenie.
* **Get On Calls** *(Enrichment)* - Retrieve current on-call participants of a specific schedule.
* **Get Alert Request Status** *(Enrichment)* - Retrieve the status of an alert request from OpsGenie.
* **Get Incident** *(Enrichment)* - Retrieve summarized data, such as issues, risks, open ports, connections, and detection information for a specific IP address.
* **Get Team** *(Enrichment)* - Retrieve specific team information from OpsGenie.
* **List Alerts** *(Enrichment)* - Retrieve a list of alerts from OpsGenie.
* **List Incidents** *(Enrichment)* - Retrieve a list of incidents from OpsGenie.
* **List Schedules** *(Enrichment)* - Retrieve a list of schedules from OpsGenie.
* **List Teams** *(Enrichment)* - Retrieve a list of teams from OpsGenie.
* **List Users** *(Enrichment)* - Retrieve a list of users from OpsGenie.
## Atlassian Opsgenie configuration
Follow the steps below to create an API key.
### Subscriptions account
1. Navigate to the **Settings** page.
1. Go to **Integrations** > **Integrations**.
1. Click on **Default API**.
1. Copy the **API key**.
### Trial accounts
1. Navigate to the **Settings** page.
1. Go to **App Settings** > **API Key Management**.
1. Click **Add New API Key**.
1. Enter a name for the API key and select the access rights to give to this API key. You can regenerate the shown API key *before saving*, if you would like to.
1. Click **Add API Key** to save the new API key.
:::info
The main purpose of usage for these API keys is configuration based API requests. They can be used for configuration actions, *List Teams, List Users, Get Team*.
:::
To run the other actions, you need to have an API from **Team Integrations**:
1. Navigate to the **Teams** page.
1. Click on the team you want to integrate with.
1. Go to **Integrations**
1. Click on **Add Integration**.
1. Select **API**.
1. Enter a name **Integration Name** and **Assign the Team**.
1. Click **Continue**.
1. Copy the **API key**.
1. Click **Turn On Integration**.
:::warning
Please keep in mind that the API keys of the team integrations can only be used for the alerts/incidents of the specific team and the team-based configurations, whereas the API keys of the global integrations can be used for all of the API requests, including account-based configurations.
:::
## Configure Atlassian OpsGenie in Automation Service and Cloud SOAR
import IntegrationsAuth from '../../../../reuse/integrations-authentication.md';
import IntegrationCertificate from '../../../../reuse/automation-service/integration-certificate.md';
import IntegrationEngine from '../../../../reuse/automation-service/integration-engine.md';
import IntegrationLabel from '../../../../reuse/automation-service/integration-label.md';
import IntegrationProxy from '../../../../reuse/automation-service/integration-proxy.md';
import IntegrationTimeout from '../../../../reuse/automation-service/integration-timeout.md';
*
* **API URL**. Enter the OpsGenie API URL. The default value is `https://api.opsgenie.com`
* **API Key**. Enter the [OpsGenie API key](https://support.atlassian.com/opsgenie/docs/api-key-management/) that you [created earlier](#atlassian-opsgenie-configuration).
*
*
*
*
})
For information about Atlassian OpsGenie, see [OpsGenie documentation](https://support.atlassian.com/opsgenie/resources/).
## Alert creation and retrieval across teams
During testing, alerts were created successfully, but retrieving them returned the error:
`Your team does not have access to this alert`
This occurs when the API key used to retrieve the alert belongs to a different team than the team that owns the alert. In Opsgenie, alerts created through an integration can be assigned to a specific team. Opsgenie allows alerts to be created for other teams, but retrieving alerts is restricted based on the team associated with the API key.
### Recommendation
Ensure that the integration API key used for retrieving alerts belongs to the same team that owns the alerts being created, or use an API key with appropriate permissions to access alerts across teams.
## Change Log
* March 22, 2024 - First upload
* July 11, 2024 - Added the Actions:
+ Get On Calls
+ List Schedules
* Sep 16, 2024 - Update the Action:
+ Create Incident - Fixed the bug that caused the action not to add responders to the incident.
* July 1, 2025 - Fixed an issue related to timeout.
* January 30, 2026 - Added a retry mechanism to the Create Alert action.
* March 6, 2026 - Fixed validation logic in the Create Alert action.
* March 23, 2026 (v1.6)
+ Upgraded the `python3_generic` Docker image (Python 3.8) to `python3_12_generic` (Python 3.12) to address Python 3.8 end-of-life and improve security and performance.
+ Fixed validation logic in the following actions: `Acknowledge Alert`, `Add Note to Alert`, `Add Responder to Alert`, `Add Tag to Alert`, `Assign Alert`, `Close Alert`, `Delete Alert` and `Escalate Alert`.