Zero-based resource offset to start the response from
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 a paginated collection of saved filter resources.
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 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 |
Filters can be filtered by:
- filterResourceType
- id
- type
The following examples are not an exhaustive list of all possible filtering options.
Return filters where a property equals a value. <property> eq <value>
Return filters where a property equals a value, using a url. <property>%20eq%20%27<value>
Return filters where a property does not equal a value not <property> eq <value>
Return filters with populated property. not <property> eq null
Return filters where property contains a value. contains(<property>, <value>)
Return filters where property is populated and property contains value. not <property> eq null and contains(<property>, <value>)
Return filters where property is one of multiple values. <property> in (<value>,<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
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/filters
- API endpoint for US West
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/filters
- API endpoint for EU Central
https://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/filters
- API endpoint for AP Northeast
https://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/filters
- 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/filters \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'
OK
Total number of items in the collection that match the filter query, if one was provided in the request
Array of saved filter resources in the page of the collection.
Primary identifier for the filter resource given by the system.
Time of filter resource creation.
Time of the last update to the filter resource.
URI to the filter resource itself (i.e. a self link).
If true, the filter is pre-defined and cannot be edited or deleted.
The type of the resource that the filter matches against. New resource types may be added as a backward compatible change to the API.
Flags the filter for use with resource restriction policies used by scope-based access control (SBAC). Only administrators with full access to all scopes can create, edit, or delete RRP-enabled filters. The use of some resource properties may be disallowed in RRP-enabled filters.
The filter expression, in the same syntax as the filter
query parameter common to many collection endpoints. At least one of filter
and filterTags
must be specified. If both are specified, both filter expressions much match for a resource to match the filter.
An optional filter expression for tags, in the same syntax as the filter-tags
query parameter common to many collection endpoints. Used to handle tag keys with special characters. At least one of filter
and filterTags
must be specified. If both are specified, both filter expressions much match for a resource to match the filter.
Opaque JSON structure used by the Compute Ops Management UI. Other clients should not read or set this property. Note that the format of the data is subject to change without notice, even with the same API version of filters.
{ "offset": 0, "count": 1, "total": 12, "items": [ { … } ] }
Request
Create a new saved filter resource.
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.
A unique value generated by the client which the server uses to recognize subsequent retries of the same request.
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.
A saved filter on other resources.
The filter expression, in the same syntax as the filter
query parameter common to many collection endpoints. At least one of filter
and filterTags
must be specified. If both are specified, both filter expressions much match for a resource to match the filter.
The type of the resource that the filter matches against. New resource types may be added as a backward compatible change to the API.
Flags the filter for use with resource restriction policies used by scope-based access control (SBAC). Only administrators with full access to all scopes can create, edit, or delete RRP-enabled filters. The use of some resource properties may be disallowed in RRP-enabled filters.
An optional filter expression for tags, in the same syntax as the filter-tags
query parameter common to many collection endpoints. Used to handle tag keys with special characters. At least one of filter
and filterTags
must be specified. If both are specified, both filter expressions much match for a resource to match the filter.
- 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/filters
- API endpoint for US West
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/filters
- API endpoint for EU Central
https://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/filters
- API endpoint for AP Northeast
https://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/filters
- 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/filters \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"name": "string",
"filterTags": "'\''OS'\'' eq '\''Linux'\''"
}'
Created
Primary identifier for the filter resource given by the system.
Time of filter resource creation.
Time of the last update to the filter resource.
URI to the filter resource itself (i.e. a self link).
If true, the filter is pre-defined and cannot be edited or deleted.
The type of the resource that the filter matches against. New resource types may be added as a backward compatible change to the API.
Flags the filter for use with resource restriction policies used by scope-based access control (SBAC). Only administrators with full access to all scopes can create, edit, or delete RRP-enabled filters. The use of some resource properties may be disallowed in RRP-enabled filters.
The filter expression, in the same syntax as the filter
query parameter common to many collection endpoints. At least one of filter
and filterTags
must be specified. If both are specified, both filter expressions much match for a resource to match the filter.
An optional filter expression for tags, in the same syntax as the filter-tags
query parameter common to many collection endpoints. Used to handle tag keys with special characters. At least one of filter
and filterTags
must be specified. If both are specified, both filter expressions much match for a resource to match the filter.
Opaque JSON structure used by the Compute Ops Management UI. Other clients should not read or set this property. Note that the format of the data is subject to change without notice, even with the same API version of filters.
{ "id": "b870f080-6448-48c5-b23a-d04f2d489174", "type": "compute-ops-mgmt/filter", "generation": 1, "createdAt": "2022-02-11T01:04:20.799937+00:00", "updatedAt": "2022-02-11T01:04:20.799937+00:00", "resourceUri": "/compute-ops-mgmt/v1beta1/filters/b870f080-6448-48c5-b23a-d04f2d489174", "name": "string", "description": "string", "readOnly": false, "filterResourceType": "compute-ops-mgmt/server", "enabledForRRP": false, "filter": "group/id eq '031adad0-f77c-403d-84f5-e0bb46e0d927'", "filterTags": "'OS' eq 'Linux'", "uiData": null, "matchesUri": "/compute-ops-mgmt/v1beta1/filters/b870f080-6448-48c5-b23a-d04f2d489174/matches" }
Request
Retrieve information about resource properties usable in saved filters.
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/filters/properties
- API endpoint for US West
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/filters/properties
- API endpoint for EU Central
https://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/filters/properties
- API endpoint for AP Northeast
https://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/filters/properties
- 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/filters/properties \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'
{ "id": "properties", "type": "compute-ops-mgmt/filters-properties", "filterResourceTypes": { "compute-ops-mgmt/server": { … } } }
Request
Retrieve a single saved filter resource 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/filters/{id}
- API endpoint for US West
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/filters/{id}
- API endpoint for EU Central
https://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/filters/{id}
- API endpoint for AP Northeast
https://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/filters/{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/filters/{id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'
OK
Primary identifier for the filter resource given by the system.
Time of filter resource creation.
Time of the last update to the filter resource.
URI to the filter resource itself (i.e. a self link).
If true, the filter is pre-defined and cannot be edited or deleted.
The type of the resource that the filter matches against. New resource types may be added as a backward compatible change to the API.
Flags the filter for use with resource restriction policies used by scope-based access control (SBAC). Only administrators with full access to all scopes can create, edit, or delete RRP-enabled filters. The use of some resource properties may be disallowed in RRP-enabled filters.
The filter expression, in the same syntax as the filter
query parameter common to many collection endpoints. At least one of filter
and filterTags
must be specified. If both are specified, both filter expressions much match for a resource to match the filter.
An optional filter expression for tags, in the same syntax as the filter-tags
query parameter common to many collection endpoints. Used to handle tag keys with special characters. At least one of filter
and filterTags
must be specified. If both are specified, both filter expressions much match for a resource to match the filter.
Opaque JSON structure used by the Compute Ops Management UI. Other clients should not read or set this property. Note that the format of the data is subject to change without notice, even with the same API version of filters.
{ "id": "b870f080-6448-48c5-b23a-d04f2d489174", "type": "compute-ops-mgmt/filter", "generation": 1, "createdAt": "2022-02-11T01:04:20.799937+00:00", "updatedAt": "2022-02-11T01:04:20.799937+00:00", "resourceUri": "/compute-ops-mgmt/v1beta1/filters/b870f080-6448-48c5-b23a-d04f2d489174", "name": "string", "description": "string", "readOnly": false, "filterResourceType": "compute-ops-mgmt/server", "enabledForRRP": false, "filter": "group/id eq '031adad0-f77c-403d-84f5-e0bb46e0d927'", "filterTags": "'OS' eq 'Linux'", "uiData": null, "matchesUri": "/compute-ops-mgmt/v1beta1/filters/b870f080-6448-48c5-b23a-d04f2d489174/matches" }
Request
Delete a saved filter resource.
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/filters/{id}
- API endpoint for US West
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/filters/{id}
- API endpoint for EU Central
https://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/filters/{id}
- API endpoint for AP Northeast
https://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/filters/{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/filters/{id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'
Request
Update a saved filter resource by using the RFC 7396 (JSON Merge Patch) format.
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/merge-patch+json' in order for the request to be performed.
Value which must match the "generation" property of the resource 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.
The type of the resource that the filter matches against. New resource types may be added as a backward compatible change to the API.
Flags the filter for use with resource restriction policies used by scope-based access control (SBAC). Only administrators with full access to all scopes can create, edit, or delete RRP-enabled filters. The use of some resource properties may be disallowed in RRP-enabled filters.
The filter expression, in the same syntax as the filter
query parameter common to many collection endpoints. At least one of filter
and filterTags
must be specified. If both are specified, both filter expressions much match for a resource to match the filter.
An optional filter expression for tags, in the same syntax as the filter-tags
query parameter common to many collection endpoints. Used to handle tag keys with special characters. At least one of filter
and filterTags
must be specified. If both are specified, both filter expressions much match for a resource to match the filter.
- 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/filters/{id}
- API endpoint for US West
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/filters/{id}
- API endpoint for EU Central
https://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/filters/{id}
- API endpoint for AP Northeast
https://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/filters/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X PATCH \
'https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v1beta1/filters/{id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/merge-patch+json' \
-d '{}'
OK
Primary identifier for the filter resource given by the system.
Time of filter resource creation.
Time of the last update to the filter resource.
URI to the filter resource itself (i.e. a self link).
If true, the filter is pre-defined and cannot be edited or deleted.
The type of the resource that the filter matches against. New resource types may be added as a backward compatible change to the API.
Flags the filter for use with resource restriction policies used by scope-based access control (SBAC). Only administrators with full access to all scopes can create, edit, or delete RRP-enabled filters. The use of some resource properties may be disallowed in RRP-enabled filters.
The filter expression, in the same syntax as the filter
query parameter common to many collection endpoints. At least one of filter
and filterTags
must be specified. If both are specified, both filter expressions much match for a resource to match the filter.
An optional filter expression for tags, in the same syntax as the filter-tags
query parameter common to many collection endpoints. Used to handle tag keys with special characters. At least one of filter
and filterTags
must be specified. If both are specified, both filter expressions much match for a resource to match the filter.
Opaque JSON structure used by the Compute Ops Management UI. Other clients should not read or set this property. Note that the format of the data is subject to change without notice, even with the same API version of filters.
{ "id": "b870f080-6448-48c5-b23a-d04f2d489174", "type": "compute-ops-mgmt/filter", "generation": 1, "createdAt": "2022-02-11T01:04:20.799937+00:00", "updatedAt": "2022-02-11T01:04:20.799937+00:00", "resourceUri": "/compute-ops-mgmt/v1beta1/filters/b870f080-6448-48c5-b23a-d04f2d489174", "name": "string", "description": "string", "readOnly": false, "filterResourceType": "compute-ops-mgmt/server", "enabledForRRP": false, "filter": "group/id eq '031adad0-f77c-403d-84f5-e0bb46e0d927'", "filterTags": "'OS' eq 'Linux'", "uiData": null, "matchesUri": "/compute-ops-mgmt/v1beta1/filters/b870f080-6448-48c5-b23a-d04f2d489174/matches" }
Request
Retrieve a paginated collection of match entries that indicate which resources match a saved filter.
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.
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/filters/{id}/matches
- API endpoint for US West
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/filters/{id}/matches
- API endpoint for EU Central
https://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/filters/{id}/matches
- API endpoint for AP Northeast
https://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/filters/{id}/matches
- 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/filters/{id}/matches' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'
{ "offset": 0, "count": 1, "total": 12, "items": [ { … } ] }