Backwards compatibility
All minor HERE Geocoding and Search updates and bug fixes are implemented to preserve compatibility with existing applications. Major updates that significantly change the API behavior are released on a different URL.
Backwards compatible changes
The following request interface changes are considered backward compatible:
- Adding new endpoints
- Adding new optional parameters
- Adding new enumeration values
- Changing a parameter from mandatory to optional
- Softening a parameter constraint
The following changes in response structures are considered backward compatible:
- Adding new response elements
- Adding new enumeration values without changing the semantic of previous ones
- Switching from mandatory to optional for an element but still ensuring that the element will be populated for existing requests
- Adding new error subtypes
- Hardening constraint for an response element value