HERE Geocoding and Search v7 provides increased POI coverage and a higher cadence of data updates. In addition, HERE Geocoding and Search v7 offers a simplified API that integrates the features of both the "HERE Places (Search) API" and "HERE Geocoder API" products.
HERE Places (Search) API is currently in Maintenance.
In this document, we will use the following shorter names:
The following general actions must be taken to complete the migration:
There are some input as well as output parameters that are no longer supported due to conceptual changes. These are detailed in this guide.
Places API and GS7 use different names for similar concepts:
|"Entrypoint"||"Service"||See below from Entrypoints to Services|
|Entrypoint "parameter"||endpoint query "parameter"|
|"Media Type"||"response element"|
|Media Type "attribute"||"response element"|
Places API is accessible via URLs depending on both target segments and authorization method:
|Base URL||Variant||Authorization method|
| ||Public, Automotive||Oauth2 or API key|
GS7 related URLs are not based on target segments nor authorization methods, but on the general concept of HERE platform "Service". A "Service" corresponds to what is known in Places API as an "Entrypoint".
HERE platform Service domain names comply to the schema
GS7 product part is
search, so that the base URLs to migrate follows the schema
There are 4 services in GS7 corresponding to the Places API entrypoints. Those are Discover, Browse, Autosuggest and Lookup. All service are authorized through either a Oauth token or an API Key. So that the base URLs in are:
|Base URL||Service||Authorization method|
| ||Autosuggest Service||Oauth2 or API key|
| ||Discover Service||Oauth2 or API key|
| ||Browse Service||Oauth2 or API key|
| ||Lookup Service||Oauth2 or API key|
The mapping below summarizes how Places API entrypoints corresponds to GS7 services.
|Places API Entrypoint||GS7 equivalence||status||Comment|
|Autosuggest Entrypoint||Autosuggest Service||available|
|Search Entrypoint||Discover Service||available|
|Browse Entrypoint||Browse Service||available|
|Lookup Entrypoint||Lookup Service||available|
|Explore Entrypoint||Browse Service||partly||A service comparable to the Places API entrypoint is not currently available. |
Please note that the GS7 Browse Service may fulfill your needs.
If not, please contact GS7 Management.
|Browse by Corridor Entrypoint||Browse Service||available|
|Suggest Entrypoint||Autosuggest Service||available||The Suggest Entrypoint was deprecated in Places API. See Entrypoint maturity.|
|Here Entrypoint||Browse Service||available||The Here Entrypoint was deprecated in Places API. See Entrypoint maturity.|
|Around Entrypoint||Browse Service||available||The Around Entrypoint was deprecated in Places API. See Entrypoint maturity.|
|Place Categories Entrypoint||currently not available||A GS7 service comparable to the Places Categories is not currently available. Check Categories list in Developer Guide for details about GS7 supported places categories.|
|Cuisine Categories Entrypoint||currently not available||A GS7 service comparable to the Places Cuisines is not currently available. Food-Types list in Developer Guide for details about GS7 supported places cuisines.|
|Actions Entrypoint||currently not available|
|Health Entrypoint||currently not available|
|Corridor Shortener Entrypoint||(none)||out of scope||Simplification described in Developer Guide|
|Browse-Pt-Stops Entrypoint||(none)||out of scope||Please use HERE Public Transit API.|
Technically each Places API entrypoint and GS7 service is mapped to a REST API endpoint resource. Below is a subset of the different endpoint resource paths used in both products:
|Product||Entrypoint||Places API |
|Places API |
|Places API |
|Places API||Search|| || || |
|Places API||Autosuggest|| || || |
|Places API||Browse|| || || |
|Places API||Lookup|| || || |
|GS7||Autosuggest|| || || |
|GS7||Discover|| || || |
|GS7||Browse|| || || |
|GS7||Lookup|| || || |