TomTom Search API

Name: TomTom Search API API
Brand: TomTom Search API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMaps GeolocationPlaces SearchapiKey16 EndpointsREST

For Agents

Search for addresses, POIs, and places using fuzzy, category, geometry, or along-route queries. Geocode and reverse geocode with cross-street resolution.

Connect the TomTom Search API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TomTom Search API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 TomTom Search API API.

Perform fuzzy search across addresses, POIs, and geographic features with typo tolerance and typeahead support

Geocode addresses using free-form or structured queries with country code, street, and postal code components

Reverse geocode coordinates to street-level addresses with optional speed limit and road use data

Search for points of interest by category within a bounding box or radius

GET STARTED

Start building with TomTom Search API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for TomTom Search API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for TomTom Search API, keeping it validated and agent-ready. Run fuzzy, category, POI, nearby, and geometry-based searches across TomTom's global location database to find addresses, businesses, and points of interest. The API supports forward and structured geocoding, reverse geocoding with cross-street lookup, search along a driving route with detour-time constraints, and geometry filtering to restrict results to custom polygons or circles — all returning coordinates, address components, and POI metadata across 16 endpoints.

Use Cases

Patterns agents use TomTom Search API API for, with concrete tasks.

★ AI Agent Location Search via Jentic

AI agents use TomTom's fuzzy search endpoint to resolve ambiguous location references from user queries into precise coordinates and structured addresses. Through Jentic, agents search for 'find a location' and receive the operation schema for the fuzzy search endpoint, which handles misspellings, partial addresses, and POI names in a single query. The typeahead mode enables real-time suggestions, and results include coordinates, formatted addresses, and match scores.

Search for 'pizza near Times Square' using the /search/2/search/{query}.json endpoint with lat=40.758 and lon=-73.985 and return the top 3 results with coordinates

Along-Route POI Discovery for Navigation

Navigation and trip-planning applications find fuel stations, restaurants, or rest areas along a planned route without requiring significant detours. The searchAlongRoute endpoint accepts a route geometry (as an array of lat/lon points) and a maximum detour time in seconds, returning only POIs reachable within that constraint. This eliminates irrelevant results that are geographically close but require long detours to reach.

Search for 'gas' along a route from San Francisco to San Jose with a maximum detour time of 600 seconds using the /search/2/searchAlongRoute/{query}.json POST endpoint

Geometry-Based Geofence Querying

Logistics and delivery platforms query POIs within custom delivery zones defined as polygons or circles. The geometrySearch endpoint accepts a query term and a list of geometry shapes (circles with center/radius or polygons with vertices), returning only results that fall within those boundaries. The geometry filter endpoint further narrows existing result sets to custom areas.

Search for 'restaurant' within a circle of 2000m radius centered at 37.7749,-122.4194 using the /search/2/geometrySearch/{query}.json endpoint

Reverse Geocoding for Vehicle Telematics

Telematics systems convert raw GPS streams from vehicles into street-level addresses for driver logs, trip reports, and compliance records. The reverse geocode endpoint returns the street address, and optionally the posted speed limit and road use classification (arterial, local, ramp). Cross-street lookup provides the nearest intersection name for more human-friendly location descriptions.

Reverse geocode position 37.8328,-122.27669 using the /search/2/reverseGeocode/{position}.json endpoint with returnSpeedLimit=true and return the address and speed limit

Key Endpoints

16 endpoints — jentic publishes the only available openapi specification for tomtom search api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/search/{versionNumber}/search/{query}.{ext}

Fuzzy search for addresses, POIs, and features

GET

/search/{versionNumber}/geocode/{query}.{ext}

Forward geocode an address

GET

/search/{versionNumber}/structuredGeocode.{ext}

Structured geocode with address components

GET

/search/{versionNumber}/reverseGeocode/{position}.{ext}

Reverse geocode coordinates to address

GET

/search/{versionNumber}/poiSearch/{query}.{ext}

Search for points of interest

GET

/search/{versionNumber}/nearbySearch/.{ext}

Find nearby POIs by location

POST

/search/{versionNumber}/searchAlongRoute/{query}.{ext}

Search POIs along a driving route

GET

/search/{versionNumber}/geometrySearch/{query}.{ext}

Search within custom geometry shapes

GET

/search/{versionNumber}/search/{query}.{ext}

Fuzzy search for addresses, POIs, and features

GET

/search/{versionNumber}/geocode/{query}.{ext}

Forward geocode an address

GET

/search/{versionNumber}/structuredGeocode.{ext}

Structured geocode with address components

GET

/search/{versionNumber}/reverseGeocode/{position}.{ext}

Reverse geocode coordinates to address

GET

/search/{versionNumber}/poiSearch/{query}.{ext}

Search for points of interest

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

TomTom API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — the raw `key` query parameter value never enters the agent's context window.

Intent-based discovery

Agents search by intent (e.g., 'search for places along a route' or 'geocode an address') and Jentic returns matching TomTom Search operations with their full input schemas, so the agent can call the correct endpoint without parsing TomTom developer docs.

Time to first call

Direct TomTom integration: 2-4 days for auth, endpoint selection across 16 operations, and error handling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

HERE Geocoding & Search API

Similar geocoding and place search with autosuggest, category browse, and place detail lookup

Choose HERE when you need autosuggest with character-level highlights, category-based browsing by HERE category IDs, or place detail lookup by ID — features TomTom Search does not offer.

Alternative

LocationIQ API

OSM-based geocoding and search with routing and lower pricing

Choose LocationIQ when you need OpenStreetMap-based results, combined geocoding and turn-by-turn routing in one API, or lower-cost high-volume geocoding.

Complementary

TomTom Routing API

Calculate routes, distances, and travel times to complement search results

Use TomTom Routing when you need full route calculation between waypoints — Search along route finds POIs on a route, but Routing API calculates the route geometry itself.

FAQs

Specific to using TomTom Search API API through Jentic.

Why is there no official OpenAPI spec for TomTom Search API?

TomTom does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call TomTom Search API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the TomTom Search API use?

The TomTom Search API uses an API key passed as the `key` query parameter on every request. Through Jentic, your TomTom API key is stored encrypted in the MAXsystem vault and injected automatically — agents never see the raw key value.

Can I search for POIs along a driving route with the TomTom API?

Yes. The /search/2/searchAlongRoute/{query}.json POST endpoint accepts a route geometry (array of lat/lon points) and a `maxDetourTime` parameter (up to 3600 seconds). It returns only POIs reachable within that detour constraint, sorted by detour time from the route.

What are the rate limits for the TomTom Search API?

TomTom returns HTTP 403 when queries-per-second or account rate limits are exceeded. Free tier accounts allow 2,500 transactions per day with 5 QPS. Paid plans scale based on contract terms with higher concurrency and monthly quotas.

How do I perform a geometry-based search through Jentic?

Install the Jentic SDK with `pip install jentic` and search for 'search within a polygon'. Jentic returns the /search/2/geometrySearch/{query}.json operation schema. Pass your query term, a geometryList with POLYGON vertices or CIRCLE position/radius, and execute through Jentic to get POIs within your custom boundary.

What is the difference between fuzzy search and POI search?

Fuzzy search (/search/2/search/) queries across all index types — addresses, streets, POIs, and geographic features — with typo tolerance. POI search (/search/2/poiSearch/) is restricted to points of interest only and is optimized for business/place name queries. Use fuzzy search when the input could be anything; use POI search when you specifically want business results.