Places (Search) API Developer's Guide

Paginating Results

Typically, large collections of results from the Places (Search) API are paginated – divided into a list of pages – using hyperlinks to point to the previous page and the next page. These collections are wrapped in an object that provides details on both the pagination status and the items in the current page.

Depending on your use case, the available attribute may be present. This attribute holds the total number of items available for a place. However, the number of items in the available attribute depends on the number of results for the particular place and the use case criteria. For example, if you search for an airport, the API may return a response where the first page contains only results within a maximum distance. In this scenario, when you request for the next page, the API could return results with a larger maximum distance.

The following is an example of a paginated object:
{
  "available": 26,
  "next": "http://alphabet.com/page/3",
  "offset": 3,
  "items": ["d", "e", "f"]
}

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 selfservesupport@here.com.