Skip to main content
This guide explains how to work with devices from an integrator’s perspective. Device-to-cloud communication is handled entirely by Stealthera — your platform reads device data and status through the API.

​
Identifying a device

Every device is identified by its deviceId, which is the watch IMEI (for example 863758060992848). This value is stable for the life of the device and is the key you use across all endpoints. The live device list returns one row per device:

​
Device information

GET /api/device/{deviceId}/info returns hardware and network metadata for a single device.
Use battery to drive low-power warnings in your dashboard and signal to explain coverage gaps. A device that stops updating lastSeen is offline or out of coverage.

​
Monitoring status

For a lightweight check, read status and lastSeen from the device list (/api/health-data) or from /api/device/{deviceId}/info. Device connectivity changes also surface in the alarm log (for example Low battery and Not worn).

​
Assigning devices

In this version, the link between a device and a patient is maintained on your side using deviceId as the key. Keep the assignment and its history in your own records so readings remain attributed correctly over time. A patient registry and assignment-history workflow is planned for a future version.