Deprecation and Change Notice
Note
Following features are deprecated or include breaking changes. The changes will be effective not earlier than 180 days after publication of a notice on this page.
Alternative property values
Note
- Stage 1 - Effective starting January 2026 - release '7.34.0'.
- Stage 2 - Effective starting TBD - not defined yet.
Current behavior
The service currently supports a variety of alternative property keys for selecting individual properties. However, these alternatives are now deprecated and will be removed in two stages.
Developers are encouraged to use the updated keys to ensure compatibility and avoid issues with deprecated properties.
New behavior
Only the leaf nodes of the JSON structure, along with their actual property keys returned by the Geocoding and Search V7 API, will continue to be supported. Alternative keys and object mappings will be removed and will no longer match future result selections.
For a complete list of valid property keys, refer to the following:
Motivation
Provide clear and consistent guidance for developers across the HERE documentation. Ensure alignment with the Geocoding and Search v7 API and its response model to minimize potential misunderstandings or confusion.
Implemented Changes
Alternative property values - Stage 1
Note
Effective starting January 2026 - release '7.34.0'.
Details see summary above.
Update job lifecycle and stop behavior
Note
Effective starting September 2025
Current behavior
Customers can stop and start a job during processing. When a job is stopped, downloading results or error reports is not possible.
New behavior
Customers can stop a job during processing with the following outcomes depending on the job state:
- Queued jobs (queued state) move back to submitted and are removed from the queue.
- Jobs in progress (pending or inProgress state) stop processing. The available results and error report are collected and made available for download. Once a job’s output is collected and ready for download, the job cannot be restarted. Customers must submit a new job with the remaining input records to process any unprocessed data.
Note Only processed records are billed.
If a job is deleted during processing, billing applies to all records processed up to that point.
Motivation
Previously, customers could not stop a job and download partial results or error reports. If errors appeared in the counters, customers had to wait for the job to complete before analyzing the errors, which resulted in all records being billed, even when the job was known to be problematic.
With this change, customers can stop a job early, review errors, and submit a corrected job without processing every record. Billing only applies to processed records.
Additionally, customers can return a queued job to submitted if they need to prioritize a different, later-submitted job. The first job can be re-queued later by calling the start endpoint.
Delete jobs
Note
Effective starting September 2024 Implemented version: 1.13.0
Current behavior
DELETE /jobs deletes all jobs of the current user.
New behavior
DELETE /jobs will require the status parameter. This does not have a default anymore and an error is returned if it's missing.
All Jobs can still be deleted using the status=any query parameter.
Motivation
This endpoint is error-prone for accidentally deleting all Jobs, if a jobId is missed or the related variable is empty . With this change nothing is deleted, but an error is returned. The feature to delete all Jobs is still possible by intentionally adding a query parameter.
Updated this month