Autocomplete
Autocomplete search
Search for places by text query
query Parameters
qSearch query. Optional when at least one filter (e.g. layers, stopPlaceTypes, fareZones) is given; the response then lists every place matching the filters (e.g. every airport, or every stop place in a fare zone).
latFocus point latitude. When provided with lon, results near this point are boosted.
lonFocus point longitude. Must be provided together with lat.
radiusFocus radius in kilometres (decimals accepted). Results within this distance from the focus point receive the strongest boost.
weightFocus weight: how strongly to prefer results near the focus point. 0 = no preference, 1 = maximum preference.
bbox^\s*-?\d+(\.\d+)?(\s… · style: form · explode: trueRestrict results to a bounding box: minLon,minLat,maxLon,maxLat. Unlike the focus point (a soft bias), this is a hard filter.
limitMaximum number of results
langLanguage code for result names
layersLayer filter. See stopPlaceTypes for how the two compose.
stopPlaceTypesSelect stop places of these NeTEx types. Without layers, returns only these stop places and excludes other layers. With layers, constrains the stopPlace layer while other requested layers are returned additively (e.g. layers=stopPlace,groupOfStopPlaces&stopPlaceTypes=railStation returns rail stations plus groups). Ignored when layers is set but omits stopPlace.
sourcesData source filter
countriesISO 3166-1 alpha-2 country code filter
countiesCounty IDs filter
localitiesLocality IDs filter
fareZonesFare zone IDs filter. Refs must be FareZone-shaped (e.g. RUT:FareZone:1); legacy TariffZone refs are not supported.
fareZoneAuthoritiesFare zone authorities filter
multimodalMultimodal stop place filter. Standalone (monomodal) stop places always appear; this only decides whether multimodal parents, children, or both appear alongside them: parent (default) hides multimodal children, child hides multimodal parents, all shows both
Headers
ET-Client-NameEntur Client Header.
It is required that all consumers identify themselves by using this header.
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> for companies, and <personal name>-<application> for individuals.
X-Correlation-IdCorrelation id