Register at developer.tomtom.com and generate an API key from the dashboard.
Call the TomTom Calculate Route endpoint (GET /routing/1/calculateRoute/{origin}:{destination}/json) with travelMode set to car and include the traffic parameter to get live-traffic-aware ETAs.
To enable EV range routing, add EV-specific parameters: vehicleMaxSpeed, currentChargeInkWh, maxChargeInkWh, and chargingModes (including connectorType and chargingPower) to the request.
Parse the response route sections; for EV routes with charging stops TomTom returns chargingInformationAtEndOfLeg for each leg, indicating charging duration and departure charge.
Retrieve turn-by-turn guidance instructions from the guidance.instructions array in the response; each instruction includes maneuver type, road name, and distance to the next maneuver.
Use the TomTom Traffic Flow API alongside routing to display speed segments on the map and highlight congested sections to help users understand ETA confidence.
Known gotchas
EV routing in TomTom requires well-calibrated vehicle parameters (efficiency curve, max charge); using default/estimated values produces inaccurate range predictions — obtain OEM consumption data where possible.
The TomTom Routing API key is included as a query parameter in the URL; never log full request URLs in production logs as they will expose the API key.
TomTom deprecated several v1 Routing API parameters in 2024 in favour of v1 Long Distance EV Routing endpoint — verify the correct endpoint and parameter set in the current developer.tomtom.com docs.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp