Sorry, you need to enable JavaScript to visit this website.

Browse the FAQs to find solutions to common questions.

No. The Routing API always uses the freshest available traffic situation where it is relevant for the planned route.

Depending on the call, it may use both. Real-time route calculations (where departAt=now, or where the default of now is assumed) will use real-time traffic information where it's available. Longer-term traffic information such as road closures will also be included where it is relevant. In addition, all routes planned use TomTom's IQ Routes database of historic traffic information for the day and time provided.

Yes. Groups of up to 20 waypoints can be returned in an optimized route order if the computeBestOrder parameter is set to true. See the documentation for further information on this feature.

The Routing API does not offer this facility. Application developers should use the list of coordinates in the points section of the API response to draw the route path on their maps.

In addition to the start and end points, the API can be called with a maximum of 50 intermediate points. See the documentation for how to include them in the call.

Note that optimized routing calls are limited to 20 waypoints in addition to the journey start and end.

The Routing API uses latitude and longitude (EPSG4326/WGS84) coordinates for both input and output. The request must have a start point and an end point, and may have up to 50 intermediate waypoints between them. All input coordinates must be colon-delimited latitude,longitude pairs (lat1,lon1:lat2,lon2:lat3,lon3...). The first and last coordinates will be used as the start and end points of the route.

Not all functionality offered in the Map Kit Routing API is available from the Routing API call yet. If the functionality you need is available, contact an account manager for guidance on how to transition your usage. If it is not, continue to use the Map Kit Routing API.


Production key holders will be given advance notice before the Map Kit Routing API is withdrawn from use, and assistance with the migration will be available.

In theory, you could check that all of the path points in the response match. That would guarantee that the two routes have exactly the same geometry. However, a quick way to check is to compare the lengthInMeters of two routes. Although it's possible that two different routes to the same place could have exactly the same length, it's not likely.

The Routing API calculates the fastest route through the given waypoints, taking traffic into account if the traffic parameter is true. For example, suppose there are two routes from point A to point B. One of them is a motorway with a speed limit of 100kph, but traffic has slowed cars down to 80 kph. The other route is an empty surface street with a speed limit of 30kph. In those circumstances the software will choose the motorway route, because even though it goes through traffic, it is still the quickest way from A to B.