This API can be used in synchronous and asynchronous modes. The default mode of operation is synchronous mode where the API response with toll information is returned immediately.

Asynchronous mode is used in the following cases:

Bulk upload of multiple GPS tracks files
Uploading large GPS tracks files

In asynchronous mode, the response is returned immediately with a requestId and requestedTimestamp. The results will be available for download for upto 30 days by calling the route/download API. Asynchronous mode can used by specifying the url parameter isAsync=true.

GPS traces can be passed in the following format

Upload CSV file
Upload kml file
Upload gpx file
Upload nmea file

The first line in the CSV needs to contain the attribute names. The subsequent lines needs to contain the data in temporal order. The following parameters are available:

Parameter	Description
latitude	Latitude coordinate in WGS84 degree (mandatory)
longitude	Longitude coordinate in WGS84 degree (mandatory)
timestamp	indicates the time and date, for example 2018-05-21T17:05:06Z (mandatory since tolls may change based on time)
speed_mps	speed in meters per second (optional)
speed_mph	speed in miles per hour (optional)
speed_kmh	speed in kilometers per hour (optional)
heading	heading in degrees clockwise from North (optional)

You can download sample file from here

Or use the CSV format file as shown in the table below:

latitude	longitude	timestamp
38.90479	-77.02607	2019-12-16T15:45:23Z
38.90479	-77.02606	2019-12-16T15:47:24Z
38.9048	-77.02608	2019-12-16T15:49:25Z
38.9044	-77.02604	2019-12-16T15:50:42Z
38.90424	-77.02646	2019-12-16T15:50:49Z
38.90422	-77.02686	2019-12-16T15:50:55Z

Take care of the following things:

GPX: Each trace point can have the following information:
Coordinates, for example <trkpt lat="38.90479" lon="-77.02607"> (always present), WGS84 degree
A timestamp, for example <time>2019-12-16T15:45:23Z</time> (optional), time zone UTC
Elevation, for example <ele>102.5999</ele> (optional), meter above the WGS84 ellipsoid
HDOP, for example <hdop>15.0</hdop> (optional)
Speed, for example <extensions><speed>21.9432334</speed></extensions> (optional), meter per second
NMEA: The information from the $GPRMC records is used. If an NMEA trace does not contain $GPRMC records, then the $GPGGA records are used.
KML: Either <Placemarks with <Points> or <Placemarks> with <LineStrings> can be submitted. Note: Folders with multiple traces are not supported.
KML files may not work if user is looking for timebased tolls