Patch the properties of several devices at once by specifying JSON patch operations in accordance with RFC 6902, each of which names the device or devices it applies to. The operations of a device are applied in their order in the request, and all devices are updated together or not at all. The same rights apply as for patching a single device. A failed operation is reported by its index in the request.
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
Before executing the update, validate the updated device using the schema corresponding to its nodeType (if such a schema exists)
Reject operations on missing locations as RFC 6902 prescribes. When false, add, replace, copy and move create the location they write to along with its missing ancestors, as empty objects (a missing array element only as the next element at the end of its array), and remove, copy and move do nothing when the location they remove or read from is missing. Every operation but test is then idempotent, so a request can safely be repeated.
trueAn ISO 8601 time or a time of the format '<day-name>, <day> <month> <year> <hour>:<minute>:<second> GMT', specifying the latest timestamp any of the affected devices might have received an update in order for the request to be executed. A code 412 error will be returned if at least one device was updated after the specified time
application/json
The JSON patch operations, each with the device or devices it applies to
TypeScript Definitions
Use the request body type in TypeScript.
The JSON patch operations, each with the device or devices it applies to
1 <= itemsapplication/json
application/json
application/json
application/json
application/json
application/json
curl -X PATCH "https://example.com/v1/device" \ -H "Content-Type: application/json" \ -d '[ { "op": "add", "path": "string", "value": null, "deviceId": 0 } ]'{ "device": [ { "id": 0, "lastUpdate": "2019-08-24T14:15:22Z", "properties": { "property1": null, "property2": null }, "userRights": { "propertyEditabilities": { "property1": true, "property2": true }, "monitorManagement": true } } ]}Perform a series of targeted update operations PATCH
Patch the properties of one or more devices by specifying JSON patch operations which should be applied to the device properties in accordance with RFC 6902. A user can only execute this call when 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.
Create a new device and the monitors relation which connects this device to a role POST
A user can only execute this call is he is a member of an authorizing role which satisfies one of the following conditions: <ul> <li> The authorizing role has *direct or indirect* deviceManagement rights for the role for which a device is created </li> <li> The authorizing role has *indirect* roleManagement rights for the role for which a device is created </li> </ul>