Skip to content

TomTom API

Platform Users — Engineers & Low-code Ops Users (ORA / Panel Builder) OR Platform ORA — AI Planning Interface Agent Workflows Plan Visualisation ADK Integration SDK UI — Frontend Shell FDK Architecture Low code Config-driven DDK Schema Definition Code Generator Generated Server MDK WEM DAL Experiment Manager Nexus Deployment Control Live Monitoring Registry Browser SCDK Source Control Pipeline Mgmt Azure DevOps deploys ↓ SDK API — GraphQL Federation Gateway Federation Gateway Component Resolvers Auth & Licensing Plugins: gql-autogeneration Migrator Helm KinD Boilerplate GenAI ··· Microservices — Domain IP Services Data Pipeline Core Platform Metrics & Analytics Spatial & Geo Simulation Event Detection Camera & Device Fire & Resource Opt. Satellite Modelling ↓ Nexus deploys Deployed OR Applications Rail Ops Dashboard Mine Mgmt Dashboard Port Ops Dashboard ··· FDK-built · DDK-backed · MDK-powered · deployed via Nexus ↑ Application Users — Operations Teams (shift managers, analysts, planners)

Overview

The TomTom API service provides geospatial and traffic intelligence by integrating with TomTom's location services. It enables geocoding, route optimization, traffic flow analysis, and incident detection — bringing real-world location and traffic data into your workflows.

This service is designed for logistics teams, transportation planners, and location-based applications that need accurate mapping, routing, and real-time traffic information.

Key Capabilities

Geocoding

  • Address to Coordinates — Convert street addresses to latitude/longitude
  • Reverse Geocoding — Convert coordinates to street addresses
  • Fuzzy Matching — Handle incomplete or imprecise addresses
  • Structured Output — Get formatted addresses with components (street, city, country)

Route Calculation

  • Optimal Routes — Find fastest or shortest routes between points
  • Multi-Stop Routing — Calculate routes through multiple waypoints
  • Route Optimization — Reorder waypoints for most efficient sequence
  • Alternative Routes — Generate multiple route options

Real-Time Traffic Data

  • Traffic Flow — Get current traffic speeds on road segments
  • Congestion Detection — Identify areas of heavy traffic
  • Travel Time Estimation — Predict journey duration with current traffic
  • Historical Patterns — Access typical traffic patterns by time of day

Incident Detection

  • Traffic Incidents — Road closures, accidents, construction
  • Incident Details — Location, severity, expected duration
  • Impact Assessment — How incidents affect travel times
  • GeoJSON Output — Map-ready incident data

Use Cases

Logistics Route Optimization

Scenario: A delivery company needs to plan optimal routes for daily deliveries with real-time traffic consideration.

Workflow:

  1. Geocode all delivery addresses
  2. Calculate optimal waypoint sequence
  3. Generate route with traffic-aware timing
  4. Check for incidents along route
  5. Adjust routes dynamically if incidents detected

Value: Reduce fuel costs and delivery times by optimizing routes with current conditions.

Transportation Planning

Scenario: A city planning department evaluates the impact of road closures on traffic patterns.

Workflow:

  1. Get baseline traffic flow on affected roads
  2. Model alternative routes for diverted traffic
  3. Estimate travel time impacts
  4. Identify areas likely to experience increased congestion
  5. Plan mitigation strategies

Value: Understand and minimize disruption from infrastructure work.

Location-Based Services

Scenario: A mobile app needs to show users nearby points of interest and directions.

Workflow:

  1. Geocode user's current location
  2. Search for nearby locations (restaurants, stores, etc.)
  3. Calculate routes and travel times to each
  4. Display on map with traffic-aware ETAs
  5. Update dynamically as traffic changes

Value: Provide users with accurate, real-time navigation and location information.

Fleet Management

Scenario: A trucking company monitors vehicle locations and optimizes dispatch.

Workflow:

  1. Track vehicle positions (lat/long)
  2. Reverse geocode to street addresses
  3. Calculate distances to next delivery points
  4. Factor in real-time traffic and incidents
  5. Dispatch nearest available vehicle

Value: Improve fleet utilization and customer service through optimized dispatch.

Model Inputs

The TomTom API service accepts:

  • Addresses — Street addresses to geocode
  • Coordinates — Latitude/longitude pairs for reverse geocoding or routing
  • Waypoints — Ordered or unordered list of stops for route planning
  • Route Options — Fastest, shortest, or custom optimization criteria
  • Bounding Boxes — Geographic areas for traffic or incident queries

