GET /system/licenses/{licenseID}/features
This will contain all the features of a specific license.
Used when you are operating a browser without access to the header parameter. This allows you to choose which encoding you want to use for the response:
All these resources can be used according what the resource allows.
To address the raw value of a primitive property, clients append a path segment containing the string $value to the property URL.
To use this query option you need to use the classic resource and add the element name you want to print followed by the query string name.
<span class="warning"><span class="glyphicon glyphicon-warning-sign" aria-hidden="true"> Be careful, the parameter query string is used in the URL and is not like other parameters.
The $select system query option allows clients to request a limited set of properties for each entity.
The value pass in the parameter can be:
If there is no value after the select query option, the parameter will be ignored. All the values that are not specified will not be printed in the response.
The $expand system query option specifies the related resources to be included in line with retrieved resources.
The value passed in the parameter can be:
The $expand system query option can be used with the $levels query option, to expand recursively.
If this parameter is not in the request, the Application/Json will be chosen by default.
There are multiple possible values (according the resource):
The first two are the most often used.
This is the id of the file.
Object Name: Features
Property Name | Type | Description | Method |
---|---|---|---|
Features | Array<Feature> | This is an array of Feature. It contains all the the feature that the license allow. |
GET |
URL Example: https://0.0.0.0/api/rest/v1/system/licenses/1/features
[
{
"href": "/api/rest/v1/system/licenses/1/features/bleGatewayEngineering",
"name": "bleGatewayEngineering"
},
{
"href": "/api/rest/v1/system/licenses/1/features/envysion",
"name": "envysion"
},
{
"href": "/api/rest/v1/system/licenses/1/features/bleGateway",
"name": "bleGateway"
},
{
"href": "/api/rest/v1/system/licenses/1/features/email",
"name": "email"
},
{
"href": "/api/rest/v1/system/licenses/1/features/hardwareIO",
"name": "hardwareIO"
},
{
"href": "/api/rest/v1/system/licenses/1/features/mstp",
"name": "mstp"
}
]
URL Example: https://0.0.0.0/api/rest/v1/system/licenses/1/features
<?xml version="1.0" encoding="utf-8"?>
<Features>
<Feature>
<Href>/api/rest/v1/system/licenses/1/features/bleGatewayEngineering</Href>
<Name>bleGatewayEngineering</Name>
</Feature>
<Feature>
<Href>/api/rest/v1/system/licenses/1/features/envysion</Href>
<Name>envysion</Name>
</Feature>
<Feature>
<Href>/api/rest/v1/system/licenses/1/features/bleGateway</Href>
<Name>bleGateway</Name>
</Feature>
<Feature>
<Href>/api/rest/v1/system/licenses/1/features/email</Href>
<Name>email</Name>
</Feature>
<Feature>
<Href>/api/rest/v1/system/licenses/1/features/hardwareIO</Href>
<Name>hardwareIO</Name>
</Feature>
<Feature>
<Href>/api/rest/v1/system/licenses/1/features/mstp</Href>
<Name>mstp</Name>
</Feature>
</Features>