OnlineAVL2 v3.6 Published Interface
OnlineAVL2 v3.6 Published Interface
v3.6
USER DOCUMENTATION
3.6 7 Jul 2016 Updated to include new event sub-types for Gopinath
Qube 300 firmware upgrade start/end. Sundharam
3.7 7th Nov 2016 Updated to include all of the new methods Jonathan Bailey
added as part of the HOS/DVIR PI update
which added PI V2.0 to AVL2 16-4. Updated
table of contents.
th
3.8 25 July 2017 Updated GetPeriodActivity and Sachin Patil
GetVehicleSnapshots methods for Input
and Output parameters to include sensor
temperature details. These changes are
part of PI V2.1released as part of DIRECTOR
17-1-SP2 release
th
3.9 15 December Added notes about current status of Murtaza Tinwala
2017 GetPeriodActivityEx method and
discontinued support for
“PreviousCallEndTime” parameter
th
4.0 14 June 2018 Updated to include the new Simon Crick
GetSafetyAnalyticsEvents method added in PI
V2.4.
4.0 14th August Added notes about Workflow – Deepthi Kendyala
2018 “GetPlanTemplates” and “ImportPlan”
API’s
5.0 14TH November Added notes about v2.6 GetPeriodActivity Murtaza Tinwala
2018
6.0 15th February Added notes for v2.7 GetPeriodActivity and Murtaza Tinwala
2019 GetVehicleSnapshots new field
“VehicleActivityName”
7.0 29th April Add notes for v2.8 GetVehicleTypes, Deepthi Kendyala
2019 SetVehicleDetails new field
8.0 21st May 2019 Added notes for v2.8 "GetDrivers ", Sachin Patil
"GetHOSDrivers", "AddDriverByType",
"EditDriverInfo" for new field
“RestrictLogonPINInUse”
rd
9.0 23 May 2019 Adding CredentialExpiryDate parameter in Deepthi Kendyala
EditDriverInfo Method
9.1 2nd Sept 2019 Adding section for v2.9 and a section for Jon Bailey
the new method ‘GetHOSDayTimers’.
Minor alterations to outdated
‘GetHOSTimers’ information.
9.2 3-Oct-2019 Adding section for v3.0 and a section for Chuyen Dong
the new methods ‘GetELDDriverDailyLogs’,
‘GetUserHeaders’,
‘GetCarrier’,’DoAssignUserToVehicle’,
‘DoAssignUserToGroup’ and
Modified method ‘GetHOSDrivers’
9.3 17-Feb-2020 Adding section for v3.1 and a section for Chuyen Dong
the new methods ‘CreateVehicleGroup’ and
‘DeleteVehicleGroup’
9.4 29-June-2020 Adding section for v3.2 and s section for Chuyen Dong
the new APIs ‘GetELDProductInfo’,
‘GetELDUnassignedDriveTime’ and
‘GetELDDriverLogEditRecords’. Modified the
API ‘GetELDDriverDailyLogs’ to include the
Yard Move and Personal User statuses
9.5 22-Sep-2020 Fixed the Active flag of the UpdateOwner Chuyen Dong
API and added the descriptions of this API
in this document.
2-Nov-2020
Added the Hire Date field in the GetDrivers;
GetHOSDrivers; AddDriverByType and
EditDriverInfo APIs
9.6 22-Feb-2021 Added Chuyen Dong
the MobilePhone and LastPinLogindateTim
e. The RFID Pin is filled in the DallasKeyPin
9.7 30-Mar-2021 - Added server-side threshold to limit Sachin Patil
data extraction of existing PI method
“GetSentFormsStatus”.
- Added new PI method
“GetSentFormsStatusHistorical”
9.8 14-Apr-2021 Added new GetGPSHistoryByVehicle API Chuyen Dong
Copyright
Copyright © 2009 - 2021 Teletrac Navman Ltd
All rights reserved.
No part of this publication may be reproduced, stored in a retrieval system, of transmitted in any form
or by any means, electronic, mechanical, photocopying, recording or otherwise without the prior
written permission of Teletrac Navman Ltd.
This document is the property of Teletrac Navman Ltd and may not be disclosed to a third party, other
than to any wholly owned subsidiary of Teletrac Navman Ltd, or copied without consent.
Table of Contents
INTRODUCTION.................................................................................................................................................... 11
V 3.6:.................................................................................................................................................................................. 11
V 3.5:.................................................................................................................................................................................. 11
V 3.4:.................................................................................................................................................................................. 11
V 3.3:.................................................................................................................................................................................. 11
V 3.2:.................................................................................................................................................................................. 11
V 3.1:.................................................................................................................................................................................. 11
V 3.0:.................................................................................................................................................................................. 11
V 2.9:.................................................................................................................................................................................. 12
V 2.8:.................................................................................................................................................................................. 12
V 2.7:.................................................................................................................................................................................. 12
V 2.6:.................................................................................................................................................................................. 12
V2.5:................................................................................................................................................................................... 13
V2.4:................................................................................................................................................................................... 13
V2.3:................................................................................................................................................................................... 13
V2.2:................................................................................................................................................................................... 13
V2.1:................................................................................................................................................................................... 13
V2.0:................................................................................................................................................................................... 13
V 1.9:.................................................................................................................................................................................. 14
V 1.8:.................................................................................................................................................................................. 14
V 1.7:.................................................................................................................................................................................. 14
V 1.6:.................................................................................................................................................................................. 14
V 1.5:.................................................................................................................................................................................. 14
OVERVIEW............................................................................................................................................................ 14
This document provides an overview of the Teletrac Navman Published Interface and detailed
notes on usage and technical features.
The Published Interface web-methods and usage information discussed in this document are
relative to the 21.2 version of the Teletrac Navman system.
Version History
V 3.6:
Added a new GetGPSHistoryByVehicle API to get the High Definition data.
V 3.5:
1. Added server-side logic to extract maximum last 1 year data of existing PI method
“GetSentFormsStatus”. No changes are needed from PI consumers of this OLD PI method
for this change to reflect. This change is applicable to OLD PI versions also.
2. Added new PI method “GetSentFormsStatusHistorical” to allow PI consumers to specify
start date and end date to which data is to be fetched. MaximumDataFetchHoursWindow
is set as standard 24 hours and MaximumDataHistoryDaysWindow is set as upto recent 1
year (356 days).
V 3.4:
3. Added MobilePhone, LastPinLogin DateTime in the GetDrivers(), Filled in the RFID Pin in
the existing field DallasKeyPin.
V 3.3:
1. Fixed the Active flag of the UpdateOwner API and added the descriptions of this API in this
document.
2. Added Hire Date in the GetDrivers(), GetHOSDrivers(), AddDriverByType() and
EditDriverInfo()
V 3.2:
1) New PI GetELDProductInfo(), GetELDDriverLogEditRecords()and GetELDUnassignedDriveTime()
methods have been added.
2) Modified the GetELDDriverDailyLogs to include the Yard Move and Personal Use statuses.
V 3.1:
3) New PI CreateVehicleGroup() and DeletVehicleGroup() methods have been added
V 3.0:
4) New PI Method GetELDDriverDailyLogs() has been added. It is similar to the
GetHOSDriverDailyLogs() with additional ELD data.
5) New PI Method DoAssignUserToVehicle() has been added. It returns the status message
success or fail. If it fails, it will return a list of the vehicles that have failed during the
assignment process.
6) New PI Method DoAssignUserToGroup() has been added. It returns the status message
success or fail. If it fails, it will return a list of the vehicle groups that have failed during the
assignment process.
7) New PI Method GetUserHeaders() has been added. It returns list of users from the owner
8) New PI Method GetCarrier() has been added. It returns a short carrier information that
Published Interface User Documentation 30-Mar-2021 Page 11
/362
includes the US DOT number.
9) Modified PI Method GetHOSDrivers() to return additional ELD information – ELD Exempt
and ELD account type
V 2.9:
1) New PI Method GetHOSDayTimers() has been added. It is similar to the GetHOSTimers()
method which was introduced in v2.0, only GetHOSDayTimers() will be returning ‘day
based’ timers rather than ‘shift based’ timers. Both methods are returning some other
additional information that is exclusive to each method.
V 2.8:
1) New PI method GetVehicleTypesByOwner() is added and SetVehicleDetails () have extra
request parameters “Make”, “Model”, “Color”, “Year”, “Group”, “VehicleType”,
“VehicleClassID”, “Country”, ”State”
V 2.7:
2) PI methods GetPeriodActivity() and GetVehicleSnapshots() both now have an extra
request parameter “IncludeVehicleName”. If this parameter is set to true, the response
data element “VehicleName” would be populated. If it is set to false (which is default),
“VehicleName” field in response would be empty.
V 2.6:
1) PI method GetPeriodActivity() has been enhanced to fix TFS 201400 and include
additional features of GetPeriodActivityEx(). GetPeiodActivity v2.6 now handles out-of-
order (late arriving) events in a better way. In past, out-of-order events used to cause
problem in max version calculation. Presence of out-of-order events in a time window
would cause on-time events to get filtered in next time window because of wrong
elevated versions. This problem has been fixed. Following are the changes in v2.6
GetPeriodActivity.
1. GetPeriodActivity v2.6 response XML element “VehicleActivity” now includes
“OutOfOrder” Boolean field. It will be true for late arriving out-of-order events.
2. The version 2.6 supports a new parameter in request – “IncludePrivateEvents”. This
parameter has been added to merge functionality of “GetPeriodActivityEx” with
“GetPeriodActivity”.
3. Integrators using “GetPeriodActivityEx” can migrate to v2.6 “GetPeriodActivity” to
have TFS 201400 resolved. The GetPeriodActivityEx request will need to be adapted
to match GetPeriodActivity. Following table shows how parameters need to be
adapted.
GetPeriodActivityEx GetPeriodActivity Comment
parameter parameter
OwnerId Ids Add OwnerId in
array “Ids"
PreviousCallEndTime N/A Discard it
N/A IncludePrivateEvents=true
N/A RequestType=Owner
Published Interface User Documentation 30-Mar-2021 Page 12
/362
Rest of the parameters are directly compatible and remain unchanged.
4. Integrators using “GetPeriodActivity” can use v2.6 to have TFS 201400 resolved
directly without any changes.
5. The new version may return some events that have already been returned in
previous calls. This will happen only if there are late arriving events returned in
previous calls. This can be verified using “OutOfOrder” field.
V2.5:
V2.4:
V2.3:
1. New APIs added for Workflow feature viz. GetPlanTemplates, ImportPlan,
GetWorkflowTaskSettings, GetWorkflowTaskUpdates.
This PI version is part of 18.1 release.
V2.2:
2. Updated GetPeriodActivity, GetPeriodActivityEx and GetVehicleSnapshots to include
calibration data for OdoMeter. This PI version is part of 17.3 release.
V2.1:
3. Updated GetPeriodActivity and GetVehicleSnapshots methods for Input and Output
parameters to include sensor temperature details. The PI version 2.1 is part of AVL 17-1-
SP2 release
V2.0:
4. Added a number of different HOS/DVIR methods including: AddDriverByType(),
UpdateHOSDriverInfo(), GetHOSDriverDailyLogs(), GetHOSDriverLogEditRecords(),
GetVehicleDVIR(), UpdateDVIRByMechanic(), GetVehicleEngineHours(),
GetHOSDrivers(), GetHOSProfileTables(), GetHOSTimers(), GetDriverVehicleTables().
V 1.8:
1. Added a new method GetFleetDiagnostics method to accommodate a new diagnostic
message from Teletrac TM4xxx to support J1708, J1939, J1979 and J1850 JBUS protocols
2. Added additional fields to GetEMSPeriodActivity method to support TM 4xxx units
additional fields in the End Of Trip message
V 1.7:
1. DoSendRouteMessage() & DoSendRouteMessages() request parameter is modified to
accept ReplyToSentDateTime.
V 1.6:
1. GetPeriodActivityEx() supports business + private events. Refer to Issue 73313 in TFS.
2. Forms API (GetFormsDetails and GetFormListDetails) supports signature field
V 1.5:
1. GetPeriodActivityEx() added for LDV-62062. Also includes changes for LDV-79758. No
other changes.
Your Regional Support office will vary depending on your geographic region. Please visit
www.navmanwireless.com for details of your support office.
Overview
The Published Interface is designed to provide programmatic access via the internet to the
Teletrac Navman Vehicle Tracking and Fleet Management product. This document is aimed at
both business and technical users to allow you to understand what information is available via
the Published Interface.
To cater for these different audiences, this document will provide the following:
6. Data and functionality available through the Published Interface
7. Security and Access to the Published Interface functionality
8. How usage of the Published Interface is monitored and controlled
9. Recommended Usage to get the most from the Published Interface
Usage of the Teletrac Navman Published Interface is monitored and controlled using throttling
techniques to ensure consistent and acceptable usage across all users of the interface.
Not all information returned via the Published Interface will be of interest to the consumer so
please consult the technical details section to validate fields and what information they supply.
Published Interface Versioning
From AVL2 Release 12.2 onwards, the Published Interface is version controlled.
Once a version has been released, no further changes will be made to it, including:
10. No new method calls
11. No changes to any data structures used by any method calls
12. No new data types or event types will be returned
Customers who wish to avail themselves of new features must upgrade to later versions.
Versions
These versions exist:
13. Version 1.0 Published Interface - released with AVL2 12.1 and prior, available at
https://ServerName/OnlineAVL/API/V1.0/
14. Version 1.1 Published Interface - released with AVL2 12.2, available at
https://ServerName/OnlineAVL/API/V1.1/
15. Version 1.2 Published Interface - minor update for AVL2 12.3, available at
https://ServerName/OnlineAVL/API/V1.2/
16. Version 1.3 Published Interface - minor update for AVL2 13.1, available at
https://ServerName/OnlineAVL/API/V1.3/
17. Version 1.4 Published Interface - minor update for AVL2 13.2, available at
https://ServerName/OnlineAVL/API/V1.4/
18. Version 1.5 Published Interface - minor update for AVL2 14.1, available at
https://ServerName/OnlineAVL/API/V1.5/
19. Version 1.6 Published Interface - minor update for AVL2 14.2, available at
https://ServerName/OnlineAVL/API/V1.6/
20. Version 1.7 Published Interface - minor update for AVL2 15.1, available at
https://ServerName/OnlineAVL/API/V1.7/
21. Version 1.8 Published Interface - JBUS update for AVL2 16.1 to support TM units,
available at:
https://ServerName/OnlineAVL/API/V1.8/
22. Version 1.9 Published Interface - VPOD update for AVL2 16.2, available at
https://ServerName/OnlineAVL/API/V1.9/
23. Version 2.0 Published Interface - New HOS and DVIR related methods for AVL2 16.4,
available at
https://ServerName/OnlineAVL/API/V2.0/
24. Version 2.1 Published Interface – Temperature sensor details information available
as part GetPeriodActivity and GetVehicleSnapshots methods.
https://ServerName/OnlineAVL/API/V2.1/
25. Version 2.2 Published Interface – GetPeriodActivity, GetPeriodActivityEx
and GetVehicleSnapshots to include calibration data for OdoMeter.
https://ServerName/OnlineAVL/API/V2.2/
https://ServerName/OnlineAVL/API/V2.3/
https://ServerName/OnlineAVL/API/V2.4/
https://ServerName/OnlineAVL/API/V2.5/
31. Version 3.0 Published Interface – New GetELDDriverDailyLogs method, available at:
https://ServerName/OnlineAVL/API/V3.0/
However, users may choose to upgrade to later versions to take advantage of new features or
new events.
In order to upgrade:
The URL for the desired version of the Published Interface must be correctly specified in
the client application
The client application may need to be enhanced to use the new methods or consume new
events made available in the desired version
The end user application may need to be recompiled, if written in a programming
language that requires compilation.
Published Interface Functionality and Data
The Published Interface to the Teletrac Navman system consists of a set of web-methods made
available over the internet to authenticated users of the Published Interface. The Published
Interface provides the ability to send information to and retrieve information from the Vehicles
connected to the Teletrac Navman system. Specifically, this version of the Published Interface
provides the following functionality:
Similarly, any temperature information fed into the system or output from the system will be in
Celsius and has to be converted if it has to be displayed in other formats like Fahrenheit.
Security is present on all calls to the interface. Security is implemented by way of a time-based
token. This token is mandatory for all calls into the Web Methods made available via the
Published Interface. All calls via the Published Interface are checked, and may be recorded and
traced using this token.
The following methods are used to gain access to the system once you have received your
username and password:
1
The Method accepts a list of vehicles if information on more than one vehicle is required
for the same time period
2
The Method accepts an ActivityLogId as a key input parameter. The ActivityLogId is
returned from the GetPeriodActivity method
Specific Units are used for certain fields returned by the EMS web-method:
The following Method provides access to EMS Data in Teletrac Navman application:
3
The Method accepts a list of vehicles if information on more than one vehicle is required
for the same time period
4
The Method accepts a list of vehicles if information on more than one vehicle is required
for the same time period
To implement this, some usage and data thresholds have been established. It is important that
all developers who use the Published Interface are fully conversant with these thresholds and
adapt their system to work with them:
Usage Thresholds
Usage thresholds are in place to monitor and maintain the load on the system and ensure
consistent and acceptable service for all users of the Published Interface. Thresholds are in
place which limits the number of active sessions as well as how those sessions are used.
Maximum Sessions
Each Published Interface User has a maximum number of sessions they can have active at any
one time. This limit is set to 5. To ensure this limit is managed, best practice is to ensure that
every session is actively logged-out using the DoLogout method.
Note – there is an active process running which removes sessions that have been inactive for
more than 60 minutes
Maximum Calls
Each Published Interface User can make a maximum number of calls in a 60 second period. This
limit is set to 10.
Note – if a user has concurrent sessions running, the number of calls made by all concurrent
sessions for this user will be aggregated and measured against this limit
Data Thresholds
When accessing historical data thresholds have been established to ensure acceptable and
consistent usage. For specified Methods the following rules are in place:
The maximum period in which data is available is the last 8 days
Within this 8 day window, data can only be fetched for a maximum of 24 hours
Within this 24hr period, only 900 rows of data are returned for any given call.
Should more than 900 rows of data be required, subsequent calls should be made
to extract the remaining data
Take the example below. The current date is 16th December 2008 and the User wants to get all activity
data for 12th December:
th
8 Dec
2008
th
9 Dec
2008
th MoreItemsAvailable Version
Rows
10 Dec
900 TRUE 14003
2008
th 2
11 Dec Rows MoreItemsAvaila Version
2008
th 200 FALSE 16813
12 Dec 4
2008
th
(1100 Rows)
13 Dec
2008 GetPeriodActivity 1
th
14 Dec GetPeriodActivity 3
2008
th
15 Dec
2008
Figure 1 : Extracting more than 900 rows of data via 2 Method calls
With the thresholds in place, the following steps are required to retrieve all the required data. For
simplicity only the key parameters are shown – the call to the web method would contain a
number of other parameters as well:
1. Call the Web-method specifying the period required, using the default
version number of 0 (zero) – this will get all rows of data up until the 900 limit
2. Collect the result set and note the setting of
MoreItemsAvailable
Version
3. If the MoreItemsAvailable flag is set to TRUE, then the period specified contains
more than the limit of 900 rows. Call the Web-method again with the same
parameters as in Step 1, but this time specify the version number returned in the
previous call.
4. Collect the result set and note the setting of MoreItemsAvailable which should be
FALSE if all data is successfully returned to the Client.
5. Data threshold parameters have been added related to Forms API. These
parameters restrict request and response data. Defined parameters is as follows:
a) MaxFormDefinitions: This will specify maximum number of form definitions
can be retrieved or request in any call. Default value is 25. The following
web- methods have this data threshold in place:
GetFormListDetails : API has restriction on form definition requested and
returned.
o User request form definition with owner id only then response
has form definitions for given owner id. Maximum form
definitions returned is restricted to “MaxFormDefiniton”.
o User can request specific form definitions by specifying
DefinitionNumber list in request. Maximum requested
DefinitionNumber list restrict to “MaxFormDefinition”.
As methods are called and executed via the Published Interface a range of other error messages
will be reported. This list can be found in Appendix 4.
To represent the XML schema of each message, tables have been used. Each method will
contain one table outlining the various input parameters to be used with the method. A
separate table(s) will be used to detail the output parameters. Where an XML message
contains nested XML attributes, a separate table is provided to document the detailed
descriptions each attribute.
The WSDL provides a summary overview (Figure 1) and detailed web-service definitions (Figure
2). The WSDL is SOAP 1.1 and SOAP 1.2 compliant.
DoLogin
Use to authenticate your username and password with the Published Interface. The method
will return a Session Id (token) with which all future calls to methods must be made
Input Parameters
Output Parameters
The Session Id returned by the method is not persistent and will expire in 60mins if not used.
To avoid a session timeout actively calling the methods in the Published Interface will reset the
expiration period to 60mins.
The Session Id returned is only valid for the server IP address from where it was requested. It
cannot be saved and used by another PI client on another machine. Each machine that
interfaces with the Published Interface must request its own Session Id.
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
DoLogoff
Used to disconnect the Session Id from the Published Interface
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetOwners
This method provides information on the Owners (Fleets) that the username has access to
Input Parameters
Output Parameters
UpdateOwner
This method updates information on the Owner (Fleet). Before using this method, it
recommends to call the GetOwners API to get the existing information on the Owner and make a
change on the desired field. The fix of this method in the v3.3 is the Active flag to activate or
deactive the Owner (Fleet).
Note: The PI user must have the Published Interface Admin User role to use this method.
(*) the field is required.
Input Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetDrivers
This method provides information on the Drivers that the username has access to
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetVehicles
Provides a list of Vehicles for a given owner / fleet e.g. Default Driver, Display Name,
Description, Registration, Vehicle Group etc.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetVehicleSnapShots
Provides the current status of all the vehicles belonging to a specified owner / fleet e.g.
Longitude, Latitude, Speed, Driver Id etc.
Input Parameters
Parameter Type Definition
Version Long The starting point of versioned data – pass in 0 to start from first
record
SessionId Guid Valid session returned from DoLogin method
OwnerId Guid Owner (Fleet) for which vehicle(s) attributes are required
MaximumSeri Enumeration (Optional) The maximum event sub type understood by the client. If
alizableEventS not supplied, it defaults to
ubType SMDP_EVENT_TEMPERATURE_SETPOINT_IN_BOUNDS_MESSAGE,
which was introduced in AVL 11.1.
If supplied, all event sub types up to, and including the specified
MaximumSerializableEventSubType are returned.
FetchTempera Boolean When value of this flag is set to true, latest temperature values of
tureData active sensors (if available) of the respective vehicle will returned as
part of response. When set to false, SensorDetail property won’t be
present in the response. See SensorDetail property of response
object.
IncludeVehicl Boolean Available in v2.7 and above. When set to true, response would
eName include vehicle display name. When set to false (default), vehicle
display name will not be returned.
Output Parameters
TemperatureDateTime DateTime Date & Time (in UTC) when the event was
recorded.
The Vehicle Snapshot information contains a number of detail fields. These fields are also
returned in the GetPeriodActivity method and are described there.
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetVehicleTypesByOwner
This method provides information about VehicleTypes available in the fleet
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetPeriodActivity
This method provides detailed information on all the specified vehicle(s) 1 e.g. Longitude,
Latitude, Speed, Driver Id etc. for the specified period. This method extracts significant
numbers of records and could be used inappropriately and impact your use of the Published
Interface. Please see the Recommended Usage section for appropriate ways to use this
method.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetGPSHistoryByVehicle
This method provides High Definition data points on the specified vehicle. This method
extracts significant numbers of records and could be used inappropriately and impact your
use of the Published Interface. The recommendation is to set one day max between the
StartTime and EndTime.
Input Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetHardwareDetails
This web method gets the collection of the serial number and other hardware details of the
device for all the vehicles under the specified Owner.
Input Parameters
Output Parameters
Usage Notes:
Pass all the mandatory parameters.
Vehicle ID is optional input parameter. Based on Vehicle ID parameter is passed or not, the
hardware details will be returned in following ways.
And in case, there are more than 900 vehicles then first 900 vehicles are retuned with the
MoreItemsAvailable output parameter is returned as ‘true’.
a) User must read the value of Version output parameter as well. Version parameter
specifies the timestamp that should be used as a starting point to retrieve subsequent
records.
b) Then to fetch the next 900 records, call the same method again by passing the Version
as input parameter which was read from the response of previous call in step a.
GetMessages
This method will return all text messages sent from vehicles for a specified fleet in a specified
time period. Although this method will not extract the volumes of data the GetPeriodActivity
method will extract, it is important that it is used appropriately – see the The SOAP packets that
are sent and received as part of this Method are provided in the WSDL.
DoSendForms
DoSendForms allows one or more Form Instances to be sent to one or more vehicles. This API is
also performing following validations on service side:
1) Validate whether form feature is enabled on all recipients
2) Validate whether form is sent according to latest form definition
3) Validate filled form for each of its field against the latest form definition
4) Validate whether form is not sent by driver
Note: In case a form has signature fields this API doesn’t support sending signature fields to the
MNav. If you still want to send such forms keep the Value field in SignatureFieldValue class
empty.
Input Parameters
Field value types supported by form feature and their respected classes are as follows:
Field Value Type Class Name
Decimal DecimalFieldValue
String StringFieldValue
Address AddressFieldValue
Date DateFieldValue
Time TimeFieldValue
DateTime DateTimeFieldValue
Select SelectFieldValue
Checkbox CheckBoxFieldValue
Signature SignatureFieldValue
While sending forms, the field value collection (BaseFieldValue[ ]) of form would be filled with
objects of field value types mentioned above. The type of field value class while filling up field
value collection of form can be derived by form definition which is being used to send a
particular form. Detailed explanation for each of field value class as follows:
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
Samples
Click here for navigating to samples
GetSentFormsStatus
GetSentFormsStatus retrieves the status of one or form instances sent to one or more vehicles.
It would return form instance latest statuses’ along with all its previous status changes with
their timestamps. Possible statuses are as follows:
- Not received by driver
- Received by driver
- Read by driver (if read receipt is enabled).
If latest status for one of form instance sent to particular vehicle is “Read by driver” then
response would return in following order of status changes along with their timestamp when
they got changed:
1) Read by driver
2) Received by driver
3) Not received by driver
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
Samples
Click here for navigating to samples
GetSentFormsStatusHistorical
GetSentFormsStatusHistorical retrieves the status of one or more form instances sent to one or
more vehicles by specifying lower and upper boundaries of sentdatetime in the request. It
would return form instance latest statuses’ along with all its previous status changes with their
timestamps. Possible statuses are as follows:
- Not received by driver
- Received by driver
- Read by driver (if read receipt is enabled).
If latest status for one of form instance sent to particular vehicle is “Read by driver” then
response would return in following order of status changes along with their timestamp when
they got changed:
4) Read by driver
5) Received by driver
6) Not received by driver
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
AssignToVehicleGroup
Method will assign the vehicle to the given vehicle group display name. Vehicle group
display name is unique across the owner/fleet. Following is the detail of the method:
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
UpdateVehicleCustomStatus
UpdateVehicleCustomStatus is used to update custom status for vehicle. User will use this
method to manage custom status for vehicle. Following is the detail of the method:
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
SendMNavMessage
SendMNavMessage is used by Third Party services to communicate with Third Party
Applications which are installed on the M-NAV. For this API to be successfully used, the
Third Party application must be installed and enabled on the target M-NAV.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetPeriodActivityEx
This method is very similar to GetPeriodActivity() with few differences for addressing late
arriving data. This method was specifically added to resovle LDV-62062. The limitation with
GetPeriodActivity() is that it can miss some lower versions activities when a consumer supplies
an elevated “Version” parameter due to late arriving data present in result set returned by any
previous calls.
The main differences between GetPeriodActivity() and this method are as follows.
1. Fetches activities for all vehicles for the given fleet.
2. GetPeriodActivity() does not return any activities with a lower timestamp than the
version given in request. This method provides a way to override such behavior. Using
the “PreviousCallEndTime” parameter, consumer can specify that any activities that
occurred after “PreviousCallEndTime” should be returned irrespective of their versions.
As noted earlier, currently this parameter is ignored.
3. Returns additional “RequestPeriodEndTime” field in result set that can be used to set up
next call to this method.
4. Returns private events
This method provides detailed information for all the specified vehicle(s) belonging to given
fleet e.g. Longitude, Latitude, Speed, Driver Id etc. for the specified period. This method
extracts significant numbers of records and could be used inappropriately and impact your use
of the Published Interface. Please see the Recommended Usage section for appropriate ways
to use this method.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
HOS/DVIR API
AddDriverByType
This method allows a user to add a Driver to a specific fleet in Director via the Published
Interface. The type of Driver that the user adds to Director depends on the input parameter
‘RequestType’ which can take one of three values: ‘_DRIVER_REQUEST_BASIC’,
‘_DRIVER_REQUEST_HOS’ OR ‘_DRIVER_REQUEST_DRIVERID’. As the names of the Request Type values
suggest, this allows a user to add a basic Driver, a HOS Driver (requires additional information in HOS
related fields) or a Driver enabled for DriverID (requires DriverPortalUserID field).
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
EditDriverInfo
This Published Interface method works on similar parameters to the AddDriverByType method,
but it instead allows a user to update a Driver’s details instead of adding a new Driver. The
Driver is identified using OwnerId and DriverId. Dependent on the input parameters, the user
can update both basic and HOS Drivers using this method. If a Driver is not enabled for HOS,
none of the HOS related input parameters need to be provided since these won’t make any
changes to the non-HOS Driver. If an Input parameter is empty or null, it will saved as
empty or null respectively.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetHOSDriverDailyLogs
This Published Interface method retrieves the Status Logs from the HOS Service where the
Status Timestamp of the Status Log is between a Start and End Date Time defined by the user.
The user can choose to select all Status Logs in the date range on a per Fleet or per Driver basis
by changing the Request Type and providing a valid OwnerId/DriverId.
Input Parameters
Output Parameters
GetHOSDriverLogEditRecords
This Published Interface method works in a similar way to the GetHOSDriverDailyLogs method,
but instead retrieves the Edit History records, derived from the Status Logs, from the HOS
Service where the timestamp of the last edit is between a Start and End Date Time defined by
the user. The user can choose to select all Edit History records in the date range and per Fleet
or per Driver basis by changing the Request Type and providing a valid OwnerId/DriverId.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetVehicleDVIR
This Published Interface method allows a user to retrieve DVIRs (Driver Vehicle Inspection
Reports) from the DVIR Service. The user can choose to select DVIRs within a set time range,
defined by the StartDateUTC and EndDateUTC parameters, or the user can choose to use either
or both of these parameters as null to leave the time range open ended. The user can either
search for DVIRs by Fleet, Vehicle, or Driver as long as they have provided a valid OwnerId,
VehicleId or DriverId respectively.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
UpdateDVIRByMechanic
This method has been provided to allow a user (in particular, a Mechanic as the name suggests)
to make an update to the DVIR via the Published Interface. The user can provide a ReportID of
the DVIR they would like to update, as well as an Update Type Id, a Status Type and comments
which will be used to update the DVIR and will go into the update history. The user must also
provide a valid OwnerId that the DVIR belongs to.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetVehicleEngineHours
This method allows a user to retrieve Engine Hours readings for a Vehicle via the Published
Interface. The Engine Hours reading is a total of all Engine Hours accumulated within a date and
time range, specified using the StartDateUTC and EndDateUTC parameters. The user can
choose to leave either or both of these nulls to make the date and time range open ended e.g.
leaving StartDateUTC null will retrieve the Engine Hours accumulated from all records up until
the date and time specified by the EndDateUTC. The user can choose to retrieve Engine Hours
for one or more Fleets/Vehicles, dependent on the value of the RequestType enum and
provided they have given valid OwnerId(s)/VehicleId(s) respectively.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetHOSDrivers
This Published Interface method allows a user to retrieve HOS enabled Drivers for a Fleet by
specifying an OwnerId. However, the method isn’t confined to only retrieving HOS enabled
Drivers – it will retrieve all active Drivers for the Fleet specified by the OwnerId, but if the Driver
does have HOS enabled then HOS related fields will be retrieved also.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetHOSProfileTables
This Published Interface method retrieves all HOS Profile Tables and their related fields. A valid
OwnerId is required since the Terminal table contains data which is unique to a Fleet. However,
the other tables (Regulations, Regulation Types, Regulation Cycles, Time Zones and Status
Definitions) are not unique at a fleet level, so a call to GetHOSProfileTables will retrieve the
same data for these tables regardless of the OwnerId provided.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetHOSTimers
This Published Interface method retrieves some calculated timer information related to HOS
Drivers that is available on the HOS Overview screen of Director, mainly ‘On Duty Used’ and
‘Drive Time Used’ respectively for the shift based On Duty and Driving timers. Sleeper Berth
Used and Off Duty Used are not available in Director, and are calculated as the Sleeper Berth
timer and Off Duty timer respectively, exclusively for this function.
The user can choose to retrieve HOS Timers for a specific Driver or for all Drivers in a Fleet,
given that they have provided a valid DriverId or OwnerId respectively.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetHOSDayTimers
The main purpose of this Published Interface method is to retrieve the same calculated timer
information related to HOS Drivers that is available on the HOS Logs screen of Director e.g.
accumulated timers from midnight to midnight (‘day based’). Timers are provided for the
current day and also the last 7 days.
The user can choose to retrieve HOS Timers for a specific Driver or for all Drivers in a Fleet,
given that they have provided a valid DriverId or OwnerId respectively and that the
Driver/Drivers are all considered active HOS Drivers.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetDriverVehicleTables
This Published Interface method allows a user to retrieve Driver and Vehicle related tables for a
specified Fleet, given that the user has provided a valid OwnerId. The method retrieves data for
the Vehicle Types, Vehicle Groups, Driver Licence Classes and Driver Groups in a Fleet.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetConExConfigurationsByVehicles
Access the current configuration of Conex equipment installed on specified vehicle(s)
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
You must pass at least one ActivityLogId. Passing invalid ActivityLogIds to the method will
result in the method call working i.e. OperationStatus = True, but no rows will be returned.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetSites
Provides a list of Sites for a given owner / fleet e.g. Display Name, Shape Type, Latitudes and
Longtitudes etc.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetGeofences
Provides a list of Geofences for a given owner / fleet e.g. Display Name, Shape Type, Latitudes
and Longtitudes etc.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetEMSPeriodActivity
Access Engine Management System (EMS) data e.g. rpm, oil/water temp, braking information
etc. for a defined time period for a specified vehicle(s). The EMS data is summarized across a
trip which is defined as the period between ignition on and ignition off.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetFleetDiagnostics
Access Engine Management System (EMS) diagnostic codes for various protocols e.g. J1708,
J1939, J1979 and J1850 e.g. rpm, for specified vehicle(s)/owners. The EMS data is reported on
a regular basis as defined by the EMS reporting times.
Input Parameters
Output Parameters
GetFormList
This API will basically return latest form definition of forms in a specified fleet.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
Samples
Click here to view samples
GetFormListDetails
GetFormListDetails retrieves the latest form definitions for defined fleet. This API has definition
number as optional parameter to retrieve specific form definition. The response includes fields
and associated actions.
Input Parameters
All parameters are mandatory except those marked in Red Text. Default latest Form definitions
for given owner will be returned.
Output Parameters
Field types supported by form feature and their respected classes are as follows:
Field Type Class Name
Decimal DecimalField
String StringField
Address AddressField
Date DateField
Time TimeField
DateTime DateTimeField
Select SelectField
Checkbox CheckBoxField
Signature SignatureField
FormDefinition object has (BaseField[]) object collection property of field types mentioned
above. Detailed explanation for each of field class is as follows:
LinkFormAction and RouteToAction are derived from “BaseAction” class. FormDefinition object
has (BaseAction[]) object collection property of action type mentioned above. Detail
explanation for each action is as follows:
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
Samples
Click here for navigating to samples
GetForms
GetForms retrieves list of all form instance for defined fleet and for restricted period of time.
This API has optional parameter to retrieve list of all Form instances for one or more vehicles
for specific form number for restricted period of time. The response includes form instance
detail like Form number, definition number, value of the key field and other message details.
Input Parameters
All parameters are mandatory except those marked in Red Text. Default all form instances for
given owner id and duration will be retrieved.
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
Samples
Click here for navigating to samples
GetFormsDetails
GetFormsDetails retrieve list of all form instance detail for defined fleet and for restricted
period of time. This API has optional parameter to retrieve list of all form instances detail for
one or more vehicles for specific form number for restricted period of time. The response
includes form instance detail like form number, definition number, list of Field-Value and other
message details. From API version 1.6 it supports signature field. The signature bitmap is
exposed as base64 encoded string in the Value field of the FormField class.
Input Parameters
All parameters are mandatory except those marked in Red Text. Default all form instance
details for given owner id and duration will be retrieved.
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
Samples
Click here for navigating to samples
GetVehicleGroups
Method reterevies list of the vehicle group for given owner/fleet. It will have detail information
of vehicle group like Display Name, Descrption, Vehicle group Paraent Id etc.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
DoSendTextMessage
This method allows a text message to be sent to one or more vehicles. The sent text message
also contains the Id of the sender and will be displayed on the Vehicle’s MDT. SenderId is
returned from the UserInfo details section of the message returned from the DoLogin method.
The Text message being sent has a maximum length of 400 characters.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
DoSendRouteMessage
Allows a Route-To message to be sent to a Vehicle’s MDT. The sent text message will contain
location information as well as the Id of the sender and will be displayed on the Vehicle’s MDT.
A lot of the parameters and message fields discussed here are also referred to in the
GetMessages Method. The Text message being sent has a maximum length of 250
characters.
Published Interface User Documentation Page 121
/362
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
DoSendRouteMessages
Please note that this method requires additional setup to support asynchronous batch
operation. Contact your regional support staff to have it setup.
Allows multiple Route-To messages to be sent to the MDT of multiple vehicles. The sent text
message will contain location information as well as the Id of the sender and will be displayed
on the Vehicle’s MDT. The Text message being sent has a maximum length of 250 characters.
Note that the batch operation is done asynchronously. This method returns as soon as a batch
execution process has been created to perform the batch operation.
Input Parameters
All parameters are mandatory except those marked in Red Text. Note that, for simplicity, we
have mixed properties related to the batch, along with properties associated with a single
route-to message. In essence, the parameters taken by this method is a list of multiple singular
route-to message send requests.
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetSendRouteMessagesStatus
Allows the PI Client to retrieve the status of the batched route-to messages request which is
asynchronously processed by the server.
Please note that any date time values in the output of this method are NOT in UTC format for
the 10.2 release. These values are in server time (based on the server time zone). This has
been identified as an issue, and fixed for Release 10.2.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
DoSendDeleteTextMessages
Allows a message to be sent to the Vehicle(s) which will instruct the MDT to delete all Text
Messages on the device. You must specify at least one Vehicle Id in this method call.
Unrecognised or invalid Vehicle Ids will see the OperationStatus return False and list of problem
Vehicle Ids identified in the associated StatusMessage.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
DoSetDeviceOutputs
This method provides the ability to set the values on the serial ConEx port of a Vehicle. The
method can be used on a per Vehicle basis only.
Input Parameters
5
This information is available from the GetConExConfigurationsByVehicles Method
Output Parameters
DoSendForms
DoSendForms allows one or more Form Instances to be sent to one or more vehicles. This API is
also performing following validations on service side:
5) Validate whether form feature is enabled on all recipients
6) Validate whether form is sent according to latest form definition
7) Validate filled form for each of its field against the latest form definition
8) Validate whether form is not sent by driver
Note: In case a form has signature fields this API doesn’t support sending signature fields to
the MNav. If you still want to send such forms keep the Value field in SignatureFieldValue
class empty.
Input Parameters
Field value types supported by form feature and their respected classes are as follows:
Field Value Type Class Name
Decimal DecimalFieldValue
String StringFieldValue
Address AddressFieldValue
Date DateFieldValue
Time TimeFieldValue
DateTime DateTimeFieldValue
Select SelectFieldValue
Checkbox CheckBoxFieldValue
Signature SignatureFieldValue
While sending forms, the field value collection (BaseFieldValue[ ]) of form would be filled with
objects of field value types mentioned above. The type of field value class while filling up field
value collection of form can be derived by form definition which is being used to send a
particular form. Detailed explanation for each of field value class as follows:
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
Samples
Click here for navigating to samples
GetSentFormsStatus
GetSentFormsStatus retrieves the status of one or form instances sent to one or more vehicles.
It would return form instance latest statuses’ along with all its previous status changes with
their timestamps. Possible statuses are as follows:
- Not received by driver
- Received by driver
- Read by driver (if read receipt is enabled).
If latest status for one of form instance sent to particular vehicle is “Read by driver” then
response would return in following order of status changes along with their timestamp when
they got changed:
4) Read by driver
5) Received by driver
6) Not received by driver
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
Samples
Click here for navigating to samples
UpdateVehicleCustomStatus
UpdateVehicleCustomStatus is used to update custom status for vehicle. User will use this
method to manage custom status for vehicle. Following is the detail of the method:
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
SendMNavMessage
SendMNavMessage is used by Third Party services to communicate with Third Party
Applications which are installed on the M-NAV. For this API to be successfully used, the
Third Party application must be installed and enabled on the target M-NAV.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetPeriodActivityEx
This method is very similar to GetPeriodActivity() with few differences for addressing late
arriving data. This method was specifically added to resovle LDV-62062. The limitation with
GetPeriodActivity() is that it can miss some lower versions activities when a consumer supplies
an elevated “Version” parameter due to late arriving data present in result set returned by any
previous calls.
The main differences between GetPeriodActivity() and this method are as follows.
5. Fetches activities for all vehicles for the given fleet.
6. GetPeriodActivity() does not return any activities with a lower timestamp than the
version given in request. This method provides a way to override such behavior. Using
the “PreviousCallEndTime” parameter, consumer can specify that any activities that
occurred after “PreviousCallEndTime” should be returned irrespective of their versions.
As noted earlier, currently this parameter is ignored by server.
7. Returns additional “RequestPeriodEndTime” field in result set that can be used to set up
next call to this method.
8. Returns private events
This method provides detailed information for all the specified vehicle(s) belonging to given
fleet e.g. Longitude, Latitude, Speed, Driver Id etc. for the specified period. This method
extracts significant numbers of records and could be used inappropriately and impact your use
of the Published Interface. Please see the Recommended Usage section for appropriate ways
to use this method.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
Input Parameters
Output Parameters
This method will assign a user to the given vehicle display names. The vehicle display
name is unique across the owner/fleet and the GetUserHeaders method helps to get a list
of users in the fleet. Following is the detail of the method:
Input Parameters
Output Parameters
DoAssignUserToGroups
This method will assign a user to the given group display names. The group display name
is unique across the owner/fleet and the GetUserHeaders method helps to get a list of
users in the fleet. Following is the detail of the method:
Input Parameters
Output Parameters
Attribute Type Result Definition
OperationStatus Boolean See Appendix 2: Commonly Returned
Objects > OperationStatus
StatusMessage XML See Appendix 2: Commonly Returned
Objects > StatusMessage Array
FailedGroupList Guid Array Array of the Guid groups
CreateVehicleGroup
This method will create a vehicle group. The group display name is unique across the
owner/fleet. The GetUserHeaders method helps to get a list of users in the fleet, the
GeVehicleGroups method helps to get a parent vehicle group ID and the DoLogin method
helps to get the SessionId and OwnerId. Following is the detail of the method:
Input Parameters
Output Parameters
DeleteVehicleGroup
This method will delete a vehicle group. The DoLogin method helps to get the SessionId
and OwnerId and the GetVehicleGroups method helps to get the VehicleGroupID.
Following is the detail of the method:
Input Parameters
Output Parameters
SetVehicleDetails
This method will update specified vehicle properties for a specified vehicle and grant user
to access to that vehicle.The DoLogin method helps to get the SessionId and OwnerId and
the GetVehicleGroups method helps to get the VehicleGroupID. Following is the detail of
the method:
Input Parameters
Output Parameters
AddDriverByType
This method allows a user to add a Driver to a specific fleet in Director via the Published
Interface. The type of Driver that the user adds to Director depends on the input parameter
‘RequestType’ which can take one of three values: ‘_DRIVER_REQUEST_BASIC’,
‘_DRIVER_REQUEST_HOS’ OR ‘_DRIVER_REQUEST_DRIVERID’. As the names of the Request Type values
suggest, this allows a user to add a basic Driver, a HOS Driver (requires additional information in HOS
related fields) or a Driver enabled for DriverID (requires DriverPortalUserID field).
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
EditDriverInfo
This Published Interface method works on similar parameters to the AddDriverByType method,
but it instead allows a user to update a Driver’s details instead of adding a new Driver. The
Driver is identified using OwnerId and DriverId. Dependent on the input parameters, the user
can update both basic and HOS Drivers using this method. If a Driver is not enabled for HOS,
none of the HOS related input parameters need to be provided since these won’t make any
changes to the non-HOS Driver. If an Input parameter is empty or null, it will save empty or
null respectively.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetHOSDriverDailyLogs
This Published Interface method retrieves the Status Logs from the HOS Service where the
Status Timestamp of the Status Log is between a Start and End Date Time defined by the user.
The user can choose to select all Status Logs in the date range on a per Fleet or per Driver basis
by changing the Request Type and providing a valid OwnerId/DriverId.
Input Parameters
Output Parameters
GetHOSDriverLogEditRecords
This Published Interface method works in a similar way to the GetHOSDriverDailyLogs method,
but instead retrieves the Edit History records, derived from the Status Logs, from the HOS
Service where the timestamp of the last edit is between a Start and End Date Time defined by
the user. The user can choose to select all Edit History records in the date range on a per Fleet
or per Driver basis by changing the Request Type and providing a valid OwnerId/DriverId.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetVehicleDVIR
This Published Interface method allows a user to retrieve DVIRs (Driver Vehicle Inspection
Reports) from the DVIR Service. The user can choose to select DVIRs within a set time range,
defined by the StartDateUTC and EndDateUTC parameters, or the user can choose to use either
or both of these parameters as null to leave the time range open ended. The user can either
search for DVIRs by Fleet, Vehicle, or Driver as long as they have provided a valid OwnerId,
VehicleId or DriverId respectively.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
UpdateDVIRByMechanic
This method has been provided to allow a user (in particular, a Mechanic as the name suggests)
to make an update to the DVIR via the Published Interface. The user can provide a ReportID of
the DVIR they would like to update, as well as an Update Type Id, a Status Type and comments
which will be used to update the DVIR and will go into the update history. The user must also
provide a valid OwnerId that the DVIR belongs to.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetVehicleEngineHours
This method allows a user to retrieve Engine Hours readings for a Vehicle via the Published
Interface. The Engine Hours reading is a total of all Engine Hours accumulated within a date and
time range, specified using the StartDateUTC and EndDateUTC parameters. The user can
choose to leave either or both of these nulls to make the date and time range open ended e.g.
leaving StartDateUTC null will retrieve the Engine Hours accumulated from all records up until
the date and time specified by the EndDateUTC. The user can choose to retrieve Engine Hours
for one or more Fleets/Vehicles, dependent on the value of the RequestType enum and
provided they have given valid OwnerId(s)/VehicleId(s) respectively.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetHOSDrivers
This Published Interface method allows a user to retrieve HOS enabled Drivers for a Fleet by
specifying an OwnerId. However, the method isn’t confined to only retrieving HOS enabled
Drivers – it will retrieve all active Drivers for the Fleet specified by the OwnerId, but if the Driver
does have HOS enabled then HOS related fields will be retrieved also.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetHOSProfileTables
This Published Interface method retrieves all HOS Profile Tables and their related fields. A valid
OwnerId is required since the Terminal table contains data which is unique to a Fleet. However,
the other tables (Regulations, Regulation Types, Regulation Cycles, Time Zones and Status
Definitions) are not unique at a fleet level, so a call to GetHOSProfileTables will retrieve the
same data for these tables regardless of the OwnerId provided.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetHOSTimers
This Published Interface method retrieves all the calculated timer information related to HOS
Drivers that is available on the HOS screen of Director. The user can choose to retrieve HOS
Timers for a specific Driver or for all Drivers in a Fleet, given that they have provided a valid
DriverId or OwnerId respectively.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetDriverVehicleTables
This Published Interface method allows a user to retrieve Driver and Vehicle related tables for a
specified Fleet, given that the user has provided a valid OwnerId. The method retrieves data for
the Vehicle Types, Vehicle Groups, Driver Licence Classes and Driver Groups in a Fleet.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetSafetyAnalyticsEvents
This method provides the harsh acceleration, harsh braking, harsh cornering, speeding, and stop-
sign violations for the specified vehicle(s) and/or driver(s) for the specified period. This method
extracts significant numbers of records and could be used inappropriately and impact your use of
the Published Interface. Please see the Recommended Usage section for appropriate ways to use
this method.
Input Parameters
VehicleIDs Guid Specify valid VehicleID(s) (available from the GetVehicles method)
DriverIDs Guid Specify valid DriverID(s) (available from the GetDrivers method)
StartTime DateTime Start Date and Time (in UTC) of Activity Period
EndTime DateTime End Date and Time (in UTC) of Activity Period
Latitude Double The latitude (in degrees) where the event occurred
Longitude Double The longitude (in degrees) where the event occurred
PostedSpeed Double The posted speed limit (KPH) where the event
occurred
Workflow Service API
GetPlanTemplates
This Published Interface method retrieves Plan Templates from WorkflowService for a
specific fleet. User should provide a valid OwnerId. Plan Template provides attribute
information in order to upload route through WorkflowService and flow it to MNav
devices, so that drivers can accept and start the route.
Input Parameters
Output Parameters
Templates
TemplateAttribute
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
ImportPlan
This method allows a user to upload single route with multiple stops and at least one
single tasks for each stop. Once uploaded Driver can search route in MNav device and
proceed with the route.
Input Parameters
Parameter Type Definition
Stop
Task
Attribute
GetWorkflowTaskSettings
This method allows a user to pull the tasks for given plan template. It provides with
details of all the action (form) definition.
Input Parameters
TemplateID Guid Unique identifier for the template, which you receive by calling
GetPlanTemplates API.
OwnerID Guid Unique Id associated with the Fleet
Session XML SessionInfo object containg Guid field ‘SessionId’ – this Guid
should come from a valid session returned from DoLogin method
Output Parameters
WorkflowTask
WorkflowAction
ActionField
ActionFieldValue
GetWorkflowTaskUpdates
This method allows a user to pull the workflow task updates across various workflows
within the fleet for specified time range.
Input Parameters
Output Parameters
WorkflowTaskUpdate
RouteUpdate
StopUpdate
TaskUpdate
InstanceAttribute
ActivityDetail
AssignRouteToVehicle
This Published Interface method assigns an existing route to a vehicle. Any route before
activation on mobile device can be assigned to a vehicle. Route Planned, Route Assigned,
Route Accepted and Route Decline statuses occur before activating a vehicle.
Route can be assigned to a vehicle before Activation of the route.
Route Assigned message is sent to vehicle after updating on server.
Route Unassigned message is sent if route is already associated with a vehicle.
Input Parameters
Attribute
Parameter Type Definition
AttributeID Attribute Unique identifier for an Attribute
ExternalName string It determines external name for attribute, is exposed to
customer
Output Parameters
CancelRouteInstance
Attribute
Output Parameters
Recommended Usage
This section provides recommended usage patterns for the Published Interface. These
guidelines are aimed at working within the usage and data thresholds established to ensure a
Published Interface user can get what they need from the Teletrac Navman system in the most
practical way possible.
All methods available through the Published Interface would follow the following typical
format:
where DoRequest and DoResponse represent the appropriate objects for the method being
called.
The SessionId will always be required for all commands (with the exception of the Login
process wherein the SessionId will be generated to serve as an Authorization token for
succeeding requests. In the login process, although the SessionId will not be supplied in the
request process the session would still have to be initialized as seen in the following line:
The status Boolean value means that the request was accepted by the server and processed
successfully. This serves as an acknowledgement to the request.
Retrieving Reference / Static Data
All IDs are immutable so there is no need to continually fetch them each session. The call to
DoLogin returns the session id. The session id is then used by all subsequent calls. Every call
except for DoLogin takes a SessionID as a mandatory parameter.
Entity Versions
Many of the datasets honor the concept of a ‘version’. This is in place to restrict the need for
unnecessarily transferring data that has not changed.
When a call is made to a Web Method, a version number for the result set is returned. This is
simply an ‘arbitrary’ incrementing integer (monotonically increasing 64Bit Integer). You cannot
rely on any patterns in this number except that it is always increasing. The next time the same
query is made with the same parameters, you provide the version number you were returned
last time. If no changes have been made, you will simply receive an empty dataset in response.
If any changes have been made, simply the rows ‘touched’ (added/altered/deleted) are
returned. This holds true for any given inputs, so if you run the same query against the system
and nothing has changed, you will get an empty result set. If you have no history, you pass in ‘0’
as your version number. See examples of ‘versioning’ in the . Although this method will not
extract the volumes of data the GetPeriodActivity method will extract, it is important that it is
used appropriately – see the The SOAP packets that are sent and received as part of this
Method are provided in the WSDL.
DoSendForms
DoSendForms allows one or more Form Instances to be sent to one or more vehicles. This API is
also performing following validations on service side:
9) Validate whether form feature is enabled on all recipients
10) Validate whether form is sent according to latest form definition
11) Validate filled form for each of its field against the latest form definition
12) Validate whether form is not sent by driver
Input Parameters
Field value types supported by form feature and their respected classes are as follows:
Field Value Type Class Name
Decimal DecimalFieldValue
String StringFieldValue
Address AddressFieldValue
Date DateFieldValue
Time TimeFieldValue
DateTime DateTimeFieldValue
Select SelectFieldValue
Checkbox CheckBoxFieldValue
Signature SignatureFieldValue
While sending forms, the field value collection (BaseFieldValue[ ]) of form would be filled with
objects of field value types mentioned above. The type of field value class while filling up field
value collection of form can be derived by form definition which is being used to send a
particular form. Detailed explanation for each of field value class as follows:
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
Samples
Click here for navigating to samples
GetSentFormsStatus
GetSentFormsStatus retrieves the status of one or form instances sent to one or more vehicles.
It would return form instance latest statuses’ along with all its previous status changes with
their timestamps. Possible statuses are as follows:
- Not received by driver
- Received by driver
- Read by driver (if read receipt is enabled).
If latest status for one of form instance sent to particular vehicle is “Read by driver” then
response would return in following order of status changes along with their timestamp when
they got changed:
7) Read by driver
8) Received by driver
9) Not received by driver
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
Samples
Click here for navigating to samples
AssignToVehicleGroup
Method will assign the vehicle to the given vehicle group and grant user to access to that
vehicle. Vehicle group display name is unique across the owner/fleet. Following is the
detail of the method:
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
UpdateVehicleCustomStatus
UpdateVehicleCustomStatus is used to update custom status for vehicle. User will use this
method to manage custom status for vehicle. Following is the detail of the method:
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
SendMNavMessage
SendMNavMessage is used by Third Party services to communicate with Third Party
Applications which are installed on the M-NAV. For this API to be successfully used, the
Third Party application must be installed and enabled on the target M-NAV.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetPeriodActivityEx
This method is very similar to GetPeriodActivity() with few differences for addressing late
arriving data. This method was specifically added to resovle LDV-62062. The limitation with
GetPeriodActivity() is that it can miss some lower versions activities when a consumer supplies
an elevated “Version” parameter due to late arriving data present in result set returned by any
previous calls.
The main differences between GetPeriodActivity() and this method are as follows.
9. Fetches activities for all vehicles for the given fleet.
10. GetPeriodActivity() does not return any activities with a lower timestamp than the
version given in request. This method provides a way to override such behavior. Using
the “PreviousCallEndTime” parameter, consumer can specify that any activities that
occurred after “PreviousCallEndTime” should be returned irrespective of their versions.
As noted earlier, currently this parameter is ignored by server.
11. Returns additional “RequestPeriodEndTime” field in result set that can be used to set up
next call to this method.
12. Returns private events
This method provides detailed information for all the specified vehicle(s) belonging to given fleet
e.g. Longitude, Latitude, Speed, Driver Id etc. for the specified period. This method extracts
significant numbers of records and could be used inappropriately and impact your use of the
Published Interface. Please see the Recommended Usage section for appropriate ways to use
this method.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
AddDriverByType
This method allows a user to add a Driver to a specific fleet in Director via the Published
Interface. The type of Driver that the user adds to Director depends on the input parameter
‘RequestType’ which can take one of three values: ‘_DRIVER_REQUEST_BASIC’,
‘_DRIVER_REQUEST_HOS’ OR ‘_DRIVER_REQUEST_DRIVERID’. As the names of the Request Type values
suggest, this allows a user to add a basic Driver, a HOS Driver (requires additional information in HOS
related fields) or a Driver enabled for DriverID (requires DriverPortalUserID field).
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
EditDriverInfo
This Published Interface method works on similar parameters to the AddDriverByType method,
but it instead allows a user to update a Driver’s details instead of adding a new Driver. The
Driver is identified using OwnerId and DriverId. Dependent on the input parameters, the user
can update both basic and HOS Drivers using this method. If a Driver is not enabled for HOS,
none of the HOS related input parameters need to be provided since these won’t make any
changes to the non-HOS Driver.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetHOSDriverDailyLogs
This Published Interface method retrieves the Status Logs from the HOS Service where the
Status Timestamp of the Status Log is between a Start and End Date Time defined by the user.
The user can choose to select all Status Logs in the date range on a per Fleet or per Driver basis
by changing the Request Type and providing a valid OwnerId/DriverId.
Input Parameters
Output Parameters
GetHOSDriverLogEditRecords
This Published Interface method works in a similar way to the GetHOSDriverDailyLogs method,
but instead retrieves the Edit History records, derived from the Status Logs, from the HOS
Service where the timestamp of the last edit is between a Start and End Date Time defined by
the user. The user can choose to select all Edit History records in the date range on a per Fleet
or per Driver basis by changing the Request Type and providing a valid OwnerId/DriverId.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetVehicleDVIR
This Published Interface method allows a user to retrieve DVIRs (Driver Vehicle Inspection
Reports) from the DVIR Service. The user can choose to select DVIRs within a set time range,
defined by the StartDateUTC and EndDateUTC parameters, or the user can choose to use either
or both of these parameters as null to leave the time range open ended. The user can either
search for DVIRs by Fleet, Vehicle, or Driver as long as they have provided a valid OwnerId,
VehicleId or DriverId respectively.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
UpdateDVIRByMechanic
This method has been provided to allow a user (in particular, a Mechanic as the name suggests)
to make an update to the DVIR via the Published Interface. The user can provide a ReportID of
the DVIR they would like to update, as well as an Update Type Id, a Status Type and comments
which will be used to update the DVIR and will go into the update history. The user must also
provide a valid OwnerId that the DVIR belongs to.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetVehicleEngineHours
This method allows a user to retrieve Engine Hours readings for a Vehicle via the Published
Interface. The Engine Hours reading is a total of all Engine Hours accumulated within a date and
time range, specified using the StartDateUTC and EndDateUTC parameters. The user can
choose to leave either or both of these nulls to make the date and time range open ended e.g.
leaving StartDateUTC null will retrieve the Engine Hours accumulated from all records up until
the date and time specified by the EndDateUTC. The user can choose to retrieve Engine Hours
for one or more Fleets/Vehicles, dependent on the value of the RequestType enum and
provided they have given valid OwnerId(s)/VehicleId(s) respectively.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetHOSDrivers
This Published Interface method allows a user to retrieve HOS enabled Drivers for a Fleet by
specifying an OwnerId. However, the method isn’t confined to only retrieving HOS enabled
Drivers – it will retrieve all active Drivers for the Fleet specified by the OwnerId, but if the Driver
does have HOS enabled then HOS related fields will be retrieved also.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetHOSProfileTables
This Published Interface method retrieves all HOS Profile Tables and their related fields. A valid
OwnerId is required since the Terminal table contains data which is unique to a Fleet. However,
the other tables (Regulations, Regulation Types, Regulation Cycles, Time Zones and Status
Definitions) are not unique at a fleet level, so a call to GetHOSProfileTables will retrieve the
same data for these tables regardless of the OwnerId provided.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetHOSTimers
This Published Interface method retrieves all the calculated timer information related to HOS
Drivers that is available on the HOS screen of Director. The user can choose to retrieve HOS
Timers for a specific Driver or for all Drivers in a Fleet, given that they have provided a valid
DriverId or OwnerId respectively.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetDriverVehicleTables
This Published Interface method allows a user to retrieve Driver and Vehicle related tables for a
specified Fleet, given that the user has provided a valid OwnerId. The method retrieves data for
the Vehicle Types, Vehicle Groups, Driver Licence Classes and Driver Groups in a Fleet.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetConExConfigurationsByVehicles
Access the current configuration of Conex equipment installed on specified vehicle(s)
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetVehicleActivityDetails
This method provides extended information regarding a specific Vehicle activity record. This
extended information contains things like temperature logger information or other devices
connected via ConEx.
You must pass at least one ActivityLogId. Passing invalid ActivityLogIds to the method will
result in the method call working i.e. OperationStatus = True, but no rows will be returned.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetSites
Provides a list of Sites for a given owner / fleet e.g. Display Name, Shape Type, Latitudes and
Longtitudes etc.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetGeofences
Provides a list of Geofences for a given owner / fleet e.g. Display Name, Shape Type, Latitudes
and Longtitudes etc.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetEMSPeriodActivity
Access Engine Management System (EMS) data e.g. rpm, oil/water temp, braking information
etc. for a defined time period for a specified vehicle(s). The EMS data is summarized across a
trip which is defined as the period between ignition on and ignition off.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetFleetDiagnostics
Access Engine Management System (EMS) diagnostic codes for various protocols e.g. J1708,
J1939, J1979 and J1850 e.g. rpm, for specified vehicle(s)/owners. The EMS data is reported on
a regular basis as defined by the EMS reporting times.
Input Parameters
Output Parameters
GetFormList
This API will basically return latest form definition of forms in a specified fleet.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
Samples
Click here to view samples
GetFormListDetails
GetFormListDetails retrieves the latest form definitions for defined fleet. This API has definition
number as optional parameter to retrieve specific form definition. The response includes fields
and associated actions.
Input Parameters
All parameters are mandatory except those marked in Red Text. Default latest Form definitions
for given owner will be returned.
Output Parameters
Field types supported by form feature and their respected classes are as follows:
Field Type Class Name
Decimal DecimalField
String StringField
Address AddressField
Date DateField
Time TimeField
DateTime DateTimeField
Select SelectField
Checkbox CheckBoxField
Signature SignatureField
FormDefinition object has (BaseField[]) object collection property of field types mentioned
above. Detailed explanation for each of field class is as follows:
LinkFormAction and RouteToAction are derived from “BaseAction” class. FormDefinition object
has (BaseAction[]) object collection property of action type mentioned above. Detail
explanation for each action is as follows:
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
Samples
Click here for navigating to samples
GetForms
GetForms retrieves list of all form instance for defined fleet and for restricted period of time.
This API has optional parameter to retrieve list of all Form instances for one or more vehicles
for specific form number for restricted period of time. The response includes form instance
detail like Form number, definition number, value of the key field and other message details.
Input Parameters
All parameters are mandatory except those marked in Red Text. Default all form instances for
given owner id and duration will be retrieved.
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
Samples
Click here for navigating to samples
GetFormsDetails
GetFormsDetails retrieve list of all form instance detail for defined fleet and for restricted
period of time. This API has optional parameter to retrieve list of all form instances detail for
one or more vehicles for specific form number for restricted period of time. The response
includes form instance detail like form number, definition number, list of Field-Value and other
message details. From API version 1.6 it supports signature field. The signature bitmap is
exposed as base64 encoded string in the Value field of the FormField class.
Input Parameters
All parameters are mandatory except those marked in Red Text. Default all form instance
details for given owner id and duration will be retrieved.
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
Samples
Click here for navigating to samples
GetVehicleGroups
Method reterevies list of the vehicle group for given owner/fleet. It will have detail information
of vehicle group like Display Name, Descrption, Vehicle group Paraent Id etc.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
DoSendTextMessage
This method allows a text message to be sent to one or more vehicles. The sent text message
also contains the Id of the sender and will be displayed on the Vehicle’s MDT. SenderId is
returned from the UserInfo details section of the message returned from the DoLogin method.
Please note that if the recipient does not have a MDT in their vehicle, the method will complete
successfully and the message will be stored in the database. It will simply never reaches it’s
intended destination.
The Text message being sent has a maximum length of 400 characters.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
DoSendRouteMessage
Allows a Route-To message to be sent to a Vehicle’s MDT. The sent text message will contain
location information as well as the Id of the sender and will be displayed on the Vehicle’s MDT.
A lot of the parameters and message fields discussed here are also referred to in the
GetMessages Method. The Text message being sent has a maximum length of 250
characters.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
DoSendRouteMessages
Please note that this method requires additional setup to support asynchronous batch
operation. Contact your regional support staff to have it setup.
Allows multiple Route-To messages to be sent to the MDT of multiple vehicles. The sent text
message will contain location information as well as the Id of the sender and will be displayed
on the Vehicle’s MDT. The Text message being sent has a maximum length of 250 characters.
Note that the batch operation is done asynchronously. This method returns as soon as a batch
execution process has been created to perform the batch operation.
All parameters are mandatory except those marked in Red Text. Note that, for simplicity, we
have mixed properties related to the batch, along with properties associated with a single
route-to message. In essence, the parameters taken by this method is a list of multiple singular
route-to message send requests.
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
Please note that any date time values in the output of this method are NOT in UTC format for
the 10.2 release. These values are in server time (based on the server time zone). This has
been identified as an issue, and fixed for Release 10.2.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
DoSendDeleteTextMessages
Allows a message to be sent to the Vehicle(s) which will instruct the MDT to delete all Text
Messages on the device. You must specify at least one Vehicle Id in this method call.
Unrecognised or invalid Vehicle Ids will see the OperationStatus return False and list of problem
Vehicle Ids identified in the associated StatusMessage.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
DoSetDeviceOutputs
This method provides the ability to set the values on the serial ConEx port of a Vehicle. The
method can be used on a per Vehicle basis only.
Input Parameters
5
This information is available from the GetConExConfigurationsByVehicles Method
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
DoSendForms
DoSendForms allows one or more Form Instances to be sent to one or more vehicles. This API is
also performing following validations on service side:
13) Validate whether form feature is enabled on all recipients
14) Validate whether form is sent according to latest form definition
15) Validate filled form for each of its field against the latest form definition
16) Validate whether form is not sent by driver
Note: In case a form has signature fields this API doesn’t support sending signature fields to
the MNav. If you still want to send such forms keep the Value field in SignatureFieldValue
class empty.
Input Parameters
Field value types supported by form feature and their respected classes are as follows:
Field Value Type Class Name
Decimal DecimalFieldValue
String StringFieldValue
Address AddressFieldValue
Date DateFieldValue
Time TimeFieldValue
DateTime DateTimeFieldValue
Select SelectFieldValue
Checkbox CheckBoxFieldValue
Signature SignatureFieldValue
While sending forms, the field value collection (BaseFieldValue[ ]) of form would be filled with
objects of field value types mentioned above. The type of field value class while filling up field
value collection of form can be derived by form definition which is being used to send a
particular form. Detailed explanation for each of field value class as follows:
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
Samples
Click here for navigating to samples
If latest status for one of form instance sent to particular vehicle is “Read by driver” then
response would return in following order of status changes along with their timestamp when
they got changed:
10) Read by driver
11) Received by driver
12) Not received by driver
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
Samples
Click here for navigating to samples
AssignToVehicleGroup
Method will assign the vehicle to the given vehicle group display name. Vehicle group
display name is unique across the owner/fleet. Following is the detail of the method:
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
UpdateVehicleCustomStatus
UpdateVehicleCustomStatus is used to update custom status for vehicle. User will use this
method to manage custom status for vehicle. Following is the detail of the method:
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
SendMNavMessage
SendMNavMessage is used by Third Party services to communicate with Third Party
Applications which are installed on the M-NAV. For this API to be successfully used, the
Third Party application must be installed and enabled on the target M-NAV.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
GetPeriodActivityEx
This method is very similar to GetPeriodActivity() with few differences for addressing late
arriving data. This method was specifically added to resovle LDV-62062. The limitation with
GetPeriodActivity() is that it can miss some lower versions activities when a consumer supplies
an elevated “Version” parameter due to late arriving data present in result set returned by any
previous calls.
The main differences between GetPeriodActivity() and this method are as follows.
13. Fetches activities for all vehicles for the given fleet.
14. GetPeriodActivity() does not return any activities with a lower timestamp than the
version given in request. This method provides a way to override such behavior. Using
the “PreviousCallEndTime” parameter, consumer can specify that any activities that
occurred after “PreviousCallEndTime” should be returned irrespective of their versions.
Note – currently this parameter is obsolete. It is ignored by server.
15. Returns additional “RequestPeriodEndTime” field in result set that can be used to set up
next call to this method.
16. Returns private events
This method provides detailed information for all the specified vehicle(s) belonging to given
fleet e.g. Longitude, Latitude, Speed, Driver Id etc. for the specified period. This method
extracts significant numbers of records and could be used inappropriately and impact your use
of the Published Interface. Please see the Recommended Usage section for appropriate ways
to use this method.
Input Parameters
Output Parameters
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
Recommended Usage section.
Note that all returned result sets will also have a ‘removed items’ list which will contain a list of
all the identifiers that have been removed out of the list since the last call.
GetSafetyAnalyticsEvents
This method provides the harsh acceleration, harsh braking, harsh cornering, speeding, and stop-
sign violations for the specified vehicle(s) and/or driver(s) for the specified period. This method
extracts significant numbers of records and could be used inappropriately and impact your use of
the Published Interface. Please see the Recommended Usage section for appropriate ways to use
this method.
Input Parameters
VehicleIDs Guid Specify valid VehicleID(s) (available from the GetVehicles method)
DriverIDs Guid Specify valid DriverID(s) (available from the GetDrivers method)
StartTime DateTime Start Date and Time (in UTC) of Activity Period
EndTime DateTime End Date and Time (in UTC) of Activity Period
Latitude Double The latitude (in degrees) where the event occurred
Longitude Double The longitude (in degrees) where the event occurred
PostedSpeed Double The posted speed limit (KPH) where the event
occurred
This Published Interface method retrieves Plan Templates from WorkflowService for a
specific fleet. User should provide a valid OwnerId. Plan Template provides attribute
information in order to upload route through WorkflowService and flow it to MNav
devices, so that drivers can accept and start the route.
Input Parameters
Output Parameters
Templates
TemplateAttribute
SOAP/XML Messages
The SOAP packets that are sent and received as part of this Method are provided in the WSDL.
ImportPlan
This method allows a user to upload single route with multiple stops and at least one
single tasks for each stop. Once uploaded Driver can search route in MNav device and
proceed with the route.
Input Parameters
Stop
Task
Attribute
Output Parameters
Published Interface User Documentation 5-Dec-16 Page 274
/362
Attribute Type Result Definition
ImportErrors ImportPla
nErrors
GetWorkflowTaskSettings
This method allows a user to pull the tasks for given plan template. It provides with
details of all the action (form) definition.
Input Parameters
TemplateID Guid Unique identifier for the template, which you receive by calling
GetPlanTemplates API.
OwnerID Guid Unique Id associated with the Fleet
Session XML SessionInfo object containg Guid field ‘SessionId’ – this Guid
should come from a valid session returned from DoLogin method
Output Parameters
WorkflowTask
WorkflowAction
ActionField
ActionFieldValue
GetWorkflowTaskUpdates
Published Interface User Documentation 5-Dec-16 Page 276
/362
This method allows a user to pull the workflow task updates across various workflows
within the fleet for specified time range.
Input Parameters
Output Parameters
WorkflowTaskUpdate
RouteUpdate
StopUpdate
TaskUpdate
InstanceAttribute
ActivityDetail
AssignRouteToVehicle
This Published Interface method assigns an existing route to a vehicle. Any route before
activation on mobile device can be assigned to a vehicle. Route Planned, Route Assigned,
Route Accepted and Route Decline statuses occur before activating a vehicle.
Route can be assigned to a vehicle before Activation of the route.
Route Assigned message is sent to vehicle after updating on server.
Route Unassigned message is sent if route is already associated with a vehicle.
Input Parameters
Attribute
Output Parameters
CancelRouteInstance
Input Parameters
Attribute
Output Parameters
The location string in the Teletrac Navman applicaton is produced from a combination of
database fields for display in the client as follows:
OffRoadMetres (distance in metres from the nearest feature)
LocationType (enum: ltNoLocation = 0, ltNamedRoad = 1, ltUnnamedRoad
= 2, ltPOI = 3)
DegreesBearing (bearing in degrees to the nearest feature)
Location (string containing nearest feature)
If the location type is a road (locationType = ltNamedRoad) then we just display the
Location field and ignore the others e.g.: "583 E Coast Rd, Rosedale, Auckland, New
Zealand, 0630"
Location = 583 E Coast Rd, Rosedale, Auckland, New Zealand, 0630
Location type = 1
off road meters = 7.27623468447137
degrees bearing = 1
If the Location string does not belong to a "road", then the location string is
constructed on the fly along a pattern similar to: "x distance SE of nearest
suburb/city" eg ""0.1 mi SW of Weavers Lane, Stone, United Kingdom, ST15 8""
location = Weavers Lane, Stone, United Kingdom, ST15 8
location type = 3
degree bearing = 240
off road metres = 162.282631503341
GetCarrier
This Published Interface method retrieves the US DOT number and information of the carrier.
Input Parameters
Output Parameters
Input Parameters
Output Parameters
GetELDProductInfo
This Published Interface method retrieves the TeletracNavman ELD compliance product
information.
Input Parameters
Output Parameters
GetELDUnassignedDriveTime
This Published Interface method retrieves the Unassigned Drive Time (UDT) records where the
StatusTimestamp of the Status Log is between a Start and End Date Time defined by the user.
The user can choose to select all Status Logs in the date range and per Fleet or per Vehicle
basis by changing the Request Type and providing a valid OwnerId/VehicleId.
Input Parameters
Output Parameters
GetELDDriverLogEditRecords
This Published Interface method retrieves the DriverLog Edit records where the LastChanged of
the Status Log is between a Start and End Date Time defined by the user. The user can choose
to select all Status Logs in the date range and per Fleet or per Driver basis by changing the
Request Type and providing a valid OwnerId/DriverId. The search of any driver log edit is up to
a maximum of 7 days.
Input Parameters
Output Parameters
The Teletrac Navman system has been architected such that the methods used to access data
assume they are authorized. The rationale for this design is simply to avoid the implementation
and performance costs that come with performing full parameter checking on every function
call. The client application is assumed to be validated and authorized so this checking is not
required.
The use of GUIDs (random 128 bits identifiers) in the application to identify entities in the
system, whilst providing an additional layer of security, does not make the system immune
from a user accessing data they are not authorized to see. For a PI User to guess a GUID with
the intent to access unauthorized data is a rare occurrence given the complexity of the GUID
and it’s construction.
However, where there is a weakness is with PI users who have their access to data revoked.
The PI User will have stored or recorded a GUID and using the methods available, continue to
access data which they have since had revoked. A good example of this is where a PI User had
access to a vehicle (referenced using a GUID) on their fleet which has since been revoked or
removed from their fleet. In this scenario, supplying the GUID to the GetVehicles method will
still return data.
Appendix 1 : SMDP Event Sub-type Descriptions
The following SMDP Event Sub-Types are returned in the GetPeriodActivityResponse XML. These can be translated as:
Operation Status
This should be checked after calling any method to make sure it is true. A True return code
means the method was successful. If the OperationStatus is False, you should check the
StatusMessages to assess why the operation failed.
<OperationStatus>boolean</OperationStatus>
MoreItemsAvailable
Determines all data in scope is returned. True indicates the method should be executed again using the
last known Version.
Version
The maximum version of retrieved record set. Use this as part of the next method call if
MoreItemsAvailable is set to true in the Response object to retrieve the next set of data.
StatusMessage array
This object contains a list of SystemMessage objects.
<StatusMessage>
<SystemMessage>
<MessageCode>int</MessageCode>
<ExceptionMessage>string</ExceptionMessage>
<ExceptionStackTrace>string</ExceptionStackTrace>
<ExceptionType>string</ExceptionType>
</SystemMessage>
<SystemMessage>
<MessageCode>int</MessageCode>
<ExceptionMessage>string</ExceptionMessage>
<ExceptionStackTrace>string</ExceptionStackTrace>
<ExceptionType>string</ExceptionType>
</SystemMessage>
</StatusMessage>
SystemMessage
Contains:
MessageCode -> (see later in document for an explanation of all the
MessageCodes).
ExceptionMessage -> Has an optional English description of the problem
ExceptionStackTrace -> Not implemented
GetFormList
VB.NET Sample:
Imports System
Imports System.Collections.Generic
Imports System.Text
Imports System.Web.Services
Imports System.Configuration
Imports OnlineAVL.PITest.Core
Imports OnlineAVL.PITest.Core.OnlineAVL2PI
Imports OnlineAVL.PITest.Core.Samples
Public Class GetFormListVBSample
currentSession = loginResponse.SecurityProfile.Session
End Function
End Class
C# Sample:
using System;
using System.Collections;
using System.Collections.Generic;
using System.Data;
using System.Diagnostics;
using System.Text;
using System.Web.Services;
using System.Configuration;
using OnlineAVL.PITest.Core;
using OnlineAVL.PITest.Core.OnlineAVL2PI;
using OnlineAVL.PITest.Core.Samples;
public class GetFormListCSharpSample
{
public GetFormSummaryItemsResponse MakeGetFormListAPICall()
{
SessionInfo currentSession = null;
Service service = new Service();
service.Url = "http://localhost/OnlineAVL/API/V1.0/Service.asmx";
currentSession = loginResponse.SecurityProfile.Session;
return getFormSummaryItemsResponse;
}
}
GetFormListDetails
VB.NET Sample:
Imports System.Collections
Imports System.Collections.Generic
Imports System.Data
Imports System.Diagnostics
Imports System.Text
Imports System.Web.Services
Imports System.Configuration
Imports OnlineAVL.PITest.Core
Imports OnlineAVL.PITest.Core.OnlineAVL2PI
Imports OnlineAVL.PITest.Core.Samples
currentSession = loginResponse.SecurityProfile.Session
'Supply Owner ID for which latest form definitions for forms need to be
'fetched
request.OwnerId = New Guid("9F79EA9B-8B43-47A6-92C1-2461167BB8D5")
'Set the credentials using a valid OnlineAVl2 token
request.Session = currentSession
'Set form definition number for which definition to be fetched. Its optional
‘parameter.
request.FormDefinitionSpecificationList = formDefSpecificationList.ToArray()
Return response
End Function
End Class
C# Sample:
using System;
using System.Collections;
using System.Collections.Generic;
using System.Data;
using System.Diagnostics;
using System.Text;
using System.Web.Services;
using System.Configuration;
using OnlineAVL.PITest.Core;
using OnlineAVL.PITest.Core.OnlineAVL2PI;
using OnlineAVL.PITest.Core.Samples;
currentSession = loginResponse.SecurityProfile.Session;
//Supply Owner ID for which latest form definitions for forms need to be
//fetched
request.OwnerId = new Guid("9F79EA9B-8B43-47A6-92C1-2461167BB8D5");
//Set form definition number for which definition to be fetched. Its optional
// parameter.
request.FormDefinitionSpecificationList = formDefSpecificationList.ToArray();
return response;
}
}
GetForms
VB.NET Sample:
Imports System.Collections
Imports System.Collections.Generic
Imports System.Data
Imports System.Diagnostics
Imports System.Text
Imports System.Web.Services
Imports System.Configuration
Imports OnlineAVL.PITest.Core
Imports OnlineAVL.PITest.Core.OnlineAVL2PI
Imports OnlineAVL.PITest.Core.Samples
currentSession = loginResponse.SecurityProfile.Session
'Supply Owner ID for which latest form definitions for forms need to be
'fetched
request.OwnerId = New Guid("9F79EA9B-8B43-47A6-92C1-2461167BB8D5")
'Set starts of time period (in UTC) within form instance are to be retrieved.
request.StartDate = New DateTime(2011, 6, 8)
'Set end of time period (in UTC) within form instance are to be retrieved.
request.EndDate = New DateTime(2011, 6, 9)
'Set form number for which form instance to be fetched. Its optional parameter.
request.FormNumbers = New Integer() {25, 52}
Return response
End Function
End Class
C# Sample:
using System;
using System.Collections;
using System.Collections.Generic;
using System.Data;
using System.Diagnostics;
using System.Text;
using System.Web.Services;
using System.Configuration;
using OnlineAVL.PITest.Core;
using OnlineAVL.PITest.Core.OnlineAVL2PI;
using OnlineAVL.PITest.Core.Samples;
currentSession = loginResponse.SecurityProfile.Session;
//Supply Owner ID for which latest form definitions for forms need to be
//fetched
request.OwnerId = new Guid("9F79EA9B-8B43-47A6-92C1-2461167BB8D5");
//Set starts of time period (in UTC) within form instance are to be retrieved.
request.StartDate = new DateTime(2011, 6, 8);
//Set end of time period (in UTC) within form instance are to be retrieved.
request.EndDate = new DateTime(2011, 6, 9);
//Set form number for which form instance to be fetched. Its optional parameter.
request.FormNumbers = new int[] { 25, 52 };
//Set vehicle id for which form instance to be fetched. Its optional parameter.
request.VehicleIds = new Guid[] {
new Guid("6E646103-C9DF-4687-9BB7-4A80145E1DC7"),
new Guid("F5567041-178F-4657-93DD-E9A43CC23ED1") };
return response;
}
}
GetFormsDetails
VB.Net Sample:
Imports System.Collections
Imports System.Collections.Generic
Imports System.Data
Imports System.Diagnostics
Imports System.Text
Imports System.Web.Services
Imports System.Configuration
Imports OnlineAVL.PITest.Core
Imports OnlineAVL.PITest.Core.OnlineAVL2PI
Imports OnlineAVL.PITest.Core.Samples
currentSession = loginResponse.SecurityProfile.Session
'Supply Owner ID for which latest form definitions for forms need to be
'fetched
request.OwnerId = New Guid("{9F79EA9B-8B43-47A6-92C1-2461167BB8D5}")
'Set starts of time period (in UTC) within form instance are to be retrieved.
request.StartDate = New DateTime(2011, 6, 8)
'Set end of time period (in UTC) within form instance are to be retrieved.
request.EndDate = New DateTime(2011, 6, 9)
'Set form instance ids for which form instance to be fetched. Its optional
‘parameter.
request.FormInstanceIds = New Guid() {
New Guid("F576D251-98FB-4B0A-93C8-767A0B4ADF0D"),
New Guid("FF81E8D0-E494-4B1D-B83D-D4986B1FE2AA")}
'Set form number for which form instance to be fetched. Its optional parameter.
request.FormNumbers = New Integer() {25, 52}
Return response
End Function
End Class
using OnlineAVL.PITest.Core;
using OnlineAVL.PITest.Core.OnlineAVL2PI;
using OnlineAVL.PITest.Core.Samples;
currentSession = loginResponse.SecurityProfile.Session;
//Supply Owner ID for which latest form definitions for forms need to be
//fetched
request.OwnerId = new Guid("{9F79EA9B-8B43-47A6-92C1-2461167BB8D5}");
//Set starts of time period (in UTC) within form instance are to be retrieved.
request.StartDate = new DateTime(2011, 6, 8);
//Set end of time period (in UTC) within form instance are to be retrieved.
request.EndDate = new DateTime(2011, 6, 9);
//Set form instance ids for which form instance to be fetched. Its optional
//parameter.
request.FormInstanceIds = new Guid[] {
new Guid("F576D251-98FB-4B0A-93C8-767A0B4ADF0D"),
new Guid("FF81E8D0-E494-4B1D-B83D-D4986B1FE2AA") };
//Set form number for which form instance to be fetched. Its optional parameter.
request.FormNumbers = new int[] { 25, 52 };
//Set vehicle id for which form instance to be fetched. Its optional parameter.
request.VehicleIds = new Guid[] {
new Guid("6E646103-C9DF-4687-9BB7-4A80145E1DC7"),
new Guid("F5567041-178F-4657-93DD-E9A43CC23ED1") };
return response;
}
}
DoSendForms
VB.NET Sample:
Imports System
Imports System.Collections.Generic
Imports System.Text
Imports System.Web.Services
Imports System.Configuration
Imports OnlineAVL.PITest.Core
Imports OnlineAVL.PITest.Core.OnlineAVL2PI
Imports OnlineAVL.PITest.Core.Samples
Public Class DoSendFormsVBSample
currentSession = loginResponse.SecurityProfile.Session
'Supply list of forms. For each form set Tracking ID,Recipient IDs,Form
Definition Number, Form fields etc.
doSendFormsInstnaceMessages.Add(tempSendFormInstanceMessage)
doSendFormsInstnaceMessages.Add(tempSendFormInstanceMessage)
Return DoSendFormsResponse
End Function
End Class
C# Sample:
using System;
using System.Collections;
using System.Collections.Generic;
using System.Data;
using System.Diagnostics;
using System.Text;
using System.Web.Services;
using System.Configuration;
using OnlineAVL.PITest.Core;
using OnlineAVL.PITest.Core.OnlineAVL2PI;
using OnlineAVL.PITest.Core.Samples;
public class DoSendFormsCSharpSample
{
currentSession = loginResponse.SecurityProfile.Session;
//Supply list of forms. For each form set Tracking ID,Recipient IDs,Form
//Definition Number, Form fields etc.
//Set Tracking ID
tempSendFormInstanceMessage.TrackingID = Guid.NewGuid();
//Set Form Definition Number
tempSendFormInstanceMessage.DefinitionNumber = 240;
//Set Form Number
tempSendFormInstanceMessage.FormNumber = 50;
//Set Recipients
Guid[] recipientIDs = new Guid[2];
recipientIDs[0] = new Guid("1AD64143-75A2-4665-B0B1-C4B4307CBFEC");
recipientIDs[1] = new Guid("54701928-F7FC-45CA-BED7-9853276EBB6B");
tempSendFormInstanceMessage.RecipientIds = recipientIDs;
//String Field
StringFieldValue objStringFieldValue = new StringFieldValue();
objStringFieldValue.Value = "Dispatcher1";
tempSendFormInstanceMessage.BaseFieldValues.Values.SetValue(
objStringFieldValue, 1);
//Select Field
SelectFieldValue objSelectFieldValue = new SelectFieldValue();
objSelectFieldValue.Value = "1";
tempSendFormInstanceMessage.BaseFieldValues.Values.SetValue(
objSelectFieldValue, 2);
//Address Field
AddressFieldValue objAddressFieldValue = new AddressFieldValue();
objAddressFieldValue.Value = "London";
objAddressFieldValue.Lat = 75.33f;
objAddressFieldValue.Lon = 80.22f;
tempSendFormInstanceMessage.BaseFieldVal
ues.Values.SetValue(
objAddressFieldValue, 3);
//Date Field
DateFieldValue objDateFieldValue = new DateFieldValue();
objDateFieldValue.Value = DateTime.Now.Date;
tempSendFormInstanceMessage.BaseFieldValues.Values.SetValue(
objDateFieldValue, 4);
//Time Field
TimeFieldValue objTimeFieldValue = new TimeFieldValue();
objTimeFieldValue.Value = DateTime.Now.ToLocalTime();
tempSendFormInstanceMessage.BaseFieldValues.Values.SetValue(
objTimeFieldValue, 5);
doSendFormsInstnaceMessages.Add(tempSendFormInstanceMessage);
tempSendFormInstanceMessage.BaseFieldValues.Values.SetValue(
objStringFieldValue, 0);
doSendFormsInstnaceMessages.Add(tempSendFormInstanceMessage);
return DoSendFormsResponse;
}
}
GetSentFormsStatus
VB.NET Sample:
Imports System
Imports System.Collections.Generic
Imports System.Text
Imports System.Web.Services
Imports System.Configuration
Imports OnlineAVL.PITest.Core
Imports OnlineAVL.PITest.Core.OnlineAVL2PI
Imports OnlineAVL.PITest.Core.Samples
Public Class GetSentFormsStatusVBSample
currentSession = loginResponse.SecurityProfile.Session
Dim getSentFormsStatusRequest As New GetSentFormsStatusRequest
Return getSentFormsStatusResponse
End Function
End Class
C# Sample:
using System;
using System.Collections;
using System.Collections.Generic;
using System.Data;
using System.Diagnostics;
using System.Text;
using System.Web.Services;
using System.Configuration;
using OnlineAVL.PITest.Core;
using OnlineAVL.PITest.Core.OnlineAVL2PI;
using OnlineAVL.PITest.Core.Samples;
public class GetSentFormsStatusCSharpSample
{
currentSession = loginResponse.SecurityProfile.Session;
GetSentFormsStatusRequest getSentFormsStatusRequest =
new GetSentFormsStatusRequest();
return getSentFormsStatusResponse;
}
}
GetHardwareDetails
C# Sample:
using System;
using System.Collections.Generic; using System.ComponentModel; using System.Data;
using System.Drawing; using System.Linq; using System.Text;
using System.Threading.Tasks; using System.Windows.Forms;
namespace InstallAppAPISamples
{
// iterate the logic to fetch all items becuase API returns 900 records in
one go
.. // pass the next version in every iteration
do
{
request.Version = version;
response = service.GetHardwareDetails(request);
if (!response.OperationStatus)
return list;
if (response.HardwareDetails != null)
{
list.AddRange(response.HardwareDetails);
}
version = response.Version;
} while (response.MoreItemsAvailable);
return list;
}
}
}
Appendix 4 : Error Messages
Error messages reported by the Published Interface methods are listed below:
Malfunction Definition
Diagnostic Definition
Country:
CountryID FullName Abbreviation
0 United States Of America USA
1 Canada CAN
52 Mexico MEX
61 Australia AUS
64 New Zealand NZ
99 Other OTH
States:
USAStateID FullName Abbreviation CountryID
0 Alabama AL 0
1 Alaska AK 0
2 Arizona AZ 0
3 Arkansas AR
4 California CA 0
5 Colorado CO 0
6 Connecticut CT 0
7 Delaware DE 0
8 District of Columbia DC 0
9 Florida FL 0
10 Georgia GA 0
11 Hawaii HI 0
12 Idaho ID 0
13 Illinois IL 0
14 Indiana IN 0
15 Iowa IA 0
16 Kansas KS 0
17 Kentucky KY 0
18 Louisiana LA 0
19 Maine ME 0
20 Maryland MD 0
21 Massachusetts MA 0
22 Michigan MI 0
23 Minnesota MN 0
24 Mississippi MS 0
25 Missouri MO 0
26 Montana MT 0
27 Nebraska NE 0
28 Nevada NV 0
29 New Hampshire NH 0
30 New Jersey NJ 0
31 New Mexico NM 0
32 New York NY 0
33 North Carolina NC 0
34 North Dakota ND 0
35 Ohio OH 0
36 Oklahoma OK 0
37 Oregon OR 0
38 Pennsylvania PA 0
39 Rhode Island RI 0
40 South Carolina SC 0
41 South Dakota SD 0
42 Tennessee TN 0
43 Texas TX 0
44 Utah UT 0
45 Vermont VT 0
46 Virginia VA 0
47 Washington WA 0
48 West Virginia WV 0
49 Wisconsin WI 0
50 Wyoming WY 0
51 American Samoa AS 0
52 Guam GU 0
53 Northern Marianas MP 0
54 Puerto Rico PR 0
55 Virgin Islands VI 0
100 Alberta AB 1
101 British Columbia BC 1
102 Manitoba MB 1
103 New Brunswick NB 1
104 Newfoundland and Labrador NF 1
105 Northwest Territories NT 1
106 Nova Scotia NS 1
107 Nunavut NU 1
108 Ontario ON 1
109 Prince Edward Island PE 1
110 Quebec QC 1
111 Saskatchewan SK 1
112 Yukon YT 1
5200 Aguascalientes AG 52
5201 Baja California BN 52
5202 Baja California Sur BS 52
5203 Campeche CP 52
5204 Chiapas CS 52
5205 Chihuahua CI 52
5206 Coahuila CH 52
5207 Colima CL 52
5208 Federal District (Mexico City) DF 52
5209 Durango DG 52
5210 Guanajuato GJ 52
5211 Guerrero GE 52
5212 Hidalgo HD 52
5213 Jalisco JA 52
5214 México MX 52
5215 Michoacán MC 52
5216 Morelos MR 52
5217 Nayarit NA 52
5218 Nuevo León NL 52
5219 Oaxaca OA 52
5220 Puebla PU 52
5221 Querétaro QE 52
5222 Quintana Roo QI 52
5223 San Luis Potosí SL 52
5224 Sinaloa SI 52
5225 Sonora SO 52
5226 Tabasco TB 52
5227 Tamaulipas TA 52
5228 Tlaxcala TL 52
5229 Veracruz VC 52
5230 Yucatán YU 52
5231 Zacatecas ZA 52
6100 Australian Capital Territory ACT 61
6101 New South Wales NSW 61
6102 Northern Territory NT 61
6103 Queensland QLD 61
6104 South Australia SA 61
6105 Tasmania TAS 61
6106 Victoria VIC 61
6107 Western Australia WA 61
6200 New Zealand NZ 64
9999 Other OT 99