FleetUp API Docs
  1. Location
FleetUp API Docs
  • Quick Start
    • Your First API Call
    • Token Expiration
    • Rate Limit
    • Error Codes
  • API Reference
    • Introduction
    • Authentication
      • /token
      • Obtain JWT Token
    • Account & User & Device
      • /account-info
      • /users
      • /drivers/list
      • /devices
      • /devices/status
      • /devices/unlock
      • /devices/driver-overview
      • /devices/engine-hours
      • /devices/fuel-level
      • /devices/odometer
      • /devices/latest-ecu-data
      • /devices/{device-id}
      • /devices/{device-type}
      • /devices/{device-type}/details
      • /devices/{device-type}/history
    • Trips
      • /trips/history
      • /trips/ongoing-trips
    • Trip Share
      • /tripshare/live-eta
      • /tripshare/partners
      • /tripshare/share
    • Alerts
      • /alerts/summary
      • /alerts/history
      • /alerts/bulk-history
      • /fencealerts/fence-names
      • /fencealerts/geo-fencealerts
    • Location
      • Retrieve GPS data within a 24-hour time range
        POST
      • /gpsdata/device-last-location
        POST
      • /gpsdata/latest
        POST
      • /gpsdata/latest/4cj
        POST
      • /gpsdata/latest/5ta
        POST
      • /bulk-gpsdata
        POST
    • Maintenance
      • /maintenance/history
      • /maintenance/indicators
      • /maintenance/settings/indicators
      • /maintenance/settings/measurements
    • Reports
      • /reports/temperature-sensors
      • /reports/{report-key}
    • Geofence
      • Get all fences
      • Get fence detail
      • Retrieve geofence alerts
    • Others
      • /jobs
  • API Guides
    • Retrieve All Devices from an Enterprise
  1. Location

/gpsdata/latest/4cj

POST
/gpsdata/latest/4cj
This API will return the most recent gps data of the 4CJ/CT device for a given Account ID or Device ID. User can send either Account ID or Device ID as input to get data of all 4CJ/CT devices under an account or to get data of given 4CJ/CT device.

Request

Authorization
Add parameter in header
x-api-key
Example:
x-api-key: ********************
Header Params
token
string 
required
Access token which was generated earlier
Body Params application/json
acctId
string 
optional
Account ID
devId
string 
optional
Device ID
Example
{
    "acctId": "string",
    "devId": "string"
}

Request samples

Shell
JavaScript
Java
Swift
Go
PHP
Python
HTTP
C
C#
Objective-C
Ruby
OCaml
Dart
R
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request POST '/gpsdata/latest/4cj' \
--header 'token;' \
--header 'Content-Type: application/json' \
--header 'x-api-key;' \
--data-raw '{
    "acctId": "string",
    "devId": "string"
}'

Responses

🟢200成功
application/json
200 response
Body
status
number 
optional
response status (http status)
data
array [object {7}] 
optional
devId
string 
optional
Device ID
tmTime
number 
optional
GPS trigger time, UTC time zone, yyyyMMddHHmmss
acconTime
number 
optional
Vehicle Ignition time, UTC time zone, yyyyMMddHHmmss
lat
number 
optional
GPS data latitude, e.g. 142198116
Conversion to Decimal Degree format:
142198116 / 3600000 = 39.4994767 (Positive # = North, Negative # = South)
lng
number 
optional
GPS data longitude, e.g., -438079242
Conversion to Decimal Degree format:
-438079242 / 3600000 = -121.688678 (Positive # = East, Negative # = West)
speed
number 
optional
The value for instant speed, unit: cm/s, e.g. 2861
Conversion:
2861 * 0.036 km/h = 102.99 km/h
direction
number 
optional
The returned number is between 0 and 3600, e.g. 1311
Conversion:
1311/10 = 131.1
The direction of where the vehicle is driving toward. There are 360 degrees, with zero at the 12 o’clock position, increasing in clock-wise direction. For example:
0 = 12 o’clock 90 = 3 o’clock
e.g. 1311 will be 1311 / 10 = 131.1 (direction in between 4 o’clock and 5 o’clock)
Example
{
    "status": 0,
    "data": [
        {
            "devId": "string",
            "tmTime": 0,
            "acconTime": 0,
            "lat": 0,
            "lng": 0,
            "speed": 0,
            "direction": 0
        }
    ]
}
Modified at 2025-02-28 08:12:14
Previous
/gpsdata/latest
Next
/gpsdata/latest/5ta
Built with