JUNIPER BOOKING ENGINE XML WEBSERVICE FOR...

53
JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS XML WebServices Interface OTA 2006B Specification Version 20090805 Juniper España Gremi Fusters 33 · Oficina 302 | 07009 Palma de Mallorca T. (+34) 971 764 415 / 902 121 489 | F. (+34) 971 764 182 Juniper USA 168 SE 1st Street-Suite 903 | 33131 Miami P. (+1) 305 755 0251 | F. (+1) 305 755 0252 Innovating Internet Travel Technology

Transcript of JUNIPER BOOKING ENGINE XML WEBSERVICE FOR...

Page 1: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS

XML WebServices Interface OTA 2006B Specification

Version 20090805

Juniper España

Gremi Fusters 33 · Oficina 302 | 07009 Palma de Mallorca T. (+34) 971 764 415 / 902 121 489 | F. (+34) 971 764 182

Juniper USA

168 SE 1st Street-Suite 903 | 33131 Miami P. (+1) 305 755 0251 | F. (+1) 305 755 0252

Innovating Internet Travel Technology

Page 2: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 2

This document is a preliminary release and may be changed prior to final commercial release. This document is provided for information purposes only and JUNIPER makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use, or the results from the use, of this document remains with the user. The information contained in this document represents the current view of JUNIPER on the issues discussed as of the date of publication. Because JUNIPER must respond to changing market conditions, it should not be interpreted to be a commitment on the part of JUNIPER, and JUNIPER cannot guarantee the accuracy of any information presented after the date of publication. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Page 3: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 3

TABLE OF CONTENTS

Version History .............................................................................................................................. 4

20090805 ................................................................................................................................... 4 20080915 ................................................................................................................................... 4 20080826 ................................................................................................................................... 4 20080616 ................................................................................................................................... 4 20080612 ................................................................................................................................... 4

Introduction .................................................................................................................................... 5 About the Juniper Webservice for flights ................................................................................... 5 Additional information and support ............................................................................................ 5 About Juniper ............................................................................................................................. 5

Juniper Webservice for flights overview ........................................................................................ 6 About the Webservice ................................................................................................................ 6 The OpenTravelTM Alliance (OTA) Specification ...................................................................... 6 How the Juniper Webservice Works .......................................................................................... 7

Getting Started .............................................................................................................................. 7 XML messaging overview ............................................................................................................. 7

How to connect to the webservices ........................................................................................... 8 Connecting using .Net and Visual Studio .NET ..................................................................... 8 Connecting using another technology .................................................................................... 8

Compression .............................................................................................................................. 8 How to create a new booking using webservices ...................................................................... 9 Changing bookings .................................................................................................................... 9 Cancelling a booking ................................................................................................................. 9

XML Messages .............................................................................................................................. 9 Authentication ............................................................................................................................ 9 Language ................................................................................................................................... 9 Availability request (OTA_AirLowFareSearch.asmx) .............................................................. 10 Reservation Request (OTA_AirBook.asmx) ............................................................................ 16

How to book outbound + inbound flight ............................................................................... 22 Booking Cancelation (OTA_Cancel.asmx) .............................................................................. 26 Read a reservation (OTA_Read.asmx) ................................................................................... 27 Retrieve Fare Rules (OTA_AirRules.asmx) ............................................................................. 29

Page 4: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 4

Version History

20090805

- Added OTA_AirRules service

20080915

- Added more explanations to examples - Added “How to book outbound + inbound flight” section - Added Adjustments in fare breakdown - Added ResStatus in OTA_AirBookRS - Added BirthDate in AirTraveler node

20080826

- Changed date-time format - Added LastTicketDate in OTA_AirLowFareSearchRS - Added RefNumber in OriginDestinationOption element - Added Service Fee and Credit Card Payment Fee

20080616

- Changed date-time format - Added SpecificFlightInfo element in OTA_AirLowFareSearchRQ to search for LowCost

flights or not. - Added attribute DirectionInd in OTA_AirLowFareSearchRS to identify the trip type

20080612

- Initial release.

Page 5: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 5

Introduction

About the Juniper Webservice for flights

The Juniper Webservice for flights was designed to help facilitate the integration of third parties with the Juniper Booking Engine. The Webservice allows third parties to develop clients that can search for available flights and make reservations. Through the utilization of XML over HTTP, clients (i.e. web applications, handheld devices, etc.) can connect directly with the reservation system. The following guide is designed to provide a greater understanding of the Juniper Webservice and assist in development of third party clients. This guide assumes the following:

Familiarity with XML schemas and specifications

Familiarity with OpenTravelTM Alliance (OTA) Specifications

Familiarity with web application development technologies

Additional information and support

Many sources of information, including online documentation, training and support services, exist to increase your knowledge and understanding of the Juniper Webservice:

The OpenTravelTM Alliance (OTA) site. OTA is a non-profit organization working to establish a common electronic vocabulary, represented in XML format, for use in the exchange of travel information. Refer to this site for more information about the OTA specifications and schemas.

The World Wide Web Consortium (W3C) site. W3C is an international consortium where Member organizations, a full-time staff, and the public, work together to develop Web standards.

About Juniper

We are a Team of professionals, experts in Internet Technology and in the Travel Industry, with Offices in Spain and the USA, offering a permanent quality and service commitment to all our clients, taking care of your needs in an environment which is in permanent change and evolution. We are leaders in providing solutions for Travel Companies established in North America, South America and in Europe, allowing us to investigate and develop new solutions in the most innovative markets and offer them to our clients globally, providing Travel Companies with exactly what their markets need and remain innovative in their own Industry. Our solutions are extremely easy to use and have been designed to be very intuitive, where we provide our clients with tools that give them complete freedom of action over the different Internet Sales Distribution Channels they might have, as well as over their own Website, thus giving them the opportunity to take a more proactive approach toward all the different Sales opportunities available in Internet. We offer Travel Companies all of the online tools, from dynamic information relating to each Product’s Sales and the Management of all the Bookings, up to the Management of all the Content displayed on their Web as well as providing them with the possibility of designing their own Marketing Campaigns aimed at their customers and their repeat business. Travel companies have the opportunity to offer their own Inventory as well as complementary Inventory from external Suppliers, through completely transparent connections to their own Data Bases. In this way, they will be able to offer their clients a variety of services and dynamic packaging that was, until now, simply impossible to manage from one single Website.

Page 6: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 6

We have developed our own XML connection, following OTA standards, and we can connect our clients to external Suppliers, Host to Host, offering a great variety of vacation products, like Accommodation from Hotelbeds/Bedsonline, Tourico Holidays, Gullivers Travel, Mark Travel, AlliedTPro, Transhotel, ATI, JonView, Packages from Wholesalers like Soltour or Marsol, Flights through the GDS of Galileo, Sabre, Worldspan or Amadeus, Car Rentals through Hertz, Alamo and HolidayAutos, amongst several others.

Juniper Webservice for flights overview

About the Webservice

The Juniper Webservice provides third parties the ability to develop clients that can access the reservation system through the use of XML messaging via standard HTTP protocol. The Webservice is a hosted service that enables third parties to perform availability searches and reservation bookings for flights. The Juniper Webservice allows partners and affiliates to realize several business benefits:

Non-exclusive; allowing the adding of more products to your site for maximum profit

Full ownership of customers who book through your client’s site

Offer Net Rates or commissionable rates

Real-time availability direct from the reservation system

Ability to integrate into existing applications that support HTTP protocol The Juniper Webservice supports the following technologies:

SOAP Requests. SOAP 1.1 and SOAP 1.2.

Secure Transactions. Juniper Webservice supports SSL, ensuring the protection of customer credit card information sent over the Internet.

Authentication. Data passed through the Webservice client and server is protected from unauthorized parties by use of HTTP Basic Authentication to control access to our systems. Parties failing to provide an authorized username/password are denied access.

The OpenTravelTM Alliance (OTA) Specification

The OpenTravelTM Alliance (OTA) is a self-funded, nonprofit organization comprised of major airlines, hoteliers, car rental companies, leisure suppliers, travel agencies, Global Distribution Systems (GDS), technology providers and other interested parties. These parties work to create and implement open, industry wide e-business specifications. OTA has defined open messages in Extensible Markup Language (XML), making it possible to exchange business data seamlessly among different systems, companies and industries over the World Wide Web. XML is an open and platform independent standard that provides a specification approach for describing, capturing, processing, and publishing information. OTA specifications form a common e-business language that encourages system developers to create new collections of services that better meet the demands and expectations of travelers and the travel industry. The specifications also provide a framework for companies in the travel industry to create new relationships with customers, as well as create new partnerships with fellow companies in the business. Web site: http://www.opentravel.org/

Page 7: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 7

How the Juniper Webservice Works

The Juniper Webservice provides access to the Juniper Booking Engine by using the HTTP protocol to send and receive XML messages. Once you have developed and configured the connection to the Juniper Webservice, XML messages can be transmitted via HTTP Post to the Juniper Webservice to perform searches, bookings and cancellations as well as receive the results back via standard XML messaging.

The XML messaging of the Juniper Webservice for flights is based on the OTA XML standards for services related to airlines. The response messages are also OTA compliant. It currently supports the following transactions via XML messaging:

Availability Request for specific dates - Retrieves availability for a city pair with all corresponding rates

Reservation Request - Allows clients to make a flight reservation

Reservation Cancellation Request - Allows clients to cancel a booking confirmation

Reservation Read Request - Allows clients to retrieve information for a booking confirmation

Getting Started The first step is to contact your Supplier and Juniper in order to gain Access to the system. To gain Access to the system you will need to provide:

Name of your organization and primary technical contact (Name, Title, Phone and email)

Service that you want to have access to

IP address from where you will accessing

XML messaging overview This section describes the currently supported transactions available via XML messaging within the Juniper Webservice. A detailed overview of the XML request and response message tags is provided to assist you in the development. XML messaging involves an HTTP post to a specific URL based on two items:

Access to the environment (Test or Production) you are posting the request to.

The specific transaction being performed (Search, Booking, Cancel) These requests that are based according to the OTA standards have a root element to perform all requests depending on the type of request.

Request Header Request Header Response

Page 8: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 8

Availability OTA_AirLowFareSearchRQ OTA_AirLowFareSearchRS

Book OTA_AirBookRQ OTA_AirBookRS

Cancel OTA_CancelRQ OTA_CancelRS

Read Reservation OTA_ReadRQ OTA_ResRetrieveRS

How to connect to the webservices

Each message or request goes with a specific webservice. So, a request OTA_AirLowFareSearch has a specific webservice at xml.myprovider.com/webservice/ota_airlowfaresearch.asmx All webservices have their own function, in the case of availability we have: OTA_AirLowFareSearchService: Request that expects an object with type Request and that also returns an object.

Connecting using .Net and Visual Studio .NET If you are using Visual Studio .NET, you can connect directly to webservices using a web reference. On the Internet, there are many pages explaining how to connect to a webservice using Visual Studio .NET. In that case, you can use the webservice function, like OTA_AirLowFareSearchService with the .NET objects. Those objects use a very similar structure to the XML messages that appear in this document. Here we show only the XML messages because visually the structure is easier to understand than the objects.

Connecting using another technology If you are using a technology unable to create the SOAP object and serialize and deserialize automatically, you will have to do it manually in order to retrieve the information from the Webservice. For example, if you want to read a reservation, you will have to do:

POST /webservice/OTA_Read.asmx HTTP/1.1

Host: host

Content-Type: application/soap+xml; charset=utf-8

Content-Length: length

<?xml version="1.0" encoding="utf-8"?>

<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">

<soap12:Body>

xml

</soap12:Body>

</soap12:Envelope>

Where host is the domain of the webservice (like xml.myprovider.com/webservice), length is

the length of the message and xml is the xml request (like the request examples of this

documentation). To know the name of the function and parameters of the rest of webservices you can see the documentation in each webservice, like OTA_Read.asmx.

Compression

For big responses, the system will spend some extra time sending this information through the Internet. The system is designed to reduce the amount of time in the transmission step

Page 9: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 9

through the compression tool, by reducing the transmission time and response size by about 95%. We strongly recommend using compression in your request. For using it, the request should have the header "Accept-Encoding:gzip, deflate". If the server detects it then the response is compressed, and the client will receive our response with the header "Content-Encoding: gzip". The client that receives the response has to decompress it on the fly before processing. This is a part of the HTTP standard protocol.

How to create a new booking using webservices

The process of creating a new booking typically will flow as follows: 1. Creation of a Availability Request 2. Retrieve the Response from the webservice (rates and availability) 3. Creation of a Flight Booking Request (with customer info) 4. Retrieve the response from the webservice (confirmation number, etc)

Changing bookings

The webservice does not support changes. For changes you will need to cancel your existing booking and make a new one.

Cancelling a booking

A reservation can be canceled by creating a Cancelation request and including the confirmation number.

XML Messages

Authentication

Authentication must be included in all messages. The system will respond with the appropiate information only if authentication succeeds. Example: <POS> <Source AgentDutyCode="[email protected]"> <RequestorID Type="1" MessagePassword="pass" /> </Source> </POS> It is mandatory:

AgentDutyCode: customer’s email

MessagePassword: customer’s password

