Get Veeam Backup & Replication License Usage

You can get a representation of Veeam Backup & Replication license usage information by a specific tenant.


To get a representation of license units used to protect tenant workloads, send the GET HTTPS request to the URL of the /tenants/{instanceUid}/licensing/backupServerUsage/byVCCTenantUid resource.

HTTP Request

GET https://<hostname>:1281/v2/tenants/{instanceUid}/licensing/backupServerUsage/byVCCTenantUid

Request Headers

The request header must contain the authorization token for the current logon session.


The server returns the following response to the client.

Response Code

A successfully completed operation returns response code 200 Success.

Response Headers

The response to this request contains the following headers. The response may also include additional standard HTTP headers.




The length of the response body.


The media type and syntax of the request body message: application/json; charset=utf-8

Response Body

In the response body, Veeam Service Provider Console returns a representation of the /tenants/{instanceUid}/licensing/backupServerUsage/byVCCTenantUid resource.

Example Get Veeam Backup & Replication License Usage

The following request returns information about Veeam Backup & Replication license units used by a tenant with UID 19b5fbc6-b0ac-4bc7-b989-021c6f5effbc.


GET https://localhost:1281/v2/tenants/19b5fbc6-b0ac-4bc7-b989-021c6f5effbc/licensing/backupServerUsage/byVCCTenantUid


Request Header:

Authorization: Bearer <Access-Token>


Response Code:

200 Success


Response Body:



   "type": "VBR_vSphere_VM",

   "unitType": "Instances"

   "rentalUnits": 100,

   "newUnits": 20,

   "usedUnits": 0,

   "rentalCount": 100,

   "newCount": 20,

   "usedCount": 0



   "type": "VBR_HyperV_VM",

   "unitType": "Instances"

   "rentalUnits": 50,

   "newUnits": 4,

   "usedUnits": 0,

   "rentalCount": 50,

   "newCount": 4,

   "usedCount": 0



I want to report a typo

There is a misspelling right here:


I want to let the Veeam Documentation Team know about that.