How to Query Device Health

Once you know which device you want to inspect, the next question is simple: what is the latest health record for that device?

This post focuses on one API call:

• A latest-health view for one specific device

If you are using the Python SDK, the wrapper handles request signing for you once you provide your access key and secret key. If you are calling the API directly, use the same HMAC SHA256 signing flow from the previous post.

What You Need

• An authenticated session or a signed API request

• The device ID if you want a single-device query

What This Endpoint Returns

Use GET /v1/devicehealth/getlatest/{deviceID} when you want the latest health record for one device.

Example request:

GET /v1/devicehealth/getlatest/12345 HTTP/1.1
Authorization: <your-session-or-signed-request>

The response is a single device health record with fields like:

• key

• userID

• deviceID

• healthDate

• healthJSON

• creationDate

• createdBy

• lastModifiedDate

• lastModifiedBy

The healthJSON field contains the detailed telemetry payload as a JSON string. That is where you will find the lower-level metrics if you need them for deeper diagnostics or charting.

If you need a fleet-wide list of devices and current status, use the previous post first. This article is the deeper follow-up when you already know which device to inspect.

How To Read The Health Data

This record is the current snapshot for one device:

• healthDate tells you when the data was recorded

• deviceID ties the record back to the device

• healthJSON contains the full telemetry payload

In practice, use this endpoint when you need to troubleshoot one device, inspect raw telemetry, or feed a device-specific detail view.

How The Python SDK Fits In

If you are using the Python SDK, you do not need to sign these requests by hand.

The SDK takes the access key and secret key in its config object, then handles signing in the wrapped calls. The health workflow is the same either way. The only difference is whether you build the HTTP request yourself or let the wrapper do it.

Common Mistakes

• Using the wrong device ID

• Querying a device you do not have access to

• Treating the latest health record as historical trend data

• Reading only the summary row when you actually need the raw healthJSON

Why This Matters

Health queries are usually the first operational API call after you start using the device list.

They let you answer questions like:

• Is the camera online?

• What is the latest battery and temperature state?

• Which devices need attention?

• Which devices are safe to include in the next automation step?

What Comes Next

The next post will cover historical device health data, which is what you use when you need trends, line charts, and time-based analysis instead of a current snapshot.