Language

In every heading you can specify which language you want to obtain your response in. <OTA_XXX PrimaryLangID="es" >

Page 10: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 10

Availability request (OTA_AirLowFareSearch.asmx)

Request: OTA_AirLowFareSearchRQ Response: OTA_AirLowFareSearchRS This service retrieves flight availability for specific city pairs and dates. All results will contain the final price, and all taxes will be included. The following example is an availability request, and the mandatory information for this request is:

City pair

Departure date

Number and type of passengers

Example: We look for 1 adult passenger

<?xml version="1.0" encoding="UTF-8"?> <OTA_AirLowFareSearchRQ xmlns="http://www.opentravel.org/OTA/2003/05" PrimaryLangID="es" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=http://www.opentravel.org/OTA/2003/05 OTA_AirLowFareSearchRQ.xsd PrimaryLangID="es"> <POS> <Source AgentDutyCode="[email protected]"> <RequestorID Type="1" MessagePassword="pass" /> </Source> </POS> <OriginDestinationInformation> <DepartureDateTime>2008-10-20</DepartureDateTime> <OriginLocation LocationCode="MAD"/> <DestinationLocation LocationCode="LON"/> </OriginDestinationInformation> <OriginDestinationInformation> <DepartureDateTime>2008-10-23</DepartureDateTime> <OriginLocation LocationCode="LON"/> <DestinationLocation LocationCode="MAD"/> </OriginDestinationInformation> <TravelerInfoSummary> <AirTravelerAvail> <PassengerTypeQuantity Code="ADT" Quantity="1"/> </AirTravelerAvail> </TravelerInfoSummary> </OTA_AirLowFareSearchRQ>

Optional elements in OTA_AirLowFareSearchRQ:

1- You can add an element in OTA_AirLowFareSearch request to apply resident discount in flight fares. Example:

<?xml version="1.0" encoding="utf-8"?> <OTA_AirLowFareSearchRQ xmlns="http://www.opentravel.org/OTA/2003/05" PrimaryLangID="es" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=http://www.opentravel.org/OTA/2003/05 OTA_AirLowFareSearchRQ.xsd PrimaryLangID="es"> <POS> <Source AgentDutyCode="[email protected]"> <RequestorID Type="1" MessagePassword="pass" /> </Source> </POS>

Page 11: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 11

<OriginDestinationInformation> <DepartureDateTime>2008-11-20</DepartureDateTime> <OriginLocation LocationCode="MAD"/> <DestinationLocation LocationCode="TFN"/> <TPA_Extensions> <ResidentDiscount Value="1" /> </TPA_Extensions> </OriginDestinationInformation> <OriginDestinationInformation> <DepartureDateTime>2008-11-25</DepartureDateTime> <OriginLocation LocationCode="TFN"/> <DestinationLocation LocationCode="MAD"/> <TPA_Extensions> <ResidentDiscount Value="1" /> </TPA_Extensions> </OriginDestinationInformation> <TravelerInfoSummary> <AirTravelerAvail> <PassengerTypeQuantity Code="ADT" Quantity="1"/> </AirTravelerAvail> </TravelerInfoSummary> </OTA_AirLowFareSearchRQ>

If city pairs are valid for resident discount, the response will have the appropriate discount applied.

2- You can obtain LowCost flights including SpecificFlightInfo element in OTA_AirLowFareSearchRQ. CodeContext attribute in Airline node must have the value LC. Here is an example:

<?xml version="1.0" encoding="utf-8"?> <OTA_AirLowFareSearchRQ xmlns="http://www.opentravel.org/OTA/2003/05" PrimaryLangID="es" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_AirLowFareSearchRQ.xsd" SequenceNmbr="Code123"> <POS> <Source> <RequestorID Type="1" MessagePassword="pass" /> </Source> </POS> <OriginDestinationInformation> <DepartureDateTime>2008-11-20</DepartureDateTime> <OriginLocation LocationCode="MAD"/> <DestinationLocation LocationCode="LON"/> </OriginDestinationInformation> <OriginDestinationInformation> <DepartureDateTime>2008-11-25</DepartureDateTime> <OriginLocation LocationCode="LON"/> <DestinationLocation LocationCode="MAD"/> </OriginDestinationInformation> <SpecificFlightInfo> <Airline CodeContext="LC" /> </SpecificFlightInfo> <TravelerInfoSummary> <AirTravelerAvail> <PassengerTypeQuantity Code="ADT" Quantity="1"/> </AirTravelerAvail> </TravelerInfoSummary> </OTA_AirLowFareSearchRQ>

Page 12: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 12

The response below shows the alternatives found. There are some important items: <PricedItineraries> Contains the list of alternatives found <PricedItinerary> It’s composed by Itinerary info (AirItinerary) and Pricing info (AirItineraryPricingInfo) <OriginDestinationOptions> A collection of OriginDestinationOption <OriginDestinationOption> Contains the list of legs for this itinerary <FlightSegment> Contains full information about a segment (departure and arrival dates, flight number, operating and marketing airline, etc) <ItinTotalFare> It contains the total fare for this “PricedItinerary”. This fare has tax included, and the FareBreakdown is in the “PTC_FareBreakdown” item which is contained in the following element <PTC_ FareBreakdowns> Contains a list of “PTC_FareBreakdown” items. There is one item per passenger type <PTC_FareBreakdown> Contains all fare information for a passenger type <PassengerFare> Contains the tax list, base fare, fare equivalence “EquivFare” (in case base fare is in different currency) and total fare for this passenger type

<?xml version="1.0"?> <OTA_AirLowFareSearchRS xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchemainstance" xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_AirLowFareSearchRS.xsd" Version="2.001" SequenceNmbr="Code123"> <Success /> <PricedItineraries> <PricedItinerary SequenceNumber="1"> <AirItinerary DirectionInd="Roundtrip"> <OriginDestinationOptions> <OriginDestinationOption RefNumber="ref123"> <FlightSegment DepartureDateTime="2008-10-20T10:20:00" FlightNumber="2065" ArrivalDateTime="2008-10-20T12:40:00" StopQuantity="0" RPH="1" ResBookDesigCode="E"> <DepartureAirport LocationCode="MAD" /> <ArrivalAirport LocationCode="MUC" /> <OperatingAirline Code="JK" /> <MarketingAirline Code="LH" /> </FlightSegment> <FlightSegment DepartureDateTime="2008-10-20T13:15:00" FlightNumber="4756" ArrivalDateTime="2008-10-20T14:15:00" StopQuantity="0" RPH="2" ResBookDesigCode="E"> <DepartureAirport LocationCode="MUC" /> <ArrivalAirport LocationCode="LHR" /> <MarketingAirline Code="LH" /> </FlightSegment> </OriginDestinationOption>

Page 13: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 13

<OriginDestinationOption RefNumber="ref123"> <FlightSegment DepartureDateTime="2008-10-23T09:40:00" FlightNumber="4751" ArrivalDateTime="2008-10-23T12:25:00" StopQuantity="0" RPH="3" ResBookDesigCode="L"> <DepartureAirport LocationCode="LHR" /> <ArrivalAirport LocationCode="MUC" /> <MarketingAirline Code="LH" /> </FlightSegment> <FlightSegment DepartureDateTime="2008-10-23T13:15:00" FlightNumber="2064" ArrivalDateTime="2008-10-23T15:45:00" StopQuantity="0" RPH="4" ResBookDesigCode="T"> <DepartureAirport LocationCode="MUC" /> <ArrivalAirport LocationCode="MAD" /> <OperatingAirline Code="JK" /> <MarketingAirline Code="LH" /> </FlightSegment> </OriginDestinationOption> </OriginDestinationOptions> </AirItinerary> <AirItineraryPricingInfo> <ItinTotalFare> <TotalFare Amount="381.30" CurrencyCode="USD" DecimalPlaces="2" /> </ItinTotalFare> <PTC_FareBreakdowns> <PTC_FareBreakdown> <PassengerTypeQuantity Code="ADT" Quantity="1" /> <PassengerFare> <BaseFare Amount="179.00" CurrencyCode="EUR" DecimalPlaces="2" /> <EquivFare Amount="278.00" CurrencyCode="USD" DecimalPlaces="2" /> <Taxes> <Tax TaxCode="IVA" Amount="7.90" CurrencyCode="USD" DecimalPlaces="2" /> <Tax TaxCode="TUA" Amount="2.50" CurrencyCode="USD" DecimalPlaces="2" /> <Tax TaxCode="Qs" Amount="34.60" CurrencyCode="USD" DecimalPlaces="2" /> <Tax TaxCode="Others" Amount="58.30" CurrencyCode="USD" DecimalPlaces="2" /> </Taxes> <TotalFare Amount="381.30" CurrencyCode="USD" DecimalPlaces="2" /> </PassengerFare> </PTC_FareBreakdown> </PTC_FareBreakdowns> <FareInfos> <FareInfo> <RuleInfo> <ResTicketingRules> <AdvResTicketing LastTicketDate="2008-10-15" /> </ResTicketingRules> </RuleInfo> </FareInfo> </FareInfos> </AirItineraryPricingInfo> </PricedItinerary> <PricedItinerary SequenceNumber="2"> <AirItinerary DirectionInd="Roundtrip"> <OriginDestinationOptions> <OriginDestinationOption RefNumber="ref456"> <FlightSegment DepartureDateTime="2008-10-20T09:50:00" FlightNumber="2021" ArrivalDateTime="2008-10-20T12:05:00" StopQuantity="0" RPH="1" ResBookDesigCode="V"> <DepartureAirport LocationCode="MAD" /> <ArrivalAirport LocationCode="ZRH" /> <MarketingAirline Code="LX" /> </FlightSegment> <FlightSegment DepartureDateTime="2008-10-20T15:40:00" FlightNumber="324"

Page 14: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 14

ArrivalDateTime="2008-10-20T16:25:00" StopQuantity="0" RPH="2" ResBookDesigCode="V"> <DepartureAirport LocationCode="ZRH" /> <ArrivalAirport LocationCode="LHR" /> <MarketingAirline Code="LX" /> </FlightSegment> </OriginDestinationOption> <OriginDestinationOption RefNumber="ref456"> <FlightSegment DepartureDateTime="2008-10-23T08:40:00" FlightNumber="317" ArrivalDateTime="2008-10-23T11:35:00" StopQuantity="0" RPH="3" ResBookDesigCode="V"> <DepartureAirport LocationCode="LHR" /> <ArrivalAirport LocationCode="ZRH" /> <MarketingAirline Code="LX" /> </FlightSegment> <FlightSegment DepartureDateTime="2008-10-23T16:50:00" FlightNumber="2032" ArrivalDateTime="2008-10-23T19:05:00" StopQuantity="0" RPH="4" ResBookDesigCode="V"> <DepartureAirport LocationCode="ZRH" /> <ArrivalAirport LocationCode="MAD" /> <MarketingAirline Code="LX" /> </FlightSegment> </OriginDestinationOption> </OriginDestinationOptions> </AirItinerary> <AirItineraryPricingInfo> <ItinTotalFare> <TotalFare Amount="408.00" CurrencyCode="USD" DecimalPlaces="2" /> </ItinTotalFare> <PTC_FareBreakdowns> <PTC_FareBreakdown> <PassengerTypeQuantity Code="ADT" Quantity="1" /> <PassengerFare> <BaseFare Amount="138.00" CurrencyCode="EUR" DecimalPlaces="2" /> <EquivFare Amount="214.00" CurrencyCode="USD" DecimalPlaces="2" /> <Taxes> <Tax TaxCode="IVA" Amount="7.90" CurrencyCode="USD" DecimalPlaces="2" /> <Tax TaxCode="TUA" Amount="2.50" CurrencyCode="USD" DecimalPlaces="2" /> <Tax TaxCode="Qs" Amount="44.40" CurrencyCode="USD" DecimalPlaces="2" /> <Tax TaxCode="Others" Amount="139.20" CurrencyCode="USD" DecimalPlaces="2" /> </Taxes> <TotalFare Amount="408.00" CurrencyCode="USD" DecimalPlaces="2" /> </PassengerFare> </PTC_FareBreakdown> </PTC_FareBreakdowns> <FareInfos> <FareInfo> <RuleInfo> <ResTicketingRules> <AdvResTicketing LastTicketDate="2008-10-15" /> </ResTicketingRules> </RuleInfo> </FareInfo> </FareInfos> </AirItineraryPricingInfo> </PricedItinerary> </PricedItineraries> </OTA_AirLowFareSearchRS>

Important notes:

- The header of the OTA_AirLowFareSearchRS tag has an attribute SequenceNmbr whose value must be sent in the reservation request.

Page 15: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 15

- All date-time fields follows the format “YYYY-MM-DDTHH:MM:SS”, where YYYY is year, MM is month, DD is day, HH is hour, MM is minute and SS is second (T is a separator for date and time). For example: 2008-10-23T16:50:00 23th of October, 2008 at 16:50.

- Attribute DirectionInd in AirItinerary element specifies the type of this alternative. Possible values are: Outbound (outbound flights), Inbound (inbound flights) and Roundtrip (identifies travel from one point to another point and return to the original point)

