Telemetry
The API exposes location and signal data for your fleet, and detailed per-device telemetry for RC500 routers.
Fleet GPS and signal
Section titled “Fleet GPS and signal”GET /fleet/gpsReturns GPS locations together with location-aligned RF telemetry - the data behind the Fleet Map, including signal quality, coverage areas, and dwell information. Requires a bearer token, and availability and history depend on your billing plan.
RC500 device telemetry
Section titled “RC500 device telemetry”Per-device RC500 telemetry is served under the device path:
| Method | Path | Description |
|---|---|---|
GET | /api/rc500/:deviceId/telemetry/latest | The most recent telemetry snapshot |
GET | /api/rc500/:deviceId/telemetry/history | Telemetry over a time window |
Telemetry history
Section titled “Telemetry history”GET /api/rc500/:deviceId/telemetry/history?sinceMinutes=60&limit=1000| Parameter | Type | Description |
|---|---|---|
sinceMinutes | int | How far back to read |
limit | int | Maximum records |
kind | string | Optional filter for a telemetry kind |
These RC500 routes expose router-specific fields such as connection state, cellular signal, and system health.
Device-reported telemetry
Section titled “Device-reported telemetry”Devices report their own telemetry to POST /telemetry. This ingest path is used by managed devices, not by client integrations reading data.