TomTom

The Map Display API Raster Service delivers raster satellite image tiles, which are representations of square sections of map data. via GET https://api.tomtom.com/map/1/tile/{layer}/{style}/{zoom}/{X}/{Y}.{format}

The Map Display API Vector service delivers vector tiles which are representations of square sections of map data. via GET https://api.tomtom.com/map/1/tile/{layer}/{style}/{zoom}/{X}/{Y}.pbf

The Map Display API Raster Service delivers raster hillshade image tiles, which are representations of square sections of map data. via GET https://api.tomtom.com/map/1/tile/{layer}/{type}/{zoom}/{X}/{Y}.{format}

The Copyrights API returns copyright information for the Display API services. The response body will contain copyrights in a plain text format. via GET https://api.tomtom.com/map/2/copyrights

This API returns copyright captions for the map service. For the map service copyright request, the response body will contain a copyrights caption in JSON format. via GET https://api.tomtom.com/map/2/copyrights/caption.json

The Map Display API Vector service delivers vector tiles which are representations of square sections of map data. via GET https://api.tomtom.com/map/2/tile/{layer}/{zoom}/{X}/{Y}.pbf

This retrieves a selected resource. via GET https://api.tomtom.com/map/{versionNumber}/{resourceType}/{resourceVersion}/{resourceVariant}/{resourceName}

This retrieves a list of resources of a selected type. via GET https://api.tomtom.com/map/{versionNumber}/{resourceType}/{resourceVersion}/{resourceVariant}/metadata.{format}

The Static Image service renders a rectangular raster image in the style, size, and zoom level specified. The image can be requested using either a center point plus width and height or a bounding box. via GET https://api.tomtom.com/map/{versionNumber}/staticimage

The Map Display API Raster service delivers raster map tiles, which are representations of square sections of map data. via GET https://api.tomtom.com/map/{versionNumber}/tile/{layer}/{style}/{zoom}/{X}/{Y}.{format}

The GetMap call implements the Web Map Service 1.1.1 standard to access TomTom Raster Map tiles. This service is described in the Response to the GetCapabilities API call. via GET https://api.tomtom.com/map/{versionNumber}/wms

The WMTS GetCapabilities call implements version 1.0.0 of the Web Map Tile Service (WMTS) standard. It returns metadata that allows compatible calling systems to construct calls to TomTom's raster map tile service. See the documentation for more information on WMTS. via GET https://api.tomtom.com/map/{versionNumber}/wmts/{key}/{wmtsVersion}/WMTSCapabilities.xml

Delivers detailed information for a location. via GET https://api.tomtom.com/maps/orbis/places/details/{type}/{id}

Calculates a set of locations that can be reached from the origin point. via GET https://api.tomtom.com/routing/{versionNumber}/calculateReachableRange/{origin}/{contentType}

Calculates a route between an origin and a destination. via GET https://api.tomtom.com/routing/{versionNumber}/calculateRoute/{locations}/{contentType}

Additional Data via GET https://api.tomtom.com/search/{versionNumber}/additionalData.{ext}

Category Search via GET https://api.tomtom.com/search/{versionNumber}/categorySearch/{query}.{ext}

Low Bandwidth Category Search via GET https://api.tomtom.com/search/{versionNumber}/cS/{category}.{ext}

EV Search by Id via GET https://api.tomtom.com/search/{versionNumber}/evbyid

EV Search Nearby via GET https://api.tomtom.com/search/{versionNumber}/evsearch

Geocode via GET https://api.tomtom.com/search/{versionNumber}/geocode/{query}.{ext}

Geometry Filter via GET https://api.tomtom.com/search/{versionNumber}/geometryFilter.{ext}

Geometry Search via GET https://api.tomtom.com/search/{versionNumber}/geometrySearch/{query}.{ext}

Nearby Search via GET https://api.tomtom.com/search/{versionNumber}/nearbySearch/.{ext}

POI Categories via GET https://api.tomtom.com/search/{versionNumber}/poiCategories.{ext}

Points of Interest Search via GET https://api.tomtom.com/search/{versionNumber}/poiSearch/{query}.{ext}

Premium Geocode via GET https://api.tomtom.com/search/{versionNumber}/premiumGeocode/{query}.{ext}

Reverse Geocode via GET https://api.tomtom.com/search/{versionNumber}/reverseGeocode/{position}.{ext}

Cross Street lookup via GET https://api.tomtom.com/search/{versionNumber}/reverseGeocode/crossStreet/{position}.{ext}

Routed Filter via GET https://api.tomtom.com/search/{versionNumber}/routedFilter/{position}/{heading}.{ext}

Routed Search via GET https://api.tomtom.com/search/{versionNumber}/routedSearch/{query}/{position}/{heading}.{ext}

Low bandwith Search via GET https://api.tomtom.com/search/{versionNumber}/s/{query}.{ext}

Fuzzy Search via GET https://api.tomtom.com/search/{versionNumber}/search/{query}.{ext}

Structured Geocode via GET https://api.tomtom.com/search/{versionNumber}/structuredGeocode.{ext}

The service returns requested via Asynchronous Snap to Roads Submission endpoint data. via GET https://api.tomtom.com/snapToRoads/batch/{versionNumber}/{batchID}

The service returns status of requested via Asynchronous Snap to Roads Submission endpoint data. via GET https://api.tomtom.com/snapToRoads/batch/{versionNumber}/{batchID}/status

The service matches the received points to the map road network and reconstructs the driven road. Input points are related to themselves and are a part of the same route from the same client. via GET https://api.tomtom.com/snapToRoads/{versionNumber}

The TomTom Traffic Raster Flow Tile service serves 256 x 256 pixel or 512 x 512 pixel tiles showing traffic flow. - All tiles use the same grid system. - Because the traffic tiles use transparent images, they can be layered on top of map tiles to create a compound display. - The Raster Flow tiles use colors to indicate either the speed of traffic on different road segments, or the difference between that speed and the free-flow speed on the road segment in question. via GET https://api.tomtom.com/traffic/map/{versionNumber}/tile/flow/{style}/{zoom}/{x}/{y}.{format}

The Traffic Vector Flow Tiles API endpoint provides data on zoom levels ranging from 0 to 22. - For zoom level 0, the world is displayed on a single tile. - At zoom level 22, the world is divided into 244 tiles. See the Zoom Levels and Tile Grid. The service delivers traffic flow data packaged in a vector representation of squared sections called vector tiles. - Each tile includes a pre-defined collection of road shapes with traffic flow data. - The format of the tile is formally described using the protobuf schema. It shows either the current speed of traffic on different road segments, or the difference between current speed and the free-flow speed on the road segment. via GET https://api.tomtom.com/traffic/map/{versionNumber}/tile/flow/{type}/{zoom}/{x}/{y}.{format}

The TomTom Traffic Tile service serves 256 x 256 pixel or 512 x 512 pixel tiles showing traffic incidents. - All tiles use the same grid system. - Because the traffic tiles use transparent images, they can be layered on top of map tiles to create a compound display. - Traffic tiles render graphics to indicate traffic on the roads in the specified area. - The Traffic incidents tiles use colors to indicate the magnitude of delay associated with the particular incident on a road segment. - The magnitude of delay is determined based on the severity of traffic congestion associated with the particular incident. via GET https://api.tomtom.com/traffic/map/{versionNumber}/tile/incidents/{style}/{zoom}/{x}/{y}.{format}

The Traffic Vector Incidents Tiles API provides data on zoom levels ranging from 0 to 22. For zoom level 0, the world is displayed on a single tile, while at zoom level 22, the world is divided into 244 tiles. The service delivers traffic incidents data packaged in a vector representation of squared sections called vector tiles. - Each tile includes a pre-defined collection of road shapes with traffic incidents data. - The format of a tile is formally described using the protobuf schema. via GET https://api.tomtom.com/traffic/map/{versionNumber}/tile/incidents/{zoom}/{x}/{y}.{format}

This service provides information about the speeds and travel times of the road fragment closest to the given coordinates. - It is designed to work alongside the Flow Tiles to support clickable flow data visualizations. - With this API, the client side can connect any place in the map with flow data on the closest road and present it to the user. via GET https://api.tomtom.com/traffic/services/{versionNumber}/flowSegmentData/{style}/{zoom}/{format}

This is the new and improved version (5) of the Incident Details endpoint. We highly recommend that you use this new version 5 rather than the old version 4, which we marked as deprecated. The Incident Details service provides information on traffic incidents which are inside a given bounding box or whose geometry intersects with it. - The freshness of data is based on the provided Traffic Model ID . - The data obtained from this service can be used as standalone or as an extension to other Traffic Incident services. - In the second case, the same Traffic Model ID should be used when calling all services, in order to grant synchronization of data between APIs. via GET https://api.tomtom.com/traffic/services/{versionNumber}/incidentDetails

This service returns legal and technical information for the viewport described in the request. via GET https://api.tomtom.com/traffic/services/{versionNumber}/incidentViewport/{boundingBox}/{boundingZoom}/{overviewBox}/{overviewZoom}/{copyright}/{contentType}

Delivers fully resolved location or discoverAction results based on complete input criteria. Use this endpoint for structured or fully specified inputs, such as suggestion/button interactions, or voice queries. Not intended for as-you-type suggestions (see `/suggest`). via POST https://api.tomtom.com/maps/orbis/places/discover

Delivers as-you-type suggestions for important or nearby locations and related discoverable concepts. Use this endpoint to provide a short list of contextualized, explainable suggestions relevant the current state of the user's query-typing session. Results are optimized for listing-based displays. via POST https://api.tomtom.com/maps/orbis/places/suggest

Calculates a route between a given origin and destination, passing through waypoints if they are specified. via POST https://api.tomtom.com/routing/{versionNumber}/calculateLongDistanceEVRoute/{locations}/{contentType}

Calculates a set of locations that can be reached from the origin point. POST method handles additionally parameters: supportingPoints , allowVignette , avoidVignette , avoidAreas . via POST https://api.tomtom.com/routing/{versionNumber}/calculateReachableRange/{origin}/{contentType}

Calculates a route between an origin and a destination. POST method handles additionally parameters: supportingPoints , allowVignette , avoidVignette , avoidAreas . via POST https://api.tomtom.com/routing/{versionNumber}/calculateRoute/{locations}/{contentType}

EV Search Along the Route via POST https://api.tomtom.com/search/{versionNumber}/alongRoute

Geometry Filter (POST) via POST https://api.tomtom.com/search/{versionNumber}/geometryFilter.{ext}

Geometry Search (POST) via POST https://api.tomtom.com/search/{versionNumber}/geometrySearch/{query}.{ext}

Routed Filter (POST) via POST https://api.tomtom.com/search/{versionNumber}/routedFilter/{position}/{heading}.{ext}

Along Route Search via POST https://api.tomtom.com/search/{versionNumber}/searchAlongRoute/{query}.{ext}

The service matches the received points to the map road network and reconstructs the driven road. Input points are related to themselves and are a part of the same route from the same client. via POST https://api.tomtom.com/snapToRoads/batch/{versionNumber}

The service matches the received points to the map road network and reconstructs the driven road. Input points are related to themselves and are a part of the same route from the same client. via POST https://api.tomtom.com/snapToRoads/{versionNumber}

This is the new and improved version (5) of the Incident Details endpoint. We highly recommend that you use this new version 5 rather than the old version 4, which we marked as deprecated. The Incident Details service provides information on traffic incidents which are inside a given bounding box or whose geometry intersects with it. - The freshness of data is based on the provided Traffic Model ID . - The data obtained from this service can be used as standalone or as an extension to other Traffic Incident services. - In the second case, the same Traffic Model ID should be used when calling all services, in order to grant synchronization of data between APIs. via POST https://api.tomtom.com/traffic/services/{versionNumber}/incidentDetails