JUNIPER BOOKING ENGINE XML WEBSERVICE FOR FLIGHTS
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
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 TechnologyJuniper Booking Engine XML Webservice for Flights 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. Version 20090805 Page 2
Juniper Booking Engine XML Webservice for Flights
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 .............................................................................................................................. 9
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
Version 20090805 Page 3Juniper Booking Engine XML Webservice for Flights
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.
Version 20090805 Page 4Juniper Booking Engine XML Webservice for Flights
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.
Version 20090805 Page 5Juniper Booking Engine XML Webservice for Flights
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/
Version 20090805 Page 6Juniper Booking Engine XML Webservice for Flights
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.
Version 20090805 Page 7Juniper Booking Engine XML Webservice for Flights
Request Header Request Header Response
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
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.
Version 20090805 Page 8Juniper Booking Engine XML Webservice for Flights
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
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:
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.
Version 20090805 Page 9Juniper Booking Engine XML Webservice for Flights
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
2008-10-20
2008-10-23
Optional elements in OTA_AirLowFareSearchRQ:
1- You can add an element in OTA_AirLowFareSearch request to apply resident discount in
flight fares. Example:
Version 20090805 Page 10Juniper Booking Engine XML Webservice for Flights
2008-11-20
2008-11-25
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:
2008-11-20
2008-11-25
Version 20090805 Page 11Juniper Booking Engine XML Webservice for Flights The response below shows the alternatives found. There are some important items: Contains the list of alternatives found It’s composed by Itinerary info (AirItinerary) and Pricing info (AirItineraryPricingInfo) A collection of OriginDestinationOption Contains the list of legs for this itinerary Contains full information about a segment (departure and arrival dates, flight number, operating and marketing airline, etc) 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 Contains a list of “PTC_FareBreakdown” items. There is one item per passenger type Contains all fare information for a passenger type Contains the tax list, base fare, fare equivalence “EquivFare” (in case base fare is in different currency) and total fare for this passenger type Version 20090805 Page 12
Juniper Booking Engine XML Webservice for Flights
Juniper Booking Engine XML Webservice for Flights
ArrivalDateTime="2008-10-20T16:25:00" StopQuantity="0" RPH="2" ResBookDesigCode="V">
Important notes:
- The header of the OTA_AirLowFareSearchRS tag has an attribute SequenceNmbr
whose value must be sent in the reservation request.
Version 20090805 Page 14Juniper Booking Engine XML Webservice for Flights
- 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:
LC
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:
Version 20090805 Page 15Juniper Booking Engine XML Webservice for Flights 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. Version 20090805 Page 16
Juniper Booking Engine XML Webservice for Flights
Juniper
Test
user@provider.com
My address
Palma de Mallorca
07000
Spain
Mr
WebService
Test
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
Version 20090805 Page 17Juniper Booking Engine XML Webservice for Flights
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:
Mr
WebService
Test
Santa Cruz de Tenerife
380380
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:
WebService
Test
Version 20090805 Page 18Juniper Booking Engine XML Webservice for Flights
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:
Version 20090805 Page 19Juniper Booking Engine XML Webservice for Flights
Juniper
Test
user@provider.com
My address
Palma de Mallorca
07000
Spain
Mr
WebService
Test
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:
Version 20090805 Page 20Juniper Booking Engine XML Webservice for Flights
- 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:
Juniper
Test
user@provider.com
My address
Palma de Mallorca
07000
Spain
- 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 $
Version 20090805 Page 21Juniper Booking Engine XML Webservice for Flights
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:
Juniper
Test
user@provider.com
My address
Palma de Mallorca
07000
Spain
Version 20090805 Page 22Juniper Booking Engine XML Webservice for Flights
Mr
WebService
Test
- 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:
Version 20090805 Page 23Juniper Booking Engine XML Webservice for Flights
Juniper
Test
user@provider.com
My address
Palma de Mallorca
07000
Spain
Mr
WebService
Test
Version 20090805 Page 24Juniper Booking Engine XML Webservice for Flights
- 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).
Version 20090805 Page 25Juniper Booking Engine XML Webservice for Flights 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. 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. Version 20090805 Page 26
Juniper Booking Engine XML Webservice for Flights
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.
The response is similar to the OTA_AirBookRS obtained in a previous step. This is an example
of OTA_ResRetrieveRes:
Juniper
Test
Version 20090805 Page 27Juniper Booking Engine XML Webservice for Flights
user@provider.com
My address
Palma de Mallorca
07000
Spain
Mr
WebService
Test
Version 20090805 Page 28Juniper Booking Engine XML Webservice for Flights 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. 2009-11-10T11:15:00 127 2009-11-10T19:30:00 8019 2009-11-13T13:02:00 8018 2009-11-13T18:40:00 126 Version 20090805 Page 29
Juniper Booking Engine XML Webservice for Flights
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:
RULE - 001/JV01
UNLESS OTHERWISE SPECIFIED
1ST LEVEL INSTANT PURCHASE FARES FROM AREA 2 TO AREA 1
APPLICATION
AREA
THESE FARES APPLY
FROM AREA 2 TO AREA 1.
CLASS OF SERVICE
THESE FARES APPLY FOR ECONOMY CLASS SERVICE.
TYPES OF TRANSPORTATION
FARES GOVERNED BY THIS RULE CAN BE USED TO CREATE
ROUND-TRIP/SINGLE OPEN-JAW/DOUBLE OPEN-JAW JOURNEYS.
CAPACITY LIMITATIONS
THE CARRIER SHALL LIMIT THE NUMBER OF PASSENGERS
CARRIED
Version 20090805 Page 30Juniper Booking Engine XML Webservice for Flights
ON ANY ONE FLIGHT AT FARES GOVERNED BY THIS RULE AND
SUCH
FARES WILL NOT NECESSARILY BE AVAILABLE ON ALL FLIGHTS.
THE NUMBER OF SEATS WHICH THE CARRIER SHALL MAKE
AVAILABLE ON A GIVEN FLIGHT WILL BE DETERMINED BY THE
CARRIERS BEST JUDGMENT
UNLESS OTHERWISE SPECIFIED
THE FARE COMPONENT MUST NOT BE ON
ONE OR MORE OF THE FOLLOWING
ANY BA FLIGHT
ANY EI FLIGHT
ANY LH FLIGHT
ANY LX FLIGHT
ANY LY FLIGHT
ANY MS FLIGHT
ANY OS FLIGHT
ANY OA FLIGHT
ANY AA FLIGHT
ANY US FLIGHT
ANY UA FLIGHT
Version 20090805 Page 31Juniper Booking Engine XML Webservice for Flights
ANY FC FLIGHT
ANY UU FLIGHT
ANY DT FLIGHT
ANY PK FLIGHT
ANY JS FLIGHT
ANY FG FLIGHT
ANY GA FLIGHT
ANY QZ FLIGHT
ANY 3Y FLIGHT
ANY RI FLIGHT
ANY MZ FLIGHT
ANY 7P FLIGHT
ANY AW FLIGHT
ANY RW FLIGHT
ANY NV FLIGHT
ANY DC FLIGHT
ANY QH FLIGHT
ANY R8 FLIGHT
ANY O3 FLIGHT
ANY I7 FLIGHT
Version 20090805 Page 32Juniper Booking Engine XML Webservice for Flights
ANY ZC FLIGHT
ANY Q4 FLIGHT
ANY EO FLIGHT
ANY W5 FLIGHT
ANY UF FLIGHT
ANY KF FLIGHT
ANY C2 FLIGHT
ANY OD FLIGHT
ANY K9 FLIGHT
ANY X7 FLIGHT
ANY FT FLIGHT
ANY MQ FLIGHT
ANY 2S FLIGHT
ANY Z7 FLIGHT
ANY IB FLIGHT OPERATED BY BA
ANY AA FLIGHT OPERATED BY BA
ANY UA FLIGHT OPERATED BY LH
ANY US FLIGHT OPERATED BY LH
ANY LO FLIGHT OPERATED BY LH.
AND
Version 20090805 Page 33Juniper Booking Engine XML Webservice for Flights
THE FARE COMPONENT MUST NOT BE ON
ONE OR MORE OF THE FOLLOWING
ANY OS FLIGHT OPERATED BY LH
ANY SA FLIGHT OPERATED BY LH
ANY SK FLIGHT OPERATED BY LH
ANY SQ FLIGHT OPERATED BY LH
ANY TK FLIGHT OPERATED BY LH
ANY LH FLIGHT OPERATED BY UA
ANY LH FLIGHT OPERATED BY US
ANY AA FLIGHT OPERATED BY LY.
UNLESS OTHERWISE SPECIFIED
RESERVATIONS ARE REQUIRED FOR ALL SECTORS.
WHEN RESERVATIONS ARE MADE AT LEAST 17 DAYS BEFORE
DEPARTURE TICKETING MUST BE COMPLETED WITHIN 7 DAYS
AFTER
RESERVATIONS ARE MADE.
OR - RESERVATIONS ARE REQUIRED FOR ALL SECTORS.
WHEN RESERVATIONS ARE MADE AT LEAST 5 DAYS BEFORE
DEPARTURE TICKETING MUST BE COMPLETED WITHIN 72
HOURS
AFTER RESERVATIONS ARE MADE.
Version 20090805 Page 34Juniper Booking Engine XML Webservice for Flights
OR - RESERVATIONS ARE REQUIRED FOR ALL SECTORS.
TICKETING MUST BE COMPLETED WITHIN 24 HOURS AFTER
RESERVATIONS ARE MADE.
UNLESS OTHERWISE SPECIFIED
TRAVEL FROM LAST INTERNATIONAL STOPOVER MUST COMMENCE
NO
EARLIER THAN THE FIRST SUN AFTER DEPARTURE OF THE FIRST
INTERNATIONAL SECTOR
OR - TRAVEL FROM LAST INTERNATIONAL STOPOVER MUST
COMMENCE
NO EARLIER THAN 3 DAYS AFTER DEPARTURE OF THE FIRST
INTERNATIONAL SECTOR.
UNLESS OTHERWISE SPECIFIED
TRAVEL FROM LAST STOPOVER MUST COMMENCE NO LATER THAN
12
MONTHS AFTER DEPARTURE FROM FARE ORIGIN.
UNLESS OTHERWISE SPECIFIED NOTE - GENERAL RULE DOES
NOT
APPLY
2 STOPOVERS PERMITTED - 1 IN EACH DIRECTION IN NYC/DTT/
ATL/PAR/AMS AT EUR 75.00 EACH.
Version 20090805 Page 35Juniper Booking Engine XML Webservice for Flights
UNLESS OTHERWISE SPECIFIED
UNLIMITED TRANSFERS PERMITTED ON THE FARE COMPONENT
ONLINE ON THE PRIMARY CARRIER.
AND - 1 TRANSFER PERMITTED IN EACH DIRECTION FREE
INTERLINE INCLUDING THE PRIMARY CARRIER
FREE OUTSIDE THE UNITED STATES IN EACH DIRECTION
FARE BREAK SURFACE SECTORS NOT PERMITTED AND
EMBEDDED SURFACE SECTORS PERMITTED ON THE FARE
COMPONENT.
UNLESS OTHERWISE SPECIFIED
DOUBLE OPEN JAWS NOT PERMITTED.
ADD-ONS PERMITTED.
END-ON-END
END-ON-END COMBINATIONS PERMITTED. VALIDATE ALL FARE
COMPONENTS.
PROVIDED -
COMBINATIONS ARE FOR CARRIER KL/AF/AZ/OK/NW/DL/AS/QX
OPEN JAWS/ROUND TRIPS/CIRCLE TRIPS
Version 20090805 Page 36Juniper Booking Engine XML Webservice for Flights
FARES MAY BE COMBINED ON A HALF ROUND TRIP BASIS
-TO FORM SINGLE OPEN JAWS
-TO FORM ROUND TRIPS EXCEPT FOR AROUND-THE-WORLD
FARES
-TO FORM CIRCLE TRIPS EXCEPT FOR AROUND-THE-WORLD
FARES.
PROVIDED -
COMBINATIONS ARE WITH ANY REGULAR APEX/APEX
NONREFUNDABLE/SUPER/SPECIAL APEX/ROUND TRIP INSTANT
PURCHASE/INSTANT PURCHASE
NONREFUNDABLE/SUPER/SPECIAL
INSTANT PURCHASE/REGULAR EXCURSION/SECOND LEVEL
SUPER/
SPECIAL APEX/3RD LEVEL ADVANCE PURCHASE/INSTANT
PURCHASE 2ND LEVEL/INSTANT PURCHASE NONREF 2ND
LEVEL/
INSTANT PURCHASE 3RD LEVEL/ADVANCE PURCHASE 2ND
LEVEL/
5TH LEVEL INSTANT PURCHASE/SUPER INSTANT PURCHASE
2ND
LEVEL/4TH LEVEL INSTANT PURCHASE-TYPE FARES FOR
CARRIER
KL/AF/AZ/OK/NW/DL/AS/QX IN ANY RULE IN TARIFF
IPRA - BETWEEN USA/CA-AREA 2/3 AND GUAM-AREA 2
IPRAI - BETWEEN THE USA/CANADA-AREA 2/3 VIA ATL
IPRSAA2 - BETWEEN THE WESTERN HEMISPHERE-AREA 2 VIA
Version 20090805 Page 37Juniper Booking Engine XML Webservice for Flights
ATL.
COMBINATIONS ARE WITH ANY FARE FOR CARRIER
DL/NW/AF/KL
IN RULE 4444 IN TARIFF
ATDLR - BETWEEN AREA 1-AREA 2/3 AND GUAM-AREA 2
TAPVR - BETWEEN AREA 1-AREA 2/3 AND GUAM-AREA 2.
NOTE - THE CITY PAIRS BELOW ARE CONSIDERED THE SAME POINT-
BWI-WAS FLL-MIA OAK-SFO OAK-SJC SFO-SJC LAX-ONT
LAX-BUR LAX-LGB LAX-SNA ONT-BUR ONT-LGB ONT-SNA
BUR-LGB BUR-SNA LGB-SNA NYC-EWR
BETWEEN THE UNITED STATES AND SPAIN AND CANARY ISLANDS
IF INFANT 0-1 WITHOUT A SEAT.
THERE IS NO CHARGE FOR TRAVEL PER DIRECTION.
AND - ORIGINATING SPAIN AND CANARY ISLANDS -
THERE IS NO CHARGE FOR TRAVEL PER DIRECTION.
NOTE -
YQ FEE MAY APPLY
UNLESS OTHERWISE SPECIFIED NOTE - RULE JVR2 IN IPRG
APPLIES
Version 20090805 Page 38Juniper Booking Engine XML Webservice for Flights
UNLESS OTHERWISE SPECIFIED
CANCELLATIONS
CHARGE EUR 200.00.
WAIVED FOR ILLNESS OR DEATH OF PASSENGER OR FAMILY
MEMBER.
NOTE -
1. FARES COMBINED ON A TKT FROM DIFF RULES WITH
SAME OR DIFF CANCELLATION FEES --APPLY HIGHEST
FEE OF THE CANCELLED ITIN AND REFUND ANY REFUND
-ABLE FARES AND NON-REFUNDABLE FARE AMOUNT LESS
CANCELLATION FEE WILL BE RETURNED AS A NON-REF
VOUCHER FOR TVL VIA DL ONLY
2. ILLNESS/DEATH WAIVER MUST BE SUBSTANTIATED BY
A VALID MEDICAL/DEATH CERTIFICATE
3. CANCELLATION FEE DOES NOT APPLY TO INFANTS
UNDER 2 NOT OCCUPYING A SEAT.
CHANGES
ANY TIME
CHARGE EUR 100.00.
CHILD/INFANT DISCOUNTS APPLY.
Version 20090805 Page 39Juniper Booking Engine XML Webservice for Flights
NOTE -
-ALL TKTS MUST BE REISSUED
-CHANGE FEE DOES NOT APPLY TO INFANTS UNDER 2 NOT
OCCUPYING A SEAT
-SEE /CHILD DISCOUNT/ IN FARE RULE TO DETERMINE
IF CHILD DISCOUNTS APPLY
-CHGS RESULTING IN A HIGHER FARE MUST BE ADD-
COLLECTED AT THE TIME OF REISSUE
-MUST COMPLETE TVL BY 1 YR FROM THE DATE OF
COMMENCEMENT OF TVL
-FARES IN DIFF RULES WITH SAME OR DIFF CHG FEE -
APPLY THE HIGHEST FEE OF ANY CHGD FARE COMPONENT
ON THE TKT
-THE CHG FEE OR ITS EQUIV WILL BE CONVERTED AT
THE BANK RATE AT TIME OF REISSUE
-FOR CHGS DUE TO ILLNESS OR DEATH OF PSGR/FAMILY
MEMBER SEE INTL GEN. RULE 65 FOR PROVISIONS
.
TICKET UPGRADE PROCEDURES
VALUE OF TKT LESS CHANGE FEE MAY BE APPLIED TO-
Version 20090805 Page 40Juniper Booking Engine XML Webservice for Flights
WARD PURCHASE OF A HIGHER FARE-PAY CHG FEE AND
ANY DIFF BETWEEN ORIGINAL AND RECALCULATED FARES
IF UPGD TO ECONOMY-EU/ER OR BUSINESS-BU/BR OR
FIRST-FU/FR OR IF ER TYPE FARE UPG TO BUSINESS-
BU/BR OR FIRST-FU/FR TYPE FARE CHG FEE WILL NOT
BE ASSESSED. ALL RULE PROVISIONS OF NEW FARE
MUST BE MET.
.
TICKET DOWNGRADE PROCEDURES
PSGRS DOWNGRADING FARES MUST KEEP ORIGINALLY
BOOKED ITN-NO CHG TO DATE/TIME/ORG/DEST. ALL
RULE PROVISIONS OF NEW FARE MUST BE MET.
CHG FEE WILL BE ASSESSED.
.
TICKET REISSUE PROCEDURES
1. CHGS TO OUTBOUND PORTION OF UNUSED TKTS
A. ISSUE NEW TKT USING CURRENT FARES AND IROE
APPLICABLE. VERIFY ALL FARE RULES.
B. VALUE OF ORIGINAL TKT LESS CHG FEE MAY BE
APPLIED TOWARDS PURCHASE OF NEW TKT.
Version 20090805 Page 41Juniper Booking Engine XML Webservice for Flights
2. CHGS TO CONTINUING/RETURN OF UNUSED TKTS
A. ATTEMPT TO KEEP THE FARES AS TKTD
-NOT CHG ORG/DSTN OF ANY FARE COMPONENT
-MUST KEEP THE ORIGINAL FARES AS TKTD
-USE HISTORICAL FARES IN EFFECT ON DATE OF
ORIGINAL TKT ISSUE FOR ALL RULE VALIDATION.
B. REPRICE KEEPING OUTBOUND FARES AND REPLACING
CONTINUING/RETURN FARES USING HISTORICAL AND
MODIFIED ADVANCE PURCHASE
-NO CHG TO ORG/DSTN OF FIRST FARE COMPONENT
-USE HISTORICAL FARES IN EFFECT ON ORIGINAL
ISSUE DATE
-REPLACEMENT FARES MUST BE EQUAL/HIGHER FARE
TYPE
-MODIFIED ADVANCE PURCHASE-DETERMINE APPLIC.
ADV PURCHASE BY CALCULATING NUMBER OF DAYS
BETWEEN ORIGINAL TKT ISSUE DATE AND DATE OF
DPTR OF FIRST FLT SEGMENT. THE ADV PURCHASE
OF REPLACEMENT FARES MUST BE EQUAL OR LESS
THAN THIS NUMBER.
Version 20090805 Page 42Juniper Booking Engine XML Webservice for Flights
-ALL RULE DATA MUST BE VERIFIED
C. ISSUE NEW TKT - CANCEL/START OVER
-USE CURRENT FARES/VERIFY ALL FARE RULES
-VALUE OF ORIGINAL TKT LESS CHG FEE MAY BE
APPLIED TOWARD PURCHASE OF A NEW TKT.
3. CHGS TO PARTIALLY USED TKTS-OPTIONS
A. ATTEMPT TO KEEP THE FARES AS TKTD
-NO CHG ORG/DSTN OF ANY FARE COMPONENT
-MUST KEEP ALL OF THE ORIGINAL FARE AS TKTD.
-USE HISTORICAL FARES IN EFFECT ON THE DATE OF
ORG TKT ISSUE FOR ALL RULE VALIDATION.
B. REPRICE KEEPING FARES FOR FLOWN FARE
COMPONENTS AND REPLACE FARES FOR UNFLOWN FARE
COMPONENTS USING HISTORICAL FARES
-MAY CHG ORG/DSTN OF ANY FARE COMPONENT
-USE HISTORICAL FARES IN EFFECT ON DATE OF
ORIGINAL TKT ISSUE AND MODIFIED ADV PURCHASE.
-ALL RULE DATA MUST BE VERIFIED
-WHEN COMBINED WITH NONREF FARES - REPLACEMENT
FARES FOR UNFLOWN FARE COMPONENTS MUST BE OF
Version 20090805 Page 43Juniper Booking Engine XML Webservice for Flights
EQUAL OR HIGHER VALUE/BOOKING CLASS AND FARE
TYPE THAN ORIGINAL TKTD FARE
-USE BOOKING CLASS HIERARCHY BELOW WHEN
REPLACING FARES FOR UNFLOWN FARE COMPONENTS
ECONOMY CLASS - Y B M H Q K L U T
BUSINESS CLASS - J C D S I
FIRST CLASS - F A
C. REPLACE FARES FOR FLOWN AND UNFLOWN FARE
COMPONENTS WITH HISTORICAL FARES
-MAY CHG ORG/DSTN OF ANY FARE COMPONENT
-USE HISTORICAL FARES IN EFFECT ON DATE OF
ORIGINAL TKT ISSUE FOR RULE VALIDATION.
-REPLACEMENT FARES FOR FLOWN AND UNFLOWN
FARE COMPONENTS MUST BE EQUAL/HIGHER VALUE/
BOOKING CLASS AND FARE TYPE THAN ORIGINAL
TKTD FARE
-USE BOOKING CLASS HIERARCHY BELOW WHEN
REPLACING FARES FOR FLOWN AND UNFLOWN FARE
COMPONENTS
ECONOMY CLASS - Y B M H Q K L U T
Version 20090805 Page 44Juniper Booking Engine XML Webservice for Flights
BUSINESS CLASS - J C D S I
FIRST CLASS - F A
D. ISSUE A NEW TICKET
-USE VALUE OF ORIGINAL TKT LESS CHG FEE TOWARD
PURCHASE OF NEW TKT
-VALIDATE ALL RULES
-ANY RESIDUAL VALUE IN THE ORIGINAL TKT/LESS
CHG FEE/MAY BE APPLIED TOWARDS PURCHASE OF
NEW TKT
E. FARE TYPE HEIRARCHY-FARE TYPE MAY BE UPGD TO
ANOTHER FARE TYPE ON A LEVEL UP FROM ITS OWN.
FARE TYPES AT SAME LEVEL MAY NOT BE USED.
EXAMPLE..AN XAC MAY BE UPGD TO XAB OR ABOVE.
XPY CANNOT BE USED AS IT IS ON SAME LEVEL.
.
FR/FU
FX/FOX
BR/BU
BX/BOX
BAP
Version 20090805 Page 45Juniper Booking Engine XML Webservice for Flights
BXN
ER/EU
XEX
XES
XAP -- XPX
XAW -- XPS
XAN -- XPL
XAB -- XPB
XAC -- XPY
XAT -- XPF
UNLESS OTHERWISE SPECIFIED
THE ORIGINAL TICKET MUST BE ANNOTATED - NONREF/NONEND/PEX-
IN THE ENDORSEMENT BOX.
UNLESS OTHERWISE SPECIFIED NOTE - GENERAL RULE DOES
NOT
APPLY
ACCOMPANIED CHILD 2-11 - CHARGE 75 PERCENT OF THE FARE.
TICKET DESIGNATOR - CH AND PERCENT OF DISCOUNT
OR - INFANT UNDER 2 WITH A SEAT - CHARGE 75 PERCENT OF
Version 20090805 Page 46Juniper Booking Engine XML Webservice for Flights
THE
FARE.
TICKET DESIGNATOR - CH AND PERCENT OF DISCOUNT
OR - 1ST INFANT UNDER 2 WITHOUT A SEAT - CHARGE 10
PERCENT
OF THE FARE.
TICKET DESIGNATOR - IN AND PERCENT OF DISCOUNT
OR - UNACCOMPANIED CHILD 8-11 - CHARGE 100 PERCENT OF
THE
FARE.
TICKET DESIGNATOR - CH AND PERCENT OF DISCOUNT.
NONE UNLESS OTHERWISE SPECIFIED
NONE UNLESS OTHERWISE SPECIFIED
NONE UNLESS OTHERWISE SPECIFIED
UNLESS OTHERWISE SPECIFIED NOTE - RULE JVR2 IN IPRG
APPLIES
FOR ROUND TRIP INSTANT PURCHASE FARES
IN THE EVENT OF CHANGES TO TICKETED FLIGHTS
BEFORE DEPARTURE OF JOURNEY AND WITHIN TKT VALIDITY
Version 20090805 Page 47Juniper Booking Engine XML Webservice for Flights
CERTAIN DOMESTIC REISSUE PROVISIONS MAY BE OVERRIDDEN
BY
THOSE OF DL INTERNATIONAL FARES
CHARGE EUR 100.00 FOR REISSUE OR HIGHEST FEE OF ANY
CHANGED FARE COMPONENT WITHIN JOURNEY - INFANT/CHILD
DISCOUNT APPLIES AND
REPRICE USING CURRENTLY TKTD FARE
PROVIDED ALL OF THE FOLLOWING CONDITIONS ARE MET-
1. NO CHANGE TO 1ST FARE COMPONENT/FARE BREAKS
2. WHEN NO INTL COUPONS REMAIN - ALL NEW TRAVEL MUST
BE DOMESTIC
3. DL FARES ARE USED
4. ALL RULE AND BOOKING CODE PROVISIONS ARE MET
EXCEPT ACCOMPANIED TRAVEL
5. VALIDATE ADVANCE RES REQUIREMENTS WHEN BOOKING
DATE KNOWN
6. ADV RES IS MEASURED FROM ORIGINAL TKT DATE TO
DEPARTURE OF PRICING UNIT
OR -
REPRICE USING FARES IN EFFECT WHEN TKT WAS ISSUED
PROVIDED ALL OF THE FOLLOWING CONDITIONS ARE MET-
Version 20090805 Page 48Juniper Booking Engine XML Webservice for Flights
1. NO CHANGE TO 1ST FARE COMPONENT
2. SAME FARE ON 1ST FARE COMPONENT IS USED
3. WHEN NO INTL COUPONS REMAIN - ALL NEW TRAVEL MUST
BE DOMESTIC
4. DL FARE TYPE XPX IS USED
5. NEW TKT HAS EQUAL OR HIGHER VALUE THAN PREVIOUS
TKT
6. WHEN SAME FARE USED - ALL RULE AND BOOKING CODE
PROVISIONS ARE MET EXCEPT ACCOMPANIED TRAVEL -
OTHERWISE ALL PROVISIONS MUST BE MET
7. VALIDATE ADVANCE RES REQUIREMENTS WHEN BOOKING
DATE KNOWN
8. ADV RES IS MEASURED FROM ORIGINAL TKT DATE TO
DEPARTURE OF PRICING UNIT
OR -
REPRICE USING FARES IN EFFECT WHEN TKT WAS ISSUED
PROVIDED ALL OF THE FOLLOWING CONDITIONS ARE MET-
1. NO CHANGE TO 1ST FARE COMPONENT
2. SAME FARE ON 1ST FARE COMPONENT IS USED
3. WHEN NO INTL COUPONS REMAIN - ALL NEW TRAVEL MUST
Version 20090805 Page 49Juniper Booking Engine XML Webservice for Flights
BE DOMESTIC
4. DL FARE TYPE XEX IS USED
5. NEW TKT HAS EQUAL OR HIGHER VALUE THAN PREVIOUS
TKT
6. WHEN SAME FARE USED - ALL RULE AND BOOKING CODE
PROVISIONS ARE MET EXCEPT ACCOMPANIED TRAVEL -
OTHERWISE ALL PROVISIONS MUST BE MET
7. VALIDATE ADVANCE RES REQUIREMENTS WHEN BOOKING
DATE KNOWN
8. ADV RES IS MEASURED FROM ORIGINAL TKT DATE TO
DEPARTURE OF PRICING UNIT
OR -
REPRICE USING FARES IN EFFECT WHEN TKT WAS ISSUED
PROVIDED ALL OF THE FOLLOWING CONDITIONS ARE MET-
1. NO CHANGE TO 1ST FARE COMPONENT
2. SAME FARE ON 1ST FARE COMPONENT IS USED
3. WHEN NO INTL COUPONS REMAIN - ALL NEW TRAVEL MUST
BE DOMESTIC
4. DL FARE TYPE XES IS USED
5. NEW TKT HAS EQUAL OR HIGHER VALUE THAN PREVIOUS
Version 20090805 Page 50Juniper Booking Engine XML Webservice for Flights
TKT
6. WHEN SAME FARE USED - ALL RULE AND BOOKING CODE
PROVISIONS ARE MET EXCEPT ACCOMPANIED TRAVEL -
OTHERWISE ALL PROVISIONS MUST BE MET
7. VALIDATE ADVANCE RES REQUIREMENTS WHEN BOOKING
DATE KNOWN
8. ADV RES IS MEASURED FROM ORIGINAL TKT DATE TO
DEPARTURE OF PRICING UNIT
OR -
REPRICE USING FARES IN EFFECT WHEN TKT WAS ISSUED
PROVIDED ALL OF THE FOLLOWING CONDITIONS ARE MET-
1. NO CHANGE TO 1ST FARE COMPONENT
2. SAME FARE ON 1ST FARE COMPONENT IS USED
3. WHEN NO INTL COUPONS REMAIN - ALL NEW TRAVEL MUST
BE DOMESTIC
4. DL FARE TYPE BXN IS USED
5. NEW TKT HAS EQUAL OR HIGHER VALUE THAN PREVIOUS
TKT
6. WHEN SAME FARE USED - ALL RULE AND BOOKING CODE
PROVISIONS ARE MET EXCEPT ACCOMPANIED TRAVEL -
Version 20090805 Page 51Juniper Booking Engine XML Webservice for Flights
OTHERWISE ALL PROVISIONS MUST BE MET
7. VALIDATE ADVANCE RES REQUIREMENTS WHEN BOOKING
DATE KNOWN
8. ADV RES IS MEASURED FROM ORIGINAL TKT DATE TO
DEPARTURE OF PRICING UNIT
OR -
REPRICE USING FARES IN EFFECT WHEN TKT WAS ISSUED
PROVIDED ALL OF THE FOLLOWING CONDITIONS ARE MET-
1. NO CHANGE TO 1ST FARE COMPONENT
2. SAME FARE ON 1ST FARE COMPONENT IS USED
3. WHEN NO INTL COUPONS REMAIN - ALL NEW TRAVEL MUST
BE DOMESTIC
4. DL FARE TYPE BAP IS USED
5. NEW TKT HAS EQUAL OR HIGHER VALUE THAN PREVIOUS
TKT
6. WHEN SAME FARE USED - ALL RULE AND BOOKING CODE
PROVISIONS ARE MET EXCEPT ACCOMPANIED TRAVEL -
OTHERWISE ALL PROVISIONS MUST BE MET
7. VALIDATE ADVANCE RES REQUIREMENTS WHEN BOOKING
DATE KNOWN
Version 20090805 Page 52Juniper Booking Engine XML Webservice for Flights
8. ADV RES IS MEASURED FROM ORIGINAL TKT DATE TO
DEPARTURE OF PRICING UNIT
OR -
REPRICE USING FARES IN EFFECT WHEN TKT WAS ISSUED
PROVIDED ALL OF THE FOLLOWING CONDITIONS ARE MET-
1. NO CHANGE TO 1ST FARE COMPONENT
2. SAME FARE ON 1ST FARE COMPONENT IS USED
3. WHEN NO INTL COUPONS REMAIN - ALL NEW TRAVEL MUST
BE DOMESTIC
4. DL FARE TYPE BX IS USED
5. NEW TKT HAS EQUAL OR HIGHER VALUE THAN PREVIOUS
TKT
6. WHEN SAME FARE USED - ALL RULE AND BOOKING CODE
PROVISIONS ARE MET EXCEPT ACCOMPANIED TRAVEL -
OTHERWISE ALL PROVISIONS MUST BE MET
TOO MANY TEXT LINES - TEXT TRUNCATED
DO A CATEGORY SPECIFIC TEXT ENTRY
Version 20090805 Page 53You can also read
