Sensor readings¶

API call to get last values for all metering sensors and state values. Includes CAN, OBD, and fuel.

API actions¶

API base path: /tracker/readings.

list¶

Gets last values for all metering sensors and state values.

parameters¶

name	description	type	format
tracker_id	ID of the tracker (aka "object_id"). Tracker must belong to authorized user and not be blocked.	int	999199

examples¶

cURL

curl -X POST 'https://api.navixy.com/v2/tracker/readings/list' \
    -H 'Content-Type: application/json' \
    -d '{"hash": "a6aa75587e5c59c32d347da438505fc3", "tracker_id": 265489}'

HTTP GET

https://api.navixy.com/v2/tracker/readings/list?hash=a6aa75587e5c59c32d347da438505fc3&tracker_id=265489

response¶

{
  "success": true,
  "inputs": [
    {
      "value": 5.66,
      "label": "label",
      "units": "litres",
      "name": "fuel_level",
      "type": "fuel",
      "units_type": "custom",
      "update_time": "2023-03-16 11:15:19"
    }
  ],
  "states": [
    {
      "field": "obd_mil_status",
      "value": 12345.23,
      "update_time": "2023-03-16 11:15:19"
    }
  ],
  "virtual_sensors": [
    {
      "label": "Virtual Ignition",
      "value": "On",
      "type": "virtual_ignition",
      "update_time": "2023-03-21 20:49:41"
    },
    {
      "label": "Hood state",
      "value": "Closed",
      "type": "state",
      "update_time": "2023-03-21 20:48:40"
    }
  ]
}

states.value - can be string, int, float, boolean, or null.

errors¶

204 – Entity not found - if there is no tracker with such ID belonging to authorized user.
208 – Device blocked - if tracker exists but was blocked due to tariff restrictions or some other reason.

Last update: March 21, 2023