April 2026 Platform Release Notes

HERE Documentation

The new documentation site has launched!

HERE has launched a new product documentation site at docs.here.com, featuring several updates that provide easier access to the technical product information you need to use HERE APIs, SDKs, and data.

From improved navigation and search to a conversational “Ask AI” interface, you can now enjoy a better, faster way to get the information you need for your projects.

HERE Workspace

Deprecation Notices

Action required – [Workspace] Pipeline Stream-6.1 runtime environment for stream pipelines deprecated on May 1, 2026

The Stream-6.1 run-time environment supporting Apache Flink 1.19.1 will be deprecated on May 1, 2026. The version of Apache Flink in the platform pipeline environment and the HERE Data SDK for Java & Scala has been upgraded to 2.2 (Stream-7.0).

Both Stream-6.1 (Apache Flink 1.19.1) and Stream-7.0 (Apache Flink 2.2) will be supported between May 1, 2026, and May 1, 2027, enabling you to migrate to Stream-7.0 before the deprecation end date.

As of May 1, 2026, new releases of the HERE Data SDK for Java/Scala will only support Flink 2.2, starting from the 2.85.5 release.

Existing stream pipelines using the Stream-6.1 run-time environment will continue to operate normally until May 1, 2027. However, note that the Stream-6.1 run-time environment will only receive security patches. Until you upgrade, you can use the HERE Data SDK for Java/Scala 2.84.4 or older to continue developing pipelines with the Stream-6.1 environment.

As of May 1, 2027, the Stream-6.1 run-time environment will be removed and pipelines using it will be canceled.

Migrate your stream pipelines to the new Stream-7.0 (Flink 2.2) run-time environment to benefit from the latest functionality and improvements.

For more details about migrating an existing stream pipeline to the new Stream-7.0 run-time environment, see the Migration Guide.

HERE Real Time Traffic

Improvements and Bug Fixes

Q1 2026 Map Update

• Improved arterial road closure coverage for Saudi Arabia.

• Enabled Road Alerts for Oceania Region.

• EU, MEA Expansion for Protobuf 3.4 Realtime Flow feeds.

• Improvement to Traffic predictions, with rush hour periods using predictions for heavier traffic levels.

• Improved incident processing logic for JARTIC Feeds in Japan.

• Implemented bi-directional incident and polyline encoding handling for Canada Region incident sources.

• Implemented Roadworks feeds for the German Autobahn.

• Implemented new incident provider for Quebec, Canda.

• Implemented improved highway closure logic to prevent false indications of highway closures.

Coming Soon

• Optimize Road Closure Events handling for JARTIC feeds.

• Improve Roadworks Feed handling for Western Australia Region.

• Improve Stoplight handling for various countries in EU and APAC regions.

HERE Map Content v2 / HERE SDKs / Map Rendering Services

Coming Soon

Arabian Gulf Name Change

Beginning in Q2 2026, the default name for the Arabian Gulf will be changed to the Persian Gulf. This change also affects the default international map view utilized by HERE SDK Navigate and Explore, HERE Maps API for JavaScript, Vector Tile API, Raster Tile API and Map Image API.

The Arabian Gulf name can be preserved by setting the politicalView parameter for any of the countries listed in the table below. For Türkiye, the politicalView parameter must be configured to retain the name of the Gulf of Basra. If the Arabian Gulf/Gulf of Basra name is desired, you must update your application logic accordingly.

These references explain how to set the political views for the affected countries:

• Android SDK

• Maps API for Javascript

• Vector Tile API

• Raster Tile API

• Map Image Developer Guide

HERE EV Charge Points API v3

Busy Hours Predictions (Alpha)

The new Busy Hours Predictions feature provides time‑based information on how busy a charge point location typically is during the day.

Predictions are available in 15‑minute intervals and use a normalized value between 0.0 and 1.0 to indicate overall usage levels at a location. The information complements real‑time availability and waiting time data, which remain available at the individual charger and connector group level, by adding context on recurring usage patterns.

The feature is being released as an Alpha, and further refinements may follow based on feedback.

Tracking Cloud

Removal of deprecated old APIs

The following Tracking APIs have been removed:

• Notifications v3

• C2C v4

• Bulk jobs v4

• Shipment emission reports v4

• Shipment plans v4

• Shipment score cards v4

Refer to HERE Tracking API documentation for information on currently supported Tracking APIs.