Routes List API (List Saved Routes)

Use the TrackRoad Routes List API to retrieve previously saved routes using filters such as date range, owner, and route name. For SOAP integrations, the equivalent method is GetRouteList.

TrackRoad Routes List API showing saved routes filtered by date range, owner, and route name
List and filter previously saved routes for reporting, dashboards, and route history lookups.

Need the full contract?

Swagger includes endpoint models and fields for REST, while the WSDL exposes the SOAP contract for GetRouteList and related methods.

View Swagger UI View SOAP WSDL API Reference Overview

Table of contents

  1. What Routes List API does
  2. Endpoints and base URLs
  3. Authentication
  4. Request schema
  5. Response schema
  6. Examples
  7. Common errors
  8. Best practices
  9. FAQ
  10. Related endpoints

What Routes List API does#

The Routes List API returns a list of saved routes for your account. It is commonly used for route history views, dashboards, and search screens where users need to find previously generated routes.

Typical filters include creation date range, owner, and route name. This helps keep route searches fast, focused, and easier to manage in larger fleets.

If you need the full details for one route, including stops, directions, and timing, use the Route API .

Endpoints and base URLs#

The Routes List documentation below focuses on the SOAP integration pattern shown by GetRouteList. Follow your account documentation and Swagger where deployment-specific details differ.

SOAP

Item Value
Endpoint https://trackservice.trackroad.com/TrackService.asmx
WSDL https://trackservice.trackroad.com/TrackService.asmx?WSDL
Method GetRouteList
SOAPAction http://TrackService.TrackRoad.com/GetRouteList

Authentication#

For SOAP, send your TrackServiceKey in SessionIDHeader as SessionID. Login and Logout are not required when using TrackServiceKey.

Keep API keys server-side and avoid exposing authentication values in browser or mobile client code.

Request schema#

The request describes the filters used to find saved routes. In SOAP, these values are passed as GetRouteList parameters.

Route list filter fields

Field Type Required Description
FromDate string (date-time) No Filter routes created or updated on or after this timestamp in ISO 8601 format.
ToDate string (date-time) No Filter routes created or updated on or before this timestamp in ISO 8601 format.
Owner string No Filter by owner or username, if this is supported by your account configuration.
RouteName string No Filter by route name using exact or partial matching, depending on implementation.

If your implementation exposes extra filters such as status, paging, or maximum results, document those additional fields here as well.

Response schema#

A successful response returns a list of routes that match your filters and any status or error information returned by the service.

Routes result

Property Type Description
Routes RouteSummary[] List of matching route summary records.
Errors Error[] Optional errors or warnings returned by the service.
Status int (enum) Status code, commonly 0=None, 1=Success, 2=Failed, 3=SuccessWithErrors.

Route summary

Property Type Description
RouteID string / int Route identifier used later to fetch full route details.
RouteName string Human-friendly route name.
Distance double Total route distance.
Time int Total route time, usually in seconds unless configured differently.
Owner string Owner or creator identifier, when available.
DateCreated string (date-time) Timestamp showing when the route was created.

SOAP returns the same route list concept inside a SOAP envelope, with the result wrapped by GetRouteList response elements.

Examples#

Place the SOAP example request, example response, and multi-language code samples in this section. Example code itself does not need to be localized.

SOAP: request examples (multiple languages)#

SOAP requires SessionIDHeader (SessionID = TrackServiceKey) and the SOAPAction header http://TrackService.TrackRoad.com/GetRouteList.

<!-- POST https://trackservice.trackroad.com/TrackService.asmx -->
<!-- Content-Type: text/xml; charset=utf-8 -->
<!-- SOAPAction: "http://TrackService.TrackRoad.com/GetRouteList" -->

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
               xmlns:xsd="http://www.w3.org/2001/XMLSchema"
               xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

  <soap:Header>
    <SessionIDHeader xmlns="http://TrackService.TrackRoad.com/">
      <SessionID>YOUR_TRACKSERVICEKEY</SessionID>
    </SessionIDHeader>
  </soap:Header>

  <soap:Body>
    <GetRouteList xmlns="http://TrackService.TrackRoad.com/">
      <FromDate>2026-01-01T00:00:00Z</FromDate>
      <ToDate>2026-01-31T23:59:59Z</ToDate>
      <Owner>dispatcher@company.com</Owner>
      <RouteName>January</RouteName>
    </GetRouteList>
  </soap:Body>
</soap:Envelope>

SOAP: response example (shape)#

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
               xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
               xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <soap:Body>
    <GetRouteListResponse xmlns="http://TrackService.TrackRoad.com/">
      <GetRouteListResult>
        <Routes>
          <RouteSummary>
            <RouteID>12345</RouteID>
            <RouteName>January - North Zone</RouteName>
            <Distance>82.4</Distance>
            <Time>14250</Time>
            <Owner>dispatcher@company.com</Owner>
            <DateCreated>2026-01-12T16:21:00Z</DateCreated>
          </RouteSummary>
        </Routes>
        <Status>1</Status>
        <Errors />
      </GetRouteListResult>
    </GetRouteListResponse>
  </soap:Body>
</soap:Envelope>

Common errors#

  • Authentication error: Missing or invalid SessionIDHeader. The SessionID value must be your TrackServiceKey.
  • Invalid date format: Provide dates in ISO 8601 format, for example 2026-01-31T23:59:59Z.
  • No matching routes: Your filter range, owner, or route name may be too restrictive.
  • Service or permission issue: The key may be valid but blocked, expired, or limited for the requested account scope.

Best practices#

  • Use date filters to keep responses fast and predictable, especially for route history screens.
  • Cache route lists for dashboards that load frequently, then refresh on demand when users search again.
  • Load route details only when needed instead of fetching full route data for every result row.
  • Document account-specific fields when your deployment supports extra filters or custom response properties.

FAQ#

What does the Routes List API do?
The Routes List API returns a list of previously saved routes, usually filtered by date range, owner, or route name.
What is the SOAP equivalent of the Routes List API?
The SOAP method name is GetRouteList.
How do I authenticate?
For SOAP, send your TrackServiceKey in SessionIDHeader as SessionID. Login and Logout are not required when using TrackServiceKey.
When should I use the Routes List API instead of Route API?
Use the Routes List API to search and list saved routes. Use the Route API when you need full route details such as stops, directions, and timing.

Want route details?

Use Routes List to find saved RouteID values, then open Route API documentation to load full stop lists, route distances, and timing details.

Go to Route API View Swagger UI