Places (Search) API Developer's Guide

Gzip Compression

Responses provided by the Places (Search) API can optionally be compressed in the gzip format. Developers are strongly encouraged to make use of this option, as it can have a major positive impact on the responsiveness and performance of the client application by significantly reducing the response size.

Applications can request a gzip-compressed response in two ways. Applications can either set the standard Accept-Encoding header or set the x-accept-encoding header. If x-accept-encoding is set, it overides Accept-Encoding; the syntax and content of both variants are the same. They both conform to the standard accept-encoding header specification as set by the IETF.

Header name Header value
Accept-Encoding gzip
x-accept-encoding gzip
Note: When the response is gzip compressed, the Content-Encoding response header is sent with a value of gzip.

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