- Attribute RefNumber in OriginDestinationOption must be sent in the reservation request. If an alternative is a LowCost flight, this will be noticed in Notes element, inside PricedItinerary item. This element will contain the value LC. Example:

<TotalFare Amount="381.30" CurrencyCode="USD" DecimalPlaces="2" /> </PassengerFare> </PTC_FareBreakdown> </PTC_FareBreakdowns> </AirItineraryPricingInfo> <Notes>LC</Notes> </PricedItinerary> <PricedItinerary SequenceNumber="2"> <AirItinerary> <OriginDestinationOptions>

If Amount in TotalFare element has a Service Fee included, Fees element will be specified for each passenger type. Example:

LowCost flights can also have a Credit Card Payment Fee, and this will be reflected inside ItinTotalFare element. This Fee is always included in Total Fare Amount, inside ItinTotalFare element. Example:

<PTC_FareBreakdown> <PassengerTypeQuantity Code="ADT" Quantity="1" /> <PassengerFare> <BaseFare Amount="179.00" CurrencyCode="EUR" DecimalPlaces="2" /> <EquivFare Amount="278.00" CurrencyCode="USD" DecimalPlaces="2" /> <Taxes> <Tax TaxCode="IVA" Amount="7.90" CurrencyCode="USD" DecimalPlaces="2" /> <Tax TaxCode="TUA" Amount="2.50" CurrencyCode="USD" DecimalPlaces="2" /> <Tax TaxCode="Qs" Amount="34.60" CurrencyCode="USD" DecimalPlaces="2" /> <Tax TaxCode="Others" Amount="58.30" CurrencyCode="USD" DecimalPlaces="2" /> </Taxes> <Fees> <Fee FeeCode="ServiceFee" Amount="2.00" /> </Fees> <TotalFare Amount="383.30" CurrencyCode="USD" DecimalPlaces="2" /> </PassengerFare> </PTC_FareBreakdown>

<AirItineraryPricingInfo> <ItinTotalFare> <Fees> <Fee FeeCode="CreditCardPaymentFee" Amount="11.25" /> </Fees> <TotalFare Amount="65.74" CurrencyCode="USD" DecimalPlaces="2" /> </ItinTotalFare> <PTC_FareBreakdowns>

Page 16: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 16

Reservation Request (OTA_AirBook.asmx)

Request: OTA_AirBookRQ Response: OTA_AirBookRS The message contains three parts: 1 - Itinerary data: dates, flight numbers, booking classes, etc. 2 - Price info: final price, expected price range, main passenger information, etc. 3 - Traveller info: name, address, mail, passenger type, etc. for each passenger. First and second parts have similar structure like OTA_AirLowFareSearch request.

<?xml version="1.0"?> <OTA_AirBookRQ xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchemainstance" xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_AirBookRQ.xsd" SequenceNmbr="Code123"> <POS> <Source AgentDutyCode="[email protected]"> <RequestorID Type="1" MessagePassword="pass" /> </Source> </POS> <AirItinerary DirectionInd="Roundtrip"> <OriginDestinationOptions> <OriginDestinationOption RefNumber="ref123"> <FlightSegment DepartureDateTime="2008-10-20T10:20:00" FlightNumber="2065" ArrivalDateTime="2008-10-20T12:40:00" ResBookDesigCode="E"> <DepartureAirport LocationCode="MAD" /> <ArrivalAirport LocationCode="MUC" /> <OperatingAirline Code="JK" /> <MarketingAirline Code="LH" /> </FlightSegment> <FlightSegment DepartureDateTime="2008-10-20T13:15:00" FlightNumber="4756" ArrivalDateTime="2008-10-20T14:15:00" ResBookDesigCode="E"> <DepartureAirport LocationCode="MUC" /> <ArrivalAirport LocationCode="LHR" /> <MarketingAirline Code="LH" /> </FlightSegment> </OriginDestinationOption> <OriginDestinationOption RefNumber="ref123"> <FlightSegment DepartureDateTime="2008-10-23T09:40:00" FlightNumber="4751" ArrivalDateTime="2008-10-23T12:25:00" ResBookDesigCode="L"> <DepartureAirport LocationCode="LHR" /> <ArrivalAirport LocationCode="MUC" /> <MarketingAirline Code="LH" /> </FlightSegment> <FlightSegment DepartureDateTime="2008-10-23T13:15:00" FlightNumber="2064" ArrivalDateTime="2008-10-23T15:45:00" ResBookDesigCode="T"> <DepartureAirport LocationCode="MUC" /> <ArrivalAirport LocationCode="MAD" /> <OperatingAirline Code="JK" /> <MarketingAirline Code="LH" /> </FlightSegment> </OriginDestinationOption> </OriginDestinationOptions> </AirItinerary> <PriceInfo> <ItinTotalFare>

Page 17: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 17

<TotalFare Amount="381.30" CurrencyCode="USD" DecimalPlaces="2" /> <TPA_Extensions> <ExpectedPriceRange min="375.00" max="390.00" /> <Customer> <PersonName> <GivenName>Juniper</GivenName> <Surname>Test</Surname> </PersonName> <Telephone PhoneNumber="(703)5555555"/> <Document DocID="12345678A" /> <Email>[email protected]</Email> <Address> <AddressLine>My address</AddressLine> <CityName>Palma de Mallorca</CityName> <PostalCode>07000</PostalCode> <CountryName Code="ES">Spain</CountryName> </Address> </Customer> </TPA_Extensions> </ItinTotalFare> <FareInfos> <FareInfo CurrencyCode="USD"> <FareInfo TripType="Roundtrip"> <Fare TotalFare="381.30" /> </FareInfo> </FareInfo> </FareInfos> </PriceInfo> <TravelerInfo> <AirTraveler> <PersonName> <NamePrefix>Mr</NamePrefix> <GivenName>WebService</GivenName> <Surname>Test</Surname> </PersonName> <Document DocType="2" DocID="12345678A" /> <PassengerTypeQuantity Code="ADT" /> </AirTraveler> </TravelerInfo> </OTA_AirBookRQ>

Important notes:

- Attribute SequenceNmbr must have the same value of SequenceNmbr attribute obtained in the OTA_AirLowFareSearchRS.

- Attribute RefNumber must have the same value of RefNumber attribute obtained in OTA_AirLowFareSearchRS. You have to specify RefNumber for each OriginDestinationOption.

- You must specify the names of all passengers in TraverlerInfo item, and main passenger of the booking must be in the element Customer inside TPA_Extensions. All fields shown in Customer element are mandatory.

- All fields shown inside TravelerInfo element are mandatory. - NamePrefix element must be one of the following:

o For adults: MR, MRS, MISS o For children: MSTR, MISS o For infant: INF_M (male), INF_F (female)

- Attribute Code in PassengerTypeQuantity must be specified for each traveller. - For children and infants it’s also mandatory to send Age attribute in

PassengerTypeQuantity node and BirthDate in AirTraveler node. - Attribute DocType in Document is mandatory. Valid values are:

o 1- Passport

Page 18: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 18

o 2- NIF - TotalFare node is mandatory and it has the value of the expected price with its currency.

ExpectedPriceRange node is optional, and you can indicate the accepted price range. It can be useful if you decide to make the reservation some time after making the availability search and prices may have changed. If you don’t specify ExpectedPriceRange node or one of its attributes, it will take the Amount attribute in Total. If the price of the reservation is greater or lower than the expected price, reservation won’t be made. Take these 3 cases as example: If you expect 220$ but accept a margin of 10$, you can specify a range of 0-230$ so reservation will be done if price is lower than 230$. If it costs 231$, it won’t be done. If you specify a minimum range of 0 but do not specify a maximum range, reservation will be done if price is equal or lower than 220$, the initial expected price. If it is greater, it won’t be done. If you don’t specify a range, reservation will be made if price is exactly 220$. If it costs 219$ or 221$ it won’t be done.

- If resident discount is applied, municipal residence code must be sent for each traveller (note that this municipal residence code is different than Postal Code). This code must be in PostalCode element inside Address node; CityName must also be submited. Here is an example:

<TravelerInfo> <AirTraveler> <PersonName> <NamePrefix>Mr</NamePrefix> <GivenName>WebService</GivenName> <Surname>Test</Surname> </PersonName> <Address> <CityName>Santa Cruz de Tenerife</CityName> <PostalCode>380380</PostalCode> </Address> <Document DocType="2" DocID="12345678A" /> <PassengerTypeQuantity Code="ADT" /> </AirTraveler>

Additionally if the traveler has a residence permit instead NIF, you have to specify Passport document Type in DocType attribute (DocType="1")

In some cases, you need to send the Credit Card information to pay for the booking. In that case, you must send this information like in the example below:

<PassengerTypeQuantity Code="ADT" /> </AirTraveler> </TravelerInfo> <Fulfillment> <PaymentDetails> <PaymentDetail> <PaymentCard CardCode="VI" CardNumber="41111111111111" SeriesCode="123" ExpireDate="01/10"> <CardHolderName>WebService</CardHolderName> <CardHolderSurname>Test</CardHolderSurname> </PaymentCard> </PaymentDetail> </PaymentDetails> </Fulfillment> </OTA_AirBookRQ>

Page 19: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 19

Notes: - This information is mandatory when booking LowCost flights. - All fields shown in this example are mandatory. - CardCode attribute may have the following values. However, not all are supported.

Contact Juniper for supported credit cards. o AX: American Express o CB: Carte Blanche o DC: Diners Club o DS: Discover Card o ER: enRoute o MC: Master Card o VI: Visa

- ExpireDate attribute has the MM/YY form. The response contains: flight information sent in request, booking reference and PNR locator if the booking was successful:

<?xml version="1.0"?> <OTA_AirBookRS xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchemainstance" xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_AirBookRS.xsd" > <Success /> <AirReservation ResStatus="Pag"> <AirItinerary> <OriginDestinationOptions> <OriginDestinationOption> <FlightSegment DepartureDateTime="2008-10-20T10:20:00" FlightNumber="2065" ArrivalDateTime="2008-10-20T12:40:00" ResBookDesigCode="E"> <DepartureAirport LocationCode="MAD" /> <ArrivalAirport LocationCode="MUC" /> <OperatingAirline Code="JK" /> <MarketingAirline Code="LH" /> </FlightSegment> <FlightSegment DepartureDateTime="2008-10-20T13:15:00" FlightNumber="4756" ArrivalDateTime="2008-10-20T14:15:00" ResBookDesigCode="E"> <DepartureAirport LocationCode="MUC" /> <ArrivalAirport LocationCode="LHR" /> <MarketingAirline Code="LH" /> </FlightSegment> </OriginDestinationOption> <OriginDestinationOption> <FlightSegment DepartureDateTime="2008-10-23T09:40:00" FlightNumber="4751" ArrivalDateTime="2008-10-23T12:25:00" ResBookDesigCode="L"> <DepartureAirport LocationCode="LHR" /> <ArrivalAirport LocationCode="MUC" /> <MarketingAirline Code="LH" /> </FlightSegment> <FlightSegment DepartureDateTime="2008-10-23T13:15:00" FlightNumber="2064" ArrivalDateTime="2008-10-23T15:45:00" ResBookDesigCode="T"> <DepartureAirport LocationCode="MUC" /> <ArrivalAirport LocationCode="MAD" /> <OperatingAirline Code="JK" /> <MarketingAirline Code="LH" /> </FlightSegment> </OriginDestinationOption> </OriginDestinationOptions> </AirItinerary> <PriceInfo>

Page 20: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 20

<ItinTotalFare> <TotalFare Amount="381.30" CurrencyCode="USD" DecimalPlaces="2" /> <TPA_Extensions> <Customer> <PersonName> <GivenName>Juniper</GivenName> <Surname>Test</Surname> </PersonName> <Telephone PhoneNumber="(703)5555555"/> <Document DocID="12345678A" /> <Email>[email protected]</Email> <Address> <AddressLine>My address</AddressLine> <CityName>Palma de Mallorca</CityName> <PostalCode>07000</PostalCode> <CountryName Code="ES">Spain</CountryName> </Address> </Customer> </TPA_Extensions> </ItinTotalFare> </PriceInfo> <TravelerInfo> <AirTraveler> <PersonName> <NamePrefix>Mr</NamePrefix> <GivenName>WebService</GivenName> <Surname>Test</Surname> </PersonName> <Document DocType="2" DocID="12345678A" /> <PassengerTypeQuantity Code="ADT" /> </AirTraveler> </TravelerInfo> <Ticketing TicketTimeLimit="2008-10-15T23:50:00" /> <BookingReferenceID Type="1" ID_Context="BookingRef" Id="362EYX" /> <BookingReferenceID Type="1" ID_Context="PNRLocator" Id="Z5T3HW" /> </AirReservation> </OTA_AirBookRS>

Notes:

- Element ResStatus inside AirReservation item shows the status of the booking. Possible values are:

o Can/CaC – Reservation cancelled o Con – Reservation confirmed o Tar – Reservation confirmed (if pending credit card charge) o Pag – Reservation confirmed and paid o Ini – Initialized but not confirmed

- In successful bookings you will obtain two booking references: one related to WebService (ID_Context="BookingRef") and the other one related to GDS PNR locator (ID_Context="PNRLocator"). First one is also returned if there’s an error in the booking and must be submitted when you contact support for this matter; this booking reference is what you have to send in OTA_Read and OTA_Cancel requests.

