Opsgenie API
api.opsgenie.com removal
Stops workingSubscribe to Opsgenie APIShare
On April 5, 2027, Opsgenie will be shut down and will no longer be accessible. Any calls directed to api.opsgenie.com will fail after that day. Existing customers can continue to use the product without interruption until the shutdown date.
What to use instead of these calls
Move to Jira Service Management and use its Operations REST API for alerts, schedules, and on-call. Because this replacement is a separate product and subscription, moving requires a team decision and involves more than changing an identifier.
Opsgenie's replacement is Jira Service Management, a different product and subscription: moving there is a team decision.
In Opsgenie API's words
Existing customers will be able to continue to use Opsgenie without interruption until April 5th, 2027. At that point, Opsgenie will be shut down, and the product will no longer be accessible
Facts
- API
- Opsgenie API
api.opsgenie.com - Kind
- Removal
- Takes effect
- April 5, 2027
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Opsgenie API's own pages
Questions
When does this change take effect?
Calls to api.opsgenie.com stop working on April 5, 2027.
What happens to calls after April 5, 2027?
They fail from that day.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix before April 5, 2027.