Extensible API Contract

The API contract with client applications allows for extensibility. In general, clients can rely on the fact that anything that is documented will remain valid at least within the major version of the API to which the documentation applies. Anything that is not documented may change at any time.

Clients should be prepared to find new elements (content and features) in new releases of the API. Developers are free either to ignore the new elements or – if the new elements are documented – use them by applying generic patterns, without adverse impact on existing applications.

Developers should not be surprised to find undocumented elements in our responses. The Places API offers feature parity to all users of the API; so even experimental features that we initially develop with certain pilot API users will be visible from the start. But we will only add them to the public documentation once the new feature has fully matured and proven to add value for our users. We may change the implementation of such features at any time, or even decide to remove them from a future release. So unless you know what you are doing (and how to manage potential changes), it is best to wait to use the new features until they are publicly documented.