Tomtom Routing
Browse all Tomtom APIs★ Only Publicly Available OpenAPI DocumentMaps GeolocationRouting DirectionsapiKey4 EndpointsREST
For Agents
Programmatically reachable range, reachable range. Covers 4 operations with apiKey authentication.
Use for: I need to reachable range, I want to reachable range, Search for calculate route, Find all calculate route
Not supported: Does not handle payments, communications, or crm - use for maps and geolocation only.
Routing consists of the following service: <b>Calculate Route</b> Calculates a route between an origin and a destination, passing through waypoints (if specified). Additional routing parameters like traffic, avoidance conditions, departure/arrival time etc. can be taken into account. <b>Calculate Reachable Range</b> Calculates a set of locations that can be reached from the origin point, subject t. The API exposes 4 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Routing to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Routing, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftomtom.com%2Frouting" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftomtom.com%2Frouting" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Routing API.
Reachable Range
Calculate Route
Integrate Routing into automated workflows
Query and filter Routing records by parameters
Monitor Routing operational status and events
Use Cases
Patterns agents use Routing API for, with concrete tasks.
★ Maps and Geolocation Operations
Use the Routing to perform maps geolocation operations programmatically. The API provides 4 endpoints covering core functionality including reachable range, reachable range, calculate route.
Call POST /routing/{versionNumber}/calculateReachableRange/{origin}/{contentType} to reachable range
Automated Routing Management
Automate routing operations by combining multiple Routing endpoints. Agents can reachable range and then calculate route in a single workflow.
Call GET /routing/{versionNumber}/calculateReachableRange/{origin}/{contentType} to reachable range, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Routing endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'reachable range', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
4 endpoints — routing consists of the following service: <b>calculate route</b> calculates a route between an origin and a destination, passing through waypoints (if specified).
METHOD
PATH
DESCRIPTION
POST
/routing/{versionNumber}/calculateReachableRange/{origin}/{contentType}
Reachable Range
GET
/routing/{versionNumber}/calculateReachableRange/{origin}/{contentType}
Reachable Range
POST
/routing/{versionNumber}/calculateRoute/{locations}/{contentType}
Calculate Route
GET
/routing/{versionNumber}/calculateRoute/{locations}/{contentType}
Calculate Route
POST
/routing/{versionNumber}/calculateReachableRange/{origin}/{contentType}
Reachable Range
GET
/routing/{versionNumber}/calculateReachableRange/{origin}/{contentType}
Reachable Range
POST
/routing/{versionNumber}/calculateRoute/{locations}/{contentType}
Calculate Route
GET
/routing/{versionNumber}/calculateRoute/{locations}/{contentType}
Calculate Route
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring TomTom Routing by hand means appending its key query parameter to every call, encoding origins and locations into the URL path, and tracking the api.tomtom.com host. Through Jentic you install once, import Routing from the API Directory, store the key once, and your agent calls it.
Permission scoping
TomTom Routing is read-only route and reachable-range calculation, so scope the agent to the operations it needs, such as calculating a route or a reachable range. You choose which operations are allowed, and only those you include are callable.
Credential isolation
Your TomTom key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'calculate a route' or 'find the reachable range', and Jentic returns the matching Routing operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Routing API through Jentic.
What authentication does the Routing use?
The Routing uses an API key passed in the `key` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I reachable range with the Routing?
Yes. Use the POST /routing/{versionNumber}/calculateReachableRange/{origin}/{contentType} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Routing?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I reachable range through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'reachable range'. Jentic returns the matching Routing operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Routing have?
The Routing exposes 4 endpoints covering routing operations.
Can I limit what my agent is allowed to do with the TomTom Routing API?
Yes. Because you run Jentic One yourself, your own rules decide which TomTom Routing operations and credentials the agent can use. Since this API is read-only route and reachable-range calculation, you can scope the agent to just the calls it needs, such as calculating a route or calculating a reachable range, and leave everything else out. Only the operations you include are callable, so the agent cannot reach any endpoint you have not granted.
GET STARTED