Open APIs

Geocoding and reverse geocoding for Norwegian addresses and points of interest.

Geocoding and reverse geocoding for Norwegian addresses and points of interest. A new v3 API is available. See the [v1/v2 to v3 migration guide](https://beta.developer.entur.no/docs/open-services/geocoder/migration-v2-v3) for how the parameters and response format map.

Calculates distances between Stop Places

The Stop Place Register provides access to public transportation infrastructure data across Norway, including stop places, quays, parkings, and related NeTEx entities. This API enables developers to query stop place information with details on location, accessibility features, transport modes, fare zones, and hierarchical relationships. Ideal for journey planning applications, transportation analysis, mobility services, and public transit integrations.

API for checking the status of timetable data imports. The endpoint returns the date of the latest successful import of timetable data into Entur's systems for each data provider. Data providers are identified by their [codespaces](https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/637370434/List+of+current+Codespaces) This import date is also displayed in the list of NeTEx files available on Entur Open Data Portal. Additionally, the import date is stored in each NeTEx archive available on this page, in the "created" timestamp of the CompositeFrame. For example: created="2019-05-29T12:59:32.202" The date returned by this service is the original import date, i.e. the date Entur received the source dataset from the data provider. It may be different from the creation date of the archives listed on open data page, since these archives are regenerated every day through a filtering process that removes obsolete data. ## Authentication This API is open under NLOD licence, however, it is required that all consumers identify themselves by using the header ET-Client-Name. Entur will deploy strict rate-limiting policies on API-consumers who do not identify with a header and reserves the right to block unidentified consumers. The structure of ET-Client-Name should be: "company-application" *Header examples:* - "brakar-journeyplanner" - "fosen_utvikling-departureboard" - "nor_way_bussekspress-nwy-app"

This API is the core service for journey planning and uses OpenTripPlanner software to provide departure boards for individual stops, and point-to-point journey planning for all public transport in Norway, including real-time information, regardless of transport mode, or operator. All data is presented as a Transmodel-based GraphQL-API.

The Mobility API is an aggregation service for shared mobility data in Norway. It provides access to real-time information about shared bikes, e-scooters, and other mobility services from multiple operators across Norwegian cities.

The Vehicle Positions API is a GraphQL service that provides real-time positions and status for public transport vehicles across Norway. It enables fetching and streaming live vehicle data including location, delays, occupancy, and journey information.