Journey Types

Distribusion allows you to sell tickets for single and return journeys.

Bounds

A bound represents a single, directional leg of a journey. It defines the specific movement from an origin to a destination. In the API, bounds are submitted to the /connections/find request via the search_bounds array in the request.

The composition of bounds determines the nature of the journey:

• Single Journey: Consists of exactly one bound (the outbound leg).
• Return Journey: Consists of two bounds (the outbound leg followed by the inbound leg).
• Multi Journey: Consists of more bounds to create a multi stop trip. This is not supported yet.
• Open-Jaw: Consists of multiple bounds that depart and/or arrive from different stations. This is not supported yet.

Bound Ordering

When requesting return trips with /connections/find, the order of bounds in the array is strict:

• search_bounds[0]: Represents the outbound leg (Departure → Destination).
• search_bounds[1]: Represents the inbound leg (Destination → Departure).

Types

There are three distinct journey types available. These types are displayed under the field journey_type in the response from the /connections/find endpoint.

Journey types are defined per fare class. Please find additional details in our Fare Classes guide.

Virtual Returns

Even if a carrier does not support any explicit return journey types, Distribusion still allows return bookings to be placed within one user flow and request. Simply use a single journey fare class and specify a return date in the relevant API requests.

Fare Classes for Return Trips

When booking a return trip some carriers allow the fare class of the outbound to be different than the inbound trip. For more details check our Fares Per Segment guide.