The Data Service provides communications and other information used on a daily basis by Company's TruckPC's, Drivers, Managers, etc
Feature specific documentation
- Include Destinations in an Outbound Message — Including one or more destination locations in an outbound message allows the Driver to route from their current location to the selected destination.
Browse the Service Description WSDL and Annotated XSDs
Recent Updates:
- NEW in v2.1.82 (02/28/2018)
- PDF Export processing enhancements to improve reliability and performance
- PreTrip Violations are now provided in RealTime via GetInboundMessages operation when request includes TopifFilter EventsHosAlertsOverride - see Driver Groups for Enabling and Configuration of PreTrip. Requires ELD v6.04+
Schema:
<- click to enlargeExample response:
<- click to enlarge
- NEW in v2.1.80 (10/31/2017) - NO BREAKING CHANGES are being made; All enhancements listed are accomplished via expansion of the xsd:anyType derivatives
GetInboundMessages InboundMessageResponse.Header.VehicleContextExt expanded to include current Fuel Levels and Lifetime Vehicle details at the time of the record
WorkflowEventExt expanded to include Fuel Levels and Vehicle Lifetime values at the time of the Event
FMCSA Mandate - HOSTotals4 expanded to included new fields added for Compliance of FMCSA Mandate: HasDiagnosticIndicator, UnderELDMalfunction
FMCSA Mandate - HOSLog4 expanded to included new fields added for Compliance of FMCSA Mandate:
HOSLogEvent: added event data to expose Status Change Auditing, Diagnostic Events, Intermediate Positions, etc
- HOSLog4StatusExt: InPersonalUse, HasPositionMalfunction, HasMalfunction, MilesSincePowerOn, SeqNumber, EngineTimeSincePowerOn, HasDiagnosticEvent, VIN
- HOSLog4StatusExtHistory: SeqNumber, Remarks
- TruckData: adds YardMiles, PersonalMiles
- FMCSA Configuration supported via Web Portal SystemSettings.DriverGroupSettings: AllowYardMoves, MaxYardMiles, MaxYardSpeed, EnableELDMode
- NOTE: EnableELDMode currently defaults to 'false' but will be changed to default to 'true' near Jan 2017
Deceleration - Expanded to include Yaw/Pitch/Roll values
TruckPCStatus: DEPRECATING in favor of VehicleStatus: DeepLoad is ignored, PatchesQueued no longer provided, FilesQueued no longer provided
- NEW in v2.1.60 (01/24/2017)
- HOSLog expansion of StatusType.Other to include new values for FMCSA Mandate in order to support new ELD v6.0 on the current/old operations (HosLog3, HosLog4)
- XSD Documentation generated into a web page (6 megabyte page!!) to make it easier to navigate for those who dont have access to a Graphical XSD viewer. This document is now referenced directly from services and includes links to the Annotated XSDs
- NEW in v2.1.58
- NEW in v2.1.56 (05/25/2016)
- HOSUnassignedDriving records provide detail of Vehicle movement when Driver was not Logged on and includes the Previous Driver as well as any Drivers logged on after the Unassigned Segment.
- HOSUnassignedDriving records provide detail of Vehicle movement when Driver was not Logged on and includes the Previous Driver as well as any Drivers logged on after the Unassigned Segment.
- NEW in v2.1.54 (05/10/2016)
- HOSLog4 Status Ext now contains the CoDriverId and CoDriverLogon. Soon we will also be adding the Drivers First and Last name as required by the new regulations
- NEW in v2.1.50 (04/15/2016)
- WorkflowEvents now include notification when a workflow is received by an ELD.
The WorkflowEvent value will be "other" and the extValue will be "WorkflowReceived", Here is an example xml response:
- WorkflowEvents now include notification when a workflow is received by an ELD.
- NEW in v2.1.49 (10/12/2015)
- InboundMessage.MessageHeader.VehicleContext will be populated on the following additional event types when ELD is running v5.48+
... If your application code is simply checking for VehicleContext==null then you dont have to make any changes as your application will automatically process the additional data when provided- Messaging.PositionState
Messaging.StarndardMessage
Events.VehicleEventStateLineCrossing
Events.DriverEventPerformanceSpeeding
Events.DriverEventPerformanceHardBraking
Events.DriverEventPerformanceOverRPM
Events.DriverEventPerformanceOverIdling
- InboundMessage.MessageHeader.VehicleContext will be populated on the following additional event types when ELD is running v5.48+
- NEW in v2.1.44 (05/26/2015)
- Ability to perform DVIR Updates.
- GetInboundMessages will provide HOS Mandatory Break Warning/Viloation alerts when the TopicFilter EventsHOSAlertOverride is explicitly included
- NEW in v2.1.40 - Many operations and types to support MOA, Fuel Purchases, Manual Mileage, HOS Logs and more:
- Multiple Operating Authority Support via:
- HosTotals4 - copy of HosTotals3 which now includes current Carrier and other detail
- HosLogs4 - copy of HosLogs3 which now includes list of Carriers used for each day and other detail
- Manual Mileage
- Fuel Purchases
- Trip Detail expanded to include Operating Authority
- HosTotals4 - copy of HosTotals3 which now includes current Carrier and other detail
- Manual Mileage
- Fuel Purchases
- Multiple Operating Authority Support via:
- 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 available
- Workflow operations now available including option to "allowFormUpdates":
- Architecture Overview: Workflow White Paper
- 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+
API Examples