G’day everyone, how ya goin'?
I’m Scot, from Atlassian’s ITSM Support team, with good news about the future of api.opsgenie.com and api.eu.opsgenie.com, for our migrating Opsgenie customers and our already migrated JSM Operations customers.
We will continue to support the alerting and integration event api.opsgenie.com and api.eu.opsgenie.com endpoints indefinitely. That means, come April 2027, when Opsgenie reaches End of Support, your integrations responsible for sending and actioning alerts will still continue to work.
- You do not need to change the configuration on your end systems
- You do not need to regenerate your api keys
- You do not need to recreate each integration in JSM and move to the JSM Integration paths
- For the majority of your currently configured vendor integrations and products, creating and actioning alerts will continue to work unchanged.
- There are some integrations for particular products that need to be recreated when migrating to JSM from Opsgenie, but that is for reasons not related to the future of api.opsgenie.com and api.eu.opsgenie.com
When we get to April 2027, we will retire the other api.opsgenie.com and api.eu.opsgenie.com endpoints related to configuration changes, such as our User, Teams, Schedule, and Notification API endpoints. In line with the security principle that each configuration change should be attributable to an individual user, these endpoints will be deprecated as they use a generic GenieKey authentication.
To manage your configuration via API, you will need to have migrated to JSM Operations and be using the JSM Operations endpoints with individual authentication tokens by April 2027 . We recommend that these changes be done when you migrate from Opsgenie to JSM Operations, rather than waiting for your Opsgenie instance to shut down or April 2027, whichever comes first.
