Info |
---|
This page refers to End-user REST API version 1 only. See End-user REST API for links to other versions of the End-user REST API. |
...
To activate a license for a given, unique combination of the an activation key and a HostID using the End-user REST API version 1, use the following request:
Panel |
---|
...
|
...
where request parameters are:
- activation_key (string) (Your product is your license order activation key),
and
- hostids (base64string) are encoded hostids.Base64 encoded values. The format of HostID(s) that you can specify is a comma-separated list of types and values; for example, ETHERNET=AABBCCDDEEFF,IPADDRESS=192.168.0.5
(Note that request headers are used by default.)
Example request
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
PUT /rest/v1/liceneslicenses/4CT1V-4T10N-K3Y1S-C000L/dHlwZTE9dmFsdwUxLHR5cGUyPXZhbHVlPTIdHlwZTE9dmFsdWUxLHR5cGUyPXZhbHVlPTI= |
Response
The LAC REST API returns standard HTTP response codes as described in the following table.
Status Code | Header Field | Description |
---|---|---|
202 Accepted |
New license request has been created after successful license validation. The Location header field contains an absolute URI for automatic redirection to this resource. |
Requested activation key is invalid or the format of a |
hostid is wrong. |
Response body contains more |
detailed information about this error.
|
403 Forbidden |
License cannot be activated |
, because it is not in sync with the internal configuration. |
Response message contains more information. |
Example responseresponses
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
HTTP/1.1 202 Accepted |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
HTTP/1.1 400 Bad Request
Content-Type: application/hal+json
{
"message": "Invalid HostID format provided."
} |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
HTTP/1.1 403 Forbidden
Content-Type: application/hal+json
{
"message": "License generator was not uploaded for this product."
} |
For more information about HTTP methods, see Supported HTTP methods.