Log Driver GPS on Processed Route API

Require Authentication

This API is used to Log Driver GPS on Processed Route for the company based on combination of deviceID and token. This will be used as a raw data to create a polyline to be used in map.

URL

api/routes/gpslogging

Required parameter (POST)

deviceID
token
maintenanceScheduleID «contains maintenanceScheduleID. Value must exist in database. To get available maintenanceScheduleID, please visit Get Available Routes/Schedules»
maintenanceScheduleProcessID «contains maintenanceScheduleProcessID. Value must exist in database. To get available maintenanceScheduleProcessID, please visit Get Processed Route/Schedule List»
coordinate «array of object that contain latitude, longitude, and gpsTime»
longitude

Optional parameter

Example JSON Payload

{
  "deviceID": "ABCD-EFGH-IJKL-MNOP",
  "token": "c43fa596e7916827106b591e2bb026cd",
  "maintenanceScheduleID": 4,
  "maintenanceScheduleProcessID": 1,
  "coordinate": [{
    "latitude": -6.202315807343,
    "longitude": 106.781044006348,
    "gpsTime": 1482483077
  }, {
    "latitude": -6.202315807343,
    "longitude": 106.782043457031,
    "gpsTime": 1482583077
  }, {
    "latitude": -6.202315807343,
    "longitude": 106.782661437988,
    "gpsTime": 1482683077
  }, {
    "latitude": -6.202877044678,
    "longitude": 106.782661437988,
    "gpsTime": 1482783077
  }]
}

Possible return HTTP status code

Return message

{
  "status": "success",
  "message": 4
}

Note:
message contains number of successful coordinate that put in database

Superfy Platform API Documentation