# TomTom integration

> TomTom Developer Portal APIs: maps and tiles, search, geocoding, routing, traffic, EV charging, parking, weather and traffic analytics.

- Authentication: apiKey

## Tools (217)

- **Advanced Weather: Weather Polygons**: The Advanced Weather API delivers spatio-temporally resolved, real-time weather information. The provided content comprises polygonal information about radar-based current precipitation and precipitation forecasts in different time slices.
- **Area Analytics: Archive Report**: Archive a specified Area Analytics report to hide it from the default list of retrieved reports by sending a POST request. Auth: `?key=` query parameter.
- **Area Analytics: Calculate Report Price**: Check the price in tokens for creating an Area Analytics report by sending a POST request. Auth: `?key=` query parameter.
- **Area Analytics: Create Report**: Create an Area Analytics report by sending a POST request. Auth: `?key=` query parameter.
- **Area Analytics: Get Aggregated Report Results**: Get aggregated report results for a specific feature by sending a GET request. Auth: `?key=` query parameter.
- **Area Analytics: Get Report**: Send a GET request to retrieve detailed information about a specific report generated by the Area Analytics service. Auth: `?key=` query parameter.
- **Area Analytics: List Reports**: Send a GET request to retrieve a list of reports generated by the Area Analytics service. Auth: `?key=` query parameter.
- **Area Analytics: Restore Report**: Restore a previously archived Area Analytics report to make it visible in the list of reports again by sending a POST request. Auth: `?key=` query parameter.
- **Batch Routing: Asynchronous Batch Download**: The asynchronous batch download endpoint fetches results of the asynchronous batch processing. Auth: `?key=` query parameter.
- **Batch Routing: Asynchronous Batch Submission**: The asynchronous batch submission endpoint allows you to submit a new batch for asynchronous processing. It responds with a redirect to the location where the batch results can be obtained after processing is complete.
- **Batch Routing: Synchronous Batch**: The synchronous batch endpoint allows you to submit a new batch for synchronous processing. It responds with a batch processing result, or an HTTP `408` request timeout error if the processing time exceeds 60 seconds.
- **Batch Search: Asynchronous Batch Download**: This endpoint fetches results of the Asynchronous Batch processing. It responds with HTTP 200 and the batch results assuming batch processing has completed, or HTTP 202 Accepted if the batch is still being processed.
- **Batch Search: Asynchronous Batch Submission**: This endpoint allows the submission of a new batch for asynchronous processing. It responds with a redirect to the location at which the batch results can be obtained when the batch processing has completed. Auth: `?key=` query parameter.
- **Batch Search: Synchronous Batch**: This endpoint allows the submission of a new batch for synchronous processing. It responds with a batch processing result or an HTTP `408` request timeout error, if the processing time exceeds 60 seconds. Auth: `?key=` query parameter.
- **EV Charging Availability: EV Charging Stations Availability**: The EV Charging Stations Availability endpoint provides information about the current availability of charging points, grouped by connector type and then power level.
- **EV Search: EV Brands**: The Charge Point Operators (CPO) endpoint enables clients to access a list of available CPOs in a given country or subdivision. This helps EV drivers choose their preferred Charge Point Operators while searching for EV charging stations.
- **EV Search: EV Payment Applications**: The e-Mobility Service Providers (eMSP) endpoint enables clients to access available eMSPs in a given country. This helps EV drivers choose their preferred e-Mobility Service Providers while searching for EV charging stations.
- **EV Search: EV Search Along the Route**: The EV Search Along the Route endpoint provides information about the EV POIs along a pre-calculated route. By providing optional request parameters, the API allows filtering of the response by connector type, availability status, etc.
- **EV Search: EV Search by Id**: The EV Search by Id endpoint provides detailed information about one or more EV POIs (points of interest) requested by their ID. This includes details such as location, availability status, and attached connectors.
- **EV Search: EV Search Nearby**: The EV Search Nearby endpoint provides information about the nearest EV POIs (points of interest) based on a circular area, a bounding box, or a combination of both.
- **Fuel Prices: Fuel Price**: The Fuel Prices service provides information about the current fuel prices of fuel stations. Not available on the free evaluation or Pay As You Grow plans; contact TomTom Sales. Auth: `?key=` query parameter.
- **Geocoding: Geocode**: In many cases, the complete Search service might be too much. For instance, if you are only interested in traditional Geocoding, Search can also be exclusively accessed for address look-up.
- **Geocoding: Premium Geocode**: The TomTom Premium Geocoding API is a forward geocoding service that returns highly accurate address coordinates along with expanded address features required for last-mile delivery, such as the closest parking points, floor numbering.
- **Geocoding: Structured Geocode**: Search can also be exclusively accessed for structured address look up. The geocoding index will be queried for everything above the street level data. No POIs (Points of Interest) will be returned.
- **Junction Analytics: Create Junction Definition (Automatic)**: Junction Auto-Creation is a REST API endpoint designed for the streamlined and efficient creation of junctions. It simplifies the junction creation process by requiring minimal input parameters. Auth: `?key=` query parameter.
- **Junction Analytics: Create Junction Definition (Manual)**: The Junction Manual Creation is a specialized REST API endpoint designed to provide a customized way to create junctions. Through this endpoint, users can manually define the properties of the junction. Auth: `?key=` query parameter.
- **Junction Analytics: Create Junction Definition (Manual V2)**: The Junction Manual Creation v2 is a REST API endpoint designed to create junctions by providing explicit approach and exit geometries. Auth: `?key=` query parameter.
- **Junction Analytics: Delete Junction Definition**: Junction definition delete is a REST API endpoint that deletes a requested junction. Auth: `?key=` query parameter.
- **Junction Analytics: Generate Junction Archive Data**: The Generate Historical Data Archive endpoint allows you to create an archive generation task for selected junctions within a specified date range. Auth: `?key=` query parameter.
- **Junction Analytics: Get Archive Data Task Status**: The Get Task Status by ID endpoint retrieves the status of a specific archive generation task. Auth: `?key=` query parameter.
- **Junction Analytics: Get Enhanced Junction Data**: The Enhanced Junction Data is a REST API endpoint that provides data for a selected junction. This endpoint delivers detailed metrics for each approach within the junction, with specific focus on single trace metrics.
- **Junction Analytics: Get Enhanced Junction Data Batch**: This endpoint allows you to retrieve batch data for all your junctions in a single request, aggregated in 15-minute intervals.
- **Junction Analytics: Get Junction Archive Availability**: Junction archive availability is a REST API endpoint to query the availability period of an archive for a specified junction. Auth: `?key=` query parameter.
- **Junction Analytics: Get Junction Archive Data**: The Junction archive is a REST API endpoint designed to fetch a `.zip` file containing detailed live data for a specified junction. This archive includes snapshots of live data, captured at one-minute intervals.
- **Junction Analytics: Get Junction Definition**: Junction definition details is a REST API endpoint that reads static information about a selected junction. It contains the junction ID, name, status, and other static details of a selected junction. Auth: `?key=` query parameter.
- **Junction Analytics: Get Junction Live Data**: Junction live data details is a REST API endpoint that reads dynamic real-time information about a selected junction.
- **Junction Analytics: List Archive Data Tasks**: The Get Tasks endpoint retrieves the tasks with current statuses. This allows you to monitor the progress of tasks related to generating data archives for junctions. Auth: `?key=` query parameter.
- **Junction Analytics: List Junction Definitions**: Junction definition details is a REST API endpoint that reads static information about about a paginated list of junctions. For all of these junctions, it contains the junction ID, name, status, and other static details.
- **Junction Analytics: List Junction Live Data**: Junction live data details is a REST API endpoint that reads dynamic real-time information about a paginated list of junctions.
- **Junction Analytics: Preview Junction Definition**: Junction preview is a REST API endpoint that allows users to review and verify the generated junction based on the provided area. This endpoint does not create a new Junction. Auth: `?key=` query parameter.
- **Junction Analytics: Preview Junction Definition (V2)**: Junction preview v2 is a REST API endpoint that allows users to review and verify a junction definition based on user-provided approach and exit geometries, before committing it as an active junction.
- **Junction Analytics: Update Junction Definition (Automatic)**: Junction Auto-Update is a REST API endpoint designed for the streamlined and efficient update of junctions. It simplifies the junction update process by requiring minimal input parameters. Auth: `?key=` query parameter.
- **Junction Analytics: Update Junction Definition (Manual)**: The Junction Manual Update is a specialized REST API endpoint designed to provide a customized way to update junctions. Through this endpoint, users can manually define the properties of the junction. Auth: `?key=` query parameter.
- **Long Distance EV Routing: Calculate Long Distance EV Route**: Calculates a route between a given origin and destination, passing through waypoints if they are specified. Auth: `?key=` query parameter.
- **Map Display: GetCapabilities**: The GetCapabilities call is part of TomTom's implementation of version 1.1.1 of the Web Map Service (WMS). It provides descriptions of the other calls that are available in the implementation. Auth: `?key=` query parameter.
- **Map Display: GetMap**: 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. Auth: `?key=` query parameter.
- **Map Display: Hillshade Tile**: The Map Display API Raster Service delivers raster hillshade image tiles, which are representations of square sections of map data. Auth: `?key=` query parameter.
- **Map Display: Map Copyrights**: The Copyrights API returns copyright information for the Display API services. The response body will contain copyrights in a plain text format. Auth: `?key=` query parameter.
- **Map Display: Map Service 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. Auth: `?key=` query parameter.
- **Map Display: Map styles metadata**: This retrieves a list of resources of a selected type. Auth: `?key=` query parameter.
- **Map Display: Map styles resources**: This retrieves a selected resource. Auth: `?key=` query parameter.
- **Map Display: Map Tile**: The Map Display API Raster service delivers raster map tiles, which are representations of square sections of map data. Auth: `?key=` query parameter.
- **Map Display: Satellite Tile**: The Map Display API Raster Service delivers raster satellite image tiles, which are representations of square sections of map data. Auth: `?key=` query parameter.
- **Map Display: Static Image**: 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. Auth: `?key=` query parameter.
- **Map Display: Tile V1**: The Map Display API Vector service delivers vector tiles which are representations of square sections of map data. Auth: `?key=` query parameter.
- **Map Display: Tile V2**: The Map Display API Vector service delivers vector tiles which are representations of square sections of map data. Auth: `?key=` query parameter.
- **Map Display: WMTS**: 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.
- **Map Feedback: Complete Attachment Upload**: This call is used to confirm that a file has been uploaded. It is the last of the three calls described in Attachments. Not available on the free evaluation or Pay As You Grow plans; contact TomTom Sales. Auth: `?key=` query parameter.
- **Map Feedback: Create Feedback**: This call is used to create a feedback. Like all other methods of this API, this method requires a TomTom API key. This information will be used to identify the creator of the feedback.
- **Map Feedback: Delete Attachment**: This call is used to remove a file you attached to a feedback, for example when the wrong file was uploaded or when the file has to be removed for privacy reasons.
- **Map Feedback: Get Attachment Download URL**: This call is used to get a temporary link for downloading an attachment. Use the link with an HTTP `GET` request to read the file. The file is not returned by this call itself.
- **Map Feedback: Get Feedback by ID**: This call can be used to get feedback data for a given ID. Not available on the free evaluation or Pay As You Grow plans; contact TomTom Sales. Auth: `?key=` query parameter.
- **Map Feedback: Get Feedback by Reference ID**: This call can be used to get feedback data for a given reference ID. Not available on the free evaluation or Pay As You Grow plans; contact TomTom Sales. Auth: `?key=` query parameter.
- **Map Feedback: Get Feedback Status by ID**: This call returns the status of the feedback for a given feedback ID. Not available on the free evaluation or Pay As You Grow plans; contact TomTom Sales. Auth: `?key=` query parameter.
- **Map Feedback: Get Feedback Status by Reference ID**: This call returns the status of the feedback for a given reference ID. Not available on the free evaluation or Pay As You Grow plans; contact TomTom Sales. Auth: `?key=` query parameter.
- **Map Feedback: Initiate Attachment Upload**: This call is used to start adding a file to a feedback. It reserves a place for the file and returns a temporary link that you upload the file to. It is the first of the three calls described in Attachments.
- **Matrix Routing V2: Asynchronous Matrix Download**: This endpoint lets clients download the result of their matrix job. Auth: `?key=` query parameter.
- **Matrix Routing V2: Asynchronous Matrix Status**: This endpoint lets clients check the status of a matrix job they submitted. Auth: `?key=` query parameter.
- **Matrix Routing V2: Asynchronous Matrix Submission**: This endpoint enables the submission of a new matrix job for asynchronous processing. It responds with a unique job id which can be used to check the job status and download its result when available. Auth: `?key=` query parameter.
- **Matrix Routing V2: Synchronous Matrix**: This endpoint enables the submission of a new matrix job for synchronous processing, which is best suited for fast, small matrices of lightweight route calculations.
- **OD Analysis: Accept Analysis**: Accept an analysis by sending a POST request. Auth: `?key=` query parameter.
- **OD Analysis: Available Maps**: Use this endpoint to find the map versions available for an area.
- **OD Analysis: Cancel Analysis**: Send a POST request to cancel an analysis. Auth: `?key=` query parameter.
- **OD Analysis: Create Flow Matrix Analysis**: Create a Flow Matrix Analysis by sending a POST request. Auth: `?key=` query parameter.
- **OD Analysis: Create Selected Link Analysis**: Create a Selected Link Analysis by sending a POST request. Auth: `?key=` query parameter.
- **OD Analysis: Download Flow Matrix Histogram CSV**: Get a full histogram result as a CSV file by sending a GET request. The analysis must have been created with `tripStats` enabled. Auth: `?key=` query parameter.
- **OD Analysis: Download Flow Matrix Trips CSV**: Get the full trips result as a CSV file by sending a GET request. Auth: `?key=` query parameter.
- **OD Analysis: Get Flow Matrix Analysis**: Get a preview of the analysis by sending a GET request. Auth: `?key=` query parameter.
- **OD Analysis: Get Flow Matrix Partial Histogram Result**: Get a partial histogram result by sending a POST request. The analysis must have been created with `tripStats` enabled. Auth: `?key=` query parameter.
- **OD Analysis: Get Flow Matrix Partial Trips Result**: Get a partial trips result by sending a POST request. Auth: `?key=` query parameter.
- **OD Analysis: Get Flow Matrix Trips Result**: Get the full trips result by sending a GET request. Auth: `?key=` query parameter.
- **OD Analysis: Get Selected Link Analysis**: Perform a GET request to return an analysis preview. Auth: `?key=` query parameter.
- **OD Analysis: Get Selected Link Result**: This page describes the result files of a Selected Link analysis, their structure, their formats, and how to filter them by path hash.
- **OD Analysis: List Analyses**: Send a GET request to return an analysis list. Auth: `?key=` query parameter.
- **OD Analysis: Reject Analysis**: Reject an analysis by sending a POST request. Auth: `?key=` query parameter.
- **On-Street Parking: Parking Locations**: The On-Street Parking API Parking Locations endpoint provides information about on-street parking location probability in the requested point and within the area described by the given radius.
- **On-Street Parking: Vector Tiles**: The Vector Tiles endpoint provides information about the probability of finding available on-street parking locations, together with their geometry. It also provides data on zoom levels ranging from `0` to `22`.
- **Orbis Assets: Assets API Entrypoint**: List all available resource types with their version endpoints. Auth: `?key=` query parameter or `TomTom-Api-Key` header.
- **Orbis Assets: Fetch glyphs range**: Fetches the specified glyphs of the given fontName. Auth: `?key=` query parameter or `TomTom-Api-Key` header.
- **Orbis Assets: Fetch Sprite**: Allows the fetching of a MapLibre sprite, given its version. At least one of the [map, trafficFlow, trafficIncidents] parameters must be provided.
- **Orbis Assets: Fetch Style**: Allows the fetching of a MapLibre style, given its version. At least one of the [map, hillshade, trafficFlow, trafficIncidents] parameters needs to be provided.
- **Orbis Assets: List assets for the given asset type and version**: It contains a list of assets and endpoints, allowing them to be fetched. Auth: `?key=` query parameter or `TomTom-Api-Key` header.
- **Orbis Assets: List glyphs ranges**: List glyphs ranges of a given fontName together with endpoints that can be used to fetch them. Auth: `?key=` query parameter or `TomTom-Api-Key` header.
- **Orbis Assets: Lists assets versions for styles or sprites**: It contains a list of asset versions together with endpoints that allow listing their assets. See listAssets. Auth: `?key=` query parameter or `TomTom-Api-Key` header.
- **Orbis Assets: Lists fonts**: It contains a list of fonts and endpoints that allow listing their ranges. Auth: `?key=` query parameter or `TomTom-Api-Key` header.
- **Orbis Assets: Lists fonts versions**: It contains a list of available font versions, along with endpoints that can be used to list the fonts in the versions. See listFonts. Auth: `?key=` query parameter or `TomTom-Api-Key` header.
- **Orbis EV Charging Availability**: The EV Charging Stations Availability endpoint provides information about the current availability of charging points, grouped by connector type and then power level.
- **Orbis EV Search: Along the Route**: The EV Search Along the Route endpoint provides information about the EV POIs along a pre-calculated route. By providing optional request parameters, the API allows filtering of the response by connector type, availability status, etc.
- **Orbis EV Search: By ID**: The EV Search by Id endpoint provides detailed information about one or more EV POIs (points of interest) requested by their ID. This includes details such as location, availability status, and attached connectors.
- **Orbis EV Search: EV Brands**: The Charge Point Operators (CPO) endpoint enables clients to access a list of available CPOs in a given country or subdivision. This helps EV drivers choose their preferred Charge Point Operators while searching for EV charging stations.
- **Orbis EV Search: EV Payment Applications**: The e-Mobility Service Providers (eMSP) endpoint enables clients to access available eMSPs in a given country. This helps EV drivers choose their preferred e-Mobility Service Providers while searching for EV charging stations.
- **Orbis EV Search: Nearby**: The EV Search Nearby endpoint provides information about the nearest EV POIs (points of interest) based on a circular area, a bounding box, or a combination of both.
- **Orbis Fuel Prices: Fuel Price**: The Fuel Prices service provides information about the current fuel prices of fuel stations. Not available on the free evaluation or Pay As You Grow plans; contact TomTom Sales. Auth: `?key=` query parameter.
- **Orbis Geocoding V1: Geocode**: In many cases, the complete Search service might be too much. For instance, if you are only interested in traditional Geocoding, Search can also be exclusively accessed for address look-up. Auth: `?key=` query parameter.
- **Orbis Geocoding V1: Structured Geocode**: Search can also be exclusively accessed for structured address look up. The geocoding index will be queried for everything above the street level data. Auth: `?key=` query parameter.
- **Orbis Geocoding V2: Geocode**: Geocoding can be exclusively accessed for address look-up. The Geocoding is performed by sending requests to the Geocode endpoint with just the address or partial address in question. No POIs (Points of Interest) will be returned.
- **Orbis Geocoding V2: Structured Geocode**: The structured geocode endpoint allows you to pass address components such as house number, street and city as separate query parameters instead of a single `query` string. You can specify some or all address components in the request.
- **Orbis Map Display V1: Get copyright information for a map**: The Copyrights API is designed to serve copyright information for the Map Display services. As an alternative to copyrights for a map request, you can receive copyrights for the map service called captions. Auth: `?key=` query parameter.
- **Orbis Map Display V1: Get copyrights caption for the map**: This endpoint is serving copyrights caption for the map service. Auth: `?key=` query parameter.
- **Orbis Map Display V1: Get map display hillshade tile**: The Maps Raster Hillshade Tile API endpoint provides terrain elevation data that is divided into gridded sections called tiles. It can be used for rendering hillshade that shows the topographical shape of hills and mountains.
- **Orbis Map Display V1: Get map display raster tile**: The Maps Raster Tile API endpoint renders map data that is divided into gridded sections called tiles. Tiles are square images in various sizes which are available at 23 different zoom levels, ranging from 0 to 22.
- **Orbis Map Display V1: Get map display satellite raster tile**: The Maps Raster Satellite Tile API endpoint provides satellite map data that is divided into gridded sections called tiles. Tiles are square images with a size of 256x256 pixels.
- **Orbis Map Display V1: Get map display vector tile**: The Map Display API Vector Tiles endpoint serves data on zoom levels ranging from 0 to 22. For zoom level 0, the entire earth is displayed on a single tile. At zoom level 22, the world is divided into 244 tiles.
- **Orbis Map Display V2: Get 3D landmarks heatmap**: Serves bitmap tiles containing information about 3D landmarks in the specific area. Used to avoid empty calls for 3D landmarks, as the tiles are not present for the most coordinates.
- **Orbis Map Display V2: Get 3D landmarks tile**: Serves 3D models of landmarks divided into tiles in GLB format (GL Transmission Format Binary file). Tiles are available in 2 different zoom levels (15th and 16th). Auth: `?key=` query parameter or `TomTom-Api-Key` header.
- **Orbis Map Display V2: Get copyright information for a map**: The Copyrights API is designed to serve copyright information for the Map Display services. As an alternative to copyrights for a map request, you can receive copyrights for the map service called captions.
- **Orbis Map Display V2: Get copyrights caption for the map**: This endpoint is serving copyrights caption for the map service. Auth: `?key=` query parameter or `TomTom-Api-Key` header.
- **Orbis Map Display V2: Get map display hillshade tile**: The Maps Raster Hillshade Tile API endpoint provides terrain elevation data that is divided into gridded sections called tiles. It can be used for rendering hillshade that shows the topographical shape of hills and mountains.
- **Orbis Map Display V2: Get map display raster tile**: The Maps Raster Tile API endpoint renders map data that is divided into gridded sections called tiles. Tiles are square images in various sizes which are available at 23 different zoom levels, ranging from 0 to 22.
- **Orbis Map Display V2: Get map display satellite raster tile**: The Maps Raster Satellite Tile API endpoint provides satellite map data that is divided into gridded sections called tiles. Tiles are square images with a size of 256x256 pixels.
- **Orbis Map Display V2: Get map display vector tile**: The Map Display API Vector Tiles endpoint serves data on zoom levels ranging from 0 to 22. For zoom level 0, the entire earth is displayed on a single tile. At zoom level 22, the world is divided into 2^44 tiles.
- **Orbis On-Street Parking V1: Parking Locations**: The On-Street Parking API Parking Locations endpoint provides information about on-street parking location probability in the requested point and within the area described by the given radius.
- **Orbis On-Street Parking V1: Vector Tiles**: The Vector Tiles endpoint provides information about the probability of finding available on-street parking locations, together with their geometry. It also provides data on zoom levels ranging from `0` to `22`.
- **Orbis On-Street Parking V2: Parking Locations**: The On-Street Parking API Parking Locations endpoint provides information about on-street parking location probability in the requested point and within the area described by the given radius.
- **Orbis On-Street Parking V2: Vector Tiles**: The Vector Tiles endpoint provides information about the probability of finding available on-street parking locations, together with their geometry. It also provides data on zoom levels ranging from `0` to `22`.
- **Orbis Parking: Parking Availability**: The Parking Availability service provides information about the current availability status of parking sites. Auth: `?key=` query parameter.
- **Orbis Parking: Parking Prices**: The Parking Prices API offers the following features: - Calculation of estimated price of the off-street parking stay from the start time and for given duration - List of available payment methods - List of pricing structure with ticket
- **Orbis POI Details: POI Details**: The Points of Interest (POI) Details API provides additional information about the POIs including: rating, price range, photo IDs, and user reviews. Auth: `?key=` query parameter.
- **Orbis POI Photos: POI Photo**: The Points of Interest (POI) Photos service provides photos of the POI. Auth: `?key=` query parameter.
- **Orbis Reverse Geocoding V1: Reverse Geocode**: The TomTom Orbis Maps Reverse Geocoding API Reverse Geocode endpoint gives users a tool to translate a coordinate (for example: `37.786505, -122.3862`) into a human-understandable street address, street element, or geography.
- **Orbis Reverse Geocoding V2: Reverse geocode a location to an address**: Translate a geographic coordinate (e.g., -122.3862, 37.786505) into a human‑understandable street address, street element, or geography.
- **Orbis Routing V2: Calculate Route**: The Calculate Route service calculates a route between an origin and a destination, passing through waypoints if they are specified. Auth: `?key=` query parameter.
- **Orbis Routing V3: Calculate Route**: The Calculate Route service calculates a route between an origin and a destination, passing through waypoints if they are specified. Auth: `TomTom-Api-Key` header.
- **Orbis Search: Additional Data**: The Geometries Data Provider returns sets of coordinates that represent the outline of a city, country, or land area. The service supports batch requests of up to 20 identifiers. Auth: `?key=` query parameter.
- **Orbis Search: Along Route Search**: The Along Route Search endpoint allows you to perform a fuzzy search for POIs along a specified route. This search is constrained by specifying a detour time-limiting measure.
- **Orbis Search: Autocomplete**: The Autocomplete API enables you to make a more meaningful Search API call by recognizing entities inside an input query and offering them as query terms. Auth: `?key=` query parameter.
- **Orbis Search: Category Search**: If your search use case only requires `POI` (Points of Interest) results filtered by category, you may use the Category Search endpoint. This endpoint will only return `POI` results which are categorized as specified.
- **Orbis Search: Fuzzy Search**: The generic, default service is Fuzzy Search which handles the most fuzzy of inputs containing any combination of Indexes abbreviation values. See the Indexes abbreviation values section at the bottom of this page.
- **Orbis Search: Geometry Search**: The Geometry Search endpoint allows you to perform a free form search inside a single geometry or many of them. The search results that fall inside the geometry/geometries will be returned. The service returns `POI` results by default.
- **Orbis Search: Nearby Search**: If your use case is only retrieving POI (Points of Interest) results around a location, you may use the Nearby Search endpoint. This endpoint will _only return POI results_. It does not take in a search query parameter.
- **Orbis Search: Place by ID**: The Place by Id service endpoint provides detailed information about the Place found by its identifier (`entityId`). Currently, Place by Id supports all types by ids. Auth: `?key=` query parameter.
- **Orbis Search: POI Categories**: The POI Categories service endpoint provides a full list of POI categories and subcategories together with their translations and synonyms. Auth: `?key=` query parameter.
- **Orbis Search: Points of Interest Search**: If your search use case only requires POI results, you may use the Points of Interest endpoint for searching. This endpoint will _only return POI results_. Auth: `?key=` query parameter.
- **Orbis Traffic V1: Get a map display traffic flow raster tile**: The Traffic Raster Flow Tiles endpoint serves 256 x 256 pixel or 512 x 512 pixel tiles showing traffic flow. All tiles use the same grid system.
- **Orbis Traffic V1: Get a map display traffic flow vector tile**: The Traffic Vector Flow Tiles endpoint provides data on zoom levels ranging from 0 to 22. The service delivers traffic flow data packaged in a vector representation of squared sections called vector tiles.
- **Orbis Traffic V1: Get a map display traffic incident raster tile**: The Traffic Raster Incidents Tiles endpoint serves 256 x 256 pixel or 512 x 512 pixel tiles showing traffic incidents. All tiles use the same grid system.
- **Orbis Traffic V1: Get a map display traffic incident vector tiles**: The Traffic Vector Incidents Tiles endpoint provides data on zoom levels ranging from 0 to 22. The service delivers traffic incidents data packaged in a vector representation of squared sections called vector tiles.
- **Orbis Traffic V1: Get traffic incident details (GET)**: The Incident Details endpoint provides information on traffic incidents which are inside a given bounding box or whose geometry intersects with it.
- **Orbis Traffic V1: Get traffic incident details (POST)**: The Incident Details endpoint provides information on traffic incidents for the provided list of incident IDs. The maximum number of incident IDs in a single POST request is 100.
- **Orbis Traffic V2: Get a map display traffic flow raster tile**: The Traffic Raster Flow Tiles endpoint serves 256 x 256 pixel or 512 x 512 pixel tiles showing traffic flow. All tiles use the same grid system.
- **Orbis Traffic V2: Get a map display traffic flow vector tile**: The Traffic Vector Flow Tiles endpoint provides data on zoom levels ranging from 0 to 22. The service delivers traffic flow data packaged in a vector representation of squared sections called vector tiles.
- **Orbis Traffic V2: Get a map display traffic incident raster tile**: The Traffic Raster Incidents Tiles endpoint serves 256 x 256 pixel or 512 x 512 pixel tiles showing traffic incidents. All tiles use the same grid system.
- **Orbis Traffic V2: Get a map display traffic incident vector tile**: The Traffic Vector Incidents Tiles endpoint provides data on zoom levels ranging from 0 to 22. The service delivers traffic incidents data packaged in a vector representation of squared sections called vector tiles.
- **Orbis Traffic V2: Get traffic incident details (GET)**: The Incident Details endpoint provides information on traffic incidents which are inside a given bounding box or whose geometry intersects with it.
- **Orbis Traffic V2: Get traffic incident details (POST)**: The Incident Details endpoint provides information on traffic incidents for the provided list of incident IDs. The maximum number of incident IDs in a single POST request is 100.
- **Parking: Parking Availability**: The Parking Availability service provides information about the current availability status of parking sites. Auth: `?key=` query parameter.
- **Parking: Parking Prices**: The Parking Prices API offers the following features: - Calculation of estimated price of the off-street parking stay from the start time and for given duration - List of available payment methods - List of pricing structure with ticket
- **Places Search: Details for a location**: Delivers detailed information for a location. Auth: `TomTom-Api-Key` header.
- **Places Search: Discover a location**: 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.
- **Places Search: Suggest a location**: Delivers as-you-type suggestions for important or nearby locations and related discoverable concepts.
- **POI Details: POI Details**: The Points of Interest (POI) Details API provides additional information about the POIs including: rating, price range, photo IDs, and user reviews. Auth: `?key=` query parameter.
- **POI Photos: POI Photo**: The Points of Interest (POI) Photos service provides photos of the POI. Auth: `?key=` query parameter.
- **Reachable Range: Reachable Range (GET)**: Calculates the geographic area that can be reached from the origin point. Auth: `?key=` query parameter.
- **Reachable Range: Reachable Range (POST)**: Calculates the geographic area that can be reached from the origin point.
- **Reverse Geocoding: Cross Street lookup**: This endpoint returns address information and coordinates for a position to the nearest intersection.
- **Reverse Geocoding: Reverse Geocode**: The TomTom Reverse Geocoding API gives users a tool to translate a coordinate (for example: `37.786505, -122.3862`) into a human-understandable street address, street element, or geography.
- **Road Segment: Road Segment (GET)**: This service matches the received points to the map road network. Input points can be unrelated to themselves and don't have to be a part of the same route. Auth: `?key=` query parameter.
- **Road Segment: Road Segment (POST)**: The service matches the received points to the map road network. Input points can be unrelated to themselves and don't have to be a part of the same route. Auth: `?key=` query parameter.
- **Route Monitoring: Create Route**: Returns a confirmation of requested data and the assigned id for a route. Auth: `?key=` query parameter.
- **Route Monitoring: Delete Route**: The response contains no data. Only the correct status code is a confirmation. Auth: `?key=` query parameter.
- **Route Monitoring: Edit Route**: The request path, request body, and response are identical as in route creation. Auth: `?key=` query parameter.
- **Route Monitoring: Get Route (Detailed)**: The response contains detailed information about the active route given in the request path including data for individual segments. If OpenLR is not available for some local roads, then the data does not include current traffic information.
- **Route Monitoring: Get Route (Short)**: The response contains basic information about the active route given in a request path. If the route is not in ACTIVE status, the response lacks traffic information (see: Route Statuses at the bottom of this page).
- **Route Monitoring: List Routes**: The response contains an array of all routes created with the given API Key and basic information about each of them. It excludes deleted routes (in ARCHIVED status - see: Route Statuses at the bottom of this page).
- **Route Monitoring: Preview Route**: The response contains the geometry of a route which can be created for given path points. Auth: `?key=` query parameter.
- **Routing: Calculate Route (GET)**: Calculates a route between an origin and a destination. Auth: `?key=` query parameter.
- **Routing: Calculate Route (POST)**: Calculates a route between an origin and a destination. POST method handles additionally parameters: supportingPoints, allowVignette, avoidVignette, avoidAreas. Auth: `?key=` query parameter.
- **Safety Related Traffic Info: Get Safety Messages**: You can use this endpoint to query for recent safety-related messages detected by TomTom applications. The response will contain events that occurred within a specific and recent time period of up to 24 hours. Auth: `?key=` query parameter.
- **Search: Additional Data**: The Geometries Data Provider returns sets of coordinates that represent the outline of a city, country, or land area. The service supports batch requests of up to 20 identifiers. Auth: `?key=` query parameter.
- **Search: Along Route Search**: The Along Route Search endpoint allows you to perform a fuzzy search for POIs along a specified route. This search is constrained by specifying a detour time-limiting measure.
- **Search: Autocomplete**: The Autocomplete API enables you to make a more meaningful Search API call by recognizing entities inside an input query and offering them as query terms. Auth: `?key=` query parameter.
- **Search: Category Search**: If your search use case only requires `POI` (Points of Interest) results filtered by category, you may use the Category Search endpoint. This endpoint will only return `POI` results which are categorized as specified.
- **Search: Fuzzy Search**: The generic, default service is Fuzzy Search which handles the most fuzzy of inputs containing any combination of Indexes abbreviation values. See the Indexes abbreviation values section at the bottom of this page.
- **Search: Geometry Filter (GET)**: The Geometry Filter endpoint becomes handy when a list of POIs is already available and needs to be filtered using a list of geometries. It will return POIs that lie within any of the geometries.
- **Search: Geometry Filter (POST)**: The Geometry Filter endpoint becomes handy when a list of POIs is already available and needs to be filtered using a list of geometries. It will return POIs that lie within any of the geometries.
- **Search: Geometry Search (GET)**: The Geometry Search endpoint allows you to perform a free form search inside a single geometry or many of them. The search results that fall inside the geometry/geometries will be returned. The service returns `POI` results by default.
- **Search: Geometry Search (POST)**: The Geometry Search endpoint allows you to perform a free form search inside a single geometry or many of them. The search results that fall inside the geometry/geometries will be returned. The service returns `POI` results by default.
- **Search: Nearby Search**: If your use case is only retrieving POI (Points of Interest) results around a location, you may use the Nearby Search endpoint. This endpoint will _only return POI results_. It does not take in a search query parameter.
- **Search: Place by ID**: The Place by Id service endpoint provides detailed information about the Place found by its identifier (`entityId`). Currently, Place by Id supports all types by ids. Auth: `?key=` query parameter.
- **Search: POI Categories**: The POI Categories service endpoint provides a full list of POI categories and subcategories together with their translations and synonyms. Auth: `?key=` query parameter.
- **Search: Points of Interest Search**: If your search use case only requires POI results, you may use the Points of Interest endpoint for searching. This endpoint will _only return POI results_. Auth: `?key=` query parameter.
- **Snap to Roads: Asynchronous Snap to Roads Download**: The service returns requested via Asynchronous Snap to Roads Submission endpoint data. Auth: `?key=` query parameter.
- **Snap to Roads: Asynchronous Snap to Roads Status**: The service returns status of requested via Asynchronous Snap to Roads Submission endpoint data. Auth: `?key=` query parameter.
- **Snap to Roads: Asynchronous Snap to Roads Submission**: 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. Auth: `?key=` query parameter.
- **Snap to Roads: Synchronous Snap to Roads (GET)**: 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. Auth: `?key=` query parameter.
- **Snap to Roads: Synchronous Snap to Roads (POST)**: 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. Auth: `?key=` query parameter.
- **Tabular Weather: Weather Conditions**: The Tabular Weather API delivers current and predicted location-based weather conditions in different temporal resolutions. Auth: `?key=` query parameter.
- **Traffic: Flow Segment Data**: 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..
- **Traffic: Map Styles Metadata**: Lists the available vector traffic map resources (styles, sprites, glyphs) of a selected type, with versions and variants. Auth: `?key=` query parameter.
- **Traffic: Raster Flow Tiles**: 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..
- **Traffic Stats: Accept Job**: Accepts a job waiting in `NEED_CONFIRMATION` (manual acceptance mode) so processing continues. Auth: `?key=` query parameter.
- **Traffic Stats: Area Analysis**: The Traffic Stats API Area Analysis service calculates statistics for an area. This service is asynchronous. Auth: `?key=` query parameter.
- **Traffic Stats: Available Maps**: Use this endpoint to check what map versions are available in all Traffic Stats APIs. Map versions should be selected based on map type, date Range(s) and route(s)/network provided in the create report POST request.
- **Traffic Stats: Get Job Status**: Checks the state of a Traffic Stats job (route analysis, area analysis or traffic volume). Applies to all three analysis types. Auth: `?key=` query parameter.
- **Traffic Stats: Reject Job**: Rejects a job waiting in `NEED_CONFIRMATION` (manual acceptance mode). Auth: `?key=` query parameter.
- **Traffic Stats: Route Analysis**: The Traffic Stats API Route Analysis service calculates statistics for a defined route between an origin and a destination, optionally via waypoints. This service is asynchronous. Auth: `?key=` query parameter.
- **Traffic Stats: Search Jobs**: Use this endpoint to list all of your jobs, or just filter out a part of them. Auth: `?key=` query parameter.
- **Traffic Stats: Traffic Volume**: The Traffic Stats API Traffic Volume service provides estimated historical vehicle counts for road segments within an area. This service is asynchronous. Auth: `?key=` query parameter.
- **Traffic: Traffic Incident Details v5 (GET)**: 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. Auth: `?key=` query parameter.
- **Traffic: Traffic Incident Details v5 (POST)**: 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. Auth: `?key=` query parameter.
- **Traffic: Traffic Incident Viewport**: This service returns legal and technical information for the viewport described in the request. Auth: `?key=` query parameter.
- **Traffic: Traffic Raster Incident Tiles**: 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..
- **Traffic: Traffic Vector Incident Tiles**: 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. Auth: `?key=` query parameter.
- **Traffic: Vector Flow Tiles**: 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.
- **Waypoint Optimization: Optimize Waypoints**: This endpoint optimizes a provided waypoints sequence based on road network distances. Sequence is ordered to form the fastest route. Auth: `?key=` query parameter.
- **Weather Forecast: Daily Forecast**: Daily point-based weather forecast for a latitude and longitude, up to 14 days by default.
- **Weather Forecast: Hourly Forecast**: Hourly point-based weather forecast for a latitude and longitude, 24 hours by default.

Connect TomTom in General Input: https://www.generalinput.com/apps/tomtom