Places (Search) API Developer's Guide


This section provides information about compatibility between Places (Search) API versions and how changes affect your applications.

Backwards Compatibility

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).

You cannot use this account to purchase a commercial plan on Developer Portal, as it is already associated to plans with different payment methods.

To purchase a commercial plan on Developer Portal, please register for or sign in with a different HERE Account.

Something took longer than expected.

The project should be available soon under your projects page.

Sorry, our services are not available in this region.

Something seems to have gone wrong. Please try again later.

We've detected that your account is set to Australian Dollars (AUD).
Unfortunately, we do not offer checkouts in AUD anymore.
You can continue using your current plan as normal, but to subscribe to one of our new plans,
please register for a new HERE account or contact us for billing questions on