• Monitor Tracking Open API
  • Getting Started
  • Core API Reference
  • Realtime Push

    • Monitor Tracking Open API

    Monitor Tracking Open API v2

    Open API v2 provides authenticated access to Monitor tracking data, including devices, latest status, BLE tire pressure and temperature/humidity sensor data, historical snapshots, alarm points, geofences, and realtime push for enabled accounts.

    Base URL
    https://openapi.tftiot.com/v2/
    Version
    v2


    Getting Started

    Authentication, token refresh, request format, timestamp rules, and rate-limit guidance.

    Read usage rules


    Core API Reference

    Detailed usage for auth, devices, latest status, BLE sensors, alarm points, smart locks, and geofences.

    View endpoints


    Realtime Push

    WebSocket registration and message handling for device status, BLE sensors, smart locks, alarms, and other enabled realtime data.

    View push usage

    Base URL and Version

    Item Value
    Production base URL https://openapi.tftiot.com/v2/
    API version v2
    Health check GET /v2/test
    Authentication POST /v2/auth/action

    Data Format

    • Authenticated requests include access-token in the query string.
    • JSON responses use code: 0 for success.
    • Time fields use 13-digit Unix epoch milliseconds.
    • Coordinates use latitude and longitude decimal degrees.
    • Use latlng_valid to decide whether a GPS point is reliable for map display.

    Rate Limits

    Rule Open API v2 behavior
    Request budget Keep requests to no more than 200 per 10 seconds for each source IP, URL path, and HTTP method.
    How requests are counted GET and POST use separate budgets. Query parameters do not create a new budget for the same path. Applications sharing one public IP also share its budget.
    Reset The server clears the count about every 10 seconds. Pace requests instead of sending the full budget in one burst.
    When exceeded The current application response can be HTTP 200 with an empty body, without a JSON error code or Retry-After header. Treat an empty body as a failed request, wait at least 10 seconds, then retry with backoff.

    For frequent device updates, use realtime push instead of repeated polling. Page through large historical results. Contact Topflytech support before planning sustained traffic near this budget.

    Endpoint Summary

    Endpoint Purpose
    POST /v2/auth/action Request an access token.
    GET /v2/devices List devices, metadata/configuration, and latest status snapshot.
    GET /v2/devices/{imei} Read one device by API device identifier.
    GET /v2/device-statuses Read lightweight current status records for realtime recovery, status refresh, and current BLE sensor values.
    GET /v2/tire-ble-mac Read BLE tire pressure sensor bindings, names, and tire slot positions.
    GET /v2/device-ble-temps Read BLE temperature/humidity sensor bindings, names, and alarm thresholds.
    GET /v2/snapshots Read historical location/status points.
    GET /v2/alarm-points Read alarm records by device and time range.
    /v2/alarm-policies List, create, update, and delete alarm policies for event types, assigned devices, active windows, and notification channels.
    POST /v2/device-lock-cards/action Send smart lock unlock commands, then confirm open or closed state from status, realtime push, or alarm records.
    /v2/geofences List, create, update, and delete geofences.