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 EveryMundo to generate the O&D lists based on the data coming in from FareNet or airTRFX, as this reduces any dependency on the customer. However, a second option is available if the customer is able to provide this information as a web service or API.
The preferred method for generating the O&D lists for the flight search panel within airTRFX is to dynamically generate these lists based on valid routes searched within the customer’s internet booking engine (IBE). Through this method, EveryMundo 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.
Additionally, the customer is able to generate the O&D lists for the flight search panel within airTRFX by using the route list that is used in the system.
If the customer requires the Airports Service to exactly match the O&D list available on the customer’s core site, the customer can provide a valid web service or API. The airport information is saved within the EveryMundo Platform and made available to airTRFX through our standard airport endpoint. This option is only available to customers with clear documentation, which includes each of the elements below:
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.
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.
Usually, some type of authorization is needed to access the data. Some airlines use a token while others prefer to whitelist the EveryMundo 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.
Some airlines use the same list for Origins and Destinations, but many others load Destinations depending on the Origin selected.
It is important to have the description of the data received. A detailed breakdown of the schema is helpful in interpreting the variables provided.
The content displayed to end users is usually a combination of several fields, so EveryMundo needs to understand how the information should be displayed.