Get an employee sensor device association.
get
/connectedWorker/clientapi/v2/orgs/{orgId}/employeeTypes/{typeId}/sensorAttributes/{sensorAttributeId}/devices/{deviceId}
This operation retrieves an association between employee type, sensor attribute and device. Only users having role IoTCWSupervisor or higher can call this API.
Request
Path Parameters
-
deviceId: string
Param that identifies device
-
orgId: string
Organization identifier
-
sensorAttributeId: string
Param that identifies sensor attribute in employee wearable type
-
typeId: string
Param that identifies type
There's no request body for this operation.
Back to TopResponse
Supported Media Types
- application/json
200 Response
Employee sensor device association was successfully retrieved.
Root Schema : EmployeeSensorDevice
Type:
Show Source
object
-
deviceId:
string
Id of the device. The device must be activated and must support device model associated with the type and attributeExample:
21E15228-0C54-47E6-AC7F-41A0A8F8D10E
-
deviceModelUrn:
string
Minimum Length:
0
Maximum Length:1000
Device model identifierExample:urn:my:company:device:model
-
id(optional):
string
Id of the device. The device must be activated and must support device model associated with the type and attributeDeprecated. Use deviceId property.Example:
21E15228-0C54-47E6-AC7F-41A0A8F8D10E
-
links(optional):
array links
-
messageField:
string
Minimum Length:
0
Maximum Length:500
Message attribute identifierExample:myAttributeName
-
messageUrn:
string
Minimum Length:
0
Maximum Length:1000
Device message identifier. The message must have parent identified by value in deviceModelUrn. If not provided, it os automatically composed from value from 'deviceModelUrn' plus ':attributes'Example:urn:my:company:device:model:message
-
sensorAttributeId:
string
Id of the sensor attributeExample:
51
-
typeId:
string
Id of the typeExample:
50
Nested Schema : Link
Type:
Show Source
object
-
href:
string
The target resource's URI
-
rel:
string
Relation type