FleetUp API Docs
  1. Alerts
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
        POST
      • /alerts/history
        POST
      • /alerts/bulk-history
        POST
      • /fencealerts/fence-names
        POST
      • /fencealerts/geo-fencealerts
        POST
    • Location
      • Retrieve GPS data within a 24-hour time range
      • /gpsdata/device-last-location
      • /gpsdata/latest
      • /gpsdata/latest/4cj
      • /gpsdata/latest/5ta
      • /bulk-gpsdata
    • 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. Alerts

/fencealerts/geo-fencealerts

POST
/fencealerts/geo-fencealerts
This API will return the GeoFence Alert action type. It requires the Account ID, Device ID and Start Date and Time as an input parameter. This API will return alerts within 24 hours range starting from startDate

Request

Authorization
Add parameter in header
x-api-key
Example:
x-api-key: ********************
Header Params
token
string 
required
Body Params application/json
acctId
string 
required
Account ID
devId
string 
required
Device ID
startDate
string 
required
Start Date and Time (UTC-0)
>= 14 characters<= 14 characters
Example
{
    "acctId": "string",
    "devId": "string",
    "startDate": "stringstringst"
}

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 '/fencealerts/geo-fencealerts' \
--header 'token;' \
--header 'Content-Type: application/json' \
--header 'x-api-key;' \
--data-raw '{
    "acctId": "string",
    "devId": "string",
    "startDate": "stringstringst"
}'

Responses

🟢200成功
application/json
200 response
Body
status
number 
optional
response status (http status)
data
array [object {6}] 
optional
devId
string 
optional
Device ID
acconTime
number 
optional
Vehicle Ignition time, UTC time zone, yyyyMMddHHmmss
fenceId
number 
optional
Fence ID
tmTime
number 
optional
GPS trigger time, UTC time zone, yyyyMMddHHmmss
alertAction
number 
optional
1 : Entering Fence, 2 : Exiting Fence
fenceName
string 
optional
Fence Name
Example
{
    "status": 0,
    "data": [
        {
            "devId": "string",
            "acconTime": 0,
            "fenceId": 0,
            "tmTime": 0,
            "alertAction": 0,
            "fenceName": "string"
        }
    ]
}
Modified at 2025-02-28 08:12:14
Previous
/fencealerts/fence-names
Next
Retrieve GPS data within a 24-hour time range
Built with