- Ticketing element contains Last Ticketing Date (TicketTimeLimit attribute) because booking must be ticketed before a certain date and time (except LowCost flights).

- If no PNRLocator has sent or price has changed but is in expected price range, a warning will be sent instead of Success element. Example:

<?xml version="1.0"?> <OTA_AirBookRS xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchemainstance" xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_AirBookRS.xsd" >

Page 21: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 21

<Warnings> <Warning Type="3" ShortText="Price changed" /> </Warnings> <AirReservation> <AirItinerary>

- If FareInfo/TPA_Extensions is present in the response, it means this flight has some adjustments related to the booking. These adjustments would be Service Fee or Direct Payment and this one means that the amount of this flight is paid directly to the provider. Example:

<PriceInfo> <ItinTotalFare> <TotalFare Amount="9.00" CurrencyCode="USD" DecimalPlaces="2" /> <TPA_Extensions> <Customer> <PersonName> <GivenName>Juniper</GivenName> <Surname>Test</Surname> </PersonName> <Telephone PhoneNumber="(703)5555555" /> <Document DocID="12345678A" /> <Email>[email protected]</Email> <Address> <AddressLine>My address</AddressLine> <CityName>Palma de Mallorca</CityName> <PostalCode>07000</PostalCode> <CountryName Code="ES">Spain</CountryName> </Address> </Customer> </TPA_Extensions> </ItinTotalFare> <FareInfos> <FareInfo CurrencyCode="USD"> <FareInfo> <Fare TotalFare="47.24" /> </FareInfo> <TPA_Extensions> <Adjustments> <Adjustment Description="Ticketing fee" Amount="9.00" /> <Adjustment Description="Direct payment" Amount="-47.24" /> </Adjustments> </TPA_Extensions> </FareInfo> </FareInfos> </PriceInfo>

- In this example the final price of this booking is 9.00 $ because the price of the flight was

47.24 $ but it has two related adjustments: one for Ticketing Fee and the other one for Direct payment; so the result is 47.24 + 9.00 - 47.24 = 9.00 $

Page 22: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 22

How to book outbound + inbound flight

OTA_AirBook service has the availability to book a combined flight (outbound + inbound flight) in same request. To allow this, there are some issues that must be clarified. Take this request as an example:

<?xml version="1.0"?> <OTA_AirBookRQ xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchemainstance" xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_AirBookRQ.xsd" SequenceNmbr="Code123"> <POS> <Source AgentDutyCode="[email protected]"> <RequestorID Type="1" MessagePassword="pass" /> </Source> </POS> <AirItinerary DirectionInd="Other"> <OriginDestinationOptions> <OriginDestinationOption RefNumber="ref246"> <FlightSegment DepartureDateTime="2008-12-20T12:20:00" ArrivalDateTime="2008-12-20T13:40:00" StopQuantity="0" FlightNumber="7646" ResBookDesigCode="O"> <DepartureAirport LocationCode="MAD" /> <ArrivalAirport LocationCode="LGW" /> <OperatingAirline Code="BA" /> <MarketingAirline Code="IB" /> </FlightSegment> </OriginDestinationOption> <OriginDestinationOption RefNumber="ref468"> <FlightSegment DepartureDateTime="2008-12-23T08:00:00" ArrivalDateTime="2008-12-23T11:30:00" StopQuantity="0" FlightNumber="7643" ResBookDesigCode="O"> <DepartureAirport LocationCode="LGW" /> <ArrivalAirport LocationCode="MAD" /> <OperatingAirline Code="BA" /> <MarketingAirline Code="IB" /> </FlightSegment> </OriginDestinationOption> </OriginDestinationOptions> </AirItinerary> <PriceInfo> <ItinTotalFare> <TotalFare Amount="134.00" CurrencyCode="USD" DecimalPlaces="2" /> <TPA_Extensions> <ExpectedPriceRange min="130.00" max="140.00" /> <Customer> <PersonName> <GivenName>Juniper</GivenName> <Surname>Test</Surname> </PersonName> <Telephone PhoneNumber="(703)5555555" /> <Document DocType="2" DocID="12345678A" /> <Email>[email protected]</Email> <Address> <AddressLine>My address</AddressLine> <CityName>Palma de Mallorca</CityName> <PostalCode>07000</PostalCode> <CountryName Code="ES">Spain</CountryName> </Address> </Customer> </TPA_Extensions>

Page 23: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 23

</ItinTotalFare> <FareInfos> <FareInfo CurrencyCode="USD"> <FareInfo TripType="Outbound"> <Fare TotalFare="58.07" /> </FareInfo> </FareInfo> <FareInfo CurrencyCode="USD"> <FareInfo TripType="Inbound"> <Fare TotalFare="75.93" /> </FareInfo> </FareInfo> </FareInfos> </PriceInfo> <TravelerInfo> <AirTraveler> <PersonName> <NamePrefix>Mr</NamePrefix> <GivenName>WebService</GivenName> <Surname>Test</Surname> </PersonName> <Document DocType="2" DocID="12345678A" /> <PassengerTypeQuantity Code="ADT" /> </AirTraveler> </TravelerInfo> </OTA_AirBookRQ>

- The first thing you have to take in account is that DirectionInd in AirItinerary element must

have the value Other. - Note that RefNumber is different for each OriginDestinationOption. You have to send the

same RefNumber obtained in OTA_AirLowFareSearchRS for each flight (outbound and inbound)

- TotalFare in ItinTotalFare element will have the sum of total fares of each flight (outbound + inbound). This amount will also contain all the fees that can be applied (CreditCardPaymentFee, ServiceFee, etc.)

- FareInfos element must be send with total fare amount of each flight. Additionally each FareInfo must have the attribute TripType to indicate which is the Outbound flight and which the Inbound. CurrencyCode attribute is mandatory.

- TravelerInfo element doesn’t has any particularity for this kind of request. The response for this request has a couple of things that must be explained:

<?xml version="1.0"?> <OTA_AirBookRS xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchemainstance" xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_AirBookRS.xsd" > <Success /> <AirReservation ResStatus="Pag"> <AirItinerary DirectionInd="Other"> <OriginDestinationOptions> <OriginDestinationOption> <FlightSegment DepartureDateTime="2008-12-20T12:20:00" ArrivalDateTime="2008-12-20T13:40:00" StopQuantity="0" FlightNumber="7646" ResBookDesigCode="O"> <DepartureAirport LocationCode="MAD" /> <ArrivalAirport LocationCode="LGW" /> <OperatingAirline Code="BA" /> <MarketingAirline Code="IB" /> </FlightSegment> </OriginDestinationOption>

Page 24: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 24

<OriginDestinationOption> <FlightSegment DepartureDateTime="2008-12-23T08:00:00" ArrivalDateTime="2008-12-23T11:30:00" StopQuantity="0" FlightNumber="7643" ResBookDesigCode="O"> <DepartureAirport LocationCode="LGW" /> <ArrivalAirport LocationCode="MAD" /> <OperatingAirline Code="BA" /> <MarketingAirline Code="IB" /> </FlightSegment> </OriginDestinationOption> </OriginDestinationOptions> </AirItinerary> <PriceInfo> <ItinTotalFare> <TotalFare Amount="134.00" CurrencyCode="USD" DecimalPlaces="2" /> <TPA_Extensions> <Customer> <PersonName> <GivenName>Juniper</GivenName> <Surname>Test</Surname> </PersonName> <Telephone PhoneNumber="(703)5555555" /> <Document DocID="12345678A" /> <Email>[email protected]</Email> <Address> <AddressLine>My address</AddressLine> <CityName>Palma de Mallorca</CityName> <PostalCode>07000</PostalCode> <CountryName Code="ES">Spain</CountryName> </Address> </Customer> </TPA_Extensions> </ItinTotalFare> <FareInfos> <FareInfo CurrencyCode="USD"> <FareInfo> <Fare TotalFare="58.07" /> </FareInfo> </FareInfo> <FareInfo CurrencyCode="USD"> <FareInfo> <Fare TotalFare="75.93" /> </FareInfo> </FareInfo> </FareInfos> </PriceInfo> <TravelerInfo> <AirTraveler> <PersonName> <NamePrefix>Mr</NamePrefix> <GivenName>WebService</GivenName> <Surname>Test</Surname> </PersonName> <Document DocType="2" DocID="12345678A" /> <PassengerTypeQuantity Code="ADT" /> </AirTraveler> </TravelerInfo> <Ticketing TicketTimeLimit="2008-10-15T23:50:00" /> <BookingReferenceID ID="9DK7X5" Type="1" ID_Context="BookingRef" /> <BookingReferenceID ID="V29RCM" Type="1" ID_Context="PNRLocator_Outbound" /> <BookingReferenceID ID="V29S8A" Type="1" ID_Context="PNRLocator_Inbound" />

Page 25: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 25

</AirReservation> </OTA_AirBookRS>

- Now you will obtain 3 booking references:

o One related to WebService (ID_Context="BookingRef") o The second related to GDS PNR locator for outbound flight

(ID_Context="PNRLocator_Outbound") o And the third one related to GDS PNR locator for inbound flight

(ID_Context="PNRLocator_Inbound") - If TicketTimeLimit is present in the response, any of the flights must be ticketed before

this date and time (maybe just one of them because the other one is a LowCost flight).

Page 26: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 26

Booking Cancelation (OTA_Cancel.asmx)

Request: OTA_CancelRQ Response: OTA_CancelRS In this message you need to send the booking number and the authentication in order to cancel a booking.

<?xml version="1.0" encoding="UTF-8"?> <OTA_CancelRQ xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_CancelRQ.xsd" PrimaryLangID="es"> <POS> <Source AgentDutyCode="[email protected]"> <RequestorID Type="1" MessagePassword="pass" /> </Source> </POS> <UniqueID Type="14" ID="362EYX" /> </OTA_CancelRQ>

The webservice will respond with a success code if everything works well. Otherwise and if the booking cannot be canceled (maybe because it was already canceled) the webservice will respond with an error code.

<?xml version="1.0"?> <OTA_CancelRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.opentravel.org/OTA/2003/05"> <Success /> <UniqueID /> </OTA_CancelRS>

Page 27: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 27

Read a reservation (OTA_Read.asmx)

Request: OTA_ReadRQ Response: OTA_ResRetrieveRS In this message you need to send the booking number and the authentication in order to retrieve all booking information.

<?xml version="1.0" encoding="UTF-8"?> <OTA_ReadRQ xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_ReadRQ.xsd" PrimaryLangID="es"> <POS> <Source AgentDutyCode="[email protected]"> <RequestorID Type="1" MessagePassword="test" /> </Source> </POS> <ReadRequests> <ReadRequest> <UniqueID Type="14" ID="362EYX"/> </ReadRequest> </ReadRequests> </OTA_ReadRQ>

The response is similar to the OTA_AirBookRS obtained in a previous step. This is an example of OTA_ResRetrieveRes:

<?xml version="1.0"?> <OTA_ResRetrieveRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" Version="0" xmlns="http://www.opentravel.org/OTA/2003/05"> <Success /> <ReservationsList> <AirReservation ResStatus="Pag"> <AirItinerary DirectionInd="Outbound"> <OriginDestinationOptions> <OriginDestinationOption> <FlightSegment DepartureDateTime="2008-10-21T10:50:00" ArrivalDateTime="2008-10-21T12:15:00" StopQuantity="0" FlightNumber="2202" ResBookDesigCode="O"> <DepartureAirport LocationCode="MAD" /> <ArrivalAirport LocationCode="LTN" /> <OperatingAirline Code="BA" /> <MarketingAirline Code="IB" /> </FlightSegment> </OriginDestinationOption> </OriginDestinationOptions> </AirItinerary> <PriceInfo> <ItinTotalFare> <TotalFare Amount="66.74" CurrencyCode="USD" DecimalPlaces="2" /> <TPA_Extensions> <Customer> <PersonName> <GivenName>Juniper</GivenName> <Surname>Test</Surname> </PersonName> <Telephone PhoneNumber="(703)5555555" /> <Document DocID="12345678A" />

Page 28: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 28

<Email>[email protected]</Email> <Address> <AddressLine>My address</AddressLine> <CityName>Palma de Mallorca</CityName> <PostalCode>07000</PostalCode> <CountryName Code="ES">Spain</CountryName> </Address> </Customer> </TPA_Extensions> </ItinTotalFare> <FareInfos> <FareInfo CurrencyCode="USD"> <FareInfo> <Fare TotalFare="57.74" /> </FareInfo> <TPA_Extensions> <Adjustments> <Adjustment Description="Ticketing Fee" Amount="9.00" /> </Adjustments> </TPA_Extensions> </FareInfo> </FareInfos> </PriceInfo> <TravelerInfo> <AirTraveler> <PersonName> <NamePrefix>Mr</NamePrefix> <GivenName>WebService</GivenName> <Surname>Test</Surname> </PersonName> <Document DocType="2" DocID="12345678A" /> <PassengerTypeQuantity Code="ADT" /> </AirTraveler> </TravelerInfo> <Ticketing TicketTimeLimit="2008-10-15T23:50:00" /> <BookingReferenceID ID="362EYX" Type="1" ID_Context="BookingRef" /> <BookingReferenceID ID="TA9L8I " Type="1" ID_Context="PNRLocator" /> </AirReservation> </ReservationsList> </OTA_ResRetrieveRS>

