canonical: https://jentic.com/apis/tomtom.com

# TomTom APIs

TomTom provides location APIs covering search and geocoding, route and reachable-range calculation, and map imagery. Across its APIs an agent can resolve addresses and points of interest, convert coordinates to street-level addresses, calculate routes between waypoints, and fetch map tiles, static images, and copyright data, all secured with an API key.

## For AI agents

An agent can search for addresses and points of interest, geocode and reverse geocode coordinates, find POIs along a driving route, calculate routes and reachable ranges between locations, and retrieve map tiles, static images, and copyright information across TomTom's location APIs.

## Scope

Use for: Location search, geocoding, reverse geocoding, route and reachable-range calculation, and map tile and image retrieval using TomTom location data

Not supported:
- payments
- messaging
- crm
- real-time traffic streaming
- fleet tracking
- on-prem deployment

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| TomTom API | developer-tools | 17 | Programmatically fuzzy search, points of interest search. |
| TomTom Search API | maps-geolocation | 16 | Search for addresses, POIs, and places using fuzzy, category, geometry, or along-route queries. |
| Maps | media | 10 | Programmatically copyrights whole world, captions. |
| Routing | maps-geolocation | 4 | Programmatically reachable range, reachable range. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Search addresses, POIs, and places, with fuzzy, category, geometry, or along-route queries plus geocoding and reverse geocoding | tomtom-search-api | Dedicated search surface with 16 endpoints covering fuzzy search, forward and structured geocoding, reverse geocoding with cross-street lookup, and geometry and along-route filtering |
| General TomTom access spanning search, geocoding, routing, and traffic flow from a single API | tomtom-api | Broad 17-endpoint API that bundles fuzzy search, POI and category search, autocomplete, and place lookup alongside geocoding and routing |
| Calculate a route between waypoints or a reachable range from an origin | tomtom-routing-api | Focused routing API for calculateRoute and calculateReachableRange with traffic and avoidance parameters |
| Fetch map tiles, static images, or copyright and caption data | tomtom-maps-api | Maps imagery API for raster and vector tiles, static images, WMS/WMTS, and copyright retrieval |

## Cross-API use cases

### Resolve a place then route to it

An agent geocodes a user's destination with the Search API to get coordinates, then passes those coordinates to the Routing API to calculate a route and travel time from the origin. This turns an ambiguous address string into a full driving route in one workflow.

Example prompt: Geocode '4 North 2nd Street, San Jose' via tomtom-search-api, then call calculateRoute on tomtom-routing-api from the user's origin to those coordinates

### Find POIs along a route and calculate the detour

An agent calculates a route with the Routing API, uses the Search API to find fuel stations or restaurants along that route within a maximum detour time, and returns the reachable stops. This combines route geometry with along-route POI discovery.

Example prompt: Call calculateRoute on tomtom-routing-api, then pass the route geometry to searchAlongRoute on tomtom-search-api with a 600 second max detour time

### Search a location and render it on a map

An agent resolves a query to coordinates with the Search API and then fetches a static map image or map tile for those coordinates with the Maps API, producing a visual result for the user. Copyright data can be retrieved alongside the imagery.

Example prompt: Fuzzy search a place via tomtom-search-api, then request a static image at the returned coordinates from tomtom-maps-api

### Broad location workflow from one API plus dedicated maps

An agent uses the general TomTom API for combined search, geocoding, and routing, then supplements it with the Maps API to render tiles or static images for the resolved locations. This suits agents that prefer a single search-and-route surface with imagery added on top.

Example prompt: Run fuzzy search and routing through tomtom-api, then fetch matching map tiles from tomtom-maps-api

## Why Jentic

- **Setup:** Wiring TomTom by hand means appending the key query parameter to every call and tracking the api.tomtom.com host across search, routing, and maps paths. With Jentic One installed you import each TomTom API from the Jentic directory, store the key once, and your agent calls any of them.
- **Permission scoping:** Every TomTom API here is read-only, so you scope the agent to only the operations it needs, such as geocoding an address, calculating a route, or fetching a map tile. Your own rules in your Jentic One instance decide which operations and credentials the agent may use, and only those you include are callable.
- **Credential handling:** Your single TomTom API key is stored encrypted by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context, and the same key covers all four APIs.
- **Discovery method:** Agents search the Jentic directory by intent such as 'geocode an address', 'calculate a route', or 'fetch a static map image', and Jentic returns the matching TomTom operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related vendors

- **HERE** — Comparable location platform with geocoding, search, routing, and map imagery services
- **Google Maps Platform** — Alternative for geocoding, places search, directions, and map tiles
- **LocationIQ** — OpenStreetMap-based geocoding, search, and routing at lower volume pricing
- **Mapbox** — Alternative for map tiles, static images, geocoding, and directions

## FAQ

### What can an AI agent do across TomTom's APIs?

An agent can search for addresses and points of interest, geocode and reverse geocode coordinates, find POIs along a driving route, calculate routes and reachable ranges between locations, and fetch map tiles, static images, and copyright data. Together these APIs cover resolving a place, routing to it, and rendering it on a map.

### Do I need separate credentials for each TomTom API?

No. All TomTom APIs use the same API key passed as the key query parameter, so a single credential covers search, geocoding, routing, and maps access.

### Which TomTom API should I use for location search?

Use the TomTom Search API for dedicated address, POI, and place search with fuzzy, category, geometry, and along-route queries plus geocoding and reverse geocoding. The general TomTom API also includes search if you want one surface that spans search, geocoding, and routing.

### How do the search and routing APIs work together?

The Search API resolves an address or place into coordinates, and the Routing API calculates a route or reachable range from those coordinates. The Search API can also find POIs along a route that the Routing API has calculated, within a maximum detour time.

### Can TomTom render maps, not just data?

Yes. The Maps API returns raster and vector map tiles, static images, and WMS/WMTS layers, along with copyright and caption data. An agent can resolve a location with search and then fetch imagery for it from the Maps API.

### Are all four TomTom APIs read-only?

Yes. Search, geocoding, routing, reachable-range, and map retrieval are all read operations, so an agent can be scoped to just the operations it needs without any write access to TomTom data.