Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

OpsGenie API and OpsGenie UI don't agree

cstewart I'm New Here Jan 19, 2023

With regards to integrations, it has been noticed that the GET{integration id} does not reflect the same configuration that the OpsGenie UI does for the AzureServiceHealth integration.  In addition, the POST route does not create the requested AzureServiceHealth integration with the supplied values.  Specific fields that are not returned correctly by the GET call are the "Extra Properties".  Specific fields that are not correctly populated correctly by the POST call are "Extra Properties" and "Description"

1 answer

1 vote
Nick H Atlassian Team Jan 19, 2023

Hi @cstewart ,

I think the issue you might be facing could be due to your subscription. If you are subscribed to a Standard, Enterprise, JSM/O Premium or JSM/O Enterprise plan, an Advanced tab is offered within each integration. 

When running a GET on an integration under one of those plans, the body returned is of the simple settings of the integration, and not of the Advanced tab - which I believe is what you are referring to when stating "Specific fields that are not returned correctly by the GET call are the 'Extra Properties.' Specific fields that are not correctly populated correctly by the POST call are 'Extra Properties' and 'Description.'"

You would have to also run a GET on the integration's actions to return the reflected extra properties, description, etc. in each action. For example:




Lower tied plans offer some of these fields in the simple settings of an integration, but they do not offer the Advanced tab. So a GET on the integration for one of these plans would return something different - since the UI is also different:




Hope that makes sense, but let us know if you have any questions.

cstewart I'm New Here Jan 20, 2023

Hi @Nick H ,

Thanks for the speedy reply.  I performed the integration/action route and do see the "Extra Properties" and also the "Desciption" field values I expect.  Thank you for clearing that up for me.


Like Nick H likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events