Read Telemetry Data
Overview
This tutorial walks through the 3-Telemetry Postman collection. You will check and update sensor settings, retrieve historical data points, and read the latest values using both a user token and an M2M token.
Prerequisites
- Completed Get Access Token —
accessTokenis set - Completed Register Your Device —
deviceIdis set dataObjectIdis set — required by Data Points Historical Get and Data Object Blob Get. It is not auto-captured; get it from Get device data objects in the2-Provisioning&Activationcollection (see Device Data Definitions) and set it in your environment.- (Optional) Completed M2M Access —
cc_access_tokenis set (required for the client-token request only)
Requests in This Collection
These requests are independent — there is no required order. Run whichever fits your need.
Sensor Settings
Sensor Settings Get
Retrieves the device's current telemetry configuration — which sensors are enabled and at what collection frequency.
- API: Get Telemetry Configurations
- Result:
200 OK— the current telemetry config for the device
Sensor Settings Change
Updates the telemetry configuration for the device. Fill in the request body with the settings you want to change (e.g. sampling interval, enabled sensor list).
- API: Update Telemetry Configurations
- Result:
200 OK
Data Points
Data Points Historical Get
Retrieves historical data points for a specific Data Object (dataObjectId) within a time range.
- API: Get Historical Data Points
- Result:
200 OK— up to 1,000 data points within the time window
The pre-request script automatically sets startTime to 60 minutes ago and endTime to 1 minute from now — you do not need to fill in any time values manually.
To use a custom range, open the request's Pre-request Script tab and adjust the time calculation directly.
Data Points Latest Get by User Token
Retrieves the most recent value for every data object on the device, authenticated with accessToken (your interactive login token).
- API: Get Latest Data Points
- Result:
200 OK— one latest value per data object
Data Points Latest Get by Client Token
Retrieves the same latest values, but authenticated with cc_access_token (your M2M token) instead of the user token.
- API: Get Latest Data Points
- Result:
200 OK— same result as the user token variant, authenticated withcc_access_token
This request demonstrates that M2M tokens have the same read access as user tokens for telemetry data. This is the pattern used by automated services and backend pipelines — no human login required.
Data Object Blob Get
Downloads a binary value (e.g. image, waveform buffer) stored for a Data Object under a specific
blob key. Requires dataObjectId and blobKey.
- API: Download Binary Data
- Result:
200 OK— the binary payload for the requested blob key
Related
- M2M Access — how to obtain
cc_access_token - Deploy Container Stack — next step in the collection sequence
- Data Engine — API reference for data objects and transfer functions