This is an archive version of the document. To get the most up-to-date information, see the current version.

Authorization and Security

In this article

To start working with Veeam Availability Console RESTful API, clients must first authenticate themselves. Veeam Availability Console RESTful API authorization process is based on the OAuth 2.0 Authorization Framework and involves obtaining an access token and a refresh token.

Access token is a string that represents authorization issued to the client and must be used in all requests during the current logon session. Access token expires after 1 hour.
Refresh token is a string that represents authorization granted to the client and can be used to obtain a new access token when the current access token expires.

Veeam Availability Console RESTful API authorization process involves the following procedures:

Requesting authorization
Using refresh token
Performing logout

Requesting Authorization

To obtain a pair of tokens, the client sends the POST HTTPS request to the Veeam Availability Console token path. The request body must contain credentials of a user with the Veeam Availability Console Portal Administrator privileges.

Authorization and Security Note:

Simultaneous sessions initiated in different client applications under the same user credentials may interfere with each other. To avoid unexpected logout, use a different user account for every application.

A successfully completed operation returns the 200 Success response code and an access and a refresh token in the response body. The client inserts the access token in headers of further requests to Veeam Availability Console RESTful API. The refresh token must be saved locally.

Authorization and Security Tip:

To learn how to authorize your access using a client application, you can review the Example Requests and Responses section. Alternatively, you can use Swagger UI.

Using Refresh Token

To obtain a new pair of tokens in case the access token expires or becomes invalid, the client sends the POST HTTPS request with the refresh token in the request body to the Veeam Availability Console RESTful API token path. A successfully completed operation returns the 200 Success response code and a new pair of tokens in the response body.

Performing Logout

When the client finishes working with Veeam Availability Console RESTful API, he logs out by sending the POST HTTPS request to the v2/accounts/logout path. A successfully completed operation returns the 200 Success response code and the “Logout successful” message in the response body.

Example Requests and Responses

The following example illustrates how the client and server communicate using requests and responses.

To obtain an access and a refresh token, the client sends the POST request to the /token path.

In the body of the request, the client specifies the following parameters:

grant_type — the authorization process requires that the password value must be specified for this parameter.

username and password — credentials used to access the server; in this example, vac\administrator and Password1 are used.

Request:

POST https://localhost:1281/token

Request Header:

Content-Type: application/json

Authorization: Bearer

Request Body:

grant_type=password&username=vac\administrator&password=Password1

The server sends a response in the following format.

Response Code:

200 Success

Response Body:

{

"access_token": "908qldKH7ZZRfCqeWBNVVbnIM5UxisItP6gSnU_pZ5-qDenA5I2T0XvynyoELoEFmUUzm17_WuodIl1yRnneI15UzsgFnxlsHdhH9KQKFWKrR08PKRh-wL_NXj8PirXUa4PjK3Dx1pE-qCJh23FrrljIjsNjWeDFd63yY4j8ldyqP7fdx6bmp-hWwergK7va89AKEuYzIr_IQNir2yZMgVnXR-FqyEVw_xf_e3sFGJw",

"token_type": "bearer",

"expires_in": 3599,

"refresh_token": "EVU7FlFLT2emhwfwnbwM-RiuD0oHjCIGTGeAvT7xOk_IZeTrwDLiPMEJIvqqd6rb-t0SbUnaxUL3Hq_ZZ1tEFnZ3K8W0JFuJFKjoil8RO4TgyfVfZCrAxHkNI03NJ6miVcEAxkAyZN7Zkleu1jnZg5hT05KsZSGSgaBkAqsn49heMz3qkMTUaxZIi7
J4Uam-nPbgEd04bmrUfOhOmckjMPmUYZ_QhrPFR2NpiGxmzuQ"

}

To refresh a pair of tokens, the client sends the POST request to the /token path.

In the body of the request, the client specifies the following values for the parameters:

grant_type — to refresh the token, it is required that the refresh_token value must be specified for this parameter.

refresh_token — the previously saved refresh token.

Request:

POST https://localhost:1281/token

Request Header:

Content-Type: application/json

Authorization: Bearer

Request Body:

grant_type=refresh_token&refresh_token=EVU7FlFLT2emhwfwnbwM-RiuD0oHjCIGTGeAvT7xOk_IZeTrwDLiPMEJIvqqd6rb-t0SbUnaxUL3Hq_ZZ1tEFnZ3K8W0JFuJFKjoil8RO4TgyfVfZCrAxHkNI03NJ6miVcEAxkAyZN7Zkleu1jnZg5hT05KsZSGSgaBkAqsn49heMz3qkMTUaxZIi7
J4Uam-nPbgEd04bmrUfOhOmckjMPmUYZ_QhrPFR2NpiGxmzuQ

To log out, the client sends the POST request to the v2/accounts/logout path.

In the Authorization header, the client specifies currently valid access token in the Bearer <access_token> format.

Request:

POST https://localhost:1281/v2/accounts/logout

Request Header:

Content-Type: application/json

Authorization: Bearer 908qldKH7ZZRfCqeWBNVVbnIM5UxisItP6gSnU_pZ5-qDenA5I2T0XvynyoELoEFmUUzm17_WuodIl1yRnneI15UzsgFnxlsHdhH9KQKFWKrR08PKRh-wL_NXj8PirXUa4PjK3Dx1pE-qCJh23FrrljIjsNjWeDFd63yY4j8ldyqP7fdx6bmp-hWwergK7va89AKEuYzIr_IQNir2yZMgVnXR-FqyEVw_xf_e3sFGJw

The server sends a response in the following format.

Response body

{

"message": "Logout successful"

}