Skip to main content

Overview

Routing API helps you plot one or multiple routes on the map for transport or walking. An interactive example below shows building a route for a car:



To edit the example code, select Source code and then Edit on Codepen.

You can also work with Routing API in the playground (no authorization needed).

Key features

Route types


For each route, you can obtain:

  • Length, travel time, and full geometry.
  • Elevation change along the route.
  • Information about special points on the route, such as the start of a toll road.

Route building parameters

You can consider the following parameters when building routes, depending on the selected transport type:

  • Real-time traffic (with regular updates) or statistically predicted congestion.
  • Road closures (considered by default, can be forcibly ignored).
  • Public transport lanes for taxis and emergency services.
  • Different road types.
  • Pedestrian crossings, stairways, and detours.
  • Exclusion of a specific area.
  • Weight, dimensions, and sign restrictions for trucks.

For more information about route parameters, see API Reference.

Limitations

Route points

  • Up to 10 waypoints, including the start and finish points for cars and trucks.
  • Up to 5 waypoints, including the start and finish points for pedestrian routes.
  • Up to 50 pairs of points when building multiple routes in one request (using intermediate points is not supported).

Truck routing

Truck routing is available in the following countries:

  • Azerbaijan
  • Armenia
  • Belarus
  • Georgia
  • Kazakhstan
  • Russia
  • Uzbekistan
  • United Arab Emirates

Emergency services routing

Routing for emergency services is available in the following countries:

  • Oman
  • Saudi Arabia
  • United Arab Emirates

Tariffs

  • When building a route for one set of points (including intermediate points), the number of requests is charged. Building alternative routes is not charged additionally.
  • When building multiple routes for a set of point pairs, calculations for each pair of points are charged. For example, if you specify 5 arrays of point pairs (points field) in one request, 5 calculations are charged.

What's next?