Air Shop Frequently Asked Questions
What’s the difference between the FareQuoteShop and FareQuoteSuperBB?
How do I interpret the response of the FareQuoteShop/FareQuoteSuperB?
How do I submit a session-less rules follow-on to a FareQuote?
I get a ‘RESTRICTED’ message in my response, what does this mean?
How do time windows work?
How many air vendors can I add to the vendor preference section?
What is the difference between all the shopping calls?
How does the Optimize section work and what’s the difference between optimize and a filter?
Why can’t I find a particular flight in my response?
Can I get all fares in a given market with the FareQuoteShop/FareQuoteSuperB?
I need a breakdown of fare by segment, where can I find this?
Can I use the AirVSpecific node with FareQuoteShop/FareQuoteSuperB?
Why am I not receiving private/negotiated fares in my response?
What’s the difference between a PIC and a PTC?
Why is it that I’m requesting coach cabin using FareQuoteShop but I’m returned other cabins?
I’m performing a ‘private fares only’ request using the FareQuoteShop but I’m returned both published fares and private fares, why?
What is the maximum number of PTCs I can include with a shopping call?
Why when requesting a child PTC with an adult I get a different fare basis for the child which requires a booking in a different booking code than the adult?
How to I specify a Fare Basis (FIC) when storing the fare?
How do I request Category 35 netfares?
Q: What’s the difference between the FareQuoteShop and FareQuoteSuperBB?
A: The main difference is that FareQuoteShop is the ITA faring option. The actual content of the call is returned from ITA. FareQuoteSuperB utilizes Galileo’s NGGF faring engine. FareQuoteShop is also for North American itineraries only.
Q: How do I interpret the response of the FareQuoteShop/FareQuoteSuperB?
A: The <FlightItemCrossRef> node of the fares response indicates which available flights each fare corresponds to. For instance the first <FltItem> refers to <ODNum> = 1 which is the first <AirAvail> node in the response. <IndexNum will refer to the 2nd <AvailFlt> node under the <AirAvail> node. Each <AvailFlt> node contains details of the individual flights.
Q: How do I submit a session-less rules follow-on to a FareQuote?
A: The <RulesInfo> node must be submitted using the FareQuoteMultiDisplay call <Action> = 35. Additionally if a private fare is quoted then the <EnhancedPrivateFare> node must be submitted as well. See XML Sample FareQuoteMultiDisplay_8_3_4 in Transaction Help.
Q: I get a ‘RESTRICTED’ message in my response, what does this mean?
A: Access to the FareQuoteSuperBB/FareQuoteShop is controlled at the Agency Account table level. If you currently don’t have access please contact your Galileo account representative to discuss this as a possible charge item.
Q: How do time windows work?
A: If time window values <StartTmWnd> & <EndTmWnd> are populated then if <TmWndInd> = D only flights which depart within these values will be considered. If <TmWndInd> = A then only flights which arrive within the <StartTmWnd> & <EndTmWnd> values will be considered. If no time window values are populated then the flight search will begin 2 hours prior to the <StartTm> value.
Q: How many air vendors can I add to the vendor preference section?
A: Up to 24 can be included but optimum for each origin/destination is 4 for the FareQuoteSuperB call. This limitation doesn’t exist for the FareQuoteShop call.
Q: What is the difference between all the shopping calls?
A: Following is a table showing the differences in shopping calls:
|
Transaction |
State |
Source |
Prerequisites |
|
FareQuoteShop |
Sessioned/Sessionless |
ITA |
None |
|
FareQuoteSuperB |
Sessioned/Sessionless |
NGGF |
None |
|
FareQuoteFlightSpecific |
Sessioned/Sessionless |
NGGF |
Flight Details |
|
FareQuoteStandard |
Sessioned |
NGGF |
Booked itinerary |
|
FareQuoteClassSpecific |
Sessioned/Sessionless |
NGGF |
Flight Details |
|
FareQuoteDollarSaver |
Sessioned |
NGGF |
Booked itinerary |
|
FareQuoteMultiDisplay |
Sessioned/Sessionless* |
NGGF |
None |
|
FareQuoteCalendarDates |
Sessioned/Sessionless |
NGGF |
Fare Basis |
* Rules follow-on to Tariff Display requires session.
Q: How does the Optimize section work and what’s the difference between optimize and a filter?
A: Adding an Optimize section performs filtering on the host side. The advantage of this is smaller packet sizes resulting in increased application performance. An XML filter sent in with the request will return all data but filter on the client side (XML Select users) or within the web services platform (Web Services users). Filtering works identically for only FareQuoteShop & FareQuoteSuperB. If Optimize node is included then only those KLR IDs specified will be returned. See Response Transaction Help for KLR IDs and definitions.
Q: Why can’t I find a particular flight in my response?
A: This is more common to FareQuoteSuperB than FareQuoteShop. The FareQuoteSuperB call uses a rather limited ‘scoop’ of availability to construct itineraries. This ‘scoop’ may fill prior to a specific flight being considered. Typically narrowing flight search criteria by vendor preference, flight type, or time windows resolves this issue.
Q: Can I get all fares in a given market with the FareQuoteShop/FareQuoteSuperB?
A: No, this isn’t possible. Due to the ‘scoop’ limitations detailed above up to 7 fares and associated flight options will be returned by the FareQuoteSuperB. FareQuoteShop will return up to 150 fares.
Q: I need a breakdown of fare by segment, where can I find this?
A: <SegRelatedInfo> will return a breakdown of a base fare by segment. Taxes will be calculated for the entire trip and not included in this segment breakdown. Additionally FareQuoteShop will not include any applicable surcharges will not be included.
Q: Can I use the AirVSpecific node with FareQuoteShop/FareQuoteSuperB?
A: No, only the <GenAvail> node is supported with these calls.
Q: Why am I not receiving private/negotiated fares in my response?
A: Be sure to include a <PFInfo> node containing the Pseudo City where the private fares are filed. Also be sure to include any applicable account codes.
Q: What’s the difference between a PIC and a PTC?
A: PICs (Passenger Identification Codes) are the old Galileo standard. It’s recommended that the new PTC codes be utilized for all shopping/booking requests. PICs are submitted using the <PsgrMods> node where PTCs are submitted using the <PassengerType> node.
Q: Why is it that I’m requesting coach cabin using FareQuoteShop but I’m returned other cabins?
A: FareQuoteShop merely gives preference for the requested cabin. To ensure a robust response set it’s designed to return all classes of services. Workarounds include filtering the response based on booking code cabin designations or performing cabin specific search’s using FareQuoteSuperB. FareQuoteSuperB does not display this behavior.
Q: I’m performing a ‘private fares only’ request using the FareQuoteShop but I’m returned both published fares and private fares, why?
A: Again to ensure a robust response FareQuoteShop is designed to return both. To filter the private fares from the response the <PrivFqd> tag can be interrogated to determine whether the fare includes private fares.
Q: What is the maximum number of PTCs I can include with a shopping call?
A: Maximum number of unique PTCs is four. Total passengers cannot exceed 9.
Q: Why when requesting a child PTC with an adult I get a different fare basis for the child which requires a booking in a different booking code than the adult?
A: The FareQuoteSuperB is designed to return the best fare regardless for each unique PTC.
Q: How to I specify a Fare Basis (FIC) when storing the fare?
A: This can be accomplished using the PNRBFManagement using the PFInfo section but it’s not recommended as essentially the fare is being ‘forced’ and may override rules so that this fare is no longer guaranteed and may not be honored by the airline.
Q: How do I request Category 35 netfares?
A: A <GenQuoteInfo> node must be included with the <NetFaresOnly> tag = Y.