Opsgenie migration - Do we need to remake Integrations for correct API URL?

[Calvin]

We currently have a number of Opsgenie Integrations that use the api opsgenie com url.

Looking at this comment it seems to suggest it may stay? https://community.atlassian.com/forums/Jira-Service-Management/Migration-of-opsgenie-api-correct-url/qaq-p/2919186

And this one without any answers: https://community.atlassian.com/forums/Jira-Service-Management/Jira-Service-Management-API-URLs-for-migrated-OpsGenie/qaq-p/2936615

But I also read elsewhere that the Opgenie URL/API will only last 90 days after migration.

Anyone know if there is anywhere with clarity on this that I may have missed.

Cheers!

[Hans Polder _Devoteam_]

Hi Calvin,

Looking at the official documentation (https://support.atlassian.com/jira-service-management-cloud/docs/start-shifting-from-opsgenie-to-jira-service-management/) this does indeed state that the APIs should remain functional, even after the migration.

However, the recommendation to move to the JSM APIs is there for a reason. My guess would be:

1) In the future, the Opsgenie APIs will removed anyway, forcing you to switch in a shorter timeframe

2) In the future, any development of new features would only be done on JSM APIs, so you would miss out on these if you still use the Opsgenie APIs.

3) Since Opsgenie itself is shutting down completely in 2027 as it's marked end of life, I can imagine that at that time, they would shut down the APIs anyway.

4) It's hard to predict what will happen to alerts if you would be fully switched to Jira, and still use the Opsgenie APIs. Especially since Opsgenie becomes read-only - so I imagine it would be an issue waiting to happen, even if it was not intended by Atlassian.

So, in short: I would definitely move to the new APIs, as soon as you/your teams can.