Page 29: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 29

Retrieve Fare Rules (OTA_AirRules.asmx)

Request: OTA_AirRulesRQ Response: OTA_AirRulesRS With this message you can obtain the fare rules for specific flight. In this message you need to send the RefNumber obtained in OTA_AirLowFareSearch request and all the segments for the flight you want to obtain those fare rules. If you have a Roundtrip flight with the same RefNumber for each OriginDestinationOption, you can send all segments in the same request (like in the following example). But you have to make two different OTA_AirRules requests if you want the fare rules for an outbound and inbound flight.

<?xml version="1.0"?> <OTA_AirRulesRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" Version="0" PrimaryLangID="en" xmlns="http://www.opentravel.org/OTA/2003/05"> <POS> <Source AgentDutyCode="[email protected]"> <RequestorID Type="1" MessagePassword="pass" /> </Source> </POS> <RuleReqInfos RefNumber="ref123"> <RuleReqInfo> <DepartureDate>2009-11-10T11:15:00</DepartureDate> <DepartureAirport LocationCode="MAD"/> <ArrivalAirport LocationCode="JFK"/> <FilingAirline Code="DL"/> <FlightNumber>127</FlightNumber> <FareReference ResBookDesigCode="M"/> </RuleReqInfo> <RuleReqInfo> <DepartureDate>2009-11-10T19:30:00</DepartureDate> <DepartureAirport LocationCode="JFK"/> <ArrivalAirport LocationCode="MEX"/> <FilingAirline Code="DL"/> <FlightNumber>8019</FlightNumber> <FareReference ResBookDesigCode="U"/> </RuleReqInfo> <RuleReqInfo> <DepartureDate>2009-11-13T13:02:00</DepartureDate> <DepartureAirport LocationCode="MEX"/> <ArrivalAirport LocationCode="JFK"/> <FilingAirline Code="DL"/> <FlightNumber>8018</FlightNumber> <FareReference ResBookDesigCode="U"/> </RuleReqInfo> <RuleReqInfo> <DepartureDate>2009-11-13T18:40:00</DepartureDate> <DepartureAirport LocationCode="JFK"/> <ArrivalAirport LocationCode="MAD"/> <FilingAirline Code="DL"/> <FlightNumber>126</FlightNumber> <FareReference ResBookDesigCode="M"/> </RuleReqInfo> <FareInfo> <PTC Code="ADT" Quantity="1"/> </FareInfo> </RuleReqInfos> </OTA_AirRulesRQ>

Page 30: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 30

All the fields specified in the example are mandatory. The Code attribute in the FilingAirline element must be the same code as the MarketingAirline element in OTA_AirLowFareSearchRS, not the OperatingAirline. The response will contain different paragraphs with the fare rules description. This is an example of OTA_AirRulesRS:

<?xml version="1.0"?> <OTA_AirRulesRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" Version="0" xmlns="http://www.opentravel.org/OTA/2003/05"> <Success /> <FareRuleResponseInfo> <FareRules> <SubSection SubTitle="0. APPLICATION AND OTHER CONDITIONS"> <Paragraph> <Text>RULE - 001/JV01</Text> </Paragraph> <Paragraph> <Text>UNLESS OTHERWISE SPECIFIED</Text> </Paragraph> <Paragraph> <Text>1ST LEVEL INSTANT PURCHASE FARES FROM AREA 2 TO AREA 1</Text> </Paragraph> <Paragraph> <Text> APPLICATION</Text> </Paragraph> <Paragraph> <Text> AREA</Text> </Paragraph> <Paragraph> <Text> THESE FARES APPLY</Text> </Paragraph> <Paragraph> <Text> FROM AREA 2 TO AREA 1.</Text> </Paragraph> <Paragraph> <Text> CLASS OF SERVICE</Text> </Paragraph> <Paragraph> <Text> THESE FARES APPLY FOR ECONOMY CLASS SERVICE.</Text> </Paragraph> <Paragraph> <Text> TYPES OF TRANSPORTATION</Text> </Paragraph> <Paragraph> <Text> FARES GOVERNED BY THIS RULE CAN BE USED TO CREATE</Text> </Paragraph> <Paragraph> <Text> ROUND-TRIP/SINGLE OPEN-JAW/DOUBLE OPEN-JAW JOURNEYS.</Text> </Paragraph> <Paragraph> <Text> CAPACITY LIMITATIONS</Text> </Paragraph> <Paragraph> <Text> THE CARRIER SHALL LIMIT THE NUMBER OF PASSENGERS CARRIED</Text> </Paragraph>

Page 31: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 31

<Paragraph> <Text> ON ANY ONE FLIGHT AT FARES GOVERNED BY THIS RULE AND SUCH</Text> </Paragraph> <Paragraph> <Text> FARES WILL NOT NECESSARILY BE AVAILABLE ON ALL FLIGHTS.</Text> </Paragraph> <Paragraph> <Text> THE NUMBER OF SEATS WHICH THE CARRIER SHALL MAKE</Text> </Paragraph> <Paragraph> <Text> AVAILABLE ON A GIVEN FLIGHT WILL BE DETERMINED BY THE</Text> </Paragraph> <Paragraph> <Text> CARRIERS BEST JUDGMENT</Text> </Paragraph> </SubSection> <SubSection SubTitle="4. FLIGHT APPLICATION"> <Paragraph> <Text>UNLESS OTHERWISE SPECIFIED</Text> </Paragraph> <Paragraph> <Text> THE FARE COMPONENT MUST NOT BE ON</Text> </Paragraph> <Paragraph> <Text> ONE OR MORE OF THE FOLLOWING</Text> </Paragraph> <Paragraph> <Text> ANY BA FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY EI FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY LH FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY LX FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY LY FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY MS FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY OS FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY OA FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY AA FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY US FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY UA FLIGHT</Text> </Paragraph>

Page 32: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 32

<Paragraph> <Text> ANY FC FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY UU FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY DT FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY PK FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY JS FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY FG FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY GA FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY QZ FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY 3Y FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY RI FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY MZ FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY 7P FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY AW FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY RW FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY NV FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY DC FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY QH FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY R8 FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY O3 FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY I7 FLIGHT</Text> </Paragraph>

Page 33: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 33

<Paragraph> <Text> ANY ZC FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY Q4 FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY EO FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY W5 FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY UF FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY KF FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY C2 FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY OD FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY K9 FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY X7 FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY FT FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY MQ FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY 2S FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY Z7 FLIGHT</Text> </Paragraph> <Paragraph> <Text> ANY IB FLIGHT OPERATED BY BA</Text> </Paragraph> <Paragraph> <Text> ANY AA FLIGHT OPERATED BY BA</Text> </Paragraph> <Paragraph> <Text> ANY UA FLIGHT OPERATED BY LH</Text> </Paragraph> <Paragraph> <Text> ANY US FLIGHT OPERATED BY LH</Text> </Paragraph> <Paragraph> <Text> ANY LO FLIGHT OPERATED BY LH.</Text> </Paragraph> <Paragraph> <Text> AND</Text> </Paragraph>

Page 34: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 34

<Paragraph> <Text> THE FARE COMPONENT MUST NOT BE ON</Text> </Paragraph> <Paragraph> <Text> ONE OR MORE OF THE FOLLOWING</Text> </Paragraph> <Paragraph> <Text> ANY OS FLIGHT OPERATED BY LH</Text> </Paragraph> <Paragraph> <Text> ANY SA FLIGHT OPERATED BY LH</Text> </Paragraph> <Paragraph> <Text> ANY SK FLIGHT OPERATED BY LH</Text> </Paragraph> <Paragraph> <Text> ANY SQ FLIGHT OPERATED BY LH</Text> </Paragraph> <Paragraph> <Text> ANY TK FLIGHT OPERATED BY LH</Text> </Paragraph> <Paragraph> <Text> ANY LH FLIGHT OPERATED BY UA</Text> </Paragraph> <Paragraph> <Text> ANY LH FLIGHT OPERATED BY US</Text> </Paragraph> <Paragraph> <Text> ANY AA FLIGHT OPERATED BY LY.</Text> </Paragraph> </SubSection> <SubSection SubTitle="5. ADVANCE RES/TICKETING"> <Paragraph> <Text>UNLESS OTHERWISE SPECIFIED</Text> </Paragraph> <Paragraph> <Text> RESERVATIONS ARE REQUIRED FOR ALL SECTORS.</Text> </Paragraph> <Paragraph> <Text> WHEN RESERVATIONS ARE MADE AT LEAST 17 DAYS BEFORE</Text> </Paragraph> <Paragraph> <Text> DEPARTURE TICKETING MUST BE COMPLETED WITHIN 7 DAYS AFTER</Text> </Paragraph> <Paragraph> <Text> RESERVATIONS ARE MADE.</Text> </Paragraph> <Paragraph> <Text> OR - RESERVATIONS ARE REQUIRED FOR ALL SECTORS.</Text> </Paragraph> <Paragraph> <Text> WHEN RESERVATIONS ARE MADE AT LEAST 5 DAYS BEFORE</Text> </Paragraph> <Paragraph> <Text> DEPARTURE TICKETING MUST BE COMPLETED WITHIN 72 HOURS</Text> </Paragraph> <Paragraph> <Text> AFTER RESERVATIONS ARE MADE.</Text>

Page 35: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 35

</Paragraph> <Paragraph> <Text> OR - RESERVATIONS ARE REQUIRED FOR ALL SECTORS.</Text> </Paragraph> <Paragraph> <Text> TICKETING MUST BE COMPLETED WITHIN 24 HOURS AFTER</Text> </Paragraph> <Paragraph> <Text> RESERVATIONS ARE MADE.</Text> </Paragraph> </SubSection> <SubSection SubTitle="6. MINIMUM STAY"> <Paragraph> <Text>UNLESS OTHERWISE SPECIFIED</Text> </Paragraph> <Paragraph> <Text> TRAVEL FROM LAST INTERNATIONAL STOPOVER MUST COMMENCE NO</Text> </Paragraph> <Paragraph> <Text> EARLIER THAN THE FIRST SUN AFTER DEPARTURE OF THE FIRST</Text> </Paragraph> <Paragraph> <Text> INTERNATIONAL SECTOR</Text> </Paragraph> <Paragraph> <Text> OR - TRAVEL FROM LAST INTERNATIONAL STOPOVER MUST COMMENCE</Text> </Paragraph> <Paragraph> <Text> NO EARLIER THAN 3 DAYS AFTER DEPARTURE OF THE FIRST</Text> </Paragraph> <Paragraph> <Text> INTERNATIONAL SECTOR.</Text> </Paragraph> </SubSection> <SubSection SubTitle="7. MAXIMUM STAY"> <Paragraph> <Text>UNLESS OTHERWISE SPECIFIED</Text> </Paragraph> <Paragraph> <Text> TRAVEL FROM LAST STOPOVER MUST COMMENCE NO LATER THAN 12</Text> </Paragraph> <Paragraph> <Text> MONTHS AFTER DEPARTURE FROM FARE ORIGIN.</Text> </Paragraph> </SubSection> <SubSection SubTitle="8. STOPOVERS"> <Paragraph> <Text>UNLESS OTHERWISE SPECIFIED NOTE - GENERAL RULE DOES NOT</Text> </Paragraph> <Paragraph> <Text>APPLY</Text> </Paragraph> <Paragraph> <Text> 2 STOPOVERS PERMITTED - 1 IN EACH DIRECTION IN NYC/DTT/</Text> </Paragraph> <Paragraph>

Page 36: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 36

<Text> ATL/PAR/AMS AT EUR 75.00 EACH.</Text> </Paragraph> </SubSection> <SubSection SubTitle="9. TRANSFERS"> <Paragraph> <Text>UNLESS OTHERWISE SPECIFIED</Text> </Paragraph> <Paragraph> <Text> UNLIMITED TRANSFERS PERMITTED ON THE FARE COMPONENT</Text> </Paragraph> <Paragraph> <Text> ONLINE ON THE PRIMARY CARRIER.</Text> </Paragraph> <Paragraph> <Text> AND - 1 TRANSFER PERMITTED IN EACH DIRECTION FREE</Text> </Paragraph> <Paragraph> <Text> INTERLINE INCLUDING THE PRIMARY CARRIER</Text> </Paragraph> <Paragraph> <Text> FREE OUTSIDE THE UNITED STATES IN EACH DIRECTION</Text> </Paragraph> <Paragraph> <Text> FARE BREAK SURFACE SECTORS NOT PERMITTED AND</Text> </Paragraph> <Paragraph> <Text> EMBEDDED SURFACE SECTORS PERMITTED ON THE FARE</Text> </Paragraph> <Paragraph> <Text> COMPONENT.</Text> </Paragraph> </SubSection> <SubSection SubTitle="10. PERMITTED COMBINATIONS"> <Paragraph> <Text>UNLESS OTHERWISE SPECIFIED</Text> </Paragraph> <Paragraph> <Text> DOUBLE OPEN JAWS NOT PERMITTED.</Text> </Paragraph> <Paragraph> <Text> ADD-ONS PERMITTED.</Text> </Paragraph> <Paragraph> <Text> END-ON-END</Text> </Paragraph> <Paragraph> <Text> END-ON-END COMBINATIONS PERMITTED. VALIDATE ALL FARE</Text> </Paragraph> <Paragraph> <Text> COMPONENTS.</Text> </Paragraph> <Paragraph> <Text> PROVIDED -</Text> </Paragraph> <Paragraph> <Text> COMBINATIONS ARE FOR CARRIER KL/AF/AZ/OK/NW/DL/AS/QX</Text> </Paragraph> <Paragraph> <Text> OPEN JAWS/ROUND TRIPS/CIRCLE TRIPS</Text> </Paragraph>

