This document introduces the Intermodal Routing API v8. It explains key concepts and provides examples. It documents resources, query parameters, response structures and data types. For the terms and conditions covering this documentation, see the HERE Documentation License.

What is the Intermodal Routing API v8?

The Intermodal Routing API v8 is a HTTP JSON REST API that offers an innovative and smart routing experience across cities. This is possible when the consolidated public transit offer is intertwined with external mobility services dynamically scattered in urban areas. This scenario opens a wide set of ready-to-use mobility options to quickly and better navigate between a given pair of locations.

The Intermodal Routing API v8 combines four distinct transport types, namely vehicle, transit, taxi, and rented to create multiple intermodal services. The availability of each service depends on the availability of the transport types and modes of transport in the urban context across which you move. For more information on the services and transport types of Intermodal Routing API v8, see the Intermodal Services & Transport Types section.

Why Use the Intermodal Routing API v8?

The Intermodal Routing API v8 can use a combination of the following routing services:

  • Vehicle routing
  • Intermodal routing with real-time and timetable departures
  • Pedestrian routing with pedestrian connectivity
  • Real-time traffic and traffic incidents
  • Public transit routing
  • Public transit service delays/disruptions information from transit authorities
  • Amenities available at transit stations or nearby (such as parking, EV charging stations)
  • Rentable services available at transit stations or nearby (such as car sharing, taxi, bike)

Future developments

Urban mobility evolves in parallel with the city. The documentation anticipates the need of an open-ended list of values through the x-extensible-enum swagger functionality. For instance, unknown values such as new transport modes should be expected in the response and should be handled gracefully.

The following schema types should be considered extendable:

  • Place
  • Transport
  • Action
  • Price
  • NoticeDetail

For more information on how to use the Intermodal Routing API v8, see how to Get Started.

Support requests

When submitting bug reports and asking for support for specific route calculations, always provide the routing request URI and the corresponding errorCode, if any.

results matching ""

    No results matching ""