DriverTech offers an API to allow Clients to use their own back end systems instead of or in addition to the FleetWatcher Web Portal.

This API, known as the FleetWatcher API, is comprised of secure enterprise ready Web Services hosted by servers and networks designed for high availability. The services included in the FleetWatcher API are based upon the same core types as defined in the XSD/WSDL ensuring consistency. Also included is verbose error and exception reporting to speed initial development and enhance the ability to resolve problems programmatically.

The Admin Service provides administrative operations for:

  • Drivers
  • Form Definitions
  • Reporting Group Assignments (used by FleetWatcher portal)


The Data Service provides communications and other information used on a daily basis by Company's TruckPC's, Drivers, Managers, etc for:

  • NEW in v2.1.14!! - Many operations now support querying by "ReceivedOn" (the DateTime the record was inserted or updated at the data center):
    • Deceleration details now avaialable
    • Workflow operations now available including option to "allowFormUpdates":
    • XMessage operations now available: Provides direct communication with an application on the TruckPC
  • NEW in v2.1.12!! JBUS Faults - Reporting of 1708 and 1939 via single operation (previously only 1708 was available via GetInboundMessages)
  • Messaging - Inbound/Outbound Freeform and Form (macros) are supported
  • Files - Inbound/Outbound Documents, DTScan batches, Third Party Applications, etc
  • HOS Logs - Hours of Service Logs optionally including PDFs
  • HOS Log Send Queue - Queuing and reporting of HOS Log information to Fax or Email
  • HOS Totals - Current Hours of Service Totals
  • HOS Unassigned Driving - Unassigned Driving events
  • Trailer Events - Reporting of Trailer Hook/Drop events
  • TruckPC Hardware Inventory - Reporting on current TruckPC operational detail (software version, cell number, etc)
  • TruckPC Status - Reporting on current TruckPC Status (location, power state, etc)
  • NOTE - These services expose previous versions of operations so care should be taken to implement the latest version of an operation. Contact us if there are any questions.
  • NOTE - x_ByIndex operations are prefered over counterparts when available (especially when continually polling data).
  • NOTE - The services support both Http and Https. Use your preference.
  • NOTE - Messaging Topic Filters "EventsVehiclePing" and "EventsVehicleStateLineCrossing" are deprecated as of Device v5.12+


The Reports Service provides all reporting capabilities including End of Day Rollup (EODR) raw data
For full specification of data elements see the End of Day Rollup Specification

  • Driver Performance
  • Vehicle Performance
  • DTScan