Page 37: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 37

<Paragraph> <Text> FARES MAY BE COMBINED ON A HALF ROUND TRIP BASIS</Text> </Paragraph> <Paragraph> <Text> -TO FORM SINGLE OPEN JAWS</Text> </Paragraph> <Paragraph> <Text> -TO FORM ROUND TRIPS EXCEPT FOR AROUND-THE-WORLD FARES</Text> </Paragraph> <Paragraph> <Text> -TO FORM CIRCLE TRIPS EXCEPT FOR AROUND-THE-WORLD FARES.</Text> </Paragraph> <Paragraph> <Text> PROVIDED -</Text> </Paragraph> <Paragraph> <Text> COMBINATIONS ARE WITH ANY REGULAR APEX/APEX</Text> </Paragraph> <Paragraph> <Text> NONREFUNDABLE/SUPER/SPECIAL APEX/ROUND TRIP INSTANT</Text> </Paragraph> <Paragraph> <Text> PURCHASE/INSTANT PURCHASE NONREFUNDABLE/SUPER/SPECIAL</Text> </Paragraph> <Paragraph> <Text> INSTANT PURCHASE/REGULAR EXCURSION/SECOND LEVEL SUPER/</Text> </Paragraph> <Paragraph> <Text> SPECIAL APEX/3RD LEVEL ADVANCE PURCHASE/INSTANT</Text> </Paragraph> <Paragraph> <Text> PURCHASE 2ND LEVEL/INSTANT PURCHASE NONREF 2ND LEVEL/</Text> </Paragraph> <Paragraph> <Text> INSTANT PURCHASE 3RD LEVEL/ADVANCE PURCHASE 2ND LEVEL/</Text> </Paragraph> <Paragraph> <Text> 5TH LEVEL INSTANT PURCHASE/SUPER INSTANT PURCHASE 2ND</Text> </Paragraph> <Paragraph> <Text> LEVEL/4TH LEVEL INSTANT PURCHASE-TYPE FARES FOR CARRIER</Text> </Paragraph> <Paragraph> <Text> KL/AF/AZ/OK/NW/DL/AS/QX IN ANY RULE IN TARIFF</Text> </Paragraph> <Paragraph> <Text> IPRA - BETWEEN USA/CA-AREA 2/3 AND GUAM-AREA 2</Text> </Paragraph> <Paragraph> <Text> IPRAI - BETWEEN THE USA/CANADA-AREA 2/3 VIA ATL</Text> </Paragraph> <Paragraph>

Page 38: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 38

<Text> IPRSAA2 - BETWEEN THE WESTERN HEMISPHERE-AREA 2 VIA</Text> </Paragraph> <Paragraph> <Text> ATL.</Text> </Paragraph> <Paragraph> <Text> COMBINATIONS ARE WITH ANY FARE FOR CARRIER DL/NW/AF/KL</Text> </Paragraph> <Paragraph> <Text> IN RULE 4444 IN TARIFF</Text> </Paragraph> <Paragraph> <Text> ATDLR - BETWEEN AREA 1-AREA 2/3 AND GUAM-AREA 2</Text> </Paragraph> <Paragraph> <Text> TAPVR - BETWEEN AREA 1-AREA 2/3 AND GUAM-AREA 2.</Text> </Paragraph> <Paragraph> <Text> NOTE - THE CITY PAIRS BELOW ARE CONSIDERED THE SAME POINT-</Text> </Paragraph> <Paragraph> <Text> BWI-WAS FLL-MIA OAK-SFO OAK-SJC SFO-SJC LAX-ONT</Text> </Paragraph> <Paragraph> <Text> LAX-BUR LAX-LGB LAX-SNA ONT-BUR ONT-LGB ONT-SNA</Text> </Paragraph> <Paragraph> <Text> BUR-LGB BUR-SNA LGB-SNA NYC-EWR</Text> </Paragraph> </SubSection> <SubSection SubTitle="12. SURCHARGES"> <Paragraph> <Text>BETWEEN THE UNITED STATES AND SPAIN AND CANARY ISLANDS</Text> </Paragraph> <Paragraph> <Text> IF INFANT 0-1 WITHOUT A SEAT.</Text> </Paragraph> <Paragraph> <Text> THERE IS NO CHARGE FOR TRAVEL PER DIRECTION.</Text> </Paragraph> <Paragraph> <Text> AND - ORIGINATING SPAIN AND CANARY ISLANDS -</Text> </Paragraph> <Paragraph> <Text> THERE IS NO CHARGE FOR TRAVEL PER DIRECTION.</Text> </Paragraph> <Paragraph> <Text> NOTE -</Text> </Paragraph> <Paragraph> <Text> YQ FEE MAY APPLY</Text> </Paragraph> </SubSection> <SubSection SubTitle="16. PENALTIES"> <Paragraph> <Text>UNLESS OTHERWISE SPECIFIED NOTE - RULE JVR2 IN IPRG</Text> </Paragraph> <Paragraph>

Page 39: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 39

<Text>APPLIES</Text> </Paragraph> <Paragraph> <Text>UNLESS OTHERWISE SPECIFIED</Text> </Paragraph> <Paragraph> <Text> CANCELLATIONS</Text> </Paragraph> <Paragraph> <Text> CHARGE EUR 200.00.</Text> </Paragraph> <Paragraph> <Text> WAIVED FOR ILLNESS OR DEATH OF PASSENGER OR FAMILY</Text> </Paragraph> <Paragraph> <Text> MEMBER.</Text> </Paragraph> <Paragraph> <Text> NOTE -</Text> </Paragraph> <Paragraph> <Text> 1. FARES COMBINED ON A TKT FROM DIFF RULES WITH</Text> </Paragraph> <Paragraph> <Text> SAME OR DIFF CANCELLATION FEES --APPLY HIGHEST</Text> </Paragraph> <Paragraph> <Text> FEE OF THE CANCELLED ITIN AND REFUND ANY REFUND</Text> </Paragraph> <Paragraph> <Text> -ABLE FARES AND NON-REFUNDABLE FARE AMOUNT LESS</Text> </Paragraph> <Paragraph> <Text> CANCELLATION FEE WILL BE RETURNED AS A NON-REF</Text> </Paragraph> <Paragraph> <Text> VOUCHER FOR TVL VIA DL ONLY</Text> </Paragraph> <Paragraph> <Text> 2. ILLNESS/DEATH WAIVER MUST BE SUBSTANTIATED BY</Text> </Paragraph> <Paragraph> <Text> A VALID MEDICAL/DEATH CERTIFICATE</Text> </Paragraph> <Paragraph> <Text> 3. CANCELLATION FEE DOES NOT APPLY TO INFANTS</Text> </Paragraph> <Paragraph> <Text> UNDER 2 NOT OCCUPYING A SEAT.</Text> </Paragraph> <Paragraph> <Text> CHANGES</Text> </Paragraph> <Paragraph> <Text> ANY TIME</Text> </Paragraph> <Paragraph> <Text> CHARGE EUR 100.00.</Text> </Paragraph> <Paragraph>

Page 40: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 40

<Text> CHILD/INFANT DISCOUNTS APPLY.</Text> </Paragraph> <Paragraph> <Text> NOTE -</Text> </Paragraph> <Paragraph> <Text> -ALL TKTS MUST BE REISSUED</Text> </Paragraph> <Paragraph> <Text> -CHANGE FEE DOES NOT APPLY TO INFANTS UNDER 2 NOT</Text> </Paragraph> <Paragraph> <Text> OCCUPYING A SEAT</Text> </Paragraph> <Paragraph> <Text> -SEE /CHILD DISCOUNT/ IN FARE RULE TO DETERMINE</Text> </Paragraph> <Paragraph> <Text> IF CHILD DISCOUNTS APPLY</Text> </Paragraph> <Paragraph> <Text> -CHGS RESULTING IN A HIGHER FARE MUST BE ADD-</Text> </Paragraph> <Paragraph> <Text> COLLECTED AT THE TIME OF REISSUE</Text> </Paragraph> <Paragraph> <Text> -MUST COMPLETE TVL BY 1 YR FROM THE DATE OF</Text> </Paragraph> <Paragraph> <Text> COMMENCEMENT OF TVL</Text> </Paragraph> <Paragraph> <Text> -FARES IN DIFF RULES WITH SAME OR DIFF CHG FEE -</Text> </Paragraph> <Paragraph> <Text> APPLY THE HIGHEST FEE OF ANY CHGD FARE COMPONENT</Text> </Paragraph> <Paragraph> <Text> ON THE TKT</Text> </Paragraph> <Paragraph> <Text> -THE CHG FEE OR ITS EQUIV WILL BE CONVERTED AT</Text> </Paragraph> <Paragraph> <Text> THE BANK RATE AT TIME OF REISSUE</Text> </Paragraph> <Paragraph> <Text> -FOR CHGS DUE TO ILLNESS OR DEATH OF PSGR/FAMILY</Text> </Paragraph> <Paragraph> <Text> MEMBER SEE INTL GEN. RULE 65 FOR PROVISIONS</Text> </Paragraph> <Paragraph> <Text> .</Text> </Paragraph> <Paragraph> <Text> TICKET UPGRADE PROCEDURES</Text> </Paragraph> <Paragraph>

Page 41: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 41

<Text> VALUE OF TKT LESS CHANGE FEE MAY BE APPLIED TO-</Text> </Paragraph> <Paragraph> <Text> WARD PURCHASE OF A HIGHER FARE-PAY CHG FEE AND</Text> </Paragraph> <Paragraph> <Text> ANY DIFF BETWEEN ORIGINAL AND RECALCULATED FARES</Text> </Paragraph> <Paragraph> <Text> IF UPGD TO ECONOMY-EU/ER OR BUSINESS-BU/BR OR</Text> </Paragraph> <Paragraph> <Text> FIRST-FU/FR OR IF ER TYPE FARE UPG TO BUSINESS-</Text> </Paragraph> <Paragraph> <Text> BU/BR OR FIRST-FU/FR TYPE FARE CHG FEE WILL NOT</Text> </Paragraph> <Paragraph> <Text> BE ASSESSED. ALL RULE PROVISIONS OF NEW FARE</Text> </Paragraph> <Paragraph> <Text> MUST BE MET.</Text> </Paragraph> <Paragraph> <Text> .</Text> </Paragraph> <Paragraph> <Text> TICKET DOWNGRADE PROCEDURES</Text> </Paragraph> <Paragraph> <Text> PSGRS DOWNGRADING FARES MUST KEEP ORIGINALLY</Text> </Paragraph> <Paragraph> <Text> BOOKED ITN-NO CHG TO DATE/TIME/ORG/DEST. ALL</Text> </Paragraph> <Paragraph> <Text> RULE PROVISIONS OF NEW FARE MUST BE MET.</Text> </Paragraph> <Paragraph> <Text> CHG FEE WILL BE ASSESSED.</Text> </Paragraph> <Paragraph> <Text> .</Text> </Paragraph> <Paragraph> <Text> TICKET REISSUE PROCEDURES</Text> </Paragraph> <Paragraph> <Text> 1. CHGS TO OUTBOUND PORTION OF UNUSED TKTS</Text> </Paragraph> <Paragraph> <Text> A. ISSUE NEW TKT USING CURRENT FARES AND IROE</Text> </Paragraph> <Paragraph> <Text> APPLICABLE. VERIFY ALL FARE RULES.</Text> </Paragraph> <Paragraph> <Text> B. VALUE OF ORIGINAL TKT LESS CHG FEE MAY BE</Text> </Paragraph> <Paragraph>

Page 42: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 42

