HSL Journey Planner API

[The Journey Planner](https://www.hsl.fi/)) APIs offer data regarding routing, geocoding, map data and vehicle locations through several APIs. - Routing API: Itinerary- and timetable-queries via either a [GraphQL-API](http://graphql.org/) or a [REST](https://en.wikipedia.org/wiki/Representational_state_transfer) interface - Geocoding API: [Pelias](http://pelias.io/) [REST](https://en.wikipedia.org/wiki/Representational_state_transfer) interface - Map API: HSL's background map as a [TMS-service](https://wiki.osgeo.org/wiki/Tile_Map_Service_Specification) (Tile Map Service) and a number of public transport related points of interest (eg. ticket vending points, city bike stations & park and ride sites) as [Mapbox vectortile](https://www.mapbox.com/vector-tiles/specification/) services. - Realtime API: [GTFS-RT](https://developers.google.com/transit/gtfs-realtime/) & [MQTT](http://mqtt.org/) feeds The use of the Digitransit production APIs requires registration and use of API keys. [More information and instructions for obtaining the API key](https://digitransit.fi/en/developers/api-registration/). Further information: [digitransit.fi](https://digitransit.fi/en/) The public transport network data is updated daily from HSL's public transport register to the journey planner APIs. The OpenStreetMap data is also updated daily to the journey planner for routing graph, geocoding and background map purposes. Due to different cache-settings, the changes in the background map become visible to the users in about one week's time. ##Public transport network & timetables (GTFS) Data from HSL's public transport register is derived into GTFS-format every day. This data collection includes all routes that have a valid timetable. The collection includes data three months onwards from the moment the collection was generated. ##Traffic bulletins Information about cancelled services is available the Journey Planner APIs mentioned above. For example, routing API's disruption-info & realtime API's service-alerts.