---
updatedAt: 2026-07-22T12:39:55.000Z
agentTools:
siteIndex: https://docs.here.com/llms.txt
projectIndex: https://docs.here.com/geocoding-and-search/llms.txt
---
# API Changes
The sections below list APIs that were added, changed, or removed.
## Added
#### Release 7.157
**Discover, Autosuggest, Browse**: POST methods on `/autosuggest`, `/discover`, and `/browse` endpoints are now available to all customers (previously restricted).
This, for instance, allows customers to use the `route` parameter with a polyline up to 2000 waypoints.
#### Release 7.152
**Geocode, Reverse Geocode, Lookup**: HERE Geocoding and Search API v7 option `addressNamesVariant[city]=administrative` provides the administrative city name instead of the postal city name for address result in USA.
**Autocomplete**: Result `type filters`, `types=address`, `types=street`, and `types=houseNumber` are released as **STABLE**.
#### Release 7.150
**Reverse Geocode**: Result `type filters`, `types=houseNumber` and `types=place` are released as **STABLE.**
#### Release 7.146
**Geocode, Lookup, Reverse Geocode, Multi-Reverese Geocode**: Added attribution to an address to identify if an address is a residential address or a commercial (business) address with the parameter: `show=addressUsasge`. Note: The feature is released as **ALPHA** with a restricted access to authorized customers only.
#### Release 7.144
**Reverse Geocode, Multi-Reverese Geocode**: Match the input location to the nearest Micro Point Address (MPA), enhancing Reverse Geocoder accuracy in compounds where multiple buildings share the same address.
The feature is released as **STABLE** in the `/revgeocode` and the `/multi-revgeocode` endpoint. The access to MPA content is restricted to authorized customers only.
`with=MPA` returns the MPA closest to the input location.
`showRelated=parentPA` returns the related Point Address to which the MPA belongs.
`showMapReference=microPointAddress` returns the MPA identifier for the MPA result.
#### Release 7.142
**Geocode, Lookup**: Extended map reference information for `related` Micro Point Addresses (MPA). When the parameter `showMapReference` set to `links` or `segments`, the `/geocode` and `/lookup` endpoints now include `links` and `segments` map reference information also for MPAs in the `related` block - for MPA records that are related to a Point Address result - related MPA records are returned when the `showRelated=MPA` parameter is set. Retrieving map references is generally supported, but the feature to retrieve MPA content is only available to authorized customers.
**Autocomplete**: When `show=hasRelatedMPA` is set, a flag is provided for a Point Address result in the `/autocomplete` endpoint to indicate that sub-premises (referred to as Micro Point Addresses in HERE terminology) are associated with the house number. You can use this flag to initiate a follow-up call to the `/lookup` endpoint using the corresponding `id` and the `showRelated=MPA` parameter to retrieve the Micro Point Address (MPA) list and details. Note: This feature is released as **ALPHA**, and the access to MPA content is restricted to authorized customers only.
#### Release 7.140
**Geocode, Lookup**: Support for `showMapReferences=microPointAddress`. The HERE Geocoding and Search API v7 `/geocode` and `/lookup` endpoints now support a new value for the `showMapReferences` parameter: `microPointAddress`. When this parameter is set, the endpoints now include references to the Micro Point Address (MPA) in the following cases: For the results with `resultType=houseNumber` and `houseNumberType=MPA` - this result type is returned only if `with=MPA` parameter is specified; In the `related` block, for MPA records that are related to a Point Address result - related MPA records are returned when the `showRelated=MPA` parameter is set. This feature is available only to customers authorized to MPA features in general.
#### Release 7.139
**Geocode**: Parsing information now includes the `additionalInfo` block, which contains additional information extracted from the query that do not correspond to any recognized address components in the map data. Currently it is populated for Mexico with "house grouping" information such as, for example, "manzana" or "supermanzana".|
#### Release 7.138
**Discover, Autosuggest, Browse, Lookup**: The `driveThrough` response parameter is now released as **STABLE** with general availability. It is set to `true` if the related business allows customers to purchase products (or use the service provided by the business) without leaving their cars.
Note
All open API reference variants are adapted.
#### Release 7.136
**Geocode**: The `/geocode` endpoint now supports new value of `types` filter: `types=place`, which allows restricting results to result type: `place`. For the `/geocode` endpoint, place geocoding is treated as an alternative form of addressing. This allows, for example, geocoding business locations, including business names, in the same way as residential addresses. As a result, the `place` types filter is typically used in combination with other filters such as `address` or `houseNumber`, for example: `types=address,place`. Specifying `types=place` can be useful when the goal is to identify specific places or landmarks. Note that address results are not returned, and address queries may produce unexpected partially matching place results.
#### Release 7.134
**Discover, Browse, Lookup**: Deprecated media images optional `date` response element.
Note
This is a non-breaking change.
**Geocode**: The `addressNamesMode` feature of the `/geocode` endpoint, which enables users to choose between displaying normalized or matched address fields in the response, is extended to support not only the option to show normalized names, but also matched names: `addressNamesMode=matched`, affecting the names in the address block, the address label, and the result title.
#### Release 7.133
**Geocode**: `showTranslations` feature is released as **STABLE**.
#### Release 7.130
**Reverse Geocode, Multi-Reverse Geocode**: The feature `showRelated=nearbyAddress` is promoted to **STABLE**.
**Geocode, Autocomplete**: `postalCodeMode=cityLookup` and `postalCodeMode=districtLookup` promoted from **BETA** to **STABLE**.
#### Release 7.128
**Geocode**: `postalCodeMode=cityLookup` and `postalCodeMode=districtLookup` released as **BETA**.
**Autocomplete**: `postalCodeMode=districtLookup` released as **BETA**.
#### Release 7.127
**Reverse Geocode, Multi-Reverse Geocode**: The feature `showRelated=nearbyAddress` is released as **BETA**.
#### Release 7.126
**Geocode, Reverse Geocode, Multi-Reverse Geocode, Lookup**: `showNavAttributes=speedLimits` is released as **STABLE**.
Include speed limit and travel direction of the road in the results where available in content and when requested by the client application.
Note
* This feature is not supported in Japan.
* This feature is subject to premium pricing. For details, contact your HERE customer representative.
#### Release 7.124
**Geocode, Reverse Geocode, Multi-Reverse Geocode, Lookup**: Parameter `showMapReferences=links` is promoted to **STABLE**.
Note
The deprecated fields `links.linkId` and `links.sideOfLink` are removed from response. For more details, see the [API reference](/docs/).
#### Release 7.123
**Reverse Geocode**: Request parameter `showRelated=intersections`, for `resultType=houseNumber` or `resultType=street` result item, returns the nearby intersections in `/revgeocode` endpoint. The feature is released as **BETA**.
**Reverse Geocode**: Feature maturity of `bearing` parameter is promoted to **STABLE**.
**Geocode, Lookup**: Micro Point Address (MPA) support in Australia, Canada, New Zealand, USA, and Puerto Rico is promoted from **ALPHA** to **STABLE**.
#### Release 7.122
**Geocode, Lookup, Reverse Geocode, Multi-Reverse Geocode**
Request parameter `showNavAttributes=functionalClass` for `resultType=houseNumber` or `resultType=street` result item, returns the value that describes the functional class of the road where the result access position is located.
Request parameter `showNavAttributes=access` for `resultType=houseNumber` or `resultType=street` result item, returns the values that describe the allowed vehicle types of the road where the result access position is located.
Request parameter `showNavAttributes=physical` for `resultType=houseNumber` or `resultType=street` result item, returns the values that describe the special physical
**Geocode, Reverse Geocode, Multi-Reverse Geocode, Lookup**: Request parameter `showMapReferences=adminIds` returns the identifier of each administrative level in the `address` block for the result item, formatted according to the Here Map Content specification.
Request parameter `showMapREferences=cmVersion` returns the core map version number of the region where the result item is located.
**Reverse Geocode**: Feature maturity for returning unnamed streets in Reverse Geocode (parameter `with=unnamedStreets`) is promoted to **STABLE**.
### Release 7.119
**Geocode, Lookup, Autocomplete, Reverse Geocode, Multi-Reverse Geocode**
HERE Geocoding and Search API v7 response for these endpoints may now include additional flag: `estimatedPointAddress` - if true, it indicates that the coordinates of 'position' and 'access' points of the Point Address are estimated. This field is visible only for result items with `resultType` 'houseNumber' and `houseNumberType` 'PA' and only when the value is 'true'.
characteristics of the road where the result access position is located.
### Release 7.118
Parameter `showMapReferences` is released, which returns the references to a network link, segment, point address of the location object, to enable cross referencing into other services or data applications.
Note
The previous parameter `show=hmcReference` is deprecated and replaced by `showMapReferences=segments` which serves the same purpose.
`showMapReference=links` is released as alpha feature.
`links.linkId` is deprecated, it is renamed to `links.cmId`.
`links.sideOfLink` is deprecated, it is renamed to `links.side`.
For more details, see the [API reference](/docs/).
### Release 7.114
**Autocomplete**: `postalCodeMode=cityLookup` is promoted from **ALPHA** to **STABLE**.
### Release 7.113
**Geocode, Lookup**: Micro Point Address (MPA) support in Australia, New Zealand, and USA as **RESTRICTED ALPHA**.
**Multi-Reverse Geocode**: Multi-Reverse Geocode is released as **STABLE**.
### Release 7.104
New parameter `with=unnamedStreets` released as alpha feature. With this parameter, nearby unnamed streets are considered in the response. By default, Reverse Geocode suppresses streets for which the map does not provide a name. This is a parameter name change. The feature has been available with alpha status before. The previous parameter `includeUnnamedStreet=true` is deprecated and will not be supported anymore by end of August 2023. |
### Release 7.102
**Autocomplete**: `postalCodeMode=cityLookup` released as **ALPHA**.