Skip to content

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.

Download OpenAPI description
index.json
index.yaml
Overview
License

HPE End User License Agreement

Languages
Servers
API endpoint for US West

https://us-west.api.greenlake.hpe.com/

API endpoint for EU Central

https://eu-central.api.greenlake.hpe.com/

API endpoint for AP Northeast

https://ap-northeast.api.greenlake.hpe.com/

Mock server

https://developer.greenlake.hpe.com/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/

accounts - v1beta1

Operations

activation-keys - v1beta1

Operations

activation-tokens - v1beta1

Operations

activities - v1beta2

Operations

ahs-files - v1beta1

Operations

secure-gateway-appliances - v1beta2

Operations

List all secure gateway appliances

Request

Retrieve data for all secure gateway appliances.

Security
Bearer
Query
limitinteger[ 0 .. 1000 ]

The maximum number of records to return.

Example: limit=10
filterstring

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.

CLASSEXAMPLES
Typesinteger, decimal, timestamp, string, boolean, null
Operationseq, ne, gt, ge, lt, le, in
Logicand, or, not
Examples:

Return resources where id == c650e411-3454-475d-a1af-7a31b21a1ce4

filter=eq(id,'c650e411-3454-475d-a1af-7a31b21a1ce4')

Return server where id == c650e411-3454-475d-a1af-7a31b21a1ce4

filter=eq(id,%27c650e411-3454-475d-a1af-7a31b21a1ce4%27)

Return resources where applianceType is VM and state is connected

filter=and(eq(applianceType,'VM'),eq(state,'connected'))

Return resources where applianceType is VM or UNKNOWN

filter=in(applianceType,'VM','UNKNOWN')
sortstring

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.

Examples:

Order resources ascending by name

sort=name asc

Order resources ascending by name and then by descending by createdAt

sort=name,createdAt desc
Headers
Tenant-Acidstring(uuid)

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.

curl -i -X GET \
  https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta2/appliances \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>'

Responses

OK

Bodyapplication/json
countinteger>= 0required

Number of items returned

Example: 1
offsetinteger>= 0required

Zero-based resource offset

itemsArray of objects(appliance-v1beta2)required
items[].​idstring(uuid)required

Primary identifier for the appliance

Example: "3abc1b2c-4a5d-4e6f-9c7b-2a1d8e7f6abc"
items[].​typestringrequired

Type of resource

Value "compute-ops-mgmt/appliance"
items[].​ipAddressstring(ipv4)

IP address of the appliance

items[].​deviceIdstring

Primary unique identifier for the appliance

Example: "gateway+3abc1b2c-4a5d-4e6f-9c7b-2a1d8e7f6abc"
items[].​namestring

Name of the appliance

Example: "secure-gateway-appliance-01.net"
items[].​createdAtstring

Time of appliance entry creation

Example: "2025-03-01T10:50:33.736935+00:00"
items[].​generationinteger

Monotonically increasing update counter

Example: 2450
items[].​hostnamestring

Host name of the appliance

Example: "secure-gateway-appliance-01.net"
items[].​modelNumberstring

Model of the appliance

Example: "HPE Compute Ops Management secure gateway"
items[].​productIdstring

Product identifier for the appliance

Example: "gateway"
items[].​statestring

Connectivity state of the appliance

Enum"CONNECTED""NOT_ACTIVATED""DISCONNECTED"
items[].​updatedAtstring

Time of last appliance updated

Example: "2025-03-01T11:05:00.554140+00:00"
items[].​lastDisconnectedAtstring

Time of last appliance disconnected

Example: "2025-03-01T11:05:00.554140+00:00"
items[].​applianceTypestring

Type of the appliance

Example: "GATEWAY"
items[].​applianceCertstring

Certificate of the appliance

items[].​applianceModestring

Mode of the appliance

Enum"NORMAL""MAINTENANCE"
items[].​resourceobject

Resource URI of the appliance

items[].​versionstring

Version of the appliance

Example: "1.0.2+506412"
items[].​subscriptionstring or null or string or null

Subscription details for the appliance

totalinteger>= 0required

Total number of items in the collection that match the filter query, if one was provided in the request

Example: 12
Response
application/json
{
  "offset": 0,
  "count": 1,
  "total": 12,
  "items": [
    { … }
  ]
}

Get a secure gateway appliance by id

Request

Get a specific secure gateway appliance by id.

Security
Bearer
Path
device_idstring(uuid)required

Unique identifier of the appliance for which information is retrieved

Headers
Tenant-Acidstring(uuid)

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.

curl -i -X GET \
  'https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta2/appliances/{device_id}' \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>'

Responses

Successful Response

Bodyapplication/json
idstring(uuid)required

Primary identifier for the appliance

Example: "3abc1b2c-4a5d-4e6f-9c7b-2a1d8e7f6abc"
typestringrequired

Type of resource

Value "compute-ops-mgmt/appliance"
ipAddressstring(ipv4)

IP address of the appliance

deviceIdstring

Primary unique identifier for the appliance

Example: "gateway+3abc1b2c-4a5d-4e6f-9c7b-2a1d8e7f6abc"
namestring

Name of the appliance

Example: "secure-gateway-appliance-01.net"
createdAtstring

Time of appliance entry creation

Example: "2025-03-01T10:50:33.736935+00:00"
generationinteger

Monotonically increasing update counter

Example: 2450
hostnamestring

Host name of the appliance

Example: "secure-gateway-appliance-01.net"
modelNumberstring

Model of the appliance

Example: "HPE Compute Ops Management secure gateway"
productIdstring

Product identifier for the appliance

Example: "gateway"
statestring

Connectivity state of the appliance

Enum"CONNECTED""NOT_ACTIVATED""DISCONNECTED"
updatedAtstring

Time of last appliance updated

Example: "2025-03-01T11:05:00.554140+00:00"
lastDisconnectedAtstring

Time of last appliance disconnected

Example: "2025-03-01T11:05:00.554140+00:00"
applianceTypestring

Type of the appliance

Example: "GATEWAY"
applianceCertstring

Certificate of the appliance

applianceModestring

Mode of the appliance

Enum"NORMAL""MAINTENANCE"
resourceobject(applianceResourceUri-v1beta2)
versionstring

Version of the appliance

Example: "1.0.2+506412"
subscriptionstring or null

Subscription details for the appliance

Response
application/json
{
  "id": "3abc1b2c-4a5d-4e6f-9c7b-2a1d8e7f6abc",
  "type": "compute-ops-mgmt/appliance",
  "ipAddress": "192.168.0.1",
  "deviceId": "gateway+3abc1b2c-4a5d-4e6f-9c7b-2a1d8e7f6abc",
  "name": "secure-gateway-appliance-01.net",
  "createdAt": "2025-03-01T10:50:33.736935+00:00",
  "generation": 2450,
  "hostname": "secure-gateway-appliance-01.net",
  "modelNumber": "HPE Compute Ops Management secure gateway",
  "productId": "gateway",
  "state": "CONNECTED",
  "updatedAt": "2025-03-01T11:05:00.554140+00:00",
  "lastDisconnectedAt": "2025-03-01T11:05:00.554140+00:00",
  "applianceType": "GATEWAY",
  "applianceCert": "string",
  "applianceMode": "NORMAL",
  "resource": {
    "id": "gateway+3abc1b2c-4a5d-4e6f-9c7b-2a1d8e7f6abc",
    "type": "compute-ops-mgmt/appliance",
    "resourceUri": "/compute-ops-mgmt/v1beta2/appliances/gateway+3abc1b2c-4a5d-4e6f-9c7b-2a1d8e7f6abc"
  },
  "version": "1.0.2+506412",
  "subscription": "string"
}

Delete a secure gateway appliance by id

Request

Delete a specific secure gateway appliance by id.

Security
Bearer
Path
device_idstring(uuid)required

Unique identifier of the appliance to be deleted

Headers
Tenant-Acidstring(uuid)

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.

curl -i -X DELETE \
  'https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta2/appliances/{device_id}' \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>'

Responses

Successful Response

Response
No content

Get secure gateway appliance certificate by id

Request

Get specific secure gateway appliance certificate by id.

Security
Bearer
Path
device_idstring(uuid)required

Unique identifier of the appliance for which information is retrieved

Headers
Tenant-Acidstring(uuid)

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.

curl -i -X GET \
  'https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta2/appliances/{device_id}/certificate' \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>'

Responses

Successful Response

Headers
Content-Dispositionstring

The Content-Disposition header is used to indicate that the response body contains a file attachment, and it specifies the filename of the attachment. If the appliance hostname is available, the filename will be <appliance-hostname>.pem Otherwise, it will be certificate.pem

Example: "attachment; filename=\"certificate.pem\""
Bodyapplication/x-pem-file
object

PEM formatted certificate file

Response
No content

appliance-firmware-bundles - v1

Operations

appliance-firmware-bundles - v1beta1

Operations

approval-policy - v1beta2

Operations

approval-request - v1beta2

Operations

async-operations - v1

Operations

async-operations - v1beta1

Operations

energy-over-time - v1beta1

Operations

energy-by-entity - v1beta1

Operations

external-services - v1beta1

Operations

filters - v1beta1

Operations

firmware-bundles - v1

Operations

firmware-bundles - v1beta2

Operations

groups - v1

Operations

groups - v1beta3

Operations

groups - v1beta2

Operations

job-templates - v1beta2

Operations

jobs - v1

Operations

jobs - v1beta3

Operations

jobs - v1beta2

Operations

metrics-configurations - v1

Operations

oneview-appliances - v1beta1

Operations

oneview-settings - v1beta1

Operations

oneview-server-templates - v1beta1

Operations

reports - v1beta2

Operations

schedules - v1beta2

Operations

server-locations - v1beta1

Operations

server-settings - v1beta1

Operations

settings - v1

Operations

settings - v1beta1

Operations

servers - v1

Operations

servers - v1beta2

Operations

server-warranty - v1beta2

Operations

user-preferences - v1

Operations

user-preferences - v1beta1

Operations

utilization-over-time - v1beta1

Operations

utilization-by-entity - v1beta1

Operations

webhooks - v1beta1

Operations