This section provides information about compatibility between Places (Search) API versions and how changes affect your applications.
Implementation of minor API updates and bug fixes never breaks compatibility with existing applications. Releases of major updates that significantly change API behavior use a different URL.
The following request interface changes are considered backwards-compatible:
- Adding new endpoints
- Adding new optional parameters
- Adding new enumeration values
- Changing a parameter from mandatory to optional
- Softening a parameter constraint
In various areas, future releases of the Places (Search) API silently extend the volume and types of information provided. This ensures applications are able to handle unknown elements and enumeration values while parsing a response (see Prepare for Extensibility).