<Text> APPLIED TOWARDS PURCHASE OF NEW TKT.</Text> </Paragraph> <Paragraph> <Text> 2. CHGS TO CONTINUING/RETURN OF UNUSED TKTS</Text> </Paragraph> <Paragraph> <Text> A. ATTEMPT TO KEEP THE FARES AS TKTD</Text> </Paragraph> <Paragraph> <Text> -NOT CHG ORG/DSTN OF ANY FARE COMPONENT</Text> </Paragraph> <Paragraph> <Text> -MUST KEEP THE ORIGINAL FARES AS TKTD</Text> </Paragraph> <Paragraph> <Text> -USE HISTORICAL FARES IN EFFECT ON DATE OF</Text> </Paragraph> <Paragraph> <Text> ORIGINAL TKT ISSUE FOR ALL RULE VALIDATION.</Text> </Paragraph> <Paragraph> <Text> B. REPRICE KEEPING OUTBOUND FARES AND REPLACING</Text> </Paragraph> <Paragraph> <Text> CONTINUING/RETURN FARES USING HISTORICAL AND</Text> </Paragraph> <Paragraph> <Text> MODIFIED ADVANCE PURCHASE</Text> </Paragraph> <Paragraph> <Text> -NO CHG TO ORG/DSTN OF FIRST FARE COMPONENT</Text> </Paragraph> <Paragraph> <Text> -USE HISTORICAL FARES IN EFFECT ON ORIGINAL</Text> </Paragraph> <Paragraph> <Text> ISSUE DATE</Text> </Paragraph> <Paragraph> <Text> -REPLACEMENT FARES MUST BE EQUAL/HIGHER FARE</Text> </Paragraph> <Paragraph> <Text> TYPE</Text> </Paragraph> <Paragraph> <Text> -MODIFIED ADVANCE PURCHASE-DETERMINE APPLIC.</Text> </Paragraph> <Paragraph> <Text> ADV PURCHASE BY CALCULATING NUMBER OF DAYS</Text> </Paragraph> <Paragraph> <Text> BETWEEN ORIGINAL TKT ISSUE DATE AND DATE OF</Text> </Paragraph> <Paragraph> <Text> DPTR OF FIRST FLT SEGMENT. THE ADV PURCHASE</Text> </Paragraph> <Paragraph> <Text> OF REPLACEMENT FARES MUST BE EQUAL OR LESS</Text> </Paragraph> <Paragraph>

Page 43: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 43

<Text> THAN THIS NUMBER.</Text> </Paragraph> <Paragraph> <Text> -ALL RULE DATA MUST BE VERIFIED</Text> </Paragraph> <Paragraph> <Text> C. ISSUE NEW TKT - CANCEL/START OVER</Text> </Paragraph> <Paragraph> <Text> -USE CURRENT FARES/VERIFY ALL FARE RULES</Text> </Paragraph> <Paragraph> <Text> -VALUE OF ORIGINAL TKT LESS CHG FEE MAY BE</Text> </Paragraph> <Paragraph> <Text> APPLIED TOWARD PURCHASE OF A NEW TKT.</Text> </Paragraph> <Paragraph> <Text> 3. CHGS TO PARTIALLY USED TKTS-OPTIONS</Text> </Paragraph> <Paragraph> <Text> A. ATTEMPT TO KEEP THE FARES AS TKTD</Text> </Paragraph> <Paragraph> <Text> -NO CHG ORG/DSTN OF ANY FARE COMPONENT</Text> </Paragraph> <Paragraph> <Text> -MUST KEEP ALL OF THE ORIGINAL FARE AS TKTD.</Text> </Paragraph> <Paragraph> <Text> -USE HISTORICAL FARES IN EFFECT ON THE DATE OF</Text> </Paragraph> <Paragraph> <Text> ORG TKT ISSUE FOR ALL RULE VALIDATION.</Text> </Paragraph> <Paragraph> <Text> B. REPRICE KEEPING FARES FOR FLOWN FARE</Text> </Paragraph> <Paragraph> <Text> COMPONENTS AND REPLACE FARES FOR UNFLOWN FARE</Text> </Paragraph> <Paragraph> <Text> COMPONENTS USING HISTORICAL FARES</Text> </Paragraph> <Paragraph> <Text> -MAY CHG ORG/DSTN OF ANY FARE COMPONENT</Text> </Paragraph> <Paragraph> <Text> -USE HISTORICAL FARES IN EFFECT ON DATE OF</Text> </Paragraph> <Paragraph> <Text> ORIGINAL TKT ISSUE AND MODIFIED ADV PURCHASE.</Text> </Paragraph> <Paragraph> <Text> -ALL RULE DATA MUST BE VERIFIED</Text> </Paragraph> <Paragraph> <Text> -WHEN COMBINED WITH NONREF FARES - REPLACEMENT</Text> </Paragraph> <Paragraph>

Page 44: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 44

<Text> FARES FOR UNFLOWN FARE COMPONENTS MUST BE OF</Text> </Paragraph> <Paragraph> <Text> EQUAL OR HIGHER VALUE/BOOKING CLASS AND FARE</Text> </Paragraph> <Paragraph> <Text> TYPE THAN ORIGINAL TKTD FARE</Text> </Paragraph> <Paragraph> <Text> -USE BOOKING CLASS HIERARCHY BELOW WHEN</Text> </Paragraph> <Paragraph> <Text> REPLACING FARES FOR UNFLOWN FARE COMPONENTS</Text> </Paragraph> <Paragraph> <Text> ECONOMY CLASS - Y B M H Q K L U T</Text> </Paragraph> <Paragraph> <Text> BUSINESS CLASS - J C D S I</Text> </Paragraph> <Paragraph> <Text> FIRST CLASS - F A</Text> </Paragraph> <Paragraph> <Text> C. REPLACE FARES FOR FLOWN AND UNFLOWN FARE</Text> </Paragraph> <Paragraph> <Text> COMPONENTS WITH HISTORICAL FARES</Text> </Paragraph> <Paragraph> <Text> -MAY CHG ORG/DSTN OF ANY FARE COMPONENT</Text> </Paragraph> <Paragraph> <Text> -USE HISTORICAL FARES IN EFFECT ON DATE OF</Text> </Paragraph> <Paragraph> <Text> ORIGINAL TKT ISSUE FOR RULE VALIDATION.</Text> </Paragraph> <Paragraph> <Text> -REPLACEMENT FARES FOR FLOWN AND UNFLOWN</Text> </Paragraph> <Paragraph> <Text> FARE COMPONENTS MUST BE EQUAL/HIGHER VALUE/</Text> </Paragraph> <Paragraph> <Text> BOOKING CLASS AND FARE TYPE THAN ORIGINAL</Text> </Paragraph> <Paragraph> <Text> TKTD FARE</Text> </Paragraph> <Paragraph> <Text> -USE BOOKING CLASS HIERARCHY BELOW WHEN</Text> </Paragraph> <Paragraph> <Text> REPLACING FARES FOR FLOWN AND UNFLOWN FARE</Text> </Paragraph> <Paragraph> <Text> COMPONENTS</Text> </Paragraph> <Paragraph>

Page 45: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 45

<Text> ECONOMY CLASS - Y B M H Q K L U T</Text> </Paragraph> <Paragraph> <Text> BUSINESS CLASS - J C D S I</Text> </Paragraph> <Paragraph> <Text> FIRST CLASS - F A</Text> </Paragraph> <Paragraph> <Text> D. ISSUE A NEW TICKET</Text> </Paragraph> <Paragraph> <Text> -USE VALUE OF ORIGINAL TKT LESS CHG FEE TOWARD</Text> </Paragraph> <Paragraph> <Text> PURCHASE OF NEW TKT</Text> </Paragraph> <Paragraph> <Text> -VALIDATE ALL RULES</Text> </Paragraph> <Paragraph> <Text> -ANY RESIDUAL VALUE IN THE ORIGINAL TKT/LESS</Text> </Paragraph> <Paragraph> <Text> CHG FEE/MAY BE APPLIED TOWARDS PURCHASE OF</Text> </Paragraph> <Paragraph> <Text> NEW TKT</Text> </Paragraph> <Paragraph> <Text> E. FARE TYPE HEIRARCHY-FARE TYPE MAY BE UPGD TO</Text> </Paragraph> <Paragraph> <Text> ANOTHER FARE TYPE ON A LEVEL UP FROM ITS OWN.</Text> </Paragraph> <Paragraph> <Text> FARE TYPES AT SAME LEVEL MAY NOT BE USED.</Text> </Paragraph> <Paragraph> <Text> EXAMPLE..AN XAC MAY BE UPGD TO XAB OR ABOVE.</Text> </Paragraph> <Paragraph> <Text> XPY CANNOT BE USED AS IT IS ON SAME LEVEL.</Text> </Paragraph> <Paragraph> <Text> .</Text> </Paragraph> <Paragraph> <Text> FR/FU</Text> </Paragraph> <Paragraph> <Text> FX/FOX</Text> </Paragraph> <Paragraph> <Text> BR/BU</Text> </Paragraph> <Paragraph> <Text> BX/BOX</Text> </Paragraph> <Paragraph>

Page 46: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 46

<Text> BAP</Text> </Paragraph> <Paragraph> <Text> BXN</Text> </Paragraph> <Paragraph> <Text> ER/EU</Text> </Paragraph> <Paragraph> <Text> XEX</Text> </Paragraph> <Paragraph> <Text> XES</Text> </Paragraph> <Paragraph> <Text> XAP -- XPX</Text> </Paragraph> <Paragraph> <Text> XAW -- XPS</Text> </Paragraph> <Paragraph> <Text> XAN -- XPL</Text> </Paragraph> <Paragraph> <Text> XAB -- XPB</Text> </Paragraph> <Paragraph> <Text> XAC -- XPY</Text> </Paragraph> <Paragraph> <Text> XAT -- XPF</Text> </Paragraph> </SubSection> <SubSection SubTitle="18. TICKET ENDORSEMENT"> <Paragraph> <Text>UNLESS OTHERWISE SPECIFIED</Text> </Paragraph> <Paragraph> <Text> THE ORIGINAL TICKET MUST BE ANNOTATED - NONREF/NONEND/PEX-</Text> </Paragraph> <Paragraph> <Text> IN THE ENDORSEMENT BOX.</Text> </Paragraph> </SubSection> <SubSection SubTitle="19. CHILDREN DISCOUNTS"> <Paragraph> <Text>UNLESS OTHERWISE SPECIFIED NOTE - GENERAL RULE DOES NOT</Text> </Paragraph> <Paragraph> <Text>APPLY</Text> </Paragraph> <Paragraph> <Text> ACCOMPANIED CHILD 2-11 - CHARGE 75 PERCENT OF THE FARE.</Text> </Paragraph> <Paragraph> <Text> TICKET DESIGNATOR - CH AND PERCENT OF DISCOUNT</Text> </Paragraph> <Paragraph>

Page 47: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 47

<Text> OR - INFANT UNDER 2 WITH A SEAT - CHARGE 75 PERCENT OF THE</Text> </Paragraph> <Paragraph> <Text> FARE.</Text> </Paragraph> <Paragraph> <Text> TICKET DESIGNATOR - CH AND PERCENT OF DISCOUNT</Text> </Paragraph> <Paragraph> <Text> OR - 1ST INFANT UNDER 2 WITHOUT A SEAT - CHARGE 10 PERCENT</Text> </Paragraph> <Paragraph> <Text> OF THE FARE.</Text> </Paragraph> <Paragraph> <Text> TICKET DESIGNATOR - IN AND PERCENT OF DISCOUNT</Text> </Paragraph> <Paragraph> <Text> OR - UNACCOMPANIED CHILD 8-11 - CHARGE 100 PERCENT OF THE</Text> </Paragraph> <Paragraph> <Text> FARE.</Text> </Paragraph> <Paragraph> <Text> TICKET DESIGNATOR - CH AND PERCENT OF DISCOUNT.</Text> </Paragraph> </SubSection> <SubSection SubTitle="20. TOUR CONDUCTOR DISCOUNTS"> <Paragraph> <Text>NONE UNLESS OTHERWISE SPECIFIED</Text> </Paragraph> </SubSection> <SubSection SubTitle="21. AGENT DISCOUNTS"> <Paragraph> <Text>NONE UNLESS OTHERWISE SPECIFIED</Text> </Paragraph> </SubSection> <SubSection SubTitle="22. ALL OTHER DISCOUNTS"> <Paragraph> <Text>NONE UNLESS OTHERWISE SPECIFIED</Text> </Paragraph> </SubSection> <SubSection SubTitle="31. VOLUNTARY CHANGES"> <Paragraph> <Text>UNLESS OTHERWISE SPECIFIED NOTE - RULE JVR2 IN IPRG</Text> </Paragraph> <Paragraph> <Text>APPLIES</Text> </Paragraph> <Paragraph> <Text>FOR ROUND TRIP INSTANT PURCHASE FARES</Text> </Paragraph> <Paragraph> <Text> IN THE EVENT OF CHANGES TO TICKETED FLIGHTS</Text> </Paragraph> <Paragraph> <Text> BEFORE DEPARTURE OF JOURNEY AND WITHIN TKT VALIDITY</Text>

Page 48: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 48

</Paragraph> <Paragraph> <Text> CERTAIN DOMESTIC REISSUE PROVISIONS MAY BE OVERRIDDEN BY</Text> </Paragraph> <Paragraph> <Text> THOSE OF DL INTERNATIONAL FARES</Text> </Paragraph> <Paragraph> <Text> CHARGE EUR 100.00 FOR REISSUE OR HIGHEST FEE OF ANY</Text> </Paragraph> <Paragraph> <Text> CHANGED FARE COMPONENT WITHIN JOURNEY - INFANT/CHILD</Text> </Paragraph> <Paragraph> <Text> DISCOUNT APPLIES AND</Text> </Paragraph> <Paragraph> <Text> REPRICE USING CURRENTLY TKTD FARE</Text> </Paragraph> <Paragraph> <Text> PROVIDED ALL OF THE FOLLOWING CONDITIONS ARE MET-</Text> </Paragraph> <Paragraph> <Text> 1. NO CHANGE TO 1ST FARE COMPONENT/FARE BREAKS</Text> </Paragraph> <Paragraph> <Text> 2. WHEN NO INTL COUPONS REMAIN - ALL NEW TRAVEL MUST</Text> </Paragraph> <Paragraph> <Text> BE DOMESTIC</Text> </Paragraph> <Paragraph> <Text> 3. DL FARES ARE USED</Text> </Paragraph> <Paragraph> <Text> 4. ALL RULE AND BOOKING CODE PROVISIONS ARE MET</Text> </Paragraph> <Paragraph> <Text> EXCEPT ACCOMPANIED TRAVEL</Text> </Paragraph> <Paragraph> <Text> 5. VALIDATE ADVANCE RES REQUIREMENTS WHEN BOOKING</Text> </Paragraph> <Paragraph> <Text> DATE KNOWN</Text> </Paragraph> <Paragraph> <Text> 6. ADV RES IS MEASURED FROM ORIGINAL TKT DATE TO</Text> </Paragraph> <Paragraph> <Text> DEPARTURE OF PRICING UNIT</Text> </Paragraph> <Paragraph> <Text> OR -</Text> </Paragraph> <Paragraph> <Text> REPRICE USING FARES IN EFFECT WHEN TKT WAS ISSUED</Text> </Paragraph> <Paragraph>

Page 49: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 49

<Text> PROVIDED ALL OF THE FOLLOWING CONDITIONS ARE MET-</Text> </Paragraph> <Paragraph> <Text> 1. NO CHANGE TO 1ST FARE COMPONENT</Text> </Paragraph> <Paragraph> <Text> 2. SAME FARE ON 1ST FARE COMPONENT IS USED</Text> </Paragraph> <Paragraph> <Text> 3. WHEN NO INTL COUPONS REMAIN - ALL NEW TRAVEL MUST</Text> </Paragraph> <Paragraph> <Text> BE DOMESTIC</Text> </Paragraph> <Paragraph> <Text> 4. DL FARE TYPE XPX IS USED</Text> </Paragraph> <Paragraph> <Text> 5. NEW TKT HAS EQUAL OR HIGHER VALUE THAN PREVIOUS</Text> </Paragraph> <Paragraph> <Text> TKT</Text> </Paragraph> <Paragraph> <Text> 6. WHEN SAME FARE USED - ALL RULE AND BOOKING CODE</Text> </Paragraph> <Paragraph> <Text> PROVISIONS ARE MET EXCEPT ACCOMPANIED TRAVEL -</Text> </Paragraph> <Paragraph> <Text> OTHERWISE ALL PROVISIONS MUST BE MET</Text> </Paragraph> <Paragraph> <Text> 7. VALIDATE ADVANCE RES REQUIREMENTS WHEN BOOKING</Text> </Paragraph> <Paragraph> <Text> DATE KNOWN</Text> </Paragraph> <Paragraph> <Text> 8. ADV RES IS MEASURED FROM ORIGINAL TKT DATE TO</Text> </Paragraph> <Paragraph> <Text> DEPARTURE OF PRICING UNIT</Text> </Paragraph> <Paragraph> <Text> OR -</Text> </Paragraph> <Paragraph> <Text> REPRICE USING FARES IN EFFECT WHEN TKT WAS ISSUED</Text> </Paragraph> <Paragraph> <Text> PROVIDED ALL OF THE FOLLOWING CONDITIONS ARE MET-</Text> </Paragraph> <Paragraph> <Text> 1. NO CHANGE TO 1ST FARE COMPONENT</Text> </Paragraph> <Paragraph> <Text> 2. SAME FARE ON 1ST FARE COMPONENT IS USED</Text> </Paragraph> <Paragraph>

Page 50: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 50

<Text> 3. WHEN NO INTL COUPONS REMAIN - ALL NEW TRAVEL MUST</Text> </Paragraph> <Paragraph> <Text> BE DOMESTIC</Text> </Paragraph> <Paragraph> <Text> 4. DL FARE TYPE XEX IS USED</Text> </Paragraph> <Paragraph> <Text> 5. NEW TKT HAS EQUAL OR HIGHER VALUE THAN PREVIOUS</Text> </Paragraph> <Paragraph> <Text> TKT</Text> </Paragraph> <Paragraph> <Text> 6. WHEN SAME FARE USED - ALL RULE AND BOOKING CODE</Text> </Paragraph> <Paragraph> <Text> PROVISIONS ARE MET EXCEPT ACCOMPANIED TRAVEL -</Text> </Paragraph> <Paragraph> <Text> OTHERWISE ALL PROVISIONS MUST BE MET</Text> </Paragraph> <Paragraph> <Text> 7. VALIDATE ADVANCE RES REQUIREMENTS WHEN BOOKING</Text> </Paragraph> <Paragraph> <Text> DATE KNOWN</Text> </Paragraph> <Paragraph> <Text> 8. ADV RES IS MEASURED FROM ORIGINAL TKT DATE TO</Text> </Paragraph> <Paragraph> <Text> DEPARTURE OF PRICING UNIT</Text> </Paragraph> <Paragraph> <Text> OR -</Text> </Paragraph> <Paragraph> <Text> REPRICE USING FARES IN EFFECT WHEN TKT WAS ISSUED</Text> </Paragraph> <Paragraph> <Text> PROVIDED ALL OF THE FOLLOWING CONDITIONS ARE MET-</Text> </Paragraph> <Paragraph> <Text> 1. NO CHANGE TO 1ST FARE COMPONENT</Text> </Paragraph> <Paragraph> <Text> 2. SAME FARE ON 1ST FARE COMPONENT IS USED</Text> </Paragraph> <Paragraph> <Text> 3. WHEN NO INTL COUPONS REMAIN - ALL NEW TRAVEL MUST</Text> </Paragraph> <Paragraph> <Text> BE DOMESTIC</Text> </Paragraph> <Paragraph> <Text> 4. DL FARE TYPE XES IS USED</Text> </Paragraph> <Paragraph>

Page 51: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 51

<Text> 5. NEW TKT HAS EQUAL OR HIGHER VALUE THAN PREVIOUS</Text> </Paragraph> <Paragraph> <Text> TKT</Text> </Paragraph> <Paragraph> <Text> 6. WHEN SAME FARE USED - ALL RULE AND BOOKING CODE</Text> </Paragraph> <Paragraph> <Text> PROVISIONS ARE MET EXCEPT ACCOMPANIED TRAVEL -</Text> </Paragraph> <Paragraph> <Text> OTHERWISE ALL PROVISIONS MUST BE MET</Text> </Paragraph> <Paragraph> <Text> 7. VALIDATE ADVANCE RES REQUIREMENTS WHEN BOOKING</Text> </Paragraph> <Paragraph> <Text> DATE KNOWN</Text> </Paragraph> <Paragraph> <Text> 8. ADV RES IS MEASURED FROM ORIGINAL TKT DATE TO</Text> </Paragraph> <Paragraph> <Text> DEPARTURE OF PRICING UNIT</Text> </Paragraph> <Paragraph> <Text> OR -</Text> </Paragraph> <Paragraph> <Text> REPRICE USING FARES IN EFFECT WHEN TKT WAS ISSUED</Text> </Paragraph> <Paragraph> <Text> PROVIDED ALL OF THE FOLLOWING CONDITIONS ARE MET-</Text> </Paragraph> <Paragraph> <Text> 1. NO CHANGE TO 1ST FARE COMPONENT</Text> </Paragraph> <Paragraph> <Text> 2. SAME FARE ON 1ST FARE COMPONENT IS USED</Text> </Paragraph> <Paragraph> <Text> 3. WHEN NO INTL COUPONS REMAIN - ALL NEW TRAVEL MUST</Text> </Paragraph> <Paragraph> <Text> BE DOMESTIC</Text> </Paragraph> <Paragraph> <Text> 4. DL FARE TYPE BXN IS USED</Text> </Paragraph> <Paragraph> <Text> 5. NEW TKT HAS EQUAL OR HIGHER VALUE THAN PREVIOUS</Text> </Paragraph> <Paragraph> <Text> TKT</Text> </Paragraph> <Paragraph> <Text> 6. WHEN SAME FARE USED - ALL RULE AND BOOKING CODE</Text> </Paragraph> <Paragraph>

Page 52: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 52

<Text> PROVISIONS ARE MET EXCEPT ACCOMPANIED TRAVEL -</Text> </Paragraph> <Paragraph> <Text> OTHERWISE ALL PROVISIONS MUST BE MET</Text> </Paragraph> <Paragraph> <Text> 7. VALIDATE ADVANCE RES REQUIREMENTS WHEN BOOKING</Text> </Paragraph> <Paragraph> <Text> DATE KNOWN</Text> </Paragraph> <Paragraph> <Text> 8. ADV RES IS MEASURED FROM ORIGINAL TKT DATE TO</Text> </Paragraph> <Paragraph> <Text> DEPARTURE OF PRICING UNIT</Text> </Paragraph> <Paragraph> <Text> OR -</Text> </Paragraph> <Paragraph> <Text> REPRICE USING FARES IN EFFECT WHEN TKT WAS ISSUED</Text> </Paragraph> <Paragraph> <Text> PROVIDED ALL OF THE FOLLOWING CONDITIONS ARE MET-</Text> </Paragraph> <Paragraph> <Text> 1. NO CHANGE TO 1ST FARE COMPONENT</Text> </Paragraph> <Paragraph> <Text> 2. SAME FARE ON 1ST FARE COMPONENT IS USED</Text> </Paragraph> <Paragraph> <Text> 3. WHEN NO INTL COUPONS REMAIN - ALL NEW TRAVEL MUST</Text> </Paragraph> <Paragraph> <Text> BE DOMESTIC</Text> </Paragraph> <Paragraph> <Text> 4. DL FARE TYPE BAP IS USED</Text> </Paragraph> <Paragraph> <Text> 5. NEW TKT HAS EQUAL OR HIGHER VALUE THAN PREVIOUS</Text> </Paragraph> <Paragraph> <Text> TKT</Text> </Paragraph> <Paragraph> <Text> 6. WHEN SAME FARE USED - ALL RULE AND BOOKING CODE</Text> </Paragraph> <Paragraph> <Text> PROVISIONS ARE MET EXCEPT ACCOMPANIED TRAVEL -</Text> </Paragraph> <Paragraph> <Text> OTHERWISE ALL PROVISIONS MUST BE MET</Text> </Paragraph> <Paragraph> <Text> 7. VALIDATE ADVANCE RES REQUIREMENTS WHEN BOOKING</Text> </Paragraph> <Paragraph>

Page 53: JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTSxml.bookingengine.es/doc/Documentation/Flights/JuniperXMLDoc... · JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS ... Juniper Booking

Juniper Booking Engine XML Webservice for Flights

Version 20090805 Page 53

<Text> DATE KNOWN</Text> </Paragraph> <Paragraph> <Text> 8. ADV RES IS MEASURED FROM ORIGINAL TKT DATE TO</Text> </Paragraph> <Paragraph> <Text> DEPARTURE OF PRICING UNIT</Text> </Paragraph> <Paragraph> <Text> OR -</Text> </Paragraph> <Paragraph> <Text> REPRICE USING FARES IN EFFECT WHEN TKT WAS ISSUED</Text> </Paragraph> <Paragraph> <Text> PROVIDED ALL OF THE FOLLOWING CONDITIONS ARE MET-</Text> </Paragraph> <Paragraph> <Text> 1. NO CHANGE TO 1ST FARE COMPONENT</Text> </Paragraph> <Paragraph> <Text> 2. SAME FARE ON 1ST FARE COMPONENT IS USED</Text> </Paragraph> <Paragraph> <Text> 3. WHEN NO INTL COUPONS REMAIN - ALL NEW TRAVEL MUST</Text> </Paragraph> <Paragraph> <Text> BE DOMESTIC</Text> </Paragraph> <Paragraph> <Text> 4. DL FARE TYPE BX IS USED</Text> </Paragraph> <Paragraph> <Text> 5. NEW TKT HAS EQUAL OR HIGHER VALUE THAN PREVIOUS</Text> </Paragraph> <Paragraph> <Text> TKT</Text> </Paragraph> <Paragraph> <Text> 6. WHEN SAME FARE USED - ALL RULE AND BOOKING CODE</Text> </Paragraph> <Paragraph> <Text> PROVISIONS ARE MET EXCEPT ACCOMPANIED TRAVEL -</Text> </Paragraph> <Paragraph> <Text> OTHERWISE ALL PROVISIONS MUST BE MET</Text> </Paragraph> <Paragraph> <Text> TOO MANY TEXT LINES - TEXT TRUNCATED</Text> </Paragraph> <Paragraph> <Text> DO A CATEGORY SPECIFIC TEXT ENTRY</Text> </Paragraph> </SubSection> </FareRules> </FareRuleResponseInfo> </OTA_AirRulesRS>