API keys changed?

[MrWoodward]

Hey guys,
We just upgraded our Nagios dev box to 5.5.5 and now all of our scripts which use the API are now broken. Thankfully we haven't upgraded our production box yet.

Did the API change? We're still using v1 API, so there shouldn't be any breaking changes, right?

[benjaminsmith]

HI @Mr.Woodward,

In the minor release 5.5.0, there were a large number of updates including changes to the API. The help documentation has also been updated to reflect those changes, and more information is available on the changelog.

Let me know if I can help answer any specific questions as it relates to the API changes.

[MrWoodward]

Any reason why the API version wasn't updated when breaking changes to the API were made? This is pretty standard operating procedure for something like this, right?

This is a bit frustrating for us because we have to refactor our code base first before we can update to 5.5.x

To make our life easier, is there a full list of all the things that were changed to the API between 5.4.x and 5.5.x?

[benjaminsmith]

@MrWoodward,

We migrated from a third party JSON libary to using the standard PHP library, there is a full list of the changes on our website, please review the the API section at:
https://www.nagios.com/nagios-xi-5-5/#all-changes

The impacting change is that objects API calls will no longer return with <object>list root. JSON is now valid and using the json_encode() function built into PHP instead of a 3rd party library, allowing for better PHP version compatibility in PHP 7+.

Sorry about the frustration, we do our best to ensure maintenance release do not have breaking changes, and provide 3 licenses with Nagios XI with every purchase: one for production, one for testing, and one for high availability to aid upgrading major and minor releases.