Available Maps
Purpose
You can use this endpoint to verify the available map versions in all Origin/Destination (O/D) Analysis APIs. It returns a comprehensive list of map versions and types, allowing you to use them for map-matching purposes. This is an optional parameter in the Selected Link analysis creation endpoint and the Flow matrix analysis creation endpoint .
Request data
Format
https://{baseURL}/origindestination/{versionNumber}/maps?boundingBox={lonMin,latMin,lonMax,latMax}&key={Your_API_Key}https://{baseURL}/origindestination/{versionNumber}/maps/{mapType}?boundingBox={lonMin,latMin,lonMax,latMax}&key={Your_API_Key}Example
https://api.tomtom.com/origindestination/1/maps?boundingBox=2.2897378091610108,48.87338492728168,2.2979721908363047,48.87477506330248&key={Your_API_Key}https://api.tomtom.com/origindestination/1/maps/ORBIS?boundingBox=2.2897378091610108,48.87338492728168,2.2979721908363047,48.87477506330248&key={Your_API_Key}Request parameters
The following table describes all request parameters that can be used. Required parameters must be included for the call to succeed. Optional parameters may be used.
Required parameters | Description |
|---|---|
| The base URL for calling TomTom services. Value: |
| Version of the service to call. Value: The current value is |
| Authorization key for access to the API. Value: Your valid API Key. |
| Determines the map generation used.
|
| Coordinates defining a boundingbox in the following format: longitudeLeftDown,latitudeLeftDown,longitudeRightUpper,latitudeRightUpper. Value: 4 comma-separated float numbers. |
Required POST headers
Header | Value |
|---|---|
|
Response data
The response returns all possible map versions and types.
Response example
{ "maps": [ {"type":"DSEG_NOSPLIT","version":"2022.03","releaseTimestamp":"1644521845000"}, {"type":"DSEG_NOSPLIT","version":"2021.12","releaseTimestamp":"1636539854000"}, {"type":"DSEG_NOSPLIT","version":"2021.09","releaseTimestamp":"1628847569000"}, ... ]}