GuidesAPI Reference
Guides
  1. Public Transit API Developer Guide v8
  2. Public Transit Next Departures API examples

How to send a request to the Public Transit Next Departures API

To send a request to the Public Transit Next Departures API v8, you need the basic elements shown in the following tables.

Discover public transit departures by means of the following query parameters:

  • ids: station identifier(s)
  • in: station geographic location
  • name and in: station name and geographic location

Request by ID

ids: list of station identifiers, which are retrievable via Public Transit Station Search API v8.

Table 1. Required request parameters to query departures by IDs

NameFormatDescription
Base URLstring, https://transit.hereapi.comProduction environment
Versionstring, /v8The API version to use
Resourcestring, /departuresThe endpoint to access the resource
idsstring, id1,...Specifies a comma-separated list of station ids

For more information, see how to Search Next Departures By Ids.

Request by location

in: circle area defined using center point and radius parameters.

Table 2. Required request parameters to query departures by location

NameFormatDescription
Base URLstring, https://transit.hereapi.comProduction environment
Versionstring, /v8The API version to use
Resourcestring, /departuresThe endpoint to access the resource
instring, {lat},{lng}[;r={radius}]Specifies the center point and the optional radius of the search

For more information, see how to Search Next Departures By Location.

Notes

The response to the above request delivers the following high-level elements:

  • metadata – a notices (optional) object with a list of issues related to the response
  • response - a boards object with a list of stations, one for each specified id or in a defined circular area.

For more information on the request parameters, see the Public Transit Next Departures API v8 section of the Public Transit API Reference

Updated 14 days ago