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

# TomTom API

TomTom APIs for search, routing, geocoding, reverse geocoding, and traffic flow data. The API exposes 17 endpoints secured with apiKey authentication.

## For AI agents

Programmatically fuzzy search, points of interest search. Covers 17 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Fuzzy Search
- Points of Interest Search
- Category Search
- Nearby Search
- Geometry Search
- Autocomplete
- Place by ID

## Use cases

### Developer Tools Operations

Use the TomTom API to perform developer tools operations programmatically. The API provides 17 endpoints covering core functionality including fuzzy search, points of interest search, category search.

Example prompt: Call GET /search/2/search/{query}.{ext} to fuzzy search

### Automated Search Management

Automate search operations by combining multiple TomTom API endpoints. Agents can points of interest search and then category search in a single workflow.

Example prompt: Call GET /search/2/poiSearch/{query}.{ext} to points of interest search, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call TomTom API 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.

Example prompt: Search Jentic for 'fuzzy search', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /search/2/search/{query}.{ext} | Fuzzy Search |
| GET | /search/2/poiSearch/{query}.{ext} | Points of Interest Search |
| GET | /search/2/categorySearch/{query}.{ext} | Category Search |
| GET | /search/2/nearbySearch/.{ext} | Nearby Search |
| GET | /search/2/geometrySearch/{query}.{ext} | Geometry Search |
| GET | /search/2/autocomplete/{query}.{ext} | Autocomplete |
| GET | /search/2/place.{ext} | Place by ID |
| GET | /search/2/poiCategories.{ext} | POI Categories |

## Key resources

- **Search** — Search for addresses, POIs, and locations.
- **Geocoding** — Forward and reverse geocoding.
- **Routing** — Route calculation and reachable range.
- **Traffic** — Real-time traffic flow data.

## Why Jentic

- **Setup:** Wiring the TomTom API by hand means appending its key query parameter to every call, encoding the query and extension into the URL path, and tracking the api.tomtom.com search host. Through Jentic you install once, import the TomTom API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The TomTom API here is read-only place and point-of-interest search, so scope the agent to the operations it needs, such as fuzzy search or nearby search. You choose which operations are allowed, and only those you include are callable.
- **Credential handling:** 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.
- **Discovery method:** Agents search Jentic by intent such as 'fuzzy search for a place' or 'find nearby points of interest', and Jentic returns the matching TomTom operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the TomTom API use?

The TomTom API 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 fuzzy search with the TomTom API?

Yes. Use the GET /search/2/search/{query}.{ext} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the TomTom API?

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 fuzzy search through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'fuzzy search'. Jentic returns the matching TomTom API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the TomTom API have?

The TomTom API exposes 17 endpoints covering search, geocoding, routing operations.

### Can I limit what my agent is allowed to do with the TomTom API?

Yes. The TomTom API here is read-only place and point-of-interest search, and because Jentic One is self-hosted, you decide which of its operations your agent may call. Import only the endpoints you need, such as fuzzy search or nearby search, and any operation you leave out stays uncallable. The credentials your agent uses are governed by the same rules you set on your own instance.