Fare Classes

The Distribusion Retailer API also provides full parity on carrier fare class offerings.

Types of Fares

A fare class can describe both the class of travel such as the type of seat or compartment (e.g. standard or first class, seat or bed), as well as the journey type (single, fixed return, open return) that is on offer.

Examples

Carrier 1: A European Airport Transfer Carrier

• FARE-1 = Standard Class Single
• FARE-2 = Standard Class Open Return
• FARE-3 = First Class Single
• FARE-4 = First Class Open Return

Carrier 2: A Brazilian Intercity Carrier

• FARE-1 = Convencional (standard)
• FARE-2 = Leito (bed)
• FARE-3 = Double Decker - Convencional
• FARE-4 = Double Decker - Leito

Endpoints

Fare classes are provided and detailed in two endpoints:

• /marketing_carriers/{marketing_carrier_id}: The response includes all fare classes that the requested marketing carrier supports. Not every fare class supported by a carrier is necessarily available for every trip served by that carrier.
• /connections/find: The response includes the available fare classes for the selected trip(s) and their respective prices. In case only one fare class is available for a specific trip, only one fare class will be provided.

Fare Characteristics

Each fare class has its own code (as shown in the examples above) and is defined by the following parameters in the API:

• name: As defined by the carrier and which can be displayed to the user
• journey_type: Single vs. return types (more details)
• fare_features: Amenities & cancellation policies (more details)
• passenger_group_rules: Limit to the number of passengers per type that can be booked
• ticket_validity_rules : When a ticket for this fare class is valid for one fixed trip or a longer period of time

Fare Names

It is important to display the official fare class names to users exactly as they are provided in the API response. The names are defined directly by the carriers and often contain specific details about the travel class (e.g., standard, first class), seat type (e.g., seat, bed), or journey type (e.g., open return), which helps users distinguish between different options.

The API provides these names in the name attribute of the fare class object. We recommend using this field for display without altering or hiding the information. Carriers often require their official fare names to be shown, many of which are in the local language to ensure clarity for the end customer.