Schedule device deletions
Schedule batch deletion of devices from the Nexthink inventory.
Schedule the deletion of one or more devices from the Nexthink inventory.
Each device must be identified by both its uid and name. Devices with malformed UIDs are rejected individually with status INVALID without failing the rest of the batch.
The operation is asynchronous: the API returns 202 Accepted once the deletions are queued. Actual removal from the inventory happens in the background.
Optional client-supplied correlation identifier (UUID). Echoed back in the response x-request-id header. If omitted, the server generates one.
Batch of devices to be deleted from the Nexthink inventory.
Deletion batch accepted and queued. Check each device's status field — a 202 response does not guarantee all devices were successfully scheduled.
The request payload is invalid and was not accepted.
Unauthorized — the bearer token is missing or invalid.
Forbidden — the Data Management is not enabled for this tenant.
Internal server error. Include the x-request-id response header value when contacting Nexthink support.
POST /api/v1/data-management/device/deletions HTTP/1.1
Host: instance.api.region.nexthink.cloud
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 78
{
"devices": [
{
"uid": "123e4567-e89b-12d3-a456-426614174000",
"name": "laptop-1"
}
]
}{
"scheduledCount": 2,
"status": "ACCEPTED",
"devices": [
{
"uid": "123e4567-e89b-12d3-a456-426614174000",
"name": "laptop-1",
"status": "SCHEDULED"
},
{
"uid": "123e4567-e89b-12d3-a456-426614174001",
"name": "laptop-2",
"status": "SCHEDULED"
}
]
}Last updated
Was this helpful?
