Skip to main content

Integrate Encompass Fleet Tracker with other telematics providers using our Open API Endpoints

Distributor steps to feed data from a non-Geotab/Samsara telematics provider into Encompass Fleet Tracker using Open API import endpoints for diagnostics, trips, safety events and faults. Requires v25.07+.

B
Written by Bailey Naas-Thornton

Minimum Version Required: 25.07

Pre-Conditions

  • Fleet Tracker Open API Endpoints ARE NOT intended for Geotab or Samsara integrations. If you with to integrate Encompass Fleet Tracker with Geotab or Samsara, please rearch out to your CSM.

Steps

  1. Add record on GPSAuthentications (API Provider is Other API)
    ​
    ​

  2. Add GPS Devices records
    ​
    ​

  3. Use the new API Endpoints to import data into Encompass. See Field and Definitions section for more details.
    ​
    ​

  4. Every minute, the Encompass system will automatically sync new imported data into Encompass Fleet Tracking core tables, which include OnBoard Diagnostics, Vehicle Trips, Vehicle Safety Events, and Vehicle Faults

Encompass Open API Endpoints for Encompass Fleet Tracker:

VehicleOnBoardDiagnostics_GPSData_Import

This is the raw telematics data that will bring the Fleet Tracker Dashboard to life.

Parameters:

  • EncompassID - Your Encompass ID

  • APICommand - VehicleOnBoardDiagnostics_GPSData_Import

  • Format - CSV, HTML, or JSON

  • APIToken - Contact Encompass support or your CSM for your token

  • Filename - optional name of file

  • File - header and data including SerialNumber, Speed, IgnitionOff Latitude, Longitude, Time, Mileage

Example:

https://api.encompass8.com/api?EncompassID=Pioneer2507&APICommand=VehicleOnBoardDiagnostics_GPSData_Import&Format=CSV&APIToken=abcdefghijklmnopqrstuvwxyz

SerialNumber, Speed, IgnitionOff Latitude, Longitude, Time, Mileage
​G86220F904BF, 25, 0, 33.4498558, -86.8494339, 2025/5/11 22:28:00, 100000

VehicleTrips_GPSData_Import

This is also required to bring the Fleet Tracker dashboard to life as this will have the trips data from your telematics provider.

Parameters:

  • EncompassID - Your Encompass ID

  • APICommand - VehicleTrips_GPSData_Import

  • Format - CSV, HTML, or JSON

  • APIToken - Contact Encompass support or your CSM for your token

  • Filename - optional name of file

  • File - header and data including Distance, DriveDuration, IdlingDuration, StartTime, StopTime, NextTripStartTime, Latitude, Longitude, SerialNumber, MaxSpeed, AvgSpeed, SeatBeltOn, StopDuration, Address

Example: https://api.encompass8.com/api?EncompassID=Pioneer2507&APICommand=VehicleTrips_GPSData_Import&Format=CSV&APIToken=abcdefghijklmnopqrstuvwxyz

Distance, DriveDuration, IdlingDuration, StartTime, StopTime, NextTripStartTime, Latitude, Longitude, SerialNumber, MaxSpeed, AvgSpeed, SeatBeltOn, StopDuration, Address
​25, 150, 10, 2025/5/11 22:28:00, 2025/5/11 22:33:00, 2025/5/11 22:36:00, 33.4498558, -86.8494339, G86220F904BF, 65, 23, 1, 10, "103 N Central Ave, Locust, NC 28097, USA"

VehicleSafetyEvents_GPSData_Import

Not required, but if included, this data will be available in Fleet Tracker Dashboard (exceptions) as well as the Fleet Reports library

Parameters:

  • EncompassID - Your Encompass ID

  • APICommand - VehicleSafetyEvents_GPSData_Import

  • Format - CSV, HTML, or JSON

  • APIToken - Contact Encompass support or your CSM for your token

  • Filename - optional name of file

  • File - header and data including ExceptionEventID，ActiveFrom, ActiveTo, Distance, Duration, RuleName, ForwardVideoUrl, InwardVideoUrl, TrackedInwardVideoUrl, IncidentReportUrl, IsDistracted, ActualSpeed, SpeedLimit, SerialNumber

Example: https://api.encompass8.com/api?EncompassID=Pioneer2507&APICommand=VehicleSafetyEvents_GPSData_Import&Format=CSV&APIToken=abcdefghijklmnopqrstuvwxyz

ExceptionEventID，ActiveFrom, ActiveTo, Distance, Duration, RuleName, ForwardVideoUrl, InwardVideoUrl, TrackedInwardVideoUrl, IncidentReportUrl, IsDistracted, ActualSpeed, SpeedLimit, SerialNumber

1, 2025/5/11 22:28:00, 2025/5/11 22:38:00, 10, 20, "Test, Exception", , , , , 0, 50, 70, G86220F904BF

VehicleFaults_GPSData_Import

Not required, but if included, this data will be available in Fleet Tracker Dashboard (exceptions) as well as the Fleet Reports (Engine Faults) library.

Parameters:

  • EncompassID - Your Encompass ID

  • APICommand - VehicleFaults_GPSData_Import

  • Format - CSV, HTML, or JSON

  • APIToken - Contact Encompass support or your CSM for your token

  • Filename - optional name of file

  • File - header and data including SerialNumber, FaultTime, DismissDateTime, AmberWarningLamp, DiagnosticName, FaultLampState, FaultState, MalfunctionLamp, RedStopLamp, FaultCount, ProtectWarningLamp

Example: https://api.encompass8.com/api?EncompassID=Pioneer2507&APICommand=VehicleFaults_GPSData_Import&Format=CSV&APIToken=abcdefghijklmnopqrstuvwxyz

SerialNumber, FaultTime, DismissDateTime, AmberWarningLamp, DiagnosticName, FaultLampState, FaultState, MalfunctionLamp, RedStopLamp, FaultCount, ProtectWarningLamp
​G86220F904BF, 2025/5/11 22:28:00, ,0, Engine fuel 1 injector metering rail 1 pressure, Active, Active, 0, 10, 0, 0

Best Practices

  1. Ensure that your Vehicles table has the correct GPS Device
    ​
    ​

  2. Set your default or most likely vehicle that will run each route on the Routes table. This will set the vehicle on the load sheet, however if the default vehicle is not correct on the route for a certain day, the vehicle on the loadsheet can be changed by editing the load sheet
    ​
    ​

  3. Automate #2 above with Vehicle Verification

Did this answer your question?