OpsGenie does not support OAuth and API Tokens get automatically deactivated | The place for Zendesk users to come together and share
Skip to main content
M
Marios Andreopoulos
July 27, 2026
Question

OpsGenie does not support OAuth and API Tokens get automatically deactivated

  • July 27, 2026
  • 4 replies
  • 53 views

Hello all,

Three days ago I got an email that tomorrow our API tokens will get deactivated because they weren’t used recently.

Our OpsGenie token hasn’t been recently used, because thankfully we didn’t have a customer incident in the last few months.

Unfortunately there isn’t a clear way to force keep an API token activated. So tomorrow, our OpsGenie integration stops working unless we keep rotating our API tokens? Is there any other way to do it?

This is one of the most critical systems for us. Not responding to a ticket within an SLA means we breach our contractual obligations. And all these happen with just 4 days of notice in advance!

Thank you for any help you migh be able to provide regarding this.

    4 replies

    Sakar
    Sakar
    Newcomer
    July 28, 2026

    Since the official integration only accepts Zendesk API Key I think creating a system that will periodically Authenticate with Zendesk and rotate keys and post it through the opsginie integration api  https://docs.opsgenie.com/docs/integration-api seems to be only option for now.

    It is better to take this to OpsGinie since it seems to be their part to change the system to adapt to new oAuth flow of Zendesk

    Sakar
    saaspal.us

     

    S
    sophia brown
    July 28, 2026

    Since OpsGenie does not support OAuth and API tokens are automatically deactivated, integrating with external applications can be more challenging. Using a secure token management process and regularly updating credentials is essential to maintain reliable integrations.

      T
      tomme
      July 28, 2026


      That does seem concerning, especially for an integration that's only meant to be used during incidents. An API token for a critical service like OpsGenie shouldn't become unusable simply because everything has been running smoothly.

      If there's no option to exempt specific tokens or mark them as permanent, I'd recommend raising this directly with support and asking whether there's a way to keep tokens active for production integrations. As a temporary workaround, some teams schedule a lightweight API call at regular intervals to keep the token "active, but it would be much better if there were an official solution for critical integrations.

      Hopefully the team can clarify whether this is expected behavior or if there's a better long-term approach.

      C
      Christopher53Employee
      Employee
      July 29, 2026

      Hi Marios,

      There isn’t a way to exempt inactive tokens from deactivation.  But as Tomme mentioned, a good workaround would be to schedule a task to send a request authenticated by that token to prevent inactivity.  For overall ecosystem stability, we’ve been working with integrators in our Marketplace ahead of later phases of the API Token removal process to update the integrations and avoid disruption.  Atlassian is in the process of sunsetting OpsGenie.  So that workaround should be effective until your eventual migration.

      Terms & ConditionsAccessibility statement