The maximum number of records to return.
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://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/
https://us-west.api.greenlake.hpe.com/
https://eu-central.api.greenlake.hpe.com/
https://ap-northeast.api.greenlake.hpe.com/
Request
Retrieve data for all OneView appliances.
URI PATH PREFIX RENAME
This API now supports the URI path prefix /compute-ops-mgmt
which used to be /compute-ops
. The /compute-ops
prefix is deprecated and might become unresponsive after Tuesday, April 1, 2025. The Guide provides more information about this change.
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 charecters !
#
$
&
'
(
)
*
+
,
/
:
;
=
?
@
[
]
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 |
Return resources where id == c650e411-3454-475d-a1af-7a31b21a1ce4
Return server where id == c650e411-3454-475d-a1af-7a31b21a1ce4
Return resources where applianceType is VM and state is connected
Return resources where applianceType is VM or UNKNOWN
The order in which to return the resources in the collection.
The value of the sort query parameter is a comma separated list of sort expressions. Each sort expression is a property name optionally followed by a direction indicator asc (ascending) or desc (descending).
The first sort expression in the list defines the primary sort order, the second defines the secondary sort order, and so on. If a direciton indicator is omitted the default direction is ascending.
Order resources ascending by name
Order resources ascending by name and then by descending by createdAt
Tenant-Acid header can be used by an MSP workspace to make API calls on behalf of their tenant by specifying the tenant's application customer ID.
In order to make such an API call, the Bearer token must belong to an MSP workspace and this header value must be the application customer ID of a tenant within the MSP workspace. Use the /compute-ops-mgmt/v1beta1/accounts
API to determine the application customer IDs for your tenant accounts.
- Mock server
https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v1beta1/oneview-appliances
- API endpoint for US West
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/oneview-appliances
- API endpoint for EU Central
https://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/oneview-appliances
- API endpoint for AP Northeast
https://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/oneview-appliances
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X GET \
https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v1beta1/oneview-appliances \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'
OK
Primary identifier for the appliance
Primary unique identifier for the appliance
Key to be used by customers to activate the appliance
Compliance state of the appliance
Time of appliance entry creation
Connectivity state of the appliance
{ "offset": 0, "count": 1, "total": 12, "items": [ { … } ] }
Request
Add a OneView appliance for management.
URI PATH PREFIX RENAME
This API now supports the URI path prefix /compute-ops-mgmt
which used to be /compute-ops
. The /compute-ops
prefix is deprecated and might become unresponsive after Tuesday, April 1, 2025. The Guide provides more information about this change.
Content-Type header must designate 'application/json' in order for the request to be performed.
Tenant-Acid header can be used by an MSP workspace to make API calls on behalf of their tenant by specifying the tenant's application customer ID.
In order to make such an API call, the Bearer token must belong to an MSP workspace and this header value must be the application customer ID of a tenant within the MSP workspace. Use the /compute-ops-mgmt/v1beta1/accounts
API to determine the application customer IDs for your tenant accounts.
- Mock server
https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v1beta1/oneview-appliances
- API endpoint for US West
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/oneview-appliances
- API endpoint for EU Central
https://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/oneview-appliances
- API endpoint for AP Northeast
https://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/oneview-appliances
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X POST \
https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v1beta1/oneview-appliances \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-d '{}'
Successful Response
Primary identifier for the appliance
Primary unique identifier for the appliance
Key to be used by customers to activate the appliance
{ "id": "87654321-f71a-43d2-8b93-4c7391b31234", "type": "compute-ops-mgmt/oneview-appliance", "ipaddress": "192.168.0.1", "device-id": "oneview+87654321-f71a-43d2-8b93-4c7391b31234", "activationKey": "ABCDEFGHOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJwY2lkIjoiNjg0YTVhMWEyOTU3MTFlZGE1MDF", "applicationCustomerId": "a14b2d8b-36e7-469a-bfe7-d76cdfe9c9e0", "complianceId": "8b8f9dca-99cf-4557-a604-978243dee321", "name": "ci-005056abcdef.com", "complianceLastChecked": "2019-08-24T14:15:22Z", "complianceState": "Compliant", "createdAt": "2023-03-01T10:50:33.736935+00:00", "generation": 1, "hostname": "ci-005056abcdef.com", "lastModified": "2019-08-24T14:15:22Z", "modelNumber": "HPE OneView VM - VMware vSphere", "platformCustomerId": "ed05a375-a042-4c8b-bb6b-1c36abd2238b", "productId": "oneview", "state": "connected", "templateId": "196100ac-4eec-4fb6-a7f7-86c8b584771d", "templateName": "Snmp_template", "updatedAt": "2023-03-01T11:05:00.554140+00:00", "version": "8.00.00" }
Request
Get a specific OneView appliance by id.
URI PATH PREFIX RENAME
This API now supports the URI path prefix /compute-ops-mgmt
which used to be /compute-ops
. The /compute-ops
prefix is deprecated and might become unresponsive after Tuesday, April 1, 2025. The Guide provides more information about this change.
Tenant-Acid header can be used by an MSP workspace to make API calls on behalf of their tenant by specifying the tenant's application customer ID.
In order to make such an API call, the Bearer token must belong to an MSP workspace and this header value must be the application customer ID of a tenant within the MSP workspace. Use the /compute-ops-mgmt/v1beta1/accounts
API to determine the application customer IDs for your tenant accounts.
- Mock server
https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v1beta1/oneview-appliances/{device-id}
- API endpoint for US West
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/oneview-appliances/{device-id}
- API endpoint for EU Central
https://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/oneview-appliances/{device-id}
- API endpoint for AP Northeast
https://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/oneview-appliances/{device-id}
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X GET \
'https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v1beta1/oneview-appliances/{device-id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'
Successful Response
Primary identifier for the appliance
Primary unique identifier for the appliance
Key to be used by customers to activate the appliance
{ "id": "87654321-f71a-43d2-8b93-4c7391b31234", "type": "compute-ops-mgmt/oneview-appliance", "ipaddress": "192.168.0.1", "device-id": "oneview+87654321-f71a-43d2-8b93-4c7391b31234", "activationKey": "ABCDEFGHOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJwY2lkIjoiNjg0YTVhMWEyOTU3MTFlZGE1MDF", "applicationCustomerId": "a14b2d8b-36e7-469a-bfe7-d76cdfe9c9e0", "complianceId": "8b8f9dca-99cf-4557-a604-978243dee321", "name": "ci-005056abcdef.com", "complianceLastChecked": "2019-08-24T14:15:22Z", "complianceState": "Compliant", "createdAt": "2023-03-01T10:50:33.736935+00:00", "generation": 1, "hostname": "ci-005056abcdef.com", "lastModified": "2019-08-24T14:15:22Z", "modelNumber": "HPE OneView VM - VMware vSphere", "platformCustomerId": "ed05a375-a042-4c8b-bb6b-1c36abd2238b", "productId": "oneview", "state": "connected", "templateId": "196100ac-4eec-4fb6-a7f7-86c8b584771d", "templateName": "Snmp_template", "updatedAt": "2023-03-01T11:05:00.554140+00:00", "version": "8.00.00" }
Request
Delete a specific OneView appliance by id.
URI PATH PREFIX RENAME
This API now supports the URI path prefix /compute-ops-mgmt
which used to be /compute-ops
. The /compute-ops
prefix is deprecated and might become unresponsive after Tuesday, April 1, 2025. The Guide provides more information about this change.
Tenant-Acid header can be used by an MSP workspace to make API calls on behalf of their tenant by specifying the tenant's application customer ID.
In order to make such an API call, the Bearer token must belong to an MSP workspace and this header value must be the application customer ID of a tenant within the MSP workspace. Use the /compute-ops-mgmt/v1beta1/accounts
API to determine the application customer IDs for your tenant accounts.
- Mock server
https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v1beta1/oneview-appliances/{device-id}
- API endpoint for US West
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/oneview-appliances/{device-id}
- API endpoint for EU Central
https://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/oneview-appliances/{device-id}
- API endpoint for AP Northeast
https://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/oneview-appliances/{device-id}
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X DELETE \
'https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v1beta1/oneview-appliances/{device-id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'