Model Outputs

The service produces:

  • Geocoded Locations — Coordinates with formatted addresses
  • Routes — Turn-by-turn navigation with distances and times
  • Traffic Data — Current speeds, congestion levels, typical patterns
  • Incidents — Location, type, severity, and description of traffic incidents
  • GeoJSON — Map-ready geographic data format

Available Operations

Geocoding Operations

Forward Geocoding

  • Convert address to coordinates
  • Structured address parsing
  • Country/region filtering
  • Confidence scores for matches

Reverse Geocoding

  • Convert coordinates to address
  • Nearest street address
  • Place name identification

Routing Operations

Calculate Route

  • Point-to-point routing
  • Multi-waypoint routes
  • Avoid highways, tolls, or ferries
  • Alternative route generation

Optimize Waypoints

  • Find best visitation order
  • Minimize total distance or time
  • Respect time windows if specified

Traffic Operations

Traffic Flow

  • Current speeds on road segments
  • Free-flow vs actual speed comparison
  • Congestion ratios

Traffic Incidents

  • Real-time incident feed
  • Filtered by geographic area
  • Severity and impact estimates

GeoJSON Output

Many operations return GeoJSON format:

  • Industry Standard — Compatible with mapping libraries
  • Feature Collections — Routes, points, polygons
  • Properties — Metadata like names, speeds, times
  • Easy Visualization — Direct map plotting

Integration with Other Models

The TomTom API service works well with:

  • Traffic Model — Enrich simulations with real-world traffic data
  • Schedule Generation — Use actual travel times for scheduling
  • Data Ingestion — Combine with other location data sources
  • AI Agent Python — Agents can query location and routing information

Performance Notes

  • API Rate Limits — Be aware of TomTom service limits
  • Caching — Cache geocoded addresses to reduce API calls
  • Batch Operations — Group waypoints into single route requests
  • Geographic Scope — Limit queries to necessary regions

Getting Started

Basic Workflow

  1. Obtain TomTom Credentials — API key for authentication
  2. Configure Service — Set API key and parameters
  3. Select Operation — Geocode, route, traffic, or incident query
  4. Add to Workflow — Drag TomTom API into canvas
  5. Process Results — Use GeoJSON or structured outputs

Example: Address Geocoding

[List of Addresses] → [TomTom API: Geocode] → [Store Coordinates]

This workflow converts a list of addresses to coordinates for further processing.

Example: Route Planning with Traffic

[Delivery Stops] → [TomTom API: Optimize Waypoints] → [TomTom API: Calculate Route] → [Check Traffic] → [Generate Directions]

This workflow optimizes stop order, calculates the route, checks current traffic, and produces navigation instructions.

Best Practices

Geocoding

  1. Provide Complete Addresses — Include street, city, country for best results
  2. Handle Ambiguity — Review confidence scores, show alternatives when low
  3. Cache Results — Addresses rarely change, save geocoded locations
  4. Validate Outputs — Check if returned location makes sense for your use case

Routing

  1. Specify Preferences — Fastest, shortest, or avoid specific road types
  2. Consider Time of Day — Traffic patterns vary by time
  3. Check Alternatives — Multiple routes provide options if primary blocked
  4. Update with Incidents — Re-route if new incidents affect planned route

Traffic Data

  1. Refresh Regularly — Traffic changes rapidly, update every few minutes
  2. Use Historical Data — Predict patterns for planning future trips
  3. Monitor Incidents — Set up monitoring for critical routes
  4. Combine with Models — Use real data to calibrate traffic simulations

Data Privacy

When using location services:

  • Anonymize personal location data when possible
  • Comply with privacy regulations (GDPR, CCPA)
  • Don't store unnecessary location history
  • Inform users when tracking location

Troubleshooting

Geocoding Returns No Results

  • Check address format and completeness
  • Try broader search (city only, then add street)
  • Verify country code is correct
  • Look for typos in address components

Routes Don't Match Expected

  • Check start/end coordinates are accurate
  • Review routing preferences (fastest vs shortest)
  • Verify waypoint order is correct
  • Consider if avoid options are too restrictive

Traffic Data Seems Inaccurate

  • Verify timestamps (data may be cached)
  • Check geographic bounds include target area
  • Compare with visual traffic maps
  • Consider time of day (patterns vary)

Next Steps

User documentation for Optimal Reality