Sign in

v1

latestOpenAPI 3.0.0Proprietary2026-08-06130577659.7 KB
Tracking|Tracker health

Perform detailed tracker health check

Retrieves comprehensive diagnostic information for a vehicle's tracker, including its current status and any detected issues. Useful for automated monitoring, maintenance scheduling, and installation validation.

Performs an anomaly check on tracker data to identify irregular or inconsistent tracking behavior. This endpoint analyzes recent tracker records to detect the following anomaly types:

Jumping Trackpoints – Indicates sudden, unrealistic jumps in location.

High Voltage Without Ignition – Detects elevated voltage levels when the ignition signal is off.

Voltage Drop / Possible Tampering – Detects sudden drops or interruptions in voltage that may indicate manipulation or wiring issues.

Tracker Not Sending Data – Missing or delayed transmissions for an extended period.

No Beacon Reception – The tracker is active but does not receive any beacons for an extended time.

Poor GPS Reception – Tracker shows consistently weak or unreliable GPS signal quality.

Poor GSM Reception – Weak or unstable mobile network signal strength.

Incorrect Permanent Power Wiring – No voltage is detected when the ignition is off, indicating the permanent power source may be incorrectly connected.

Time-Tracking Sensor Check – Verifies that all time-tracking sensors transmit data.

Hidden on Map View – The tracker is not visible on the map because the “show on map” option is disabled.

Excessive Data Transmission – The vehicle sends unusually high amounts of tracking data within a day.

Flickering Ignition Signal – Rapid, inconsistent changes in the ignition state indicating unstable or faulty wiring.

Missing Tachograph Data – Tachograph data is not being transmitted.

Missing Live / FMS Data – FMS data is not being transmitted.

get/tracker_health/check

Query parameters

vehicleIdinteger

The unique identifier of the vehicle whose tracker health should be checked.

daysinteger

The number of days to include in the health check analysis, counted backwards from the current date. For example, 7 means the tracker data from the last seven days (including today) will be evaluated. Use this parameter to control how far back the system should look for anomalies or communication issues. Default value (if omitted): 30 (data from the last 30 days).

Response

Success Response:

statusstring

Overall operational status of the tracker, derived from recent performance and signal data. Possible values:

  • OK → The tracker is fully operational, no issues detected.
  • WARNING → Minor irregularities detected that may require attention.
  • FAILURE → Major malfunction detected or tracker is not reporting correctly. This field is intended for automated monitoring systems to quickly classify tracker health.

Example response

{
  "issues": [
    {
      "lastOccurrence": "2015-02-20T12:59:21+01:00"
    }
  ]
}