Geo Coordinate Search
The Geo Coordinate Search functionality is not supported by all carriers. To check if your preferred carriers are on the list, please reach out to your Partnership Manager.
The /connections/find endpoint allows users to search for available connections based on departure and arrival locations. The search can be performed also using geo coordinates which enables searching based on latitude and longitude with a defined radius.
The geo coordinate search can be useful in 2 cases:
- Your users have their exact location defined as part of the search flow e.g. they search using a hotel or an exact address as reference.
- You don't want to map stations between Distribusion and your database, and instead want to use the stored latitude and longitude of your list of stations in each search request.
We do not recommend the use geo coordinate search when searching by city, as the radius supported by this functionality is limited to 2000 meters (2km) and cities can cover a much larger area. For example, if a user selects Paris as a departure city and you use the central point of Paris to initiate the geo coordinate search, most of the stations in Paris will not appear in the search results.
Examples
The search workflow allows you to search from geo coordinate point to geo coordinate point, but also to combine a geo coordinate for departure with an arrival station, for example in case a user is searching how to go from their hotel to an airport.
Coordinate to Coordinate
{
"locale": "en",
"currency": "EUR",
"search_bounds": [
{
"is_requested": true,
"departure_date": "2026-05-30",
"departure_start_time": "10:00",
"departure_location": {
"type": "geo",
"value": "51.471502,-0.488006",
"radius": 2000
},
"arrival_location": {
"type": "geo",
"value": "51.516653,-0.176815",
"radius": 1000
}
}
],
"passengers": [
{
"pax": 1,
"max_age": 33
}
]
}
Coordinate to Station
{
"locale": "en",
"currency": "EUR",
"search_bounds": [
{
"is_requested": true,
"departure_date": "2026-03-19",
"departure_start_time": "07:00",
"departure_end_time": "16:00",
"departure_location": {
"type": "geo",
"value": "51.471502,-0.488006",
"radius": 2000
},
"arrival_location": {
"type": "stations",
"value": [
"GBLONLPB"
]
}
}
],
"passengers": [
{
"pax": 1,
"max_age": 40
}
],
"carrier_codes": [
"HEXR"
]
}
Parameters
departure[type] arrival[type] | Yes | Value should be set to |
departure[value] arrival[value] | Yes | Latitude and longitude coordinates (decimal degrees) representing the departure/arrival point. Format: {latitude},{longitude} with exactly 6 decimal places. |
departure[radius] arrival[radius] | Yes | Radius (in meters) around the departure/arrival location to search for stations. Max 2000 meters (2 km) and min 10 meters. |
Walking Steps
To get information about the walking distance and time from the specified geo coordinate to the station in the response add the parameter include=connections.steps.walking to the request.
In this case the API response will return a segments array and a new steps array. The segments array will continue to represent traditional segments, such as bus or train rides. The steps array, however, will include additional segments that represent intermediate walking distances, such as walking from the departure coordinate to the departure station or from the arrival station to the final destination.
Let's look at this sample request:
{
"locale": "en",
"currency": "EUR",
"search_bounds": [
{
"is_requested": true,
"departure_date": "2025-07-31",
"departure_start_time": "09:00",
"departure_location": {
"type": "geo",
"value": "51.516783,-0.176895",
"radius": 2000
},
"arrival_location": {
"type": "geo",
"value": "51.472902,-0.488006",
"radius": 2000
}
}
],
"passengers": [
{
"pax": 1,
"max_age": 25
}
],
"carrier_codes": [
"HEXR"
],
"include": [
"connections.steps.walking"
]
}
Steps of a Connection
In the response, below the standard segments of a connection, you will find the walking segments represented as steps. The first step STEP-DEPARTURE-GBLONLHB corresponds to the walking distance from the arrival station to the final coordinate, while the second step STEP-ARRIVAL-GBLONLPB represents the walking distance from the initial coordinate to the departure station.
{
"attributes": {
"arrival_time": "2025-07-31T09:31",
"booked_out": false,
"cheapest_fare_class_code": "FARE-5",
"cheapest_total_adult_price": 2562,
"co2_kg": 2.1942505836486816,
"co2e_kg": 2.510593891143799,
"co2e_savings": 0.7929726243019104,
"departure_time": "2025-07-31T09:10",
"duration": 1272,
"electronic_ticket_available": false,
"leg_type": "outbound",
"offer_bundle": null,
"offer_id": null,
"total_seats_left": null
},
...
"steps": {
"data": [
{
"id": "STEP-DEPARTURE-GBLONLHB",
"type": "steps"
},
{
"id": "STEP-ARRIVAL-GBLONLPB",
"type": "steps"
}
]
}
},
"type": "connections"
}
},
Step Details
Each step is assigned a unique ID. Below are the basic attributes of a step:
travel_mode: Currently, only "WALKING" is supporteddistance: The total distance of the step in metersduration: The estimated walking time in secondsdeparture_location: Contains the location ID, which refers to latitude, longitude, and station ID for the starting pointarrival_location: Contains the location ID, which refers to latitude, longitude, and station ID for the ending point
Here is how the details of a step will be represented in the response related to the experience of the passenger from their starting point to the departure station GBLONLPB:
... {
"attributes": {
"distance": 156,
"duration": 120,
"travel_mode": "WALKING"
},
"id": "STEP-DEPARTURE-GBLONLHB",
"relationships": {
"arrival_location": {
"data": {
"id": "LOCATION-31bfd625769244",
"type": "locations"
}
},
"departure_location": {
"data": {
"id": "LOCATION-a8be18ad1236c6",
"type": "locations"
}
}
},
"type": "steps"
},
{
"attributes": {
"latitude": "51.516783",
"longitude": "-0.176895"
},
"id": "LOCATION-03e5ab6a38a641",
"relationships": {
"station": {
"data": null
}
},
"type": "locations"
},
{
"attributes": {
"latitude": "51.472902",
"longitude": "-0.488006"
},
"id": "LOCATION-31bfd625769244",
"relationships": {
"station": {
"data": null
}
},
"type": "locations"
},
{
"attributes": {
"latitude": "51.516653",
"longitude": "-0.176815"
},
"id": "LOCATION-496cdb5ce61776",
"relationships": {
"station": {
"data": {
"id": "GBLONLPB",
"type": "stations"
}
}
},
"type": "locations"
},
{
"attributes": {
"latitude": "51.47150211170094",
"longitude": "-0.48800687700041"
},
"id": "LOCATION-a8be18ad1236c6",
"relationships": {
"station": {
"data": {
"id": "GBLONLHB",
"type": "stations"
}
}
},
"type": "locations"
} ...
],
On this page
- Geo Coordinate Search