Public Transit API Developer's Guide

Constructing a Request

A typical request to the Public Transit API includes the basic elements shown in the following table and, in addition, it may contain resource-specific query parameters or data.

Table 1. Basic Request Elements
Element Value/Example Description
Base URL Production environment CIT environment

For information about the available evironments, see HERE Server Environments.

Path /v3 Common path for all resources
Resource route, mroute, sectionupdate Transit Routing
branding/logos Logo Brands
board Next Nearby Departures
multiboard/by_geocoord, multiboard/by_stn_ids All Next Departures
stations/by_geocoord, stations/by_name, stations/by_ids Station Search
coverage/city, coverage/nearby, coverage/search Coverage Service
isochrone Transit Isoline
lines/by_stn_id Line Info
alerts/nearby Transit Alerts
Format Supported formats:
  • json
  • xml
If not specified in the request, the default response format is XML.
Application ID &app_id={YOUR_APP_ID} Substitute your own unique app_id
Application Code &app_code={YOUR_APP_CODE} Substitute your own unique app_code

Here is an example of a Station Search request, which uses the HTTP GET method:

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