Assign device(s) to a group

post/compute-ops-mgmt/v1beta3/groups/{group-id}/devices

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.

SecurityBearer
Request
path Parameters
group-id
required
string <uuid>
header Parameters
Content-Type
required
string

Content-Type header must designate 'application/json' in order for the request to be performed.

Value: "application/json"
Tenant-Acid
string <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.

Request Body schema: application/json
required
required
Array of objects (deviceRequest-v1beta3) non-empty

Specifies the devices to be assigned to the group.

Responses
202

Successful Response

400

Bad request

401

Unauthorized

403

Forbidden

404

Not found

406

Not acceptable

415

Unsupported media type

500

Internal server error

Request samples
application/json
{
  • "devices": [
    ]
}
Response samples
application/json
{
  • "httpStatusCode": 400,
  • "errorCode": "HPE-GL-COMPUTE_OPS-0500001",
  • "message": "string",
  • "debugId": "string",
  • "errorDetails": [
    ]
}