Description

This endpoint delivers all of Distribusion’s stations and provides the detailed information required for mapping these stations in your system. We recommend calling this API on a weekly basis to detect newly mapped stations and add them to your system.

Why onboarding of meta data is important?

In order for users to search for trips, the meta data related to marketing carriers and stations will need to be retrieved and stored locally, which can be achieved by making use of the dedicated /marketing_carriers/{marketing_carrier_id} and /stations, /cities, /areas endpoints.

Once the stations and marketing carriers have been onboarded, trips can be searched by using the /connections/find endpoint.

The Distribusion API enables you to search for trips on city, airport, and station level, flexibly catering to what the user chooses to input.

Station Codes

Distribusion standardises station and city data across the entire ground transportation industry, the same way in which IATA does in the flight industry.

Our station codes are designed to represent specific locations using a set of 8 capital letters that make it easy for you to identify and, where applicable, assign them to existing location entities within your own system.

The structure of our station codes follows a simple logic:

• The first two letters represent the country in which the station is located
• The next three represent the city in which the station is located
• The last three letters more precisely represent the location of the station

Example

GB (Great Britain) + LON (London) + VSA (Victoria station) = GBLONVSA

Station types

To facilitate the distribution of different modes of ground transportation, which are clearly marked within the station_type parameter for each station in the /stations endpoint, Distribusion supports four station types:

• Bus station: bus_station
• Train station: train_station
• Ferry station: ferry_station
• Tram station: tram_station

Get Started

To get started with the onboarding and mapping of Distribusion stations, make a request to /stations, which returns all the necessary data on stations including:

• Type
• Name
• Address
• Description
• Geo coordinates
• Time zone
• City
• Area, where applicable

Other Endpoints

In case you already know which marketing carriers are of interest to you, please refer to these additional endpoints:

• The /marketing_carriers/{marketing_carrier_id}/stations endpoint allows you to retrieve a list of all stations used by a specific marketing carrier.
• For even more precision, take a look at the /connected_stations endpoint, which shows you the stations that are connected as bookable trips. This endpoint is filterable by carrier code.

Note

As Distribusion continuously updates and extends its coverage of carriers, stations and routes, we recommend automatically checking for new stations at least twice per week.

More Info

• Full API integration
  • Basic workflow
• Key Concepts
  • Onboarding metadata
    • Station, city, and area codes
  • Currencies and locales
• Endpoints
  • GET /retailers/v4/stations

Description

This endpoint delivers data about specific stations.

Why onboarding of meta data is important?

In order for users to search for trips, the meta data related to marketing carriers and stations will need to be retrieved and stored locally, which can be achieved by making use of the dedicated /marketing_carriers/{marketing_carrier_id} and /stations, /cities, /areas endpoints.

Once the stations and marketing carriers have been onboarded, trips can be searched by using the /connections/find endpoint.

Station Codes

Distribusion standardises station and city data across the entire ground transportation industry, the same way in which IATA does in the flight industry.

Our station codes are designed to represent specific locations using a set of 8 capital letters that make it easy for you to identify and, where applicable, assign them to existing location entities within your own system.

The structure of our station codes follows a simple logic:

• The first two letters represent the country in which the station is located
• The next three represent the city in which the station is located
• The last three letters more precisely represent the location of the station

Example

GB (Great Britain) + LON (London) + VSA (Victoria station) = GBLONVSA

Station types

To facilitate the distribution of different modes of ground transportation, which are clearly marked within the station_type parameter for each station in the /stations endpoint, Distribusion supports four station types:

• Bus station: bus_station
• Train station: train_station
• Ferry station: ferry_station
• Tram station: tram_station

Get Started

To get started with the onboarding and mapping of Distribusion stations, make a request to /stations, which returns all the necessary data on stations including:

• Type
• Name
• Address
• Description
• Geo coordinates
• Time zone
• City
• Area, where applicable

Other Endpoints

In case you already know which marketing carriers are of interest to you, please refer to these additional endpoints:

• The /marketing_carriers/{marketing_carrier_id}/stations endpoint allows you to retrieve a list of all stations used by a specific marketing carrier.
• For even more precision, take a look at the /connected_stations endpoint, which shows you the stations that are connected as bookable trips. This endpoint is filterable by carrier code.

Note

As Distribusion continuously updates and extends its coverage of carriers, stations and routes, we recommend automatically checking for new stations at least twice per week.

More Info

• Full API integration
  • Basic workflow
• Key Concepts
  • Onboarding metadata
    • Station, city, and area codes
  • Currencies and locales
• Endpoints
  • GET /retailers/v4/stations

Description

This endpoint can be used to retrieve all station pairs that are available in Distribusion’s database as bookable origin-destination combinations.

Requests to this endpoint can be filtered to identify connected station pairs for one or multiple marketing carriers.

Why onboarding of meta data is important?

In order for users to search for trips, the meta data related to marketing carriers and stations will need to be retrieved and stored locally, which can be achieved by making use of the dedicated /marketing_carriers/{marketing_carrier_id} and /stations, /cities, /areas endpoints.

Once the stations and marketing carriers have been onboarded, trips can be searched by using the /connections/find endpoint.

The Distribusion API enables you to search for trips on city, airport, and station level, flexibly catering to what the user chooses to input.

Pagination

The pagination parameters can be used for scrolling when there are more than 10,000 results. The parameters support forward (page[after]) scrolling. This requires the request to be split into two or more requests.

If a response is over 10,000 results long, it includes a links.next parameter, which specifies the link that should be inserted in page[after] for the subsequent request to proceed to the next page.

Station Codes

Distribusion standardises station and city data across the entire ground transportation industry, the same way in which IATA does in the flight industry.

Our station codes are designed to represent specific locations using a set of 8 capital letters that make it easy for you to identify and, where applicable, assign them to existing location entities within your own system.

The structure of our station codes follows a simple logic:

• The first two letters represent the country in which the station is located
• The next three represent the city in which the station is located
• The last three letters more precisely represent the location of the station

Example

GB (Great Britain) + LON (London) + VSA (Victoria station) = GBLONVSA

Other Endpoints

In case you already know which marketing carriers are of interest to you, please refer to the /marketing_carriers/{marketing_carrier_id}/stations endpoint allows you to retrieve a list of all stations used by a specific marketing carrier.

Note

As Distribusion continuously updates and extends its coverage of carriers, stations and routes, we recommend automatically checking for new stations at least twice per week.

More Info

• Full API integration

  • Basic workflow

• Key Concepts

  • Onboarding metadata
    • Station, city, and area codes
  • Currencies and locales

• Endpoints

  • GET /retailers/v4/connected_stations

Description

This endpoint delivers all of Distribusion’s areas and provides the detailed information required for mapping these areas in your system. We recommend calling this API on a weekly basis to detect newly mapped areas and add them to your system.

Why onboarding of meta data is important?

In order for users to search for trips, the meta data related to marketing carriers and stations will need to be retrieved and stored locally, which can be achieved by making use of the dedicated /marketing_carriers/{marketing_carrier_id} and /stations, /cities, /areas endpoints.

Once the stations and marketing carriers have been onboarded, trips can be searched by using the /connections/find endpoint.

The Distribusion API enables you to search for trips on city, airport, and station level, flexibly catering to what the user chooses to input.

Area Codes

Besides grouping stations by cities and countries, Distribusion also provides an area grouping that unites all the stations that belong to the same airport.

Each area consists of a 7-letter-code, following this logic:

• The first two letters represent the country in which the airport is located
• The next three represent the city in which the airport is located
• The last two letters more precisely represent the location of the airport

Example

• Area
  • London Heathrow Airport (GBLONLA)
• Stations belonging to this area
  • London Heathrow Airport Terminal 3 (GBLONAHT)
  • London Heathrow Airport Terminal 4 (GBLONHAI)
  • London Heathrow Airport Terminal 5 (GBLONHAR)

Note

As Distribusion continuously updates and extends its coverage of carriers, stations and routes, we recommend automatically checking for new stations at least twice per week.

More Info

• Full API integration

  • Basic workflow

• Key Concepts

  • Onboarding metadata
    • Station, city, and area codes
  • Currencies and locales

• Endpoints

  • GET /retailers/v4/areas

Description

This endpoint delivers all of Distribusion’s cities and provides the detailed information required for mapping these cities in your system. We recommend calling this API on a weekly basis to detect newly mapped cities and add them to your system.

Why onboarding of meta data is important?

In order for users to search for trips, the meta data related to marketing carriers and stations will need to be retrieved and stored locally, which can be achieved by making use of the dedicated /marketing_carriers/{marketing_carrier_id} and /stations, /cities, /areas endpoints.

Once the stations and marketing carriers have been onboarded, trips can be searched by using the /connections/find endpoint.

The Distribusion API enables you to search for trips on city, airport, and station level, flexibly catering to what the user chooses to input.

City Codes

Distribusion also provides harmonised location codes at city level that unite all stations within a certain city.

City codes consist of 5 letters according to the following logic:

• The first two letters represent the country in which the city is located
• The next three represent the city code

Example

• City
  • London (GBLON)
• Stations belonging to this area:
  • London Victoria Coach Station(GBLONVSA)
  • London Park Inn Heathrow (GBLONPIH)
  • London Lewisham (GBLONLEW)

Note

As Distribusion continuously updates and extends its coverage of carriers, stations and routes, we recommend automatically checking for new stations at least twice per week.

More Info

• Full API integration

  • Basic workflow

• Key Concepts

  • Onboarding metadata
    • Station, city, and area codes
  • Currencies and locales

• Endpoints

  • GET /retailers/v4/cities