Skip to main content
POST
Detach points from a virtual device
A copy cannot go back to a base device, so detaching a copy deletes it. Copies are listed in deletedCopies. This cannot be undone.
Every point in pointIds must be on this virtual device. The request is all or nothing. If any id is not on the device, nothing changes. The response has detached, the ids of origin points returned to their base device, and deletedCopies, the ids of copies that were deleted. The order of ids in both lists is not defined. Repeating a request that already succeeded returns 400, because the points are no longer on the device. Schedule references move back to the base device after the detach, so they can lag behind the response.

Authorizations

Authorization
string
header
required

Paste an access token from Create an access token. Tokens expire, so request a new one if you receive 401.

Path Parameters

buildingId
string
required

Building identifier from List buildings.

virtualDeviceId
string
required

ID of virtual device

Body

application/json
pointIds
string[]
required
Required array length: 1 - 200 elements
Maximum string length: 128
Pattern: [^\p{C}\p{Z}]{1,128}

Response

The points that were detached and the copies that were deleted.