HERE Route Matching API v8 Changelog

Loading changelog...

Date	Change Type	Description
2026-06-23	Fixed	Fixed HTTP status for HTTP POST requests with unsuppported types in the `Content-Type` request header. The service will return an error of 415 "Unsupported Media Type" instead of 400 "Bad Request".
2026-04-17	Added	Added `CHAIN_ID` and `URL` attributes to the `TRUCK_PARKING_POI` layer.
2026-04-17	Deprecated	Attributes `REFERENCE_POST`, `EXIT_NAME`, `HEADING`, `ORDER8` and `ORDER1` in the `TRUCK_PARKING_POI` layer are deprecated.
2026-04-17	Changed	Changed the source of the `TRUCK_PARKING_POI` layer from `DoT` to `HERE Map Data`. The `TRUCK_PARKING_POI_STATUS` layer returns POIs from Truck Parking Club in addition to DoT POIs. Attributes `LAST_UPDATED_TIMESTAMP`, `TRUCK_PARKING_AVAILABLE_TREND`, and `OPEN` in `TRUCK_PARKING_POI_STATUS` layer can now contain a `null` value as `Truck Parking Club` doesn't provide these attributes.
2026-04-17	Added	Added a new speed limit type `Speed limiter` in the `SPEED_LIMIT_TYPE` attribute of the `TRUCK_SPEED_LIMITS_FCn` layer. The `SPEED_LIMIT_TYPE` attribute takes the following values: `1` for administrative regulations, `2` for special speed situations, or `3` for `Speed limiter`.
2026-04-17	Added	Added the `POI_ID` attribute to uniquely identify the published POIs.
2026-04-17	Removed	The `SOURCE_ID` attribute in the `TRUCK_PARKING_POI` and `TRUCK_PARKING_POI_STATUS` layers is set to `null`.
2026-04-01	Added	Added a new parameter `pathCoordinates`. When added to a request, a `pathCoordinates` array is added to the response. The array contains sets of coordinates that allow to reconstruct the journey in HERE Routing API v8.
2026-03-26	Changed	Requests for the `APPLICABLE_SPEED_LIMIT` layer specified as attribute take the `vehicleWeightClass` parameter into account
2026-02-17	Fixed	Fixed an issue where the Driving Report returned an incorrect speed limit information for non‑commercial vehicles.
2025-12-17	Deprecated	The HERE Road Roughness content product is being discontinued. As a result, support for the Road Roughness layers `ROAD_ROUGHNESS_FCn` in the Map Attributes API will also end. The final content update will be delivered at the end of Q2 2026, and the layer will be removed by the end of 2026.
2025-12-17	Deprecated	The HERE Cellular Signal content product is entering maintenance mode. The Cellular Signal layers `CELL_SIGNALS_FCn` in the Map Attributes API are also entering maintenance mode. Content updates will cease starting Q1'26, and the layer will be removed by the end of 2026.
2025-11-11	Changed	The `TRUCK_SPEED_LIMITS_FCn` layer is now created from HERE Commercial Vehicle Regulations which results in improved coverage and accuracy.
2025-10-07	Changed	The `ENV_BADGE` attribute in the `ENV_ZONE_RESTR` layer is changed to return zone access information in addition to the environmental badge information.
2025-10-07	Added	Added more vehilce-related attributes to to the `ENV_ZONE_RESTR` layer. The layer now supports `DATE_TIMES` of type `Z`. All layers with the `DATE_TIMES` attribute now support `DATE_TIMES` of type `Z`.
2025-09-18	Changed	JSON responses for the Map Attribute layers `TRUCK_RESTR_FCn` and `SPEED_LIMITS_FCn` now exclude empty (NULL) fields.
2025-05-21	Changed	Announcement - starting December 2025, HERE Route Matching API v8 will no longer support GET requests with HTTP request lines longer than 8000 characters. To ensure that your solution remains fully functional, use POST requests or limit the line length to 8000 characters or less. To learn how to send the request with POST, see the POST request example in How to match GPS traces to the most probable route.
2025-05-21	Fixed	Requests for toll costs data that use ZWG (Zimbabwe Gold) for currency don't fail. Responses now have a category `1025` warning that indicates that the currency isn't supported for toll cost calculation yet. Full support for ZWG is on the roadmap.
2025-02-25	Fixed	The format of ADAS fields in the HERE Route Matching API v8 API response match the format used in HERE Map Attributes API v8. Square brackets and spaces between values are removed from the Route Matching API v8 responses. The `REFNODE_LINKCURVHEADS` and `NREFNODE_LINKCURVHEADS` fields now have relative link IDs instead of exact link IDs. * The `HEADINGS` field values in the Route Matching API are no longer divided by 10^3. Both APIs now have the same `HEADINGS` result.