HP OneView REST API Reference

licenses
licenses.html[10/17/2013 10:35:45 AM]
QBSV C9MA H9P9 8HU3 V7B5 HWWB Y9JL KMPL KCJD NG5Q UVUW
JH2E EUUT H42V ENQG 2VCB LK4U R4UR V886 VC9X MQT3 G3AD
LVKK 5LRG E2UX
GHA3"Order123 Product123 HP_Product_Desc EON123"
_35S4X-ZQTZM-KSJ0B-T6AJC-L2P3B
POST: https://{appl}/rest/licenses
Request body:
{
"key":
"#HP Product 123\nQBSV C9MA H9P9 8HU3 V7B5 HWWB Y9JL
KMPL KCJD NG5Q UVUW JH2E EUUT H42V ENQG 2VCB LK4U R4UR V886 VC9X MQT3
G3AD LVKK 5LRG E2UX GHA3\"Order123 Product123 HP_Product_Desc
EON123\"_35S4X-ZQTZM-KSJ0B-T6AJC-L2P3B"
,
"type":"License"
}
GET Gets list of all license resources that are known by the appliance.
Parameter Attributes Description
start Optional The 0-based index of the first resource to return (start=0 starts
with the first available resource). If the specified count does not
return all resources within the maximum allowed time (see count),
use the start parameter to view additional resource pages. The
default value for start is 0 (first available resource).
count Optional Optional parameter that specifies the number of resources to return
from each API invocation. The number of resources returned on
each call is referred to as a page. If you specify a count, the API
attempts to return the specified number of resources, however this
may be limited due to response time constraints and/or actual
number of resources available to return. The results include the total
number of resources that match the filter or query, the actual
count returned, and the URIs to go to the next page, previous page,
or both. If necessary, you can make several requests using the URI
for the next or previous page (or different start parameters) to get
the desired count.
query Experimental This parameter is experimental for this release: While generally
functional when used in simple cases, restrictions might be noted in
the implementation description.
If the query is supported, the following is the way it works. A general
query string that narrows the list of resources returned by a multi-
resource GET (read) request and DELETE (delete) request. The
default is no query (all resources are returned). One advantage
query has over filter is that it can have embedded ORs. A single
query parameter can do what would take multiple parameters or
multiple GET requests using filter. Use query for more complex
queries.
filter Experimental Currently supported filters are: product, licenseType,nodeId and
additionalKeys.
Request
Header
Attributes Description
REST API Request Headers NOTE: The X-API-Version header is required for all APIs. For the