Search logo

Search

Search

TomTom Search API performs geocoding and POI search — address to coordinates, reverse geocoding, fuzzy "coffee shops near me" search.

Visit site ↗Health checked 9h ago
Use it when

Fast typeahead (<100ms typical)

Watch for

China POI not as complete as Amap/Baidu

First check

GET /search/2/search/{query}.json?key=... for keyword search; POST /search/2/reverseGeocode/{lat,lon}.json?key=... for reverse.

Auth
api_key
CORS
No
HTTPS
Yes
Signup
Required
Latency
1067 ms
Protocol
REST
Pricing

Uptime · 30-day window

Probes: 1Uptime: 100%Avg latency: 1067ms
01

About this API

Search API is one of the core APIs in TomTom's location platform. Two most common capabilities: geocoding (address to coordinates — user types "Three-Lit Town Beijing", API returns lat/lon) and reverse geocoding (coordinates to address — user drives somewhere, app shows "you're at XX Road #XX"). Search API also supports POI search ("nearby gas stations" returns categorized, distance/rated business list) and address autocomplete (user types "Three-Lit", instant complete-address suggestions). Direct competitors: Google Places, Mapbox Geocoding. TomTom's advantage: routing-adjacent scenarios (post-geocoding handoff to TomTom Routing). Mid-tier pricing.

02

What you can build

  • 1Address auto-complete input
  • 2Reverse geocoding (display street name from GPS)
  • 3Nearby business discovery
  • 4Route planning origin/destination resolution
03

Strengths & limitations

Strengths

  • Fast typeahead (<100ms typical)
  • Fuzzy search ("starbcks" still matches)
  • POI data in 200+ categories

Limitations

  • China POI not as complete as Amap/Baidu
  • Weaker address resolution for some small languages
04

Example request

Generic template — replace <endpoint> with the real path from the docs.
curl https://developer.tomtom.com/contact-us/<endpoint> \
  -H "Authorization: Bearer $API_KEY"
# Some providers use X-Api-Key instead — verify in the docs.
05

Getting started

GET /search/2/search/{query}.json?key=... for keyword search; POST /search/2/reverseGeocode/{lat,lon}.json?key=... for reverse.

06

FAQ

How many autocomplete suggestions are ideal?+

5-7 suggestions is best UX. More than that, users don't look.

Can it handle informal addresses?+

Yes. Search API defaults to fuzzy mode — handles typos and incomplete addresses.

07

Technical details

CORS: NoHTTPS: YesSignup: YesOpen source: No
Auth type
api_key
Pricing
unknown
Protocols
REST
SDKs
javascript, ios, android
Response time
1067 ms
Last health check
5/12/2026, 7:38:31 AM
08

Tags

09

More from Tomtom