Tracker is one of the key entities in our API. It represents tracking device registered in our GPS monitoring system. Lots of API calls are created for manipulation of tracker and/or its properties.

Tracker object structure

    "id": ${int},        // tracker id aka object_id
    "label": ${string},  // tracker label
    "clone": ${boolean}, // true if this tracker is clone
    "group_id": ${int},  // tracker group id, 0 if no group
    "avatar_file_name" : ${string}, // optional. passed only if present
    "source": {
        "id": ${int},             // source id
        "device_id": ${string},   // aka source_imei
        "model": ${string},       // tracker model name from "models" table
        "blocked": ${boolean},    // true if tracker was blocked due to tariff end, etc.
        "tariff_id": ${int},      // id of tracker's tariff from "main_tariffs" table
        "status_listing_id": 102, //id of the status listing associated with this tracker, or null
        "creation_date": "2011-09-21",
        "tariff_end_date": "2016-03-24", // date of next tariff prolongation or null 
        "phone" : ${string}       // phone of the device. can be null or empty if device has no GSM module 
                                  // or uses bundled SIM which number is hidden from the user

If you have more questions please contact our support team

Contact Us

USA: +1 858 815 9045

Mexico: +52 334 1642158

UK: +44 808 1641499

France: +33 644 605141

Germany: +49 157359 88250

Russia: +7 495 317 1622

Log in