TomTom Search / Places API

"Search is a RESTful API designed for developers allowing single-line fuzzy search for addresses and POIs. Search assigns a latitude/longitude to a specific address, cross street, geographic feature, or point of interest (POI)." [1]

developer.tomtom.com/search-api/documentation/product-information/introduction · By TomTom · Agent JSON · Suggest an edit · Last verified 2026-06-14 · Source confidence: high

TomTom Search / Places API is a REST service covering geocoding, reverse geocoding, fuzzy place search, POI discovery, autocomplete, along-route search, and EV charging station lookup across approximately 190 countries. Pricing starts at $2.50 per 1,000 requests with a free tier of 2,500 non-tile requests per day requiring no credit card, plus enterprise plans. The API authenticates via API key, offers a JavaScript/TypeScript SDK and an MCP server, and holds ISO 27001 certification with GDPR compliance. Automotive customers including Volkswagen Group, Stellantis, Toyota, and BMW Motorrad represent its strongest deployment vertical.

Best for / Avoid if

Best for: Prototypes and side projects - free to start, no sales call; AI agents and automation - an agent-ready surface (MCP / llms.txt); Teams needing broad API coverage out of the box

Avoid if: You have strict compliance requirements

Scores

  • 40 / 100
    Agent friendliness
  • 100 / 100
    Pricing transparency
  • 75 / 100
    Setup speed
  • 15 / 100
    Docs quality
  • 100 / 100
    Procurement ease
  • 30 / 100
    Trust readiness

Scores are computed deterministically from this profile's published, sourced fields (pricing, compliance, capabilities, docs and developer-surface signals) - not from reviews or paid placement. Each axis is 0-100; an unknown signal scores 0 for that axis. Procurement ease is the inverse of buying friction (higher = easier to adopt).

Pricing & procurement

Pricing model
Hybrid (base + usage) [2]
Published pricing
Yes [3]
Free tier
Yes [4]
Free tier details
Recurring daily allowance: 2,500 free non-tile requests/day and 50,000 free tile requests/day across all products. No credit card required. Commercial use permitted.
Self-serve signup
Yes
Requires sales call
No
Enterprise plan
Yes [5]
Published prices
PlanItemPerAmountSource
FreemiumNon-tile requests (Search, Places, Geocoding, etc.)2,500 requests/day (recurring daily allowance)$0source
FreemiumTile requests (Map Display, Traffic tiles)50,000 requests/day (recurring daily allowance)$0source
Pay As You GrowSearch API (Fuzzy Search, POI Search, all Search endpoints)1,000 requests$2.5source
Pay As You GrowEV Charging Stations Availability / EV Search API1,000 requests$2.5source
Pay As You GrowGeocoding API1,000 requests$0.75source
Pay As You GrowBatch Search API1,000 requests$0.75source
Pay As You GrowReverse Geocoding API1,000 requests$0.5source
EnterpriseSearch / Places APIs (custom pricing) - source

Capabilities

  • POI search
  • Nearby / radius
  • Autocomplete
  • Place details
Supported actions
fuzzy_search, poi_search, category_search, geometry_search, nearby_search, along_route_search, autocomplete, geometry_filter, additional_data, place_by_id, poi_categories, reverse_geocode, crossstreet_lookup, batch_fuzzy_search_sync, batch_fuzzy_search_async, ev_charging_stations_availability [6]
Regions
Americas, Asia Pacific, Europe, Middle East & Africa, global coverage across approximately 190+ countries and territories
Languages
af-ZA, ar, bg-BG, ca-ES, cs-CZ, da-DK, de-DE, el-GR, en-AU, en-GB, en-NZ, en-US, es-419, es-ES, et-EE, eu-ES, fi-FI, fr-CA, fr-FR, gl-ES, he-IL, hr-HR, hu-HU, id-ID, it-IT, kk-KZ, ko-KR, ko-Kore-KR, ko-Latn-KR, lt-LT, lv-LV, ms-MY, nb-NO, nl-BE, nl-NL, pl-PL, pt-BR, pt-PT, ro-RO, ru-Cyrl-RU, ru-Latn-RU, ru-RU, sk-SK, sl-SI, sr-RS, sv-SE, th-TH, tr-TR, uk-UA, zh-CN, zh-TW, NGT, NGT-Latn
Input types
text query, lat/lon coordinates, bounding box, polygon geometry, circle geometry (lat/lon + radius), route geometry (POST body), entity ID / place ID, category codes, brand names, ISO country codes, connector type (EV), fuel type
Output types
JSON, JSONP, JavaScript, XML, GeoJSON (Additional Data endpoint)
Webhooks
No [7]
Sandbox / test mode
No [8]
SDK languages
JavaScript/TypeScript
MCP server
Yes [9]

Trust & compliance

SOC 2
None [10]
HIPAA
No [11]
GDPR
Yes [12]
ISO 27001
Yes [13]
PCI DSS
No [14]
Published SLA
No [15]
Rate limits
Default QPS limits: Search API: 5 QPS; Geocoding: 5 QPS; Reverse Geocoding: 5 QPS; Batch Search: 5 QPS; EV Search: 25 QPS; Map display: 10 QPS; Traffic: 10 QPS; Routing: 5 QPS. Free daily cap (shared across all products): 2,500 non-tile requests/day and 50,000 tile requests/day. Batch synchronous: max 100 items; Batch asynchronous: max 10,000 items. [16]
Known restrictions
Caching only permitted where cache-control headers are present in the response; duration must not exceed the max-age indicated in cache-control headers, Caching to scale results across multiple clients or users is prohibited, Attribution required: must implement TomTom Copyright API to display applicable copyright and logo attribution, TomTom logos and copyright notices must not be removed, obscured, masked, or changed, Creating derivative works, products, or services from licensed data is prohibited, Combining licensed data with ML/AI algorithms for competitive purposes is forbidden, Use for enforcement of traffic laws or in-flight/drone navigation is prohibited, Downloaded Map Data must be deleted within 90 days (60 days for Traffic Analytics) [17]

Developer surface

Docs rendering: static

Integration

API style
rest
Base URL
https://api.tomtom.com/search/2
Version
2
Versioning
url
Stability
ga
Auth methods
api_key
Idempotency keys
No
Error format
vendor-specific
Rate limit
5 / second

SDKs

  • JavaScript/TypeScript @tomtom-org/maps-sdk · repo

Adoption & maturity

Launched
1991-01-01
Notable customers
Volkswagen Group (CARIAD), Stellantis, Daimler, BMW Motorrad, Toyota, Renault, Microsoft, Alteryx, Precisely, Omnitracs

Other Places & POI APIs

  • Azure Maps Search (POI)

    "Azure Maps is a collection of geospatial services and SDKs that use fresh mapping data to provide geographic context to web and mobile applications."

    Usage · free tier · public pricing · self-serve

  • Google Places API

    "The Places API is a service that accepts HTTP requests for location data through a variety of methods. It returns formatted location data and imagery about establishments, geographic locations, or prominent points of interest."

    Usage · free tier · public pricing · self-serve

  • Radar Geocoding API

    "Use Radar's geocoding APIs to convert addresses to latitude and longitude coordinates, or vice versa."

    Hybrid · free tier · public pricing · self-serve

  • Mapbox Search Box API

    "All-in-one location search for addresses, places, and points of interest"

    Usage · free tier · public pricing · self-serve

  • HERE Geocoding & Search API (Discover & Browse)

    "Enable precise conversion and discovery of geocoordinates, POIs and addresses to improve location accuracy and context."

    Hybrid · free tier · self-serve

  • Esri ArcGIS Places API

    "a location service hosted by Esri that can search for businesses and geographic locations around the world and return detailed information about each place."

    Usage · free tier · public pricing · self-serve

TomTom Search / Places API alternatives · TomTom Search / Places API vs Azure Maps Search (POI) · All Places & POI APIs APIs

References

Each field above carries a numbered source - hover for a preview, click to jump here.

  1. Description: developer.tomtom.com
  2. Pricing model: developer.tomtom.com
  3. Published pricing: developer.tomtom.com
  4. Free tier: docs.tomtom.com · developer.tomtom.com
  5. Enterprise plan: developer.tomtom.com
  6. Supported actions: developer.tomtom.com · developer.tomtom.com
  7. Webhooks: developer.tomtom.com
  8. Sandbox: developer.tomtom.com
  9. MCP server: developer.tomtom.com
  10. SOC 2: tomtom.com
  11. HIPAA: tomtom.com
  12. GDPR: tomtom.com
  13. ISO 27001: tomtom.com
  14. PCI DSS: tomtom.com
  15. Published SLA: developer.tomtom.com
  16. Rate limits: developer.tomtom.com
  17. Known restrictions: developer.tomtom.com

Change history

Every field change, who made it, and when - from our audited data pipeline and editors.

  1. 2026-06-15 Score Agent Friendliness: 3040
  2. 2026-06-14 Robots Allows Agents: (none)Yes
  3. 2026-06-14 Has Structured Data: (none)No
  4. 2026-06-14 Capabilities: {}{"nearby":true,"poi_search":true,"autocomplete":true,"place_details":true}
  5. 2026-06-14 Summary Md: (none)TomTom Search / Places API is a REST service covering geocoding, reverse geocod…
  6. 2026-06-14 Score Docs Quality: 015
  7. 2026-06-14 Llms Txt Present: (none)No
  8. 2026-06-14 Rendering: (none)static
  9. 2026-06-14 Docs URL: (none)https://developer.tomtom.com/documentation
  10. 2026-06-14 Score Agent Friendliness: (none)30
  11. 2026-06-14 Score Setup Speed: (none)75
  12. 2026-06-14 Score Pricing Transparency: (none)100
  13. 2026-06-14 Best For: (none)Prototypes and side projects - free to start, no sales call, AI agents and auto…
  14. 2026-06-14 Score Trust Readiness: (none)30
  15. 2026-06-14 Score Procurement Friction: (none)100
  16. 2026-06-14 Score Docs Quality: (none)0
  17. 2026-06-14 Avoid If: (none)You have strict compliance requirements
  18. 2026-06-14 Scoring Methodology: (none)Scores are computed deterministically from this profile's published, sourced fi…
  19. 2026-06-14 Free Tier Available: set to Yes
  20. 2026-06-14 Free Tier Details: set to Recurring daily allowance: 2,500 free non-tile requests/day and 50,000 free til…
  21. 2026-06-14 Self Serve Signup: set to Yes
  22. 2026-06-14 Requires Sales Call: set to No
  23. 2026-06-14 Enterprise Plan Available: set to Yes
  24. 2026-06-14 SOC 2: set to none
  25. 2026-06-14 HIPAA: set to No
  26. 2026-06-14 GDPR: set to Yes
  27. 2026-06-14 ISO 27001: set to Yes
  28. 2026-06-14 PCI DSS: set to No
  29. 2026-06-14 SLA Published: set to No
  30. 2026-06-14 SLA URL: set to https://developer.tomtom.com/terms-and-conditions
  31. 2026-06-14 Data Retention Policy URL: set to https://developer.tomtom.com/terms-and-conditions
  32. 2026-06-14 Documented Rate Limits: set to Default QPS limits: Search API: 5 QPS; Geocoding: 5 QPS; Reverse Geocoding: 5 Q…
  33. 2026-06-14 Rate Limit Requests: set to 5
  34. 2026-06-14 Rate Limit Window: set to second
  35. 2026-06-14 Known Restrictions: set to Caching only permitted where cache-control headers are present in the response;…
  36. 2026-06-14 Auth Methods: set to api_key
  37. 2026-06-14 Auth Docs URL: set to https://developer.tomtom.com/knowledgebase/platform/articles/how-to-get-an-tomt…
  38. 2026-06-14 API Style: set to rest
  39. 2026-06-14 Base URL: set to https://api.tomtom.com/search/2
  40. 2026-06-14 API Version: set to 2
  41. 2026-06-14 Versioning Scheme: set to url
  42. 2026-06-14 Stability: set to ga
  43. 2026-06-14 Deprecation Policy URL: set to https://developer.tomtom.com/deprecation-policy/overview
  44. 2026-06-14 MCP URL: set to https://mcp.tomtom.com/maps
  45. 2026-06-14 Quickstart URL: set to https://developer.tomtom.com/search-api/documentation/product-information/intro…
  46. 2026-06-14 Idempotency Supported: set to No
  47. 2026-06-14 Error Format: set to vendor-specific
  48. 2026-06-14 Slug: set to tomtom-search
  49. 2026-06-14 Starting Price Usd: set to 2.5
  50. 2026-06-14 Price Basis: set to 1,000 requests

Suggest an edit / leave a review

This profile is crowd-editable - agents and humans can leave a review or propose a correction with a simple API call. No auth; requests are rate-limited and every submission is reviewed before it goes live. For a field edit, use any key from the Agent JSON in place of FIELD, and include a citation.

Leave a review or comment

curl -X POST https://apio.sh/api/feedback/tomtom-search \
  -H 'Content-Type: application/json' \
  -d '{"kind":"review","rating":5,"body":"Your experience with this API…"}'

Suggest a correction to a field (cite a source)

curl -X POST https://apio.sh/api/suggest/tomtom-search/FIELD \
  -H 'Content-Type: application/json' \
  -d '{"value":"corrected value","citations":[{"url":"https://source.example/page","excerpt":"supporting quote"}],"note":"what changed and why"}'

All the ways to contribute →