Get the paged collection of all groups.
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.
The pagination cursor for the next page of resources.
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.
| CLASS | EXAMPLES |
|---|---|
| Types | integer, decimal, timestamp, string, boolean, null |
| Equality | eq, ne, gt, ge, lt, le, in |
| Logic | and, or, not |
| Array | any, all |
Groups can be filtered by all properties except for type, generation, and URIs.
The following examples are not an exhaustive list of all possible filtering options.
Return groups for a specific device type. <property> eq <value>
Return groups with specific auto-add tags. <property>/<nestedProperty> eq <value>
Return groups with one of several health states. <property> in (<value>,<value>)
Return groups with names containing a substring. contains(<property>, <value>)
Return groups that are not already compliant. not <property> <operator> <value>
Return server groups that still need remediation. <property> eq <value> and <property> eq <value>
Return groups with any settings entry that shows firmware is not compliant. <arrayProperty>/any(item: item/<nestedProperty> <operator> <value>)
Return groups where every element in a list property matches a condition. <arrayProperty>/all(item: item/<nestedProperty> <operator> <value>)
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
Limit the properties of the resource returned in a successful response. When applied to write operations, select controls only the properties that are returned, not which properties are operated on. All properties are returned if the select parameter is omitted.
The value of the select query parameter is a comma separated list of properties to include in the response. Nested properties use / as a separator, e.g. select=interfaces/name selects the name property within an interfaces object.
For operations that return paginated collections, select operates on the resources in the collection. The pagination properties like count and items are always included even when select is specified.
Select only the id and name properties of the resource
- API endpoint for US Westhttps://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups
- API endpoint for EU Centralhttps://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups
- API endpoint for AP Northeasthttps://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups
- Mock serverhttps://developer.greenlake.hpe.com/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v2beta1/groups
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X GET \
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'Successful response
The unique identifier for the group.
A description of the group's purpose.
The type of devices allowed in the group.
The health status rollup of all devices in the group.
The security status rollup of all devices in the group.
The compliance status rollup of all devices in the group.
A list of settings to apply to devices in the group.
Case-insensitive device tags, matching devices will be assigned to the group.
The URI of the device collection for the group.
The URI of the compliance collection for the group.
The URI of this group resource.
The date and time when the group was created.
Total number of items in the collection that match the filter query, if one was provided in the request
{ "offset": 0, "count": 1, "total": 12, "items": [ { … } ], "next": "string" }
Limit the properties of the resource returned in a successful response. When applied to write operations, select controls only the properties that are returned, not which properties are operated on. All properties are returned if the select parameter is omitted.
The value of the select query parameter is a comma separated list of properties to include in the response. Nested properties use / as a separator, e.g. select=interfaces/name selects the name property within an interfaces object.
For operations that return paginated collections, select operates on the resources in the collection. The pagination properties like count and items are always included even when select is specified.
Select only the id and name properties of the resource
A description of the group's purpose.
The type of devices allowed in the group.
A list of settings to apply to devices in the group.
Apply firmware settings when a server is added to a group.
Allow or forbid downgrade of firmware when firmware update is performed.
Power off server when firmware update is performed, otherwise leave server power on.
Apply BIOS settings when a server is added to a group.
Reset the server BIOS to its factory default configuration when applying BIOS settings.
Apply iLO settings when a server is added to a group.
Apply storage settings when a server is added to a group.
Delete existing storage volumes when applying storage settings.
Storage volume names to use when applying storage settings.
Install an operating system when a server is added to a group.
The timeout period for OS install to complete.
A case-insensitive tag that can be associated with a group to automatically add devices to the group. A group can have a maximum of one tag, and multiple groups cannot have the same tag. When a device is onboarded or its tags change, the device's tags are checked against the group's autoAddTags. If at least one of the device tags matches one group's autoAddTags, the device is placed into the associated group. Once a device has been connected, it becomes ineligible for automatically being placed into groups, even if it is later disconnected. If a device's tags match more than one group, it will not be assigned to any group. If a device is in a group, any further tag changes will not move it to another group. If the device was added to a group but has been removed, is not in any group, and still has not been activated, changing the device tags will automatically assign it to the matching group. Tags can contain any alphanumeric characters, spaces, and the following characters: _ . : = + - @.
- API endpoint for US Westhttps://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups
- API endpoint for EU Centralhttps://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups
- API endpoint for AP Northeasthttps://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups
- Mock serverhttps://developer.greenlake.hpe.com/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v2beta1/groups
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X POST \
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"name": "Production Group",
"description": "All production servers",
"deviceType": "DIRECT_CONNECT_SERVER",
"settings": [
{
"settingsId": "028652b0-7b8a-446d-828b-b064172d013c",
"category": "FIRMWARE"
}
],
"policies": {},
"autoAddTags": {
"Department": "Development - Texas"
}
}'Successful response
The unique identifier for the group.
The type of devices allowed in the group.
The health status rollup of all devices in the group.
The security status rollup of all devices in the group.
The compliance status rollup of all devices in the group.
Case-insensitive device tags, matching devices will be assigned to the group.
The URI of the device collection for the group.
The URI of the compliance collection for the group.
The URI of this group resource.
The date and time when the group was created.
{ "id": "0fe1cab7-6480-4ac1-841e-8607487b7df4", "type": "compute-ops-mgmt/group", "name": "Production Group", "description": "All production servers", "deviceType": "DIRECT_CONNECT_SERVER", "deviceCount": 42, "healthStatus": "OK", "securityStatus": "OK", "complianceStatus": "COMPLIANT", "settings": [ { … } ], "settingsCount": 2, "policies": { "firmwareUpdate": true, "firmwareDowngrade": true, "firmwarePowerOff": true, "biosApplySettings": true, "biosFactoryReset": true, "iloApplySettings": true, "storageConfiguration": true, "storageVolumeDeletion": true, "storageVolumes": [ … ], "osInstall": true, "osCompletionTimeoutMin": 240, "externalStorageConfiguration": true }, "autoAddTags": { "Department": "Development - Texas" }, "devicesUri": "/compute-ops-mgmt/v2beta1/groups/6081a383-b9e5-45e3-8371-1e0ba7b72068/devices", "complianceUri": "/compute-ops-mgmt/v2beta1/groups/35559e7c-b632-4b03-9fdd-1edea78a2d2c/compliance", "resourceUri": "/compute-ops-mgmt/v2beta1/groups/0e7f516c-0829-4135-83d6-09ce844ddd9d", "generation": 3, "createdAt": "2026-01-22T23:09:41.875102Z", "updatedAt": "2026-01-23T05:54:15.689856Z" }
Limit the properties of the resource returned in a successful response. When applied to write operations, select controls only the properties that are returned, not which properties are operated on. All properties are returned if the select parameter is omitted.
The value of the select query parameter is a comma separated list of properties to include in the response. Nested properties use / as a separator, e.g. select=interfaces/name selects the name property within an interfaces object.
For operations that return paginated collections, select operates on the resources in the collection. The pagination properties like count and items are always included even when select is specified.
Select only the id and name properties of the resource
- API endpoint for US Westhttps://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}
- API endpoint for EU Centralhttps://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}
- API endpoint for AP Northeasthttps://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}
- Mock serverhttps://developer.greenlake.hpe.com/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v2beta1/groups/{group_id}
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X GET \
'https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'Successful response
The unique identifier for the group.
The type of devices allowed in the group.
The health status rollup of all devices in the group.
The security status rollup of all devices in the group.
The compliance status rollup of all devices in the group.
Case-insensitive device tags, matching devices will be assigned to the group.
The URI of the device collection for the group.
The URI of the compliance collection for the group.
The URI of this group resource.
The date and time when the group was created.
{ "id": "0fe1cab7-6480-4ac1-841e-8607487b7df4", "type": "compute-ops-mgmt/group", "name": "Production Group", "description": "All production servers", "deviceType": "DIRECT_CONNECT_SERVER", "deviceCount": 42, "healthStatus": "OK", "securityStatus": "OK", "complianceStatus": "COMPLIANT", "settings": [ { … } ], "settingsCount": 2, "policies": { "firmwareUpdate": true, "firmwareDowngrade": true, "firmwarePowerOff": true, "biosApplySettings": true, "biosFactoryReset": true, "iloApplySettings": true, "storageConfiguration": true, "storageVolumeDeletion": true, "storageVolumes": [ … ], "osInstall": true, "osCompletionTimeoutMin": 240, "externalStorageConfiguration": true }, "autoAddTags": { "Department": "Development - Texas" }, "devicesUri": "/compute-ops-mgmt/v2beta1/groups/6081a383-b9e5-45e3-8371-1e0ba7b72068/devices", "complianceUri": "/compute-ops-mgmt/v2beta1/groups/35559e7c-b632-4b03-9fdd-1edea78a2d2c/compliance", "resourceUri": "/compute-ops-mgmt/v2beta1/groups/0e7f516c-0829-4135-83d6-09ce844ddd9d", "generation": 3, "createdAt": "2026-01-22T23:09:41.875102Z", "updatedAt": "2026-01-23T05:54:15.689856Z" }
Limit the properties of the resource returned in a successful response. When applied to write operations, select controls only the properties that are returned, not which properties are operated on. All properties are returned if the select parameter is omitted.
The value of the select query parameter is a comma separated list of properties to include in the response. Nested properties use / as a separator, e.g. select=interfaces/name selects the name property within an interfaces object.
For operations that return paginated collections, select operates on the resources in the collection. The pagination properties like count and items are always included even when select is specified.
Select only the id and name properties of the resource
The display name of the group.
A description of the group's purpose.
A list of settings to apply to devices in the group.
The settings policy configuration for the group.
A case-insensitive tag that can be associated with a group to automatically add devices to the group. A group can have a maximum of one tag, and multiple groups cannot have the same tag. When a device is onboarded or its tags change, the device's tags are checked against the group's autoAddTags. If at least one of the device tags matches one group's autoAddTags, the device is placed into the associated group. Once a device has been connected, it becomes ineligible for automatically being placed into groups, even if it is later disconnected. If a device's tags match more than one group, it will not be assigned to any group. If a device is in a group, any further tag changes will not move it to another group. If the device was added to a group but has been removed, is not in any group, and still has not been activated, changing the device tags will automatically assign it to the matching group. Tags can contain any alphanumeric characters, spaces, and the following characters: _ . : = + - @.
- API endpoint for US Westhttps://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}
- API endpoint for EU Centralhttps://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}
- API endpoint for AP Northeasthttps://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}
- Mock serverhttps://developer.greenlake.hpe.com/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v2beta1/groups/{group_id}
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X PATCH \
'https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/merge-patch+json' \
-d '{}'Successful response
The unique identifier for the group.
The type of devices allowed in the group.
The health status rollup of all devices in the group.
The security status rollup of all devices in the group.
The compliance status rollup of all devices in the group.
Case-insensitive device tags, matching devices will be assigned to the group.
The URI of the device collection for the group.
The URI of the compliance collection for the group.
The URI of this group resource.
The date and time when the group was created.
{ "id": "0fe1cab7-6480-4ac1-841e-8607487b7df4", "type": "compute-ops-mgmt/group", "name": "Production Group", "description": "All production servers", "deviceType": "DIRECT_CONNECT_SERVER", "deviceCount": 42, "healthStatus": "OK", "securityStatus": "OK", "complianceStatus": "COMPLIANT", "settings": [ { … } ], "settingsCount": 2, "policies": { "firmwareUpdate": true, "firmwareDowngrade": true, "firmwarePowerOff": true, "biosApplySettings": true, "biosFactoryReset": true, "iloApplySettings": true, "storageConfiguration": true, "storageVolumeDeletion": true, "storageVolumes": [ … ], "osInstall": true, "osCompletionTimeoutMin": 240, "externalStorageConfiguration": true }, "autoAddTags": { "Department": "Development - Texas" }, "devicesUri": "/compute-ops-mgmt/v2beta1/groups/6081a383-b9e5-45e3-8371-1e0ba7b72068/devices", "complianceUri": "/compute-ops-mgmt/v2beta1/groups/35559e7c-b632-4b03-9fdd-1edea78a2d2c/compliance", "resourceUri": "/compute-ops-mgmt/v2beta1/groups/0e7f516c-0829-4135-83d6-09ce844ddd9d", "generation": 3, "createdAt": "2026-01-22T23:09:41.875102Z", "updatedAt": "2026-01-23T05:54:15.689856Z" }
- API endpoint for US Westhttps://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}
- API endpoint for EU Centralhttps://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}
- API endpoint for AP Northeasthttps://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}
- Mock serverhttps://developer.greenlake.hpe.com/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v2beta1/groups/{group_id}
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X DELETE \
'https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'The pagination cursor for the next page of resources.
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.
| CLASS | EXAMPLES |
|---|---|
| Types | integer, decimal, timestamp, string, boolean, null |
| Equality | eq, ne, gt, ge, lt, le, in |
| Logic | and, or, not |
| Array | any, all |
Devices in a group can be filtered by all properties except for type, generation, and URIs.
The following examples are not an exhaustive list of all possible filtering options.
Return only devices that are servers. <property> eq <value>
Return devices with one of several health states. <property> in (<value>,<value>)
Return devices with a matching serial number substring. contains(<property>, <value>)
Return devices that are not currently healthy. not <property> eq <value>
Return devices that have both health and security issues. <property> eq <value> and <property> eq <value>
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
Limit the properties of the resource returned in a successful response. When applied to write operations, select controls only the properties that are returned, not which properties are operated on. All properties are returned if the select parameter is omitted.
The value of the select query parameter is a comma separated list of properties to include in the response. Nested properties use / as a separator, e.g. select=interfaces/name selects the name property within an interfaces object.
For operations that return paginated collections, select operates on the resources in the collection. The pagination properties like count and items are always included even when select is specified.
Select only the id and name properties of the resource
- API endpoint for US Westhttps://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/group-devices
- API endpoint for EU Centralhttps://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/group-devices
- API endpoint for AP Northeasthttps://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/group-devices
- Mock serverhttps://developer.greenlake.hpe.com/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v2beta1/group-devices
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X GET \
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/group-devices \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'Successful response
The unique identifier for the device.
The device display name, commonly the hostname or serial number.
The ID of the group that the device is assigned to.
The URI of the group that the device is assigned to.
The ID of the assigned device resource.
The URI of the assigned device resource. The URI version may change over time.
The type of the device.
The URI of this device resource.
The date and time when the device was assigned.
Total number of items in the collection that match the filter query, if one was provided in the request
{ "offset": 0, "count": 1, "total": 12, "items": [ { … } ], "next": "string" }
The pagination cursor for the next page of resources.
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.
| CLASS | EXAMPLES |
|---|---|
| Types | integer, decimal, timestamp, string, boolean, null |
| Equality | eq, ne, gt, ge, lt, le, in |
| Logic | and, or, not |
| Array | any, all |
Devices in a group can be filtered by all properties except for type, generation, and URIs.
The following examples are not an exhaustive list of all possible filtering options.
Return only devices that are servers. <property> eq <value>
Return devices with one of several health states. <property> in (<value>,<value>)
Return devices with a matching serial number substring. contains(<property>, <value>)
Return devices that are not currently healthy. not <property> eq <value>
Return devices that have both health and security issues. <property> eq <value> and <property> eq <value>
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
Limit the properties of the resource returned in a successful response. When applied to write operations, select controls only the properties that are returned, not which properties are operated on. All properties are returned if the select parameter is omitted.
The value of the select query parameter is a comma separated list of properties to include in the response. Nested properties use / as a separator, e.g. select=interfaces/name selects the name property within an interfaces object.
For operations that return paginated collections, select operates on the resources in the collection. The pagination properties like count and items are always included even when select is specified.
Select only the id and name properties of the resource
- API endpoint for US Westhttps://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/devices
- API endpoint for EU Centralhttps://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/devices
- API endpoint for AP Northeasthttps://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/devices
- Mock serverhttps://developer.greenlake.hpe.com/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v2beta1/groups/{group_id}/devices
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X GET \
'https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/devices' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'Successful response
The unique identifier for the device.
The device display name, commonly the hostname or serial number.
The ID of the group that the device is assigned to.
The URI of the group that the device is assigned to.
The ID of the assigned device resource.
The URI of the assigned device resource. The URI version may change over time.
The type of the device.
The URI of this device resource.
The date and time when the device was assigned.
Total number of items in the collection that match the filter query, if one was provided in the request
{ "offset": 0, "count": 1, "total": 12, "items": [ { … } ], "next": "string" }
Limit the properties of the resource returned in a successful response. When applied to write operations, select controls only the properties that are returned, not which properties are operated on. All properties are returned if the select parameter is omitted.
The value of the select query parameter is a comma separated list of properties to include in the response. Nested properties use / as a separator, e.g. select=interfaces/name selects the name property within an interfaces object.
For operations that return paginated collections, select operates on the resources in the collection. The pagination properties like count and items are always included even when select is specified.
Select only the id and name properties of the resource
- API endpoint for US Westhttps://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/devices/{device_id}
- API endpoint for EU Centralhttps://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/devices/{device_id}
- API endpoint for AP Northeasthttps://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/devices/{device_id}
- Mock serverhttps://developer.greenlake.hpe.com/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v2beta1/groups/{group_id}/devices/{device_id}
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X GET \
'https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/devices/{device_id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'Successful response
The unique identifier for the device.
The device display name, commonly the hostname or serial number.
The ID of the group that the device is assigned to.
The URI of the group that the device is assigned to.
The URI of the assigned device resource. The URI version may change over time.
The type of the device.
The URI of this device resource.
The date and time when the device was assigned.
{ "id": "0dc95df2-636e-4bde-ba4f-e9ec9127471b", "type": "compute-ops-mgmt/group/device", "name": "data-3", "groupId": "35559e7c-b632-4b03-9fdd-1edea78a2d2c", "groupUri": "/compute-ops-mgmt/v2beta1/groups/35559e7c-b632-4b03-9fdd-1edea78a2d2c", "deviceId": "873357-P04+WKQ82425HD", "deviceUri": "/compute-ops-mgmt/v1/servers/873357-P04+WKQ82425HD", "deviceType": "DIRECT_CONNECT_SERVER", "healthStatus": "OK", "securityStatus": "OK", "resourceUri": "/compute-ops-mgmt/v2beta1/groups/6081a383-b9e5-45e3-8371-1e0ba7b72068/devices/0dc95df2-636e-4bde-ba4f-e9ec9127471b", "generation": 3, "createdAt": "2026-01-22T23:09:41.875102Z", "updatedAt": "2026-01-23T05:54:15.689856Z" }
Request
Assign device(s) to a group using an asynchronous operation. On a successful request this endpoint will return a 202 Accepted response with a Location header that contains the resource URI of the operation. That resource URI can then be used to monitor the asynchronous operation's status.
- API endpoint for US Westhttps://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/assign-devices
- API endpoint for EU Centralhttps://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/assign-devices
- API endpoint for AP Northeasthttps://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/assign-devices
- Mock serverhttps://developer.greenlake.hpe.com/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v2beta1/groups/{group_id}/assign-devices
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X POST \
'https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/assign-devices' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"items": [
{
"deviceId": "873357-P04+WKQ82425HD"
}
]
}'No contentRequest
Unassign device(s) from a group using an asynchronous operation. On a successful request this endpoint will return a 202 Accepted response with a Location header that contains the resource URI of the operation. That resource URI can then be used to monitor the asynchronous operation's status.
- API endpoint for US Westhttps://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/unassign-devices
- API endpoint for EU Centralhttps://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/unassign-devices
- API endpoint for AP Northeasthttps://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/unassign-devices
- Mock serverhttps://developer.greenlake.hpe.com/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v2beta1/groups/{group_id}/unassign-devices
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X POST \
'https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/unassign-devices' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"items": [
{
"deviceId": "873357-P04+WKQ82425HD"
}
]
}'No contentThe pagination cursor for the next page of resources.
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.
| CLASS | EXAMPLES |
|---|---|
| Types | integer, decimal, timestamp, string, boolean, null |
| Equality | eq, ne, gt, ge, lt, le, in |
| Logic | and, or, not |
| Array | any, all |
Group compliance can be filtered by all properties except for type, generation, and URIs.
The following examples are not an exhaustive list of all possible filtering options.
Return compliance results for a specific settings category. <property> eq <value>
Return compliance results for one of several settings categories. <property> in (<value>,<value>)
Return compliance results for devices with a matching serial number substring. contains(<property>, <value>)
Return compliance results that are not already compliant. not <property> eq <value>
Return firmware results with less than 70% match. <property> eq <value> and <property> lt <value>
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
Limit the properties of the resource returned in a successful response. When applied to write operations, select controls only the properties that are returned, not which properties are operated on. All properties are returned if the select parameter is omitted.
The value of the select query parameter is a comma separated list of properties to include in the response. Nested properties use / as a separator, e.g. select=interfaces/name selects the name property within an interfaces object.
For operations that return paginated collections, select operates on the resources in the collection. The pagination properties like count and items are always included even when select is specified.
Select only the id and name properties of the resource
- API endpoint for US Westhttps://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/group-compliance
- API endpoint for EU Centralhttps://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/group-compliance
- API endpoint for AP Northeasthttps://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/group-compliance
- Mock serverhttps://developer.greenlake.hpe.com/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v2beta1/group-compliance
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X GET \
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/group-compliance \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'Successful response
The unique identifier for the device compliance.
The device compliance resource type.
The ID of the group that the device is assigned to.
The URI of the group that the device is assigned to.
The ID of the assigned device that compliance was computed for.
The URI of the assigned device resource. The URI version may change over time.
The settings category that compliance was computed for.
The compliance status for the device and settings category.
Remediation instructions to reach compliance with the defined settings.
The reason device compliance could not be computed.
The URI of this compliance resource.
The date and time when the device compliance was created.
Total number of items in the collection that match the filter query, if one was provided in the request
{ "offset": 0, "count": 1, "total": 12, "items": [ { … } ], "next": "string" }
The pagination cursor for the next page of resources.
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.
| CLASS | EXAMPLES |
|---|---|
| Types | integer, decimal, timestamp, string, boolean, null |
| Equality | eq, ne, gt, ge, lt, le, in |
| Logic | and, or, not |
| Array | any, all |
Group compliance can be filtered by all properties except for type, generation, and URIs.
The following examples are not an exhaustive list of all possible filtering options.
Return compliance results for a specific settings category. <property> eq <value>
Return compliance results for one of several settings categories. <property> in (<value>,<value>)
Return compliance results for devices with a matching serial number substring. contains(<property>, <value>)
Return compliance results that are not already compliant. not <property> eq <value>
Return firmware results with less than 70% match. <property> eq <value> and <property> lt <value>
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
Limit the properties of the resource returned in a successful response. When applied to write operations, select controls only the properties that are returned, not which properties are operated on. All properties are returned if the select parameter is omitted.
The value of the select query parameter is a comma separated list of properties to include in the response. Nested properties use / as a separator, e.g. select=interfaces/name selects the name property within an interfaces object.
For operations that return paginated collections, select operates on the resources in the collection. The pagination properties like count and items are always included even when select is specified.
Select only the id and name properties of the resource
- API endpoint for US Westhttps://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/compliance
- API endpoint for EU Centralhttps://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/compliance
- API endpoint for AP Northeasthttps://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/compliance
- Mock serverhttps://developer.greenlake.hpe.com/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v2beta1/groups/{group_id}/compliance
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X GET \
'https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/compliance' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'Successful response
The unique identifier for the device compliance.
The device compliance resource type.
The ID of the group that the device is assigned to.
The URI of the group that the device is assigned to.
The ID of the assigned device that compliance was computed for.
The URI of the assigned device resource. The URI version may change over time.
The settings category that compliance was computed for.
The compliance status for the device and settings category.
Remediation instructions to reach compliance with the defined settings.
The reason device compliance could not be computed.
The URI of this compliance resource.
The date and time when the device compliance was created.
Total number of items in the collection that match the filter query, if one was provided in the request
{ "offset": 0, "count": 1, "total": 12, "items": [ { … } ], "next": "string" }
Limit the properties of the resource returned in a successful response. When applied to write operations, select controls only the properties that are returned, not which properties are operated on. All properties are returned if the select parameter is omitted.
The value of the select query parameter is a comma separated list of properties to include in the response. Nested properties use / as a separator, e.g. select=interfaces/name selects the name property within an interfaces object.
For operations that return paginated collections, select operates on the resources in the collection. The pagination properties like count and items are always included even when select is specified.
Select only the id and name properties of the resource
- API endpoint for US Westhttps://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/compliance/{compliance_id}
- API endpoint for EU Centralhttps://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/compliance/{compliance_id}
- API endpoint for AP Northeasthttps://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/compliance/{compliance_id}
- Mock serverhttps://developer.greenlake.hpe.com/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v2beta1/groups/{group_id}/compliance/{compliance_id}
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X GET \
'https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v2beta1/groups/{group_id}/compliance/{compliance_id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'Successful response
The unique identifier for the device compliance.
The ID of the group that the device is assigned to.
The URI of the group that the device is assigned to.
The ID of the assigned device that compliance was computed for.
The URI of the assigned device resource. The URI version may change over time.
The settings category that compliance was computed for.
The compliance status for the device and settings category.
Remediation instructions to reach compliance with the defined settings.
The reason device compliance could not be computed.
The URI of this compliance resource.
{ "id": "f07b39e9-f01d-4778-bc13-c5aa5308d50d", "type": "compute-ops-mgmt/group/compliance", "groupId": "35559e7c-b632-4b03-9fdd-1edea78a2d2c", "groupUri": "/compute-ops-mgmt/v2beta1/groups/35559e7c-b632-4b03-9fdd-1edea78a2d2c", "deviceId": "873357-P04+WKQ82425HD", "deviceUri": "/compute-ops-mgmt/v1/servers/873357-P04+WKQ82425HD", "category": "FIRMWARE", "complianceStatus": "COMPLIANT", "percentMatch": 100, "deviations": [ {} ], "remediation": {}, "errorReason": "string", "resourceUri": "/compute-ops-mgmt/v2beta1/groups/c26e618b-4048-4aee-8e75-fbc984897a51/compliance/b73718fb-30c3-4b0f-bee3-f5dd598414f3", "generation": 0, "createdAt": "2019-08-24T14:15:22Z", "updatedAt": "2019-08-24T14:15:22Z" }