FareQuoteMultiDisplay_11 allows a user to request:
See the Air Shop FAQ for answers to questions regarding all air shopping transactions.
FareQuoteMultiDisplay_11 can return tariff fares. Tariff fares do not provide faring for available space on flights. Fare quotes can be displayed without an availability request being made. Tariff fares are also often followed by a rules display to determine the requirements and/or penalties associated with a specific tariff fare, prior to determining availability. Therefore, tariff fare displays are often useful for fare-driven travelers.
Tariff displays are similar to a price list or menu in that they show a variety of prices for various types of flights. They represent possible fares for air travel on a given date or range of dates. By viewing the rules for specific tariff fares, the user can determine the desired parameters for conducting an availability search.
There are two (2) types of tariff fares:
Validated Tariff - Displays fares applicable only to the travel dates included in the request. This type of tariff immediately eliminates fares that do not meet requirements, such as prohibited travel dates, seasonality, and minimum/maximum stay requirements.
Non-validated Tariff - Displays all published fares between two cities without validating applicability. Non-validated tariff searches require travel dates. However, these dates are not validated.
After a tariff display request is made, it is often desirable to request the rules associated with particular tariffs. See Rules Display.
The Fare Display task, as part of FareQuoteMultiDisplay_11, is a stand-alone task. However, because tariff displays do not have availability functions, FareQuoteMultiDisplay_11 must be followed by an air availability transaction, if a booked itinerary is desired.
When requesting fares within North America (US and Canada), the two (2) types of display are:
Both responses include a private fare indicator (if no indicator, public), whether fare is un-saleable, carrier, fare, indicator if fare is round trip, fare basis code, advance purchase, minimum and maximum stay, if a penalty exists for refund or cancellation, and the first and last travel and ticketing date rules. However, a validated display requires a departure travel date and an optional return travel date. If only the departure date is input, only valid one way fares are displayed. If both departure and return travel dates are entered, both valid one way and round trip fares are displayed. If a fare is not valid, it does not display. The rule categories validated are:
Days of Week.
Advance purchase.
Minimum and maximum stay.
Seasons.
Prohibited travel dates.
First and last travel dates.
First and last ticketing dates.
When requesting fares outside of North America, the two (2) types of display are:
Both responses include a private fare indicator (if no indicator, public), carrier, fare, indicator if fare is round trip, prime booking code, advance purchase, minimum and maximum stay, seasons, indicator of mileage vs. route based, global direction indicator, and day/time. However, a validated display requires a departure travel date and an optional return travel date. If only the departure date is input, only valid one way fares are displayed. If both departure and return travel dates are entered, both valid one way and round trip fares are displayed. If a fare is not valid, it does not display. The rule categories validated are:
Days of Week.
Advance purchase.
Minimum and maximum stay.
Seasons.
Prohibited travel dates.
First and last travel dates.
First and last ticketing dates.
Fare quote rules supply the requirements or penalties associated with a specific fare quote. Requirements associated with a specific fare code can include information such as minimum/maximum stay requirements, required Saturday or Sunday night stay, required travel on specific days of the week, or any other parameters required to obtain the quoted fare. Fare quote rules also provide any penalties associated with canceling or changing a ticketed reservation.
FareQuoteMultiDisplay_11 is a stand-alone transaction; however, it is commonly used in conjunction with availability and faring processes. Fare quote rules are also often displayed in conjunction with a tariff display to determine the rules associated with a specific tariff fare, prior to requesting availability for that fare.
After a tariff display request is made, it is often desirable to request the rules associated with particular tariffs.
When sessioned, a rules follow-on request can be submitted. To properly provide the requested rules, the host fares application uses two pieces of information, the tariff display line number and additional information stored on the host in the Agent Assembly Area (AAA) from the previous request.
When sessionless, a rules follow-on request can still be submitted but only under specific circumstances. By design all sessionless requests receive a clean AAA on the host. Since the host fares application will have no information stored in the AAA from the previous request, a sessionless rules follow-on request must provide all necessary additional information to be processed successfully. A rules follow-on request must include a <RulesInfo> tag taken directly from the previous host response. For example, a sessionless FareQuoteSuperBB_# response will contain a <RulesInfo> tag. A sessionless rules follow-on request using FareQuoteMultiDisplay_11 may now be made as long as the <RulesInfo> tag is included in the request. A sessionless rules follow-on request cannot be submitted when no <RulesInfo> tag is available. A tariff display response does not include a <RulesInfo> tag and thus cannot be followed with a sessionless rules request.
NOTE: Although a rules follow-on request will accept multiple <RulesInfo> tags, only the first one is processed. Therefore, a rules follow-on request should only contain one <RulesInfo> / <EnhancedPrivateFare>.
The currency conversion function translates fares and rates from one currency to another. Hotel and car rates are typically provided in the currency of the country where the vendor is located. For example, reservations made for a hotel in Paris are quoted in Euros. Currency conversion is required to obtain an equivalent value in the traveler’s native currency.
To perform a currency conversion function, two currencies must be specified. If only one currency is indicated, then United States Dollars (USD) defaults as the second currency. The host system uses the Banker’s Buying Rate (BBR) to perform the conversion.
Note: Because exchange rates fluctuate, the currency conversion transaction will use the rate for the current date. However, by the time the actual charge displays on the customer’s bill, the amount may be different.
The Ticketing Point Mileage function returns the distance between two or more locations for a customer’s travel plans. It is used for mileage based fares to determine if the customer traveling is within the maximum point mileage allowed for those city pairs.
FareQuoteMultiDisplay_11 also provides a variety of faring functions, depending on the action code contained in the <QueryHeader> tag. These functions include display of rule information for a particular fare and fare quote planner (fare quote using “open”, un-booked segments). Click here to view a list of Action Codes to enter in the <QueryHeader> tag.
Some of the queries that this transaction supports depend on a previous entry having been made to set up a session in the host system. These are termed “sessioned” entries. Other entries do not have this requirement, and are termed “sessionless”. The functions supported by this transaction and their sessioning requirements are detailed in the task documents.
It is important to realize that the FareQuoteMultiDisplay_# transaction supports many types of query and response, so that the response tags vary according to the function requested. For example, the Fare Display function requires a <TravConstraints> tag (in addition to the <QueryHeader> tag) and may return <Tariff> or <Msg> tags (depending on query settings) in the response. However, the sessionless rule function requires that a <RulesInfo> tag be present in the query, and it will return <RulesData> or <Msg> tags. The Task documents in the How To section describe the tags involved in each function.
Several tasks listed in the How To describe follow-on functions that do not yet have the help documentation written. However, the Display Booking Code task is a follow-on is documented.
API Developer Notes can assist you when developing applications that use Galileo Web Services and XML Select. The following table lists the API Developer Notes that are applicable to this transaction and provides a description.
| Document | Description |
| Travel Industry Airlines and Airfares | High-level overview of airline industry codes, airline routing, airline ticketing, and how fares are created. |
| Query Header Action Codes | Lists all Fare Quote Action Codes that are used in the <QueryHeader> (GFQH KLR). |
| Air Shop | Lists answers to frequently asked air shopping questions. |