Read a sub-device's telemetry history
A session token for an existing account, obtained from POST /auth/login (see the Authentication endpoints) - not an API key. Endpoints marked with this scheme reject API key callers outright, regardless of what that key is granted. Outside the Authentication endpoints themselves, everything requiring this scheme manages dashboard resources (rules, grants, keys, device configuration, command catalogs) and mirrors what a human does in the Nexalware web app - it is not meant to be automated by a third-party integration the way the Device Control and Schedules endpoints are.
In: header
Path Parameters
Query Parameters
Only return readings for this metric name, omit to get every metric this sub-device reports.
Max rows to return, 1-1000. Defaults to 100.
1 <= value <= 1000100Unix milliseconds - only return readings recorded at or after this time.
Response Body
application/json
application/json
curl -X GET "https://example.com/api/v1/devices/dev_a1b2c3/sub-devices/sub_x1y2z3/telemetry?metric=power_draw&limit=50&since=1732000000000"[ { "metric": "power_draw", "value": 4.2, "valueText": null, "unit": "watts", "recordedAt": "2024-11-19T10:05:00.000Z" }]List the sub-devices connected behind this device GET
A device can act as an orchestrator ("master") for other physical devices connected to it locally (Bluetooth, WiFi) rather than directly to Nexalware - this lists everything reported behind it. Empty until the master actually reports a sub-device, see the [Device Orchestration](/docs/device-orchestration) docs for how a master does that. See [Receiving Webhooks](/docs/reference/receiving-webhooks) for the equivalent live-event story, sub-device events ride the same WebSocket feed and webhook pipeline device events already use.
Read one sub-device GET
Next Page