API Versions and Parsing

Periodically, Flexera will make changes to the existing APIs. All of the latest changes will be made available on the path:

~/api/ 

If you don’t want to risk any breaking changes affecting your scripts, Flexera recommends that you hardcode the API version in the coded requests, for example, all requests to go to:

~api/v1/ 

To avoid any breaking changes introduced to the API, Flexera will offer all future changes as a new version (v2, v3, v4 and so on), while keeping the old functionality working for at least one year from the moment a new version is released.

As a rule of thumb, Flexera will NOT change the API version for small fixes where more data is added to existing calls, and it is strongly recommend that you code your JSON parsing in such way that it doesn’t expect exactly the same tags in the same order and at the same number of characters from key/tag X; use a good parsing library instead that offers dictionaries/lists for data querying.

Flexera strongly discourages any usage of pseudo-code similar to foo=j.substring(j.indexof(“Foo:”), 5) or any similar variations of non-true JSON parsing (such as crude guess-reads) as these are error prone and will likely fail in the future.

The same recommendation applies for XML Feeds, where XML parsing is recommended as opposed to string matching over the full document (for example using regexes or any guess patterns).

Important:Flexera accepts no responsibility for any breaking changes introduced by using bad coding practices over the scripts you write.