/
22. USE CASES

22. USE CASES

Here we list use cases that could appear during the search&booking process.

 

Diagram 22.1. Flight flow options

22.1. FLIGHT LOW FARE SEARCH


22.1.1. SEARCH WITH RANGE OF TIME

GP HUB allows to specify time window for requested flights.

In order to use search with range of time, need to specify DepartureDateTime/@WindowAfter and/or DepartureDateTime/@WindowBefore attributes on OTA_AirLowFareSearchRQ:

<OTA_AirLowFareSearchRQ EchoToken="12345" Version="2.0" PrimaryLangID="en" xmlns="http://www.opentravel.org/OTA/2003/05"> <POS> <Source> <RequestorID ID="client" MessagePassword="pwd" Type="22"/> <BookingChannel Type="7" PriceDomain="1"/> </Source> </POS> <OriginDestinationInformation RPH="1"> <DepartureDateTime WindowAfter="PT12H0M0.000S" WindowBefore="PT12H0M0.000S">2014-08-21T12:00:00</DepartureDateTime> <OriginLocation LocationCode="LON" CodeContext="IATA.supplierCode"/> <DestinationLocation LocationCode="SYD" CodeContext="IATA.supplierCode"/> </OriginDestinationInformation> <TravelerInfoSummary> <AirTravelerAvail> <PassengerTypeQuantity Code="ADT" Quantity="2"/> </AirTravelerAvail> </TravelerInfoSummary> </OTA_AirLowFareSearchRQ>

GP HUB allows to use only DepartureDateTime/@WindowAfter or DepartureDateTime/@WindowBefore:

<OTA_AirLowFareSearchRQ EchoToken="12345" Version="2.0" PrimaryLangID="en" xmlns="http://www.opentravel.org/OTA/2003/05"> <POS> <Source> <RequestorID ID="client" MessagePassword="pwd" Type="22"/> <BookingChannel Type="7" PriceDomain="1"/> </Source> </POS> <OriginDestinationInformation RPH="1"> <DepartureDateTime WindowAfter="PT12H0M0.000S">2022-08-21T12:00:00</DepartureDateTime> <OriginLocation LocationCode="LON" CodeContext="IATA.supplierCode"/> <DestinationLocation LocationCode="SYD" CodeContext="IATA.supplierCode"/> </OriginDestinationInformation> <TravelerInfoSummary> <AirTravelerAvail> <PassengerTypeQuantity Code="ADT" Quantity="2"/> </AirTravelerAvail> </TravelerInfoSummary> </OTA_AirLowFareSearchRQ>

22.1.2. FLEXIBLE SEARCH WITH RANGE OF DAYS

GP HUB allows to specify range of days for requested flights.

In order to use search with range of days, need to specify TravelPreferences/@DaysBefore and TravelPreferences/@DaysAfter attributes on OTA_AirLowFareSearchRQ:

<OTA_AirLowFareSearchRQ EchoToken="12345" Version="2.0" PrimaryLangID="en" xmlns="http://www.opentravel.org/OTA/2003/05"> <POS> <Source> <RequestorID ID="client" MessagePassword="pwd" Type="22"/> <BookingChannel Type="7" PriceDomain="1"/> </Source> </POS> <OriginDestinationInformation RPH="1"> <DepartureDateTime>2022-08-21T12:00:00</DepartureDateTime> <OriginLocation LocationCode="NCE" CodeContext="IATA.supplierCode"/> <DestinationLocation LocationCode="LHR" CodeContext="IATA.supplierCode"/> </OriginDestinationInformation> <TravelPreferences DaysBefore="2" DaysAfter="3"> <CabinPref Cabin="Economy"/> </TravelPreferences> <TravelerInfoSummary> <AirTravelerAvail> <PassengerTypeQuantity Code="ADT" Quantity="2"/> </AirTravelerAvail> </TravelerInfoSummary> </OTA_AirLowFareSearchRQ>

GP HUB allows to use only TravelPreferences/@DaysBefore or TravelPreferences/@DaysAfter attributes on OTA_AirLowFareSearchRQ:

22.1.3. SEARCH BY RESERVATION BOOKING DESIGNATOR CODE

GP HUB allows to search with preferred flight cabin class using Reservation Designator Code (RDC).

22.1.4. SEARCH BY CORPORATE CODES

GP HUB allows to search for flights with corporate fare code. Response will contain flights with private fares.

22.1.5. SEARCH WITH CABIN CLASS

GP HUB allows to specify cabin class for requested flights.

In order to use search with cabin class, you need to specify TravelPreferences/CabinPref/@Cabin attributes on OTA_AirLowFareSearchRQ. Possible values: First, Business, Economy, PremiumEconomy.

22.1.6. SEARCH WITH PREFERRED FLIGHT TYPE

GP HUB allows to specify indicates type of preferred flight.

In order to use search with preferred flight type, you need to specify TravelPreferences/FlightTypePref element with FlightType attribute on OTA_AirLowFareSearchRQ. Possible values of FlightType: Direct, Nonstop, Connection. Also PreferLevel attribute can be specified. It indicates a level of preference of the associated flight. Possible values: Preferred - used by default, Only, Unacceptable.

22.1.7. SEARCH WITH SpecificPTC_Indicator

SpecificPTC_Indicator allows to get offers where some passenger types (e.g. CHD- child) is rated as another (e.g. as ADT -adult). In order to engage this logic, SpecificPTC_Indicator="false" attribute should be specified in Low Fare Search request in TravelerInfoSummary element.

By default attribute is considered it as "True" – HUB expects that fares would be exactly for requested passenger types categories.

22.2. FLIGHT SCHEDULE SEARCH


22.2.1. SEARCH BY SEPARATE FlightInfo/@BookingClassPref and FlightInfo/@Arline

If the particular airline is defined in separate FlightInfo, and the BookingClassPref is defined in separate FlightInfo as well, it's expected to get all the results from all airlines with BookingClass Z, but among them at least one selected airline should appear.

22.2.2. SEARCH BY ONE FlightInfo with BookingClassPref and Arline

If either Airline or BookingClassPref are defined in one and the same element, that means that least one specified airline should appear in origDestOption and only this airline should be only with BookingClass Z, another airlines can have all Booking Classes.

22.3. BOOKING


22.3.1. BOOKING WITH SPECIAL DETAILS

GP HUB allows to book several types of special details:

Seat request allows to book seat for each passenger for each air leg of this trip.

Special Service Requests (SSR) provides detailed information regarding any special needs, requests, or remarks associated with the traveler.

Note: GP Travel HUB passes SSRs to supplier “as is”, without additional validation and data conversion. This is for client system to compose the SSR request well for supplier (airline), therefore this functionality is recommended for experienced users only.

Special Remark allows to send text associated with remark that clear to the supplier.

In order to specify special details need to add the TravelerInfo/SpecialReqDetails element with necessary details on Reservation Initiate request:

Reservation Confirmation Response structure is the same as in regular Reservation Confirmation Response, with the difference in presence of SpecialReqDetails element, which is the same as in previous step. The difference can occur in Status attribute, that may have different values.

Flight Ticketing Request doesn't differ from regular one.

Flight Booking Retrieval Quote works the same as for regular flow, only SpecialReqDetails element, described above, is added.

22.3.2. BOOKING WITH DISCOUNTS

GP HUB allows to specify special formulas for applying different discounts.

In order to use discounts, need to specify PriceInfo/FareInfos element on Reservation Initiate Request:

Reservation Confirmation Response structure is the same as in regular Reservation Confirmation Response, with the difference in presence of DiscountPricing element, which is the same as in previous step. The difference can occur in Status attribute, that may have different values.

Flight Ticketing Request works the same as for regular flow, only DiscountPricing element, described above, is added.

Flight Booking Retrieval Quote works the same as for regular flow, only DiscountPricing element, described above, is added.

22.4. EXTRA SERVICES BOOKING


GP HUB allows to book particular extra services, like additional baggage, extra seat or meal. For this the specific flow have been implemented that slightly differs from the original one.

Extra services, available for particular offer, can be seen on Flight Details Response:

In order to book extra service on Reservation Initiate request, need to add one of the AirReservation/Offer element received on Flight Details Response with the information for which traveler TravellerRPH and on which flight segment FlitghSegmentRPHList this offer should be booked:

Reservation Confirmation Response structure is the same as in regular Reservation Confirmation Response, with the difference in presence of Offer element, which is the same as in previous step. The difference can occur in Status attribute, that may have different values.

Usually service on Reservation Confirmation Response step has one of these values:

  • "Holds confirmed, EMD required" - means aircompany has confirmed yet this service. And EMD should be issue! In our case client should call AirDemandTicket.

  • "Pending confirmation" - means aircompany hasn't confirmed yet this service.

  • "Holds confirmed, no EMD required" - special service status that means that the booking is complete. EMD is not required.

Flight Ticketing Request doesn't differ from regular one. But there are differences in response. The new element “Ticketing” with TicketType="MCO" is added for Extra Services.

Flight Booking Retrieval Quote works the same as for regular flow, only Offers element, described above, is added.

22.5. LOW-COST FLOW

Low-cost (LCC, Web-fare) airline is operated with an especially high emphasis on minimizing operating costs and without some of the traditional services and amenities.

 

Diagram 22.5. Low-cost flow in GP HUB.

GP HUB allows to:

  • search for low-cost flights (LowFareSearch);

  • get information about fare rules and flight details (optional);

  • make a reservation of low-cost flight;

  • Import PNR to GP HUB if booking was made in suppliers system;

  • Retrieve PNR to update current status of the reservation.

Ticketing and Cancelling operations are impossible for Web Fare bookings.

Low-cost flow in GP HUB:

In a current API version it’s not possible to specify somehow in Low Fare Search Request that GPHUB should return only Web fares (LCC). So this request is absolutely usual. It is used to search regular flights and low-costs. It depends on supplierCode. If the supplier supports LCC, GP HUB returns this info.

Low-cost flights are designated by "WebFare" in OTA_AirLowFareSearchRS/PricedItineraries/PricedItinerary/AirItineraryPricingInfo/@PricingSource:

Also you can additionaly request Fare Rules or Flight Details. Messages structure is the same as in simple flight:

Reservation flow is also the same as in simple flight booking, but Flight Reservation Confirmation is the final step of the booking process (possible booking statuses are "Issued", "Request denied"). Then you can only do Retrieve PNR or Retrieve Import.

Related content

2.1. FLIGHT LOW FARE SEARCH REQUEST
2.1. FLIGHT LOW FARE SEARCH REQUEST
More like this
3.1. FLIGHT SCHEDULE SEARCH REQUEST
3.1. FLIGHT SCHEDULE SEARCH REQUEST
More like this
19.6. SPLIT CONFIRMATION RESPONSE
19.6. SPLIT CONFIRMATION RESPONSE
Read with this
4.1. FLIGHT TIME TABLE SEARCH REQUEST
4.1. FLIGHT TIME TABLE SEARCH REQUEST
More like this
17.3. FLIGHT REMOVE FROM QUEUE REQUEST
17.3. FLIGHT REMOVE FROM QUEUE REQUEST
Read with this
2.2. FLIGHT LOW FARE SEARCH RESPONSE
2.2. FLIGHT LOW FARE SEARCH RESPONSE
More like this