Implementation

Airports Source

Endpoint or API for origins and destinations that will appear in the dropdown in the Flight Search Panel

*This section is usually reviewed and completed by: Web Product Owner and/or Technical Liaison of airline’s website Flight Search Panel

The Airports Source, or Origin and Destination (O&D) arrays, provide the list of valid airports to populate the “From” and “To” fields within the flight search panel.

The preferred method is for PROS to generate the O&D lists using the route list that is used in the system, as this method is the fastest and gives customers the power to control. However, we offer two more options. The second option is to generate the O&D lists based on the data coming in from FareNet, and the third option is available if you would like to provide this information as a web service or API.

Preferred Method: Route List

The preferred method is for PROS to generate the O&D lists for the flight search panel within airTRFX by using the route list that is used in the system. This method gives customers the power to control the locations displayed and allows for a more efficient delivery timeline.

Secondary Method: FareNet

This method for generating the O&D lists for the flight search panel within airTRFX consists of dynamically generating these lists based on valid routes searched within the customer’s internet booking engine (IBE). Through this method, PROS can verify the routes to ensure only destinations that are available for certain origins are displayed, improving the UX (if this is not already available in the customer’s search panel). With frequent updates, seasonal routes will automatically be added as they are available in the customer’s IBE, and removed as they are no longer searched.

Third Method: API Integration

This method is available if you would like to provide route information through a web service or API.

Considerations for option three

Languages

The list of Origins and Destinations are typically saved by language. Sometimes an airline has different data by market, in the same language. We need to be clear from the beginning how many languages will be covered and what will be the market by default for each language.

Source

The customer must provide a source to access the list of valid Origins and Destinations. Usually, the customer provides an API or endpoint to get the information. When they do not have a specific endpoint, we can use route combinations collected from FareNet or airTRFX to dynamically generate the routes available, and the Core Dictionary for the location information that will be displayed.

Authorization

Usually, some type of authorization is needed to access the data. Some airlines use a token while others prefer to whitelist the PROS IPs. If authorization is required, we will need the Customer to provide an authorization token or key, or the means by which to generate this.

Route Validation

Some airlines use the same list for Origins and Destinations, but many others load Destinations depending on the Origin selected.

Data Documentation

It is important to have the description of the data received. A detailed breakdown of the schema is helpful in interpreting the variables provided.

Display Format

The content displayed to end users is usually a combination of several fields, so PROS needs to understand how the information should be displayed.

Implementation Sections:

Welcome Page

FareNet
Implementation

Flight Search Panel

Airports Source

Deeplinks

Design System

Hosting

Business Insights Surveys