VBR REST API roadmap?

[spiritie]

Hi Veeam

We are an MSP that manage a lot of VBR servers. We utilize a few different tools which utilize PowerShell to manage our VBR servers.

We would really like to go down the road of the Linux as we've already gone down this road with almost all of our IT infrastructure, but the REST API seems to still be lacking quite a bit behind compared to what your PowerShell offers.

Do you have any roadmap for your REST API to be more complete? This is kinda what is currently holding us back from being able to migrate to your Linux Appliance in the near future.

Also a different question. Why do you not have a "true" read-only permission for your REST API for all GET commands? We are currently forced to configure our service account to be "Veeam Backup Administrator" just because we want to pull the Veeam license + Encryption keys for monitoring by our monitoring platform (These are only GET commands). This is a huge unnecessary risk we have to deal with.

Regards.

[Mildur]

Hi Gert,

Our goal is to achieve feature parity between the UI, PowerShell, and REST API.
The good news for our customers and service providers is that with our new Web UI introduced in v13, adding functionality to the REST API should progress faster with minor and major releases, since the Web UI itself relies on those REST API capabilities.
What kind of API endpoints are you currently missing?

This is kinda what is currently holding us back from being able to migrate to your Linux Appliance in the near future.

PowerShell is supported as well when you use our Linux Appliance as Backup Server. No need to wait for Rest API endpoints if you have a script already for PowerShell.

Also a different question. Why do you not have a "true" read-only permission for your REST API for all GET commands? We are currently forced to configure our service account to be "Veeam Backup Administrator" just because we want to pull the Veeam license + Encryption keys for monitoring by our monitoring platform (These are only GET commands). This is a huge unnecessary risk we have to deal with.

Regarding the “why” for read‑only requests — it simply hasn’t been implemented yet. I’ll add your vote to the feature request.

Best,
Fabian

[spiritie]

Hi Mildur

Thanks for your response, I did not know PowerShell calls were supported to the appliance, that is great news

Regarding the Rest API, we're missing our on Cloud Connect specific calls. We monitor the Cloud Connect certificate to make sure it matches the name of our CCGW (Veeam sometimes replaces this on upgrades, just happened on our latest v13 update), we also monitor the expiration date.