HERE Geofencing API v8 - Changelog
Loading changelog...
| Date | Change Type | Description |
|---|---|---|
| 2026-11-06 | Deprecated | What changed: HERE services are transitioning to TLS certificates issued under the GlobalSign Root R46 certificate hierarchy. Support for certificate validation through the older GlobalSign Root R3 hierarchy will end when the GlobalSign Root R3 certificate expires on March 18, 2029. Why it matters: To maintain compatibility with older platforms, HERE currently provides a temporary cross-signed certificate path that allows clients to validate HERE service certificates through the GlobalSign Root R3 hierarchy. This compatibility path will no longer be available after March 18, 2029. After that date, clients must trust the GlobalSign Root R46 hierarchy to successfully establish TLS connections to HERE services. Who it matters to: Applications, devices, and environments that use custom or outdated trust stores and do not already trust GlobalSign Root R46. Most modern operating systems, browsers, and TLS libraries receive regular trust store updates and already trust the R46 hierarchy. Required action: Review all trust stores used by your applications and infrastructure, including development, testing, staging, non-production, and production environments. Verify that GlobalSign Root R46 is present and trusted, and update any systems that rely solely on the older GlobalSign Root R3 hierarchy. For more information, see this knowledge base article: Client Connections May Fail Due to Missing GlobalSign R46 Trust Store Support. (A HERE account is required to view this article. If you do not have a HERE account you can sign up for free.) Failure to add GlobalSign Root R46 before March 18, 2029 may cause TLS certificate validation to fail, preventing clients from connecting to HERE services. |
| 2026-09-29 | Changed | The Country field in the Geocode layer view of the Admin GUI is replaced with two fields: Country Code and Country Name. |
| 2026-06-23 | Fixed | Fixed HTTP status for HTTP POST requests with unsupported 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 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. |
| 2025-11-11 | Added | Added support for API key-based authentication in self-hosted environments. |
| 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 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-06-25 | Fixed | The END_OFFSET value of the last link of a topology now has a value of 100000 to align with other offset values that are multiplied by the factor of 100000. |
| 2025-05-21 | Changed | Announcement - starting December 2025, HERE Geofencing 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 check if the asset's position is inside a geofence. |
| 2025-02-25 | Added | Added originalLat and originalLon fields to the geofence GET/POST response. assetId parameter added to the geofence GET/POST request and response. |
Updated 11 days ago
Did this page help you?