Opsgenie Rest API endpoint migration to JSM Ops

[Tomi Sofowora]

Hi all, I'm looking to get some clarification on the API migration from Opsgenie to JSM ops.
Based on the documentation we have been told to migrate to JSM Ops Rest API before Opsgenie is shutdown. I've found that 'https://api.atlassian.com/jsm/ops/integration/v2/alerts' matches the functionality of 'https://api.opsgenie.com/v2/alerts', will the integration v2 endpoint replicate Opsgenie v2 post shutdown? This isn't documented but I want to avoid using endpoints that will no longer be in use.

[Aditya Bodke]

Hi Tomi, 
Great question! And thank you for reaching out to us on Atlassian Community.

Please check the following points -

• The /integration/v2/alerts endpoint in JSM Ops is designed to help existing Opsgenie integrations keep working after the migration.
• However, for long-term use and new development, we recommend using the official JSM Ops REST API endpoints, as these are fully supported and documented.
• The integration endpoint will continue to work for alert integrations, but the REST API is the best choice for future-proofing your setup.

If you’re building something new, go with the JSM Ops REST API. If you’re migrating an existing integration, the integration endpoint will continue to function.

Regards,
Aditya

[Tomi Sofowora]

Hi Aditya, 

Thank you for your swift response. That makes sense, much appreciated for the clarity.

I would like to confirm this for integrations, I use the "Default API" integration for generating alerts. I would imagine the integration API needs to continue to exist to support Integrations, therefore wouldn't /integration/v2/alert need to be supported post Opsgenie switch off? I would prefer to generate alerts based on integration rather than user.

Thanks,

Tomi