TomTom
TomTom · Ranked #4 of 8 in Maps & Geocoding APIs
Strong routing/traffic and maps SDKs with a large free daily tier; self-serve, though pricing is being revised effective July 2026.
Maps, routing & traffic

Overview
TomTom is a long-established Dutch location-technology company that exposes its mapping stack to developers through the TomTom Developer Portal (developer.tomtom.com) as a suite of REST APIs (Search/Places, Geocoding, Routing, Map Display, Traffic, Matrix Routing, Tracking/Logistics) plus mobile and web SDKs. Its core differentiator is proprietary map and traffic data built from billions of connected-vehicle and probe data points, which gives it strong real-time and historical traffic accuracy and a self-built address database rather than a pure OpenStreetMap derivative. The platform is aimed at developers building navigation, fleet/logistics, last-mile delivery, ride-hail, and location-aware apps who want an alternative to Google Maps Platform with more permissive licensing terms (e.g., no prohibition on displaying results over non-TomTom basemaps and fewer caching restrictions).
Commercially, TomTom uses a usage-metered model. Both the free Freemium plan and the Pay As You Grow plan include a generous daily free allowance of 50,000 tile requests plus 2,500 non-tile requests per day with no credit card required and commercial use permitted; overage is priced per 1,000 requests (map/traffic tiles at $0.08, geocoding around $0.75, reverse geocoding $0.50, Places/Search $2.50, routing $0.75-$6.00 depending on service). Enterprise is a custom contract adding data licensing, asset-based subscriptions, flexible QPS, and a dedicated account manager. Default rate limits are modest on the self-serve plans (commonly ~5 QPS for many endpoints, with documented per-API QPS limits), which can be a constraint for high-throughput workloads until raised under a contract.
Where TomTom wins is traffic intelligence, EV/last-mile features (entry points, parking points, building entrances, floor numbering in Premium Geocoding), permissive terms, and a clean free tier. Where it lags is ecosystem mass and community footprint relative to Google and Mapbox: there is no first-party Flutter SDK, fewer third-party tutorials and Stack Overflow answers, and limited POI rich-media/user-generated content (reviews, photos) compared with Google Places. Independent, standardized head-to-head accuracy benchmarks against Google/Mapbox are scarce, and TomTom's headline accuracy figures are self-published. It is a credible, cost-effective choice for traffic- and routing-heavy products, but teams needing the deepest global POI metadata or the largest developer community may still gravitate to Google or Mapbox.
How this score is derived
The APIbenchmarks Index is a weighted sum of four dimensions, each scored on an absolute 0–100 reference scale. See the methodology for every mapping.
| Dimension | Score | Weight | Contribution |
|---|---|---|---|
| Documentation & DXComprehensive developer portal with per-API reference docs, tutorials, code samples, a knowledge base, and full TypeScript support in the JavaScript SDK, though some areas (v6 web SDK) are deprecated and migration paths add friction. | 76 | 30% | 22.8 |
| ReliabilityTomTom publishes a public API status page with a rolling 5-day history per API, but offers no clearly published uptime SLA on self-serve plans (guarantees come via Enterprise contracts). | 85 | 25% | 21.3 |
| Ecosystem & SDKsSolid first-party SDKs for Android, iOS, and JavaScript and broad API coverage, but a smaller developer community than Google/Mapbox and no official Flutter SDK (developers rely on third-party plugins). | 78 | 25% | 19.5 |
| AccessibilityFrictionless onboarding with a no-credit-card Freemium tier, a large daily free allowance, and self-service signup, offset by relatively low default QPS limits on free/pay-as-you-grow plans. | 85 | 20% | 17.0 |
| APIbenchmarks Index (ABI) | 80.6 | ||
Table 1. Derivation of the ABI for TomTom. Contribution = score × weight; the index is their sum.
At a glance
- Vendor
- TomTom
- Pricing model
- Per 1k req (tile/non-tile)
- Free tier
- 50k tile + 2.5k non-tile req/day
- Official SDKs
- 5 languages
Pricing
| Freemium | Free | 50,000 tile requests + 2,500 non-tile requests per day; no credit card; commercial use permitted; self-service support. |
| Pay As You Grow | Usage-based (prepaid overage) | Same daily free cap; overage per 1,000 requests (tiles $0.08, geocoding ~$0.75, reverse geocoding $0.50, Places/Search $2.50, routing $0.75-$6.00); no commitment, cancel anytime. |
| Enterprise | Custom contract | Data licensing, asset-based subscriptions, flexible QPS limits, dedicated account manager and support engineer. |
Key features
- •Search & Places API (fuzzy single-line address + POI search, EV charging stations)
- •Geocoding and Reverse Geocoding APIs
- •Premium Geocoding API with last-mile entry/parking/entrance/floor data
- •Routing API with vehicle/engine-type variables and optimized waypoint ordering
- •Matrix Routing v2 API (sync and async)
- •Map Display API serving raster and vector tiles
- •Real-time and historical Traffic APIs
- •EV-specific routing and charging features
- •Tracking / Logistics APIs
- •Offline map support in mobile SDKs
Official SDKs
Strengths & trade-offs
- +Proprietary real-time and historical traffic data sourced from billions of connected-vehicle/probe points, among the most accurate available
- +Generous, no-credit-card free tier: 50,000 tile + 2,500 non-tile requests/day with commercial use allowed
- +More permissive licensing than Google (can display results over non-TomTom basemaps; fewer caching restrictions)
- +Premium Geocoding adds last-mile features: entry points, closest parking points, building entrances, and floor numbering
- +Cheap map/traffic tile overage at $0.08 per 1,000 requests
- +Broad API coverage (Search, Geocoding, Routing, Matrix Routing, Map Display, Traffic, Tracking) plus EV charging support
- –Low default rate limits on self-serve plans (commonly ~5 QPS for many endpoints) until raised under contract
- –No official first-party Flutter SDK; developers must use third-party plugins
- –Smaller developer community and fewer third-party tutorials/Stack Overflow answers than Google or Mapbox
- –Limited POI rich media and user-generated content (no reviews/photos like Google Places)
- –Headline accuracy figures are self-published; few independent standardized benchmarks vs competitors
- –No clearly published uptime SLA on free/pay-as-you-grow plans (SLAs are Enterprise-only)
What developers say
Developers respect TomTom for accurate traffic data, permissive terms, and a generous free tier, while noting a smaller ecosystem and lighter POI metadata than Google or Mapbox.
“TomTom has earned genuine respect in the mapping industry, with its real-time traffic data sourced from billions of connected vehicle data points remaining among the most accurate available.”
Key figures
| Premium Geocoding address accuracy | >99% within 10 feet | TomTom Developer Knowledge Base ↗ |
| Geocoding accuracy vs leading competitor (difficult addresses) | ~330 feet more accurate on average | TomTom Developer Knowledge Base ↗ |
| Free daily allowance | 50,000 tile + 2,500 non-tile requests/day | TomTom Pricing page ↗ |
| Map/Traffic tile overage price | $0.08 per 1,000 requests | TomTom Pricing page ↗ |
| Default geocoding rate limit | ~5 requests/second (self-serve plans) | TomTom Developer Knowledge Base (QPS limits) ↗ |
| Status page history window | rolling last 5 days per API | TomTom API Status Page docs ↗ |
Compare TomTom head to head
Sources
- https://developer.tomtom.com/pricing
- https://developer.tomtom.com/knowledgebase/apis/faq/premium-geocoding/how-accurate-is-the-tomtom-premium-geocoding-api/
- https://developer.tomtom.com/knowledgebase/platform/articles/qps-limits/
- https://developer.tomtom.com/platform/documentation/status-and-support/api-status-page
- https://www.tomtom.com/products/maps-sdk/
- https://volpis.com/blog/tomtom-maps-vs-google-maps-for-app-development/
- https://radar.com/blog/google-maps-api-alternatives-competitors
- https://radar.com/blog/mapbox-vs-google-maps-api
- https://developer.tomtom.com/products/sdks
Figures last verified 2026-06-27. Spotted an error? corrections@apibenchmarks.com
