Content-Type header must designate 'application/json' in order for the request to be performed.
HPE Compute Ops Management API (latest)
HPE Compute Operations Management provides a Restful API to customers who want to manage their devices programmatically or through a command line. The API enables customers to invoke operations or tasks such as list devices, see device details, device health, and manage their device's firmware.
UPDATED API ENDPOINTS
Compute Ops Management now supports the HPE GreenLake API endpoints (<region>.api.greenlake.hpe.com). The Guide contains more information about this change.
https://us-west.api.greenlake.hpe.com/
https://eu-central.api.greenlake.hpe.com/
https://ap-northeast.api.greenlake.hpe.com/
https://developer.greenlake.hpe.com/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/
Target device to be onboarded using the activation key. The following target device types are supported: iLO and secure gateway appliances.
Expiration duration of the generated activation key. Default is set as 72 hours.
The secure gateway appliance URI is required for onboarding a server for management through a secure gateway.
Specifies the device subscription to be associated with the generated activation key. The subscription must have at least one available seat. Once the activation key is generated, the subscription will be automatically added to the HPE GreenLake workspace and linked to all servers onboarded using that key, regardless of the auto-subscribe configuration.
- API endpoint for US West
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/activation-keys
- API endpoint for EU Central
https://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/activation-keys
- API endpoint for AP Northeast
https://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/activation-keys
- Mock server
https://developer.greenlake.hpe.com/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v1beta1/activation-keys
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X POST \
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/activation-keys \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"targetDevice": "ILO"
}'{ "id": "5fae6c47-13f4-42f3-97b5-540f3d085791", "type": "compute-ops-mgmt/activation-key", "targetDevice": "ILO", "expiresAt": "2024-07-25T12:21:05.448576Z", "activationKey": "string", "subscriptionKey": "string", "applianceUri": "string", "applianceName": "string", "createdAt": "2024-07-25T10:21:05.475123Z", "updatedAt": "2024-07-25T10:21:05.475123Z", "generation": 1 }
Limit the resources operated on by an endpoint or when used with a multiple-GET endpoint, return only the subset of resources that match the filter. The filter grammar is a subset of OData 4.0.
NOTE: The filter query parameter must use URL encoding. Most clients do this automatically with inputs provided to them specifically as query parameters. Encoding must be done manually for any query parameters provided as part of the URL.
The reserved characters ! # $ & ' ( ) * + , / : ; = ? @ [ ] must be encoded with percent encoded equivalents. Server IDs contain a +, which must be encoded as %2B.
For example: the value P06760-B21+2M212504P8 must be encoded as P06760-B21%2B2M212504P8 when it is used in a query parameter.
| CLASS | EXAMPLES |
|---|---|
| Types | integer, decimal, timestamp, string, boolean, null |
| Operations | eq, ne, gt, ge, lt, le, in |
| Logic | and, or, not |
Activation-Keys can be filtered by:
- targetDevice
- activationKey
- applianceUri
- subscriptionKey
The following examples are not an exhaustive list of all possible filtering options.
Returns appliance firmware where a property equals a value. <property> eq <value>
Returns appliance firmware where a property equals a value. <property> eq <value>
Returns all the activation keys that are generated for the given target device. <property>%20eq%20<value>
Returns appliance firmware where a property does not equal a value. <property> ne <value>
Returns appliance firmware where multiple conditions are met. <property> eq <value> and <property> eq <value>
Returns all the activation keys that are generated for the given target device and meet multiple conditions. <property>%20eq%20<value>%20and%20<property>%20eq%20<value>
- API endpoint for US West
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/activation-keys
- API endpoint for EU Central
https://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/activation-keys
- API endpoint for AP Northeast
https://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/activation-keys
- Mock server
https://developer.greenlake.hpe.com/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v1beta1/activation-keys
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X GET \
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/activation-keys \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'Successful Response
Array of resources in the page of the collection.
Primary identifier of the activation key resource given by the system.
Time of activation key expiration.
Time of activation key creation.
Time of activation key updation.
{ "offset": 0, "count": 1, "total": 12, "items": [ { … } ] }
- API endpoint for US West
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/activation-keys/{activation_key}
- API endpoint for EU Central
https://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/activation-keys/{activation_key}
- API endpoint for AP Northeast
https://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/activation-keys/{activation_key}
- Mock server
https://developer.greenlake.hpe.com/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v1beta1/activation-keys/{activation_key}
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X DELETE \
'https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/activation-keys/{activation_key}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'