Veeam Backup & Replication 13
REST API Reference
Related documents

Cloud Browser

The Cloud Browser section defines paths and operations for retrieving information about cloud resources (compute or storage). Cloud browser helps you map a cloud folder with an object storage repository.

Get Cloud Hierarchy

The HTTP POST request to the /api/v1/cloudBrowser path allows you to browse cloud resources (compute or storage) available for the specified storage account.

Available to: Veeam Backup Administrator.

SecurityBearer
Request
query Parameters
resetCache
boolean

If true, the cache will be reset for this request. Resetting the cache slows down request processing but it allows you to get up-to-date data.

header Parameters
x-api-version
required
string
Default: 1.1-rev2

Version and revision of the client REST API. Must be in the following format: <version>-<revision>.

Request Body schema: application/json
credentialsId
required
string <uuid>

ID of the object storage account (for browsing either storage or compute infrastructure).

serviceType
required
string (ECloudServiceType)

Type of cloud service.

regionType
string (EAzureRegionType)

Region where your Microsoft Azure container is located.

Enum: "China" "Germany" "Global" "Government"
folderType
string (ECloudBrowserFolderType)

Folder type.

Enum: "backup" "archive"
gatewayServerId
string <uuid>

ID of a gateway server you want to use to connect to the object storage. Specify this parameter to check internet connection of the server. As a gateway server you can use the backup server or any Microsoft Windows or Linux server added to your backup infrastructure. By default, the backup server ID is used.

Responses
200

OK

400

Bad request. This error is related to POST/PUT requests. The request body is malformed, incomplete or otherwise invalid.

401

Unauthorized. The authorization header has been expected but not found (or found but is expired).

403

Forbidden. The user sending the request does not have adequate privileges to access one or more objects specified in the request.

500

Internal server error. The request has been received but could not be completed because of an internal error at the server side.

post/api/v1/cloudBrowser
Request samples
application/json
{
  • "credentialsId": "08e8bcd2-3d30-4d03-8e1a-ab6ac0cbf1ed",
  • "serviceType": "AzureBlob",
  • "regionType": "China",
  • "folderType": "backup",
  • "gatewayServerId": "39c247aa-48c5-4705-90e0-b578a615649d"
}
Response samples
application/json
{
  • "credentialsId": "08e8bcd2-3d30-4d03-8e1a-ab6ac0cbf1ed",
  • "serviceType": "AzureBlob",
  • "hostId": "70e3fb2d-1cb6-4dbc-ab8d-fa7209aca5dd",
  • "regionType": "China",
  • "containers": [
    ]
}

New Folder

The HTTP POST request to the /api/v1/cloudBrowser/newFolder path allows you to create a new folder in the cloud infrastructure.

Available to: Veeam Backup Administrator.

NOTE
The REST API does not create new containers, you can create a folder in an existing container only.

SecurityBearer
Request
header Parameters
x-api-version
required
string
Default: 1.1-rev2

Version and revision of the client REST API. Must be in the following format: <version>-<revision>.

Request Body schema: application/json
credentialsId
required
string <uuid>

ID of a cloud credentials record required to connect to the object storage.

serviceType
required
string (ECloudServiceType)

Type of cloud service.

newFolderName
required
string

Name of the new folder.

regionType
required
string (EAzureRegionType)

Region where your Microsoft Azure container is located.

Enum: "China" "Germany" "Global" "Government"
containerName
required
string

Name of the container where you want to store your backup data.

hostId
string <uuid>

ID of a server you want to use to connect to the object storage. You can use the backup server or any Microsoft Windows or Linux server added to your backup infrastructure. By default, the backup server ID is used.

folderType
string (ECloudBrowserFolderType)

Folder type.

Enum: "backup" "archive"
Responses
201

Cloud folder has been created.

400

Bad request. This error is related to POST/PUT requests. The request body is malformed, incomplete or otherwise invalid.

401

Unauthorized. The authorization header has been expected but not found (or found but is expired).

403

Forbidden. The user sending the request does not have adequate privileges to access one or more objects specified in the request.

500

Internal server error. The request has been received but could not be completed because of an internal error at the server side.

post/api/v1/cloudBrowser/newFolder
Request samples
application/json
{
  • "credentialsId": "08e8bcd2-3d30-4d03-8e1a-ab6ac0cbf1ed",
  • "serviceType": "AzureBlob",
  • "newFolderName": "string",
  • "hostId": "70e3fb2d-1cb6-4dbc-ab8d-fa7209aca5dd",
  • "regionType": "China",
  • "containerName": "string",
  • "folderType": "backup"
}
Response samples
application/json
{ }