REST API version removal not mentioned in changelog

[Rune_Philip]

Just wanted to share something we ran into when upgrading from 8.2 to 8.4 that caught us off guard.

As most of you probably know, VBM365 normally supports the current API version plus two versions back. On 8.2 envoirment we had both v6 and v7 available no problem. After upgrading to 8.4 we noticed v6 was completely gone and only v7 and v8 are available now.

There is zero mention of this in the changelog or KB4843. We only found out after the upgrade broke some of our integrations. When we raised it with Veeam support they confirmed it was intentional and pointed us to the REST API reference documentation. Where it is listed under the Versioning and Deprecated Resources sections.

https://helpcenter.veeam.com/references ... Versioning
https://helpcenter.veeam.com/references ... -Resources

Who checks the API reference for changelog information?
Support suggested posting here so the product team can see it so here i am. Would be really nice if API version removals were explicitly called out in the release notes or changelog going forward, especially for those of us running custom integrations on older endpoints.

Anyone else run into this? And does anyone know if v7 is at risk of being dropped in the next release?

[Polina]

Hi Rune,

Kindly, check out this post: post569983.html#p569983.

In future, I'll make sure that such changes are mentioned in all potentially applicable sections of the user guide.

Thanks!