Delete a specified monitors relation. If the deleted monitors relation was the only monitors relation of the connected device with monitorManagement rights, the device and all its associated relations will be deleted as well. To execute this query, the user must be a member of an authorizing role which satisfies both of the following conditions: One of the following role-related conditions is true: The authorizing role has direct or indirect deviceManagement rights for the role from which the monitors relation is deleted The authorizing role has indirect roleManagement rights for the role from which the monitors relation is deleted The authorizing role has monitorManagement rights for the device to which the monitors relation is deleted
accessBearerAuth In the value field below, fill in the access token. It has a 10 minutes validity period. A valid token can be obtained via the /accesstoken endpoint (call), AFTER authorization with refreshBearerAuth and the refresh token.
In: header
Id of the role of the deleted monitors relation
0 <= valueId of the deleted monitors relation
application/json
application/json
application/json
application/json
curl -X DELETE "https://example.com/v1/role/0/monitors/0"{ "deletedNodeIds": [], "deletedRelationIds": []}Update an existing device PUT
A user can only execute this call is he is a member of an authorizing role such that this role has a monitors relation with monitorManagement rights. Alternatively, the user must be member of a set of roles with monitors relations for the specified device, such that the set of device properties which these relations allow to edit are a subset of the device properties which are specified in the current request.
Collect monitors relations (replaced by POST /v1/role/{roleId}/monitors/query) GET
Get the monitors relations which start from roles of which the user is a member and which are in the specified list of role ids. The POST /v1/role/{roleId}/monitors/query is a preferable alternative which can better handle complex filters.