HERE

This endpoint completes entered keystrokes to a valid street address or administrative area to speed-up entering address queries. via GET https://autocomplete.search.hereapi.com/v1/autocomplete

This endpoint suggests address or place candidates based on an incomplete or misspelled query, from which the user selects the best query to submit. _NOTE: The response may contain **experimental** elements not documented here. Any undocumented element is **subject to removal** at any time._ via GET https://autosuggest.search.hereapi.com/v1/autosuggest

This endpoint provides search results for places based on different filters, such as categories or name, ranked by distance from a given search center. The only mandatory elements exposed in the response are ID and position. The other elements shown in the response samples section are only dataset attributes suggestions. via GET https://browse.search.hereapi.com/v1/browse

Retrieves both the copyright information and the coordinates of the bounding box to which the text applies. If your products and/or services use map data that is made accessible using this service, you shall provide end-users of your products and/or services with notice, in a reasonably conspicuous manner. For more information, see [Include the copyright notice](https://docs.here.com/map-rendering/docs/copyright-notice). via GET https://image.maps.hereapi.com/mia/v3/copyright

Lists public transit departures. Discovers subsequent departures using structured or topological queries. The service accepts two types of queries as shown in the table below: | Query | Parameter | Description | |-------|-----------|-------------| | Departures by IDs | `ids` | takes a comma-separated list of station/stop identifiers | | Departures by Location | `in` | takes a pair of coordinates to define the center and a radius to define the extent of a circular area where to search for departures | Select a query from `one of` the options above to visualize the request parameters. via GET https://transit.hereapi.com/v8/departures

This endpoint processes a free-form text query for an address or place, and returns results in order of relevance. via GET https://discover.search.hereapi.com/v1/discover

Returns the list of available features per style. You can use these values to request an image with particular features specified as query parameters. Use only the features that are available for a particular style. For more information, see [Customize map features](https://docs.here.com/map-rendering/docs/additional-map-features). via GET https://image.maps.hereapi.com/mia/v3/features

This endpoint allows you to find the geo-coordinates of a known address, place, locality or administrative area, even if the query is incomplete or partly incorrect. It also returns a complete postal address string and address details. It supports structured, unstructured and hybrid queries - combinations of structured and unstructured query elements. via GET https://geocode.search.hereapi.com/v1/geocode

Provides details on acceptable values for API parameters, such as PPI (Pixels Per Inch), styles, and other relevant parameters. via GET https://image.maps.hereapi.com/mia/v3/info

Retrieves a list of polylines that captures the approximate reachable area from the specified center point constrained by the provided parameters. via GET https://isoline.router.hereapi.com/v8/isolines

Returns the list of available map languages per resource. You can use these values to request an image with labels in a particular language. The values follow ISO 639-1 two-letter language code and, optionally, ISO 15924 four-letter script code. For more information, see [Personalize the map language](https://docs.here.com/map-rendering/docs/languages). via GET https://image.maps.hereapi.com/mia/v3/languages

This endpoint looks up a known place using the HERE ID included in the request. via GET https://lookup.search.hereapi.com/v1/lookup

Result of successfully completed calculation. via GET https://matrix.router.hereapi.com/v8/matrix/{matrixId}

Returns the status of a submitted asynchronous matrix calculation. Redirects to the matrix result if the calculation is successfully completed. **NOTE:** Please make sure to directly use the `statusUrl` returned by the /v8/matrix call to check this status endpoint, including the provided region URL. Due to global load balancing, using matrix.router.hereapi.com for the status endpoint may end up resolving to a different region than the initial calculation, resulting in a 404 error. via GET https://matrix.router.hereapi.com/v8/matrix/{matrixId}/status

Provides a catalog of available geopolitical views. These values enable the request of an image featuring a specific country view. For more information on geopolitical views, see [Explore geopolitical views](https://docs.here.com/map-rendering/docs/political-views). via GET https://image.maps.hereapi.com/mia/v3/politicalViews

It is guaranteed that with each minor API change profiles are only added to this list, but are never removed or modified. via GET https://matrix.router.hereapi.com/v8/profiles

Get profile definition by its ID. via GET https://matrix.router.hereapi.com/v8/profiles/{profileId}

This endpoint returns the nearest address to geo coordinates specified in the request. via GET https://revgeocode.search.hereapi.com/v1/revgeocode

Calculates a route using a generic vehicle/pedestrian mode, e.g. car, truck, pedestrian, etc... via GET https://router.hereapi.com/v8/routes

Decodes and returns a route from a previously calculated route handle. **Disclaimer: A route handle is not suitable for persistent route storage! It can be invalidated at any time.** A route handle encodes a previously calculated route. A route can be decoded from a handle as long as the service uses the same map data and encoding that were used when retrieving the handle. Thus it is suitable for caching routes compactly. It can be used to retrieve updated traffic information or other data along the route. However, a user should be prepared to recalculate the route when decoding the handle fails. All parameters of the `/routes` endpoint are supported, except for `destination`, `via`, `alternatives` and `routingMode`. See also the `return` parameter of `/routes` endpoint. The `origin` parameter can be provided to update the start of the previously calculated route. The `transportMode` parameter does not have to match the transport mode previously used for route calculation. However, when using a different transport mode, the request may fail, e.g. when the route has road segments forbidden for the provided transport mode. Please refer to the Developer Guide for more information and examples. via GET https://router.hereapi.com/v8/routes/{routeHandle}

Lists public transit stations. Discovers stations using structured or topological queries. The service accepts three types of queries as shown in the table below: | Query | Parameter | Description | |-------|-----------|-------------| | Stations by IDs | `ids` | Takes a comma-separated list of station/stop identifiers. | | Stations by location | `in` | Takes a pair of coordinates to define the center and a radius to define the extent of a circular area where to search for departures. | | Stations by name and location | `name` and `in` | Takes the station name or part of the name to search for. It is composed of one or more space-separated words and does not support stopwords. | Select a query from `one of` the options above to visualize the request parameters. via GET https://transit.hereapi.com/v8/stations

Lists public transit routes. The service supports several use cases as follows: * define routes based on arrival or departure times. * filter specific transit modes, such as rail and metro only. * plan routes hours or days in advance. * set a maximum distance for the walk to the nearest transit stop/station or the speed of the walk. * define how many changes or transfers the journey may include. * request turn-by-turn navigation. * request route polyline in order to view the route over a map. via GET https://transit.hereapi.com/v8/routes

This endpoint suggests address or place candidates based on an incomplete or misspelled query, from which the user selects the best query to submit. _NOTE: The response may contain **experimental** elements not documented here. Any undocumented element is **subject to removal** at any time._ via POST https://autosuggest.search.hereapi.com/v1/autosuggest

This endpoint provides search results for places based on different filters, such as categories or name, ranked by distance from a given search center. The only mandatory elements exposed in the response are ID and position. The other elements shown in the response samples section are only dataset attributes suggestions. via POST https://browse.search.hereapi.com/v1/browse

This endpoint processes a free-form text query for an address or place, and returns results in order of relevance. via POST https://discover.search.hereapi.com/v1/discover

Creates a route from a sequence of trace points. Post body size limit is 10MiB. For best results, use 1Hz GPS data or any points that have a spacing of a few meters between them. For traces with less frequent points, the Route Import service will attempt to create an approximate reconstruction. In some situations, when consecutive points are too far apart (more than about 30 kilometers of on-road distance), they could be considered unreachable and one of them could fail to be matched. via POST https://router.hereapi.com/v8/import

Retrieves a list of polylines that captures the approximate reachable area from the specified center point constrained by the provided parameters. At the moment, only select parameters are permitted in the POST payload. In particular, those parameters that due to request size may be limited in the query string. See the request body section below. These parameters can be provided either in the query string or in the POST body. All other parameters can only be provided in the query string at the moment. via POST https://isoline.router.hereapi.com/v8/isolines

Calculates a routing matrix based on provided `origins` and `destinations`. Response will be provided synchronously (see `200` response) or asynchronously (see `202` response) depending on the `async` query parameter. Travel times will be included by default i.e., when `matrixAttributes` parameter is not specified. For other supported attributes, the corresponding flags must be specified in `matrixAttributes`. Maximum request size is 10 MiB (uncompressed). via POST https://matrix.router.hereapi.com/v8/matrix

This endpoint returns addresses/places for a list of geo-coordinates specified in the request. via POST https://multi-revgeocode.search.hereapi.com/v1/multi-revgeocode

Calculates a route using a generic vehicle/pedestrian mode, e.g. car, truck, pedestrian, etc... At the moment, only selected parameters are permitted in the POST body, particularly those that may be restricted in the query string due to request size limitations. See the request body section below for details. All other parameters must be provided in the query string. If a parameter is provided in both the query string and the POST body, their values are merged. Post body size limit is 10MiB. via POST https://router.hereapi.com/v8/routes

Decodes and returns a route from a previously calculated route handle. **Disclaimer: A route handle is not suitable for persistent route storage! It can be invalidated at any time.** A route handle encodes a previously calculated route. A route can be decoded from a handle as long as the service uses the same map data and encoding that were used when retrieving the handle. Thus it is suitable for caching routes compactly. It can be used to retrieve updated traffic information or other data along the route. However, a user should be prepared to recalculate the route when decoding the handle fails. All parameters of the `/routes` endpoint are supported, except for `destination`, `via`, `alternatives` and `routingMode`. See also the `return` parameter of `/routes` endpoint. The `origin` parameter can be provided to update the start of the previously calculated route. The `transportMode` parameter does not have to match the transport mode previously used for route calculation. However, when using a different transport mode, the request may fail, e.g. when the route has road segments forbidden for the provided transport mode. Only selected parameters are permitted in the POST body. See the request body section below for details. If a parameter is provided in both the query string and the POST body, their values are merged. Post body size limit is 10MiB. Please refer to the Developer Guide for more information and examples. via POST https://router.hereapi.com/v8/routes/{routeHandle}

**RESTRICTED** This endpoint receives user interaction data from previous search results to improve future result quality. via POST https://signals.search.hereapi.com/v1/signals