Veeam Backup & Replication 13
REST API Reference
Related documents

Proxies

The Proxies section defines paths and operations for managing backup proxies.

NOTE
In the current version, the REST API supports VMware backup proxies only.

Get All Proxies

The HTTP GET request to the /api/v1/backupInfrastructure/proxies path allows you to get an array of all backup proxies that are added to the backup infrastructure.

SecurityBearer
Request
query Parameters
skip
integer <int32>

Number of proxies to skip.

limit
integer <int32>

Maximum number of proxies to return.

orderColumn
string (EProxiesFiltersOrderColumn)

Sorts proxies by one of the proxy parameters.

Enum: "Name" "Type" "Description"
orderAsc
boolean

Sorts proxies in the ascending order by the orderColumn parameter.

nameFilter
string

Filters proxies by the nameFilter pattern. The pattern can match any proxy parameter. To substitute one or more characters, use the asterisk (*) character at the beginning, at the end or both.

typeFilter
string (EProxyType)

Filters proxies by proxy type.

Value: "ViProxy"
hostIdFilter
string <uuid>

Filters proxies by ID of the backup server.

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

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

Responses
200

OK

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.

get/api/v1/backupInfrastructure/proxies
Request samples 
Response samples 
application/json
{
  • "data": [
    ],
  • "pagination": {
    }
}
Add Proxy
The HTTP POST request to the /api/v1/backupInfrastructure/proxies path allows you to add a proxy to the backup infrastructure.


SecurityBearer 
Request 
header Parameters
x-api-version
required
string
 Default:  1.1-rev0
Version and revision of the client REST API. Must be in the following format: <version>-<revision>.


 
Request Body schema: application/json
required
description
required
string
Description of the backup proxy.


 
type
required
string (EProxyType) 
Type of the backup proxy.


 
required
object (ProxyServerSettingsModel) 
Server settings for the backup proxy.


 
Responses 
201
Infrastructure session has been created to add the proxy. To check the progress, track the session state.


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/backupInfrastructure/proxies
Request samples 
application/json
{
  • "type": "ViProxy",
  • "name": "proxy01.tech.local",
  • "description": "Created by TECH\\sheila.d.cory",
  • "server": {
    }
}
Response samples 
application/json
{
  • "sessionType": "Infrastructure",
  • "state": "Working",
  • "id": "59f85a1e-2016-4d08-aea5-2676a03d548c",
  • "name": "Infrastructure Item Saving",
  • "activityId": "59f85a1e-2016-4d08-aea5-2676a03d548c",
  • "creationTime": "2022-01-28T19:48:43.117+01:00",
  • "endTime": null,
  • "progressPercent": 0,
  • "result": null,
  • "resourceId": null,
  • "resourceReference": null,
  • "parentSessionId": null,
  • "usn": 0
}
Get Proxy
The HTTP GET request to the /api/v1/backupInfrastructure/proxies/{id} path allows you to get a backup proxy that has the specified id.


SecurityBearer 
Request 
path Parameters
id
required
string <uuid> 
ID of the backup proxy.


 
header Parameters
x-api-version
required
string
 Default:  1.1-rev0
Version and revision of the client REST API. Must be in the following format: <version>-<revision>.


 
Responses 
200
OK


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.


404
Not found. No object was found with the path parameter 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.


get/api/v1/backupInfrastructure/proxies/{id}
Request samples 
Response samples 
application/json
{
  • "server": {
    },
  • "type": "ViProxy",
  • "id": "18b661c1-d9dc-4233-90a0-7e7b10dc2d09",
  • "name": "VMware Backup Proxy",
  • "description": "Created by Veeam Backup & Replication"
}
Edit Proxy
The HTTP PUT request to the /api/v1/backupInfrastructure/proxies/{id} path allows you to edit a backup proxy that has the specified id.


SecurityBearer 
Request 
path Parameters
id
required
string <uuid> 
ID of the backup proxy.


 
header Parameters
x-api-version
required
string
 Default:  1.1-rev0
Version and revision of the client REST API. Must be in the following format: <version>-<revision>.


 
Request Body schema: application/json
required
id
required
string <uuid> 
ID of the backup proxy.


 
description
required
string
Description of the backup proxy.


 
name
required
string
Name of the backup proxy.


 
type
required
string (EProxyType) 
Type of the backup proxy.


 
required
object (ProxyServerSettingsModel) 
Server settings for the backup proxy.


 
Responses 
201
Infrastructure session has been created to edit the proxy. To check the progress, track the session state.


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.


404
Not found. No object was found with the path parameter 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.


put/api/v1/backupInfrastructure/proxies/{id}
Request samples 
application/json
{
  • "server": {
    },
  • "trafficRules": {
    },
  • "type": "ViProxy",
  • "id": "18b661c1-d9dc-4233-90a0-7e7b10dc2d09",
  • "name": "VMware Backup Proxy",
  • "description": "Created by Veeam Backup & Replication"
}
Response samples 
application/json
{
  • "sessionType": "Infrastructure",
  • "state": "Working",
  • "id": "e81a72de-9b0a-4f4a-a451-0d0ece4c54b2",
  • "name": "Infrastructure Item Saving",
  • "activityId": "e81a72de-9b0a-4f4a-a451-0d0ece4c54b2",
  • "creationTime": "2022-01-28T20:18:47.563+01:00",
  • "endTime": null,
  • "progressPercent": 0,
  • "result": null,
  • "resourceId": null,
  • "resourceReference": null,
  • "parentSessionId": null,
  • "usn": 0
}
Remove Proxy
The HTTP DELETE request to the /api/v1/backupInfrastructure/proxies/{id} path allows you to remove a backup proxy that has the specified id from the backup infrastructure.


SecurityBearer 
Request 
path Parameters
id
required
string <uuid> 
ID of the backup proxy.


 
header Parameters
x-api-version
required
string
 Default:  1.1-rev0
Version and revision of the client REST API. Must be in the following format: <version>-<revision>.


 
Responses 
204
Removed.


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.


404
Not found. No object was found with the path parameter 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.


delete/api/v1/backupInfrastructure/proxies/{id}
Request samples 
Response samples 
application/json
{ }