booklet ibs vanillaair iflyres -...

IBS Software Services 2018 | Page No. 1

P a g e | 1

Vanilla Air IBS NDC Platform DEVELOPERS GUIDE

WELCOME TO VANILLA AIR [JW]

An airline flying in Japan and offering seats and services.


P a g e | 2


Executive Summary Airline market challenges have favoured the inauguration of a new electronic communication schema that will introduce the retailing spirit in the distribution of air products to corporations, leisure and business travellers. Since 2012, IATA has being leading a collaborative industry initiative to define a novel XML based schema the New Distribution Capability (NDC) for promoting product differentiation and time to market, access to full and rich air content and finally, transparent shopping experience. Vanilla Air was founded in November 2013 by the largest carrier of Japan, All Nippon Airways. Today, Vanilla Air carries around Five million passengers per year. Vanilla Air has a fleet of 13 Airbus A320-200s operating across Japan, Taiwan, Phillippines, Vietnam & Hong Kong. iFly Res, the state-of-the-art software from IBS, the new system contains the distribution standard for ticket sales, the NDC - New Distribution Capability introduced by the International Air Transport Association (IATA). The simple and easy presentation of air fares and other travel services supports both the daily work volume of Vanilla Air partners within the travel industry and the demand of consumers using the newly redesigned website Vanilla Air.com. The Vanilla Air website is now being used more and more intensively for travellers direct bookings, for immediate travel modifications. iFly Res is also the only PSS to have NDC embedded in its core. IBS has built NDC message capability into the core messaging components of the PSS, but also by the expanded certification of NDC messages with IATA. The NDC platform is enabled with a total of 34 messages the most complete certified message set of any vendor. We are proud to be one of the first NDC-enabled airlines and we want to share our enthusiasm with any developer wishing to experience the emerging distribution era. So we welcome you to connect to our platform and search for our available flights or services, order the ones your prefer.

http://www.ibsplc.com/products/airline-passenger-services/passenger-reservation


P a g e | 3


Vanilla Air serves 11 destinations Across Japan, Hong Kong, Taiwan, Vietnam & Philippines

Sample routes for Hackathon Domestic Flights

NRT - OKA CTS NRT NRT - KIX

International Flights

NRT - HKG NRT - TPE NRT - CEB

15-Feb-18


SunExpress IBS NDC Platform

P a g e | 1


Vanilla Air Ancillary Services Sample Service Fee Rules. ##Prices are indicative.

Service Name Service Short Description

Routes Travel Type Cabin Cost

Service Code Origin Destination

Seat Extra Leg-room

NRT OKA

Domestic Economy 1,000 JPY XLEG

OKA NRT

NRT CTS

CTS NRT

NRT KIX

KIX NRT

Seat Extra Leg-room

NRT HKG

International Economy 1,200 JPY XLEG

HKG NRT

NRT TPE

TPE NRT

NRT CEB

CEB NRT

Bag Extra Bag

NRT OKA

Domestic Economy

1,000 JPY (+5kg) 2,000 JPY (+10kg)

3,000 JPY (+15kg) 4,000 JPY (+20kg)

5,000 JPY (+25kg)

6,000 JPY (+30kg)

XBAG

OKA NRT

NRT CTS

CTS NRT

NRT KIX

KIX NRT

Bag Extra Bag

NRT HKG

International Economy

1,000 JPY (+5kg) 2,000 JPY (+10kg)

3,000 JPY (+15kg)

4,000 JPY (+20kg) 5,000 JPY (+25kg)

6,000 JPY (+30kg)

XBAG

HKG NRT

NRT TPE

TPE NRT

NRT CEB

CEB NRT

Supported Airplane Types &

Seat Maps

15-Feb-18


P a g e | 3


Airbus A320-200 Seat Map Key

15-Feb-18


P a g e | 4


Supported

NDC APIs (V 15.2)

15-Feb-18


P a g e | 5


IFLY RES NDC API SERVICES

1. AirDocDisplay

2. AirShopping

3. BaggageAllowance

4. BaggageCharges

5. FlightPrice

6. FareRules

7. InvGuarantee

8. InvReleaseNotif

9. OrderCreate

10. OrderRetrieve

11. OrderList

12. ServiceList

13. ServicePrice

14. SeatAvailability

15. ItinReshop

16. OrderCancel

15-Feb-18


P a g e | 6


NDC PROCESS FLOW

1. Order Creation

15-Feb-18


P a g e | 7


2. Retrieve Order

15-Feb-18


P a g e | 8


3. Cancel & Rebooking an Order

15-Feb-18


P a g e | 9


4. Order Cancel

15-Feb-18


P a g e |

10


Service Description & Sample Requests

1. AirDocDisplay Description

This operation is used to retrieve the ticket information based on the search criteria. The ticket details search will be based on the ticket number and the operation will retrieve the ticket details including the details of conjunction tickets.

Sample Request

NDC

15.2

*******

JW

5648440344021

15-Feb-18


P a g e |

11


2. AirShopping

Description

The AirShopping service will support the following basic search options.

Basic One-Way search It will be possible to provide departure, arrival information and traveller information (represented by PTC) to list availability for the requested departure date and optional calendar days. All flights available for the requested dates will be displayed along with the one way fares and included ancillaries (if applicable) for the provided fare families. All fare information and fare class availability will be grouped inside an Offer. Each Offer, will be sub-divided into OfferItems, where an OfferItem corresponds to the fare information priced for a traveler type (Adult, Child or Infant categories) in the specified Point of Sale (POS) currency. It is the responsibility of the API consumer to find the product of the price per PTC and the PTC quantity, and display the total at this stage to the customer (passenger or agent). The OfferItem also contains the Fare Components (FCs) which were used to price the OfferItem. For one-way trips, the API consumer would normally need to refer the priced values at OfferItem level. This would contain the fare amount, discounts, applicable taxes and surcharges.

Basic Round-trip or Multi-destination search It is possible to search for multiple Origin-Destination (OD) combinations. For round-trip search, 2 ODs can be provided in the request. For multi-destination search up to 5 ODs will be supported. The Flight information would be provided for each of the searched ODs separately. The Offer in this case will be priced for the entire trip. This would mean that each Offer would correspond to a possible combination of Flights, and there will be exactly one Flight representing each and every requested OD. The Offer would be priced for all the Flights combined and the corresponding amounts would be available in the OfferItem for a PTC. If the API consumer does not wish to the Offer in this format, then a logic can be formulated at the consumer side to scan through each and every OfferItem, and check the Fare Components (FCs) involved. These FCs contain the basic price information for each Segment in the Flight. For example, consider a connection flight departing from BOM to DXB via DEL has the following segment

a) XX100/BOM-DEL b) XX200/DEL-DXB

15-Feb-18


P a g e |

12


For each offer encapsulating this connection flight, there would be two FCs say, FC_100* and FC_200*, for each of the flight segments. The consumer can scan through all OfferItems, and identify the relation between Flight Segments and OfferItems. Following this, the consumer can find out the unique FCs for each segment, and finally display Flight-Fare options for each OD on the User Interface (UI). Note: * means the IDs used to depict the FCs are for demonstration purpose only. These should not be considered as actual values Promo-code search option In combination with one-way and multi-destination trips, there is the option to specify a promo-code that can influence the pricing of the searched ODs. The request will support accepting a promo-code that is defined in iFly Res, and the corresponding discounts will be applied to the Offers in the response. The discounted price will be available at the OfferItem level as well as the FareComponent levels. Calendar dates (Lead Pricing) search option

It is possible to specify the calendar dates before and after the searched Departure date for each OD. In case the searched dates are sold out or if there is no service for the particular date, the lowest fare amount will be indicated as below a) In case there are no flights operating on a particular date, the best fare amount

will be represented as -1. This number (-1) implies that there are no flights operating on the particular day.

b) In case there are flights on a particular day, but all booking classes are sold out, then this will be represented as -2. This number (-2) implies that all booking classes of all flights operating on the day are sold-out.

15-Feb-18


P a g e |

13


Sample Request [1 Adult, One-way search]

JP

NDC

15.1.2

*******

JW

ADT

ADA 2018-05-22

AYT

15-Feb-18


P a g e |

14


SunEco

2

15-Feb-18


P a g e |

15


Sample Request [1 Adult 1 Child & 1 Infant, One-way search]

JP

NDC

15.1.2

*******

JW

ADT

CHD

INF

15-Feb-18


P a g e |

16


ADA

2018-05-22

AYT

SunEco

2

15-Feb-18


P a g e |

17


Sample Request [1 Adult 1 Child & 1 Infant, Return search]

JP

NDC

15.1.2

*******

JW

ADT

CHD

INF

15-Feb-18


P a g e |

18


ADA

2018-05-22

AYT

AYT 2018-05-24

ADA

SunEco

2

15-Feb-18


P a g e |

19


3. BaggageAllowance

Description

Baggage allowance service request contains the qualifiers such as passenger details, itinerary details including O&D and flight details, fare details, point of sale etc. to get the free baggage allowance for check-in bags. This service will not provide additional baggage options allowed by the airlines with additional charges. Details of allowed cabin baggage / carry-on baggage will not be provided in the baggage allowance response.

Sample Request

>

JP

FRA

NDC

15.2

*******

JW

ADT

15-Feb-18


P a g e |

20


JW_OD_1492924013610

JW_SEG_1492924013615

ADA 2018-05-22Z

09:05

AYT 2018-05-22Z

10:15 0

JW

7631

738 800

Y ECONOMY

PT1H10M0.000S

0

SUNECO

ST

15-Feb-18


P a g e |

21


15-Feb-18


P a g e |

22


4. BaggageCharges

Description

Baggage charges service request contains the qualifiers such as passenger details, itinerary details including O&D and flight details, fare details, point of sale etc. to get the list of charges for check in bags. iFly Res does not support fees for carry-on bags. The system will calculate the baggage charges after forming check-in-able groups and by applying baggage policy rules / fee rules on each check-in-able group. The baggage charges details will be provided at a trip / check-in-able group level in the response. If there is any tax to be applied over the baggage fees, that information will also be included in the response.

Sample Request

JP FRA

NDC

15.2

*******

JW

15-Feb-18


P a g e |

23


ADT

JW_OD_1492924013610

JW_SEG_1492924013615

ADA 2018-05-22Z

09:05

AYT 2018-05-22Z

10:15 0

JW

7631

738

800

Y ECONOMY

PT1H10M0.000S

0

15-Feb-18


P a g e |

24


SUNECO

ST

15-Feb-18


P a g e |

25


5. FlightPrice

Description

This operation is to be mandatorily invoked in order to obtain the correct price of the PNR. This operation can be triggered multiple times in an order creation flow to update the shopping cart with the final price based on each product selection by the Traveller. FlightPrice response includes the following details.

Itinerary price including base fare, applied fare, discount rate / value, surcharge details, tax breakdown, fare basis and ticket designator for each fare component, fare string etc.

Fees and applicable tax for each ancillary service. This operation can be triggered before / after collecting passenger details. If this service is triggered after collecting all the passenger details, then the OTAs / third party systems can display the accurate price details to the traveller considering the parameters such as customer profile ID / loyalty ID, customer value, nationality, tier level etc.

Sample Request

JP

NDC 15.1.2

*******

JW

15-Feb-18


P a g e |

26


EUR

ADT

JW_OD_1494289508263

JW_SEG_1494289508280

ADA 2018-05-22Z

09:05

AYT 2018-05-22Z

10:15 0

JW

7631

738

800

Y ECONOMY

D

PT1H10M0.000S

0

15-Feb-18


P a g e |

27


SUNECO

JW_SEG_1494289508280

15.75

DXDOM

JW_SEG_1494289508280

SUNECO ST

15-Feb-18


P a g e |

28


35.584744

6.27 7.64

NORMAL

15-Feb-18


P a g e |

29


6. FareRules

Description

This operation will retrieve the fare description for a particular fare basis code. The system expects fare basis and the preferred language for displaying the fare rule as Request. Based on this Request, the corresponding fare rules in the preferred language will be given as response.

Sample Request

JP FRA

NDC 15.2

*******

JW

Vanilla Air

en

ADA

2018-05-22

15-Feb-18


P a g e |

30


09:05

AYT 2018-05-22

10:15

0

LXDOM

JW

15-Feb-18


P a g e |

31


7. InvGuarantee

Description

The InvGuarantee service will support blocking/holding of seats for the flight segments that participate in an offer. It is possible only to guarantee an Offer as a whole. Partial guarantee in terms of neither flight segments, nor OfferItems is possible. All flight segments for all OfferItems will be guaranteed with a single GuaranteeID and Timelimit. Although guarantee is possible only for an Offer as a whole, it is only possible to specify the OfferItem IDs in the request. It is mandated to price the offer using flightPrice operation, before calling guaranteeInventory. This will re-create all the OfferItem IDs, and all the OfferItem IDs should be provided in the guaranteeInventory request. A single GuaranteeID with Timelimit will be generated, and it will be attached against each and every OfferItem ID in the response. The consumer should call orderCreate operation along with this GuaranteeID to ensure confirmed booking. If the consumer calls orderCreate after the Guarantee Timelimit expires, then the booking will not be possible. If the consumer session expires before calling the orderCreate operation, or the user leaves the page voluntarily, the consumer is recommended to call the releaseInventory operation, which will release the blocked/held seats and make it available to the public.

Sample Request

15.2

NDC

*******

JW Sun Express Airlines

15-Feb-18


P a g e |

32


JW_OFFERITEM_1492924013600 JW_OFFERITEM_1492924013656

ADT

ADA 2018-05-22Z

09:05

AYT 2018-05-22Z

10:15 0

JW

7631

738

800

PT1H10M0.000S

0

A

ECONOMY

ADA

2018-05-22Z

15-Feb-18


P a g e |

33


19:40

AYT 2018-05-22Z

20:50

0

JW

7711

738 800

PT1H10M0.000S

0

E

ECONOMY

P0Y0M0DT1H10M0.000S

JW_SEG_1492924013615

P0Y0M0DT1H10M0.000S

JW_SEG_1492924013606

15-Feb-18


P a g e |

34


8. InvReleaseNotif

Description

The release Inventory operation can be used to release seats that are blocked by calling the guarantee Inventory operation. It is recommended that the consumer effectively uses this service so that inventory of the ORA is not blocked in cases where the user session is lost, or the customer is not interested in the Offer any longer.

Sample Request

NDC

15.2

*******

JW Vanilla Air

22

15-Feb-18


P a g e |

35


9. OrderCreate

Description

This operation creates a PNR taking as input the basic details like guest details, segment and fare details, contact details, payment details as the basic inputs for the creation of a PNR. Seat details can also be provided, through this operation. Payment details for the entire PNR will collected as single payment. The supported payment types are Credit Card, Agency, Cash, Cheque, Gift Certificate, Credit File, Direct Debit, Convenience store, EFT, Paypal. It supports more than payment type in single request. (Sample Card Info is shared ) If in case the OrderCreate is called after marking the inventory (GuaranteeInventory operation) then it has to provide the InventoryGuarantee id along with createOrder request. ExternalRecordLocatorDetails has been brought in createOrder operation to update the iFly Res system with external record locator. The same has been added in retrieveOrder operation response to retrieve the external record locator details. Certain external booking systems would like to update their record locator number into iFly Res system. In such cases, the new change would help the external system to update and the retrieve the external record locator details.

Sample Request

JP

NDC 15.1.2

*******

15-Feb-18


P a g e |

36


JW

ADT

1972-02-01

MR Adams

Anton

Nieuwe Plaatsen 201a

NACHGERAAD

7501KO MO

Personal [email protected]

HOME

313712387

Male

15.75

JW_SEG_1494289508280

ADA

2018-05-22Z 09:05

15-Feb-18


P a g e |

37


AYT 2018-05-22Z

10:15 0

JW

7631

738

800

Y ECONOMY

D

PT1H10M0.000S

0

DXDOM

15-Feb-18


P a g e |

38


ST PT ROAD

VIA DELLE ARTI ROM

23535 ITALY

6.27

6.27

2

SUNECO

ST

JW_SEG_1494289508280

15-Feb-18


P a g e |

39


10. OrderRetrieve

Description

The itinerary details of the PNRs, satisfying the search condition are retrieved. If any of the Requested data does not match with the corresponding data in the retrieved PNR then an exception is thrown. This operation is designed mainly for retrieving the details of a particular PNR. If a set of PNRs need to be retrieved, then it is recommended to use OrderList operation. It will retrieve the summary of all PNRs based on search criteria. If more details are needed for a particular PNR call the OrderRetrieve service with that PNR in search criteria.

Sample Request

NDC

15.2

*******

JW Vanilla Air

B28L24

15-Feb-18


P a g e |

40


11. OrderList

Description

The OrderList operation will support the following basic search options.

Loyalty Number Based Search This search combination Loyalty number + Creation Date Range or Travel Date Range can be used for getting the summary of all the PNRs created by a particular loyalty customer.

ProfileId Based Search This search combination ProfileId + Creation Date Range or Travel Date Range can be used for getting the summary of all the PNRs created by a particular ProfileId.

PNR Flight Based Search This search combination FlightNumber + Travel Date Range can be used for getting the summary of all the PNRs created for these Flight dates.

EmailId Based Search This search combination EmailId + Creation Date Range or Travel Date Range can be used for getting the summary of all the PNRs created by a particular EmailId.

Sample Request

NDC 15.2

*******

JW

15-Feb-18


P a g e |

41


2018-05-01Z 2018-05-10Z

15-Feb-18


P a g e |

42


12. ServiceList

Description

All the ancillary services except baggage and seats will be handled using this service. If SSR inventory is not available for the SSR for any of the flight segment, then that SSR will not be included in the service list. The default generic fees will be calculated for each passenger type specified in the request. Fee calculation considering passenger specific properties such as nationality, loyalty tier level etc. is not applicable for this service. If there is any tax to be applied over one or more ancillary fees, that information will also be included in the response.

Sample Request

JP

FRA

NDC 15.2

*******

JW

15-Feb-18


P a g e |

43


ADT

JW_OD_1492924013610

JW_SEG_1492924013615

ADA

2018-05-20Z 09:05

AYT

2018-05-20Z 10:15

0

JW 7631

738 800

Y

ECONOMY

PT1H10M0.000S

0

SUNECO

15-Feb-18


P a g e |

44


ST

15-Feb-18


P a g e |

45


13. ServicePrice

Description

This operation returns the final price of the ancillary services selected by the traveller. All the ancillary services except baggage can be priced using this operation. This operation can be used to get the final price of seat ancillary as well.

Sample Request

JP

FRA

NDC

15.2

*******

JW Vanilla Air

EUR

ADT

IT

IT

15-Feb-18


P a g e |

46


P RAHUL

XLEG

XLEG

JW_SEGREFS_1492924013603 JW_PAX_1

true

JW_OD_1492924013610

JW_SEG_1492924013615

ADA

2018-05-20Z 09:05

AYT

2018-05-20Z 10:15

0

JW 7631

738

800

I

ECONOMY

I

15-Feb-18


P a g e |

47


PT2H0M0.000S

SUNECO

JW_SEG_1492924013615

21.19

AXDOM

AXDOM

15-Feb-18


P a g e |

48


JW_SEG_1492924013615

ECONOMY

ST

57.618643 18.92

0.0

NORMAL

15-Feb-18


P a g e |

49


14. SeatAvailability Description

Show seat availability service is used to get the details to construct the seat map and the associated default fees. The default generic fees, if any, applicable for each seat will be calculated and will be included in the response. Fee calculation considering passenger specific properties such as nationality, loyalty tier level etc. is not applicable for this service. If there is any tax to be applied over the fees charged for seat, that information will also be included in the response.

Sample Request

JP

FRA

NDC 15.1.2

*******

JW

Vanilla Air

JW 1F126AF1-7FCF-414F-8A3D-E4FFA408F747

15-Feb-18


P a g e |

50


JW_OD_1492924013610

ADA

2018-05-20Z 09:05

AYT

2018-05-20Z 10:15

JW

7631

320

ADA AYT

JW_SEG_1492924013615

15-Feb-18


P a g e |

51


15. ItinReshop Description

The ItinReshop service is used to get the refund/penalty quote if the booking were to be cancelled [Or] to get the new offer quote if the confirmed booking is to be cancelled & rebooked. ItinReshop can be invoked for the following contexts. Context 1 Refund/Penalty quote: NDC user can call ItinReshop to get the amount that would be refunded (i.e a refund quote) if the booking were to be (subsequently) cancelled. Context 3 Change Booking Reshop: NDC user can call ItinReshop for a ticketed confirmed booking to change date - time and/or change cabin/class of their confirmed flight. Context 4 Change Booking Reprice: NDC user can call ItinReshop to get the price quote for the new flights if they intend to change their current confirmed flights..

Sample Request- ItinReshopRQ for Order Cancellation

JP

NDC 15.1.2

Guest EN

Guest EN

JW

15-Feb-18


P a g e |

52


CANCEL

RY8242

Sample Request- ItinReshopRQ for Reshop

JP

NDC

15.1.2

*******

JW

Update NY2Z22

JW_OD_272855049

15-Feb-18


P a g e |

53


FRA

2018-12-09

AYT

2018-12-09

JW 141

Sample Request- ItinReshopRQ for Reprice

JP

NDC

15.1.2

*******

JW

15-Feb-18


P a g e |

54


UPDATE

NY2Z22

JW_OFFERITEM_1512635438081

94.99

JW_OD_272959770

JW_SEG_1512635438092

FRA 2018-12-09Z

14:30

AYT 2018-12-09Z

19:55 0

JW

141

737 800

5

ECONOMY

V

1

PT3H25M0.000S

15-Feb-18


P a g e |

55


VINT

ADT

K

MIKE MR

ST

15-Feb-18


P a g e |

56


16. OrderCancel Description

OrderCancel service is used to confirm the cancellation of an Order. The ItinReshopRS for cancel booking will provide the user with the penalty & refund information based on which the user can trigger OrderCancel to confirm the cancellation.

Sample Request

JP

NDC 15.1.2

Guest EN

Guest EN

JW

RY8242

15-Feb-18


P a g e |

57


NDC Developer Portal &

Documentation

15-Feb-18


P a g e |

58


How to use the iFly Res NDC API

Option 1 Client applications begin by getting the service description provided via the Web Services Description Language (WSDL).How the WSDL is retrieved varies depending upon the environment used to develop the client application. Once the WSDL defining the contract is retrieved and a proxy created by the application interacts with the API using standard SOAP requests. The Web Services are described by individual service files from which the WSDL and XML Schema Definition ( XSD) is accessed using the following end-point URL:

The Web Services API WSDL must be used to obtain the API contract for use by clients that use the API. Since the API is provided as a Web Service, the WSDL provides the needed interface definitions. This document does not intend to go into the details of Web Service technology, but focuses on how to effectively use iFly Res NDC Web Services. The basic pattern of usage for the API is to instantiate an API ServicePort which logically groups a set of APIs for the functional area, for example, NdcResServiceSOAPPort groups APIs which supports PNR creation flow. Once a ServicePort is instantiated it can be used to access to the APIs grouped within it. For programmers familiar with Object Oriented Model, the API ServicePort is similar to a class and all the APIs contained within it are methods of that class. Using an API method is similar to making a function call. iFly Res NDC API accepts input as XML objects. Parameters required for building the request object are collected by the client application either by asking a user for it / requesting it from the system or from the response of predecessor services. Once the data is collected, the RQ (request) to a given API are populated and the API is then called. For instance, the shopAir operation in the NdcResServiceSOAPPort needs an AirShoppingRQ object as an input parameter. If there are no exceptions, the API returns a response (RS) object which contains the results of the API operation. IBS would provide specific user/channel details which should be set as a mandatory data in the API request to iFly Res system. Any web service consumers who intend to use iFly Res APIs only needs to establish a connection and have a method for generating SOAP requests to communicate with Web Services.

15-Feb-18


P a g e |

59


Option 2 Send NDC request as basic HTTP Post. In this option the NDC consumer can build raw xml request and post it to the NDC end-point URL.

Following details are mandatory for all the aforementioned options. End Point URL info:

End Point NDC URL

The NDC request when triggered towards iFly Res, the system will validate the

AgentUserID information. It is important that you use the correct Party> Sender> AgentUserSender> AgentUserID.

AgentUserSender to be set in each NDC Request.

Will be provided by IBS

iFly Res requires you to set the HTTP Header with a userName and password.

userName Will be provided by IBS

password Will be provided by IBS

Card Info Applicable for Payment:

Card Type VI

Card Number 4355084355084358

CVV Code 513

Hold Name STARK

Expiry Date 1218

Note: You can Encrypt the aforementioned dummy card with the encryption standards. The document(iFlyRes_WebServiceAESEncryption.pdf) will be shared by IBS which depicts the encryption steps. OR Use the below mentioned test encryption: CardNumber: BnaqrQVwy3UnKJl+T3/rW67H6bBlU/IdaGtfari6mJ8=%~~`%~~~~~~~%^**(%$#%gwdKfdu+H8sMWOsw7JhWrQCZs+K/OXNO2RFS8KFPSPhaUx93v21JQDPGWRKCT/mePvuv/Xy4527p0FUVIzbfz0QRJPtvmGs8ibaUDrijEiACzfOLvbVurFFCTTUAZf+g7j++f8ZlN6REh0itYhSIF7S4du6xvQ/+Yy9SkwuiZKMNX81DOyQaYx1kNgFBdzpgwxGsG8bb7cxglYWl4kEZF49ZdAdmOeKQgapyGejqbpy/O6ktEdxRnvLmPfpRtVzPhLXa9h71Bhkz5jmhJWVgp/cwGHN4s6+3dpn6Iur0zCC88Nin4gii4Etwg73Iao/HRlY6HYmKtRMf34jb49pvqA== SeriesCode: Myx8YAI5iQRv/k5BCGbW6w==%~~`%~~~~~~~%^**(%$#%R+juo+cfqt/VgPXxfTBmwzrzn6oIpQBE+Ybk0vPLEobF9TzA1MLY8f6xsuJFRB6UASy+QGfpnR4pbWNUtTK2/BSC5lmhKLGkrgjYHnu49MnTSMxsZAIh85n0N4ZuLw80McJ2eG/d124s4TESKm+TzolDIQrvsI5TrtcYT9/mu95hG9CBwlYthksDz9gi6sK23iHPHbLpH0g/foHLOG6iZInOBhKL865Ah5ehCm0jhE2WaLrh

15-Feb-18


P a g e |

60


8MUcD6IlFqxTOeqLoUvCG4CbBiCMzCP9jLy6x2SeYOggau6iGkYuhMcdFfArM6nUfc71VRCHFerlUFJqgExS1a1IG7s5UHUvGa6Hhg== CardHolderName: 0gmcyDqd6KTzQxbjgmU0pw==%~~`%~~~~~~~%^**(%$#%ZdoEHJvOUTHOJXn5fh5LjcJW5FvoGsUrokQjKFn759/h2l9Rq1eG3i9GSOKr10OzJ9B2dFCSEc5fWNPwLyr3xdWP28a4xcGdhtwa8cgLiYFfRJ//yz9aP0++3MLQNTYod+PpDNlRmhft3CaS3VYPZLLHNmZQv51f0CS5xW4GlghASJnWDeXad1j5F4Opoavt8OrwcLlJDA6WcsE9R4yTSh07litl6QQ99T75uh0askwH2AskddVOTYhEdH1B7TwtRrbV2URPQE4+9Xd+90Y7IP+bOTlfmIIexFot4/rPPrOGTD122TgsqlfcQC+9OhiDnYttzUZ1U4XRdXJQF8dANA== Expiration: 5c1NTE8bR1YLrMXWSSH0wA==%~~`%~~~~~~~%^**(%$#%Jn7/bfhgzMSH0tlv5AisOVzTen/K8NxOBY99w8hXWUu0kkGhs7zmpdnUECOd4VCNmv9FQWojQIoFLu3C3YKSxE5WZaIdy6UtarB1k20XyjdZjNwT4yiK+iQBzLqv9XRgMgRkrF78gN0IQvXrR8p8pcwKamJhqkyaG4L0ahAPoyKM1lTSVY/buu9gM9PW8tPudR8QqKt3Ow8imcekGiiPrpediq5RxYI44A3zPQf5CPFVwH70FjZ4dstd361m4dIPWCaEZLB0ZEDqgcoXK7d1oLrkV7/JSknR+10AK7PNl84OneiQZpN88WEUnYaxNJ8IWC2DiliJdRrnhdne2BTwjg==

15-Feb-18


P a g e |

61


Checklist before Order Creation The HTTP request is send to the right URL. The correct WSDL end-point is used. The AgentUserSender set in the requests are as provided by IBS. Authentication credentials (HTTP header) needs to be set. Follow the encryption standards(iFlyRes_WebServiceAESEncryption.pdf) for

Card Payments via IBS NDC API.

15-Feb-18


P a g e |

62


Connect using Postman For quick connection to iFly Res NDC APIs, you can use either the Postman tool or other similar tools . Here the connection needs to be made to the following URL by sending POST HTTP request. https://iflyrestest.ibsgen.com:6013/iRes_NdcRes_WS/services/NdcResServiceSOAPPort?wsdl

An HTTP header with Content-Type: application/xml is required. An HTTP header with a valid authentication credentials (userName, password).

Note:- IBS will share the authentication credentials.

Set your NDC request and trigger the HTTP request by sending valid NDC RQ. You may use any of the samples given in this brochure.

The NDC request when triggered towards iFly Res, the system will validate the AgentUserID information. It is important that you use the correct Party> Sender> AgentUserSender> AgentUserID.

NOTE:- It is advised to first connect with the AirShopping response and then proceed with connection to other services.

15-Feb-18


P a g e |

63


15-Feb-18


P a g e |

64


Mapping between service request and predecessor service response. As most of the service request has a dependency with the predecessor service response,

the mapping between service request and corresponding predecessor service response

is depicted in the below table.

Service Request Predecessor Service Response

RQ -RS Mapping

AirShoppingRQ - As AirShoppingRQ is the first API call in the booking flow, RQ needs to be created from basic search inputs.

ServiceListRQ AirShoppingRS

ServiceListRQ.zip

BaggageAllowanceRQ AirShoppingRS

BaggageAllowance

RQ.zip

BaggageChargesRQ AirShoppingRS

BaggageChargesR

Q.zip

ServicePriceRQ AirShoppingRS ServiceListRS

SeatAvailabilityRS ServicePriceRQ.zip

SeatAvailabilityRQ AirShoppingRS

SeatAvailabilityRQ.z

ip

FlightPriceRQ AirShoppingRS BaggageAllowanceRS

SeatAvailabilityRS ServiceListRS

FlightPriceRQ.zip

OrderCreateRQ AirShoppingRS BaggageChargesRS

FlightPriceRS SeatAvailabilityRS

ServiceListRS

OrderCreateRQ.zip

OrderViewRS is the Response of OrderCreateRQ

ServiceListRQ Mapping Object Remarks

ServiceListRQ#PointOfSale#Location#CountryCode Example : IT

ServiceListRQ#PointOfSale#Location#CityCode Example : FCO

ServiceListRQ#PointOfSale#RequestTimeExample : 2016-05-13T07:38:00

ServiceListRQ#Document#Name AirShoppingRS#Document#Name

ServiceListRQ#Document#ReferenceVersion AirShoppingRS#Document#ReferenceVersion

ServiceListRQ#Party

ServiceListRQ#Party#Sender#AgentUserSender

This object is expected when the agent is a non

IATA agent . This will be used in the case where

there is direct connection between agent system

and iFlyRes

ServiceListRQ#Party#Sender#TravelAgencySender#OtherI

Ds#OtherID

This field is mandatory if OTA allows agent login

or in case of traditional agency system. Should

set iFlyRes assigned Booking Channel ID.


Ds#OtherID @Description

Constant text 'Booking Channel ID' should be set

here.

ServiceListRQ#Party#Sender#AgentUserSender#

AgentUserID

If Other ID contains Booking Channel ID, Agent

ID should be set. Else Booking Channel ID itself

should be set here

ServiceListRQ#Party#Sender#AgentUserSender#AgentUs

erID @Owner

Agency ID should be set If Agent login else this

field is not expected

ServiceListRQ#Party#Sender#TravelAgencySender

This object can be expected when the agent is

an IATA agent. In case of OTAs normally public

will do the booking but there are scenario where

a travel agent logins to an OTA system and do

the booking for the passenger. In such cases the

details of the agent details will have mentioned

within the Sender.


Ds#OtherID

This field is mandatory if OTA allows agent login

or in case of traditional agency system. iFlyRes

assigned Booking Channel ID is expected in this.


Ds#OtherID @Description

Constant text 'Booking Channel ID' should be set

here.

ServiceListRQ#Party#Sender#TravelAgencySender#Agenc

yID

If Other ID contains Booking Channel ID, Agent

ID should be set. Else Booking Channel ID itself

should be set here

ServiceListRQ#Party#Sender#TravelAgencySender#Agent

User#AgentUserID

Agent ID should be set if Agent login else this

field is not expected

ServiceListRQ#Party#Recipient#ORA_Recipient This object is mandatory

ServiceListRQ#Party#Recipient#ORA_Recipient# AirlineID

ORA (Offer Originating Airline) Recipient. Set the

Airline Iata Code of Offer Originating Airline .

(Example: XQ)

ServiceListRQ#Party#Recipient#ORA_Recipient# Name

Set the Airline Name (Example: Sun Express

Airlines)

ServiceListRQ#Parameters

ServiceListRQ#Parameters#Languages#LanguageCode Example : en

ServiceListRQ#Parameters#CurrCodes#CurrCode Example : USD

ServiceListRQ#Parameters#Inventory#GuaranteeInd Example : true

ServiceListRQ#Parameters#ServiceFilters#ServiceFilter#G

roupCo de Example : BG

ServiceListRQ#Parameters#ServiceFilters#ServiceFilter#S

ubGroup Code Example : OCC

ServiceListRQ#Parameters#Pricing @AwardIncludedIndExample : false

ServiceListRQ#Travelers

ServiceListRQ#Travelers#Traveler#AnonymousTraveler

@ObjectKey

AirShoppingRS#DataLists#AnonymousTravelerList#A

nonymou sTraveler

@ObjectKey

Any one of the Travelller

type(AnonymousTraveler or RecognizedTraveler

)is required

ServiceListRQ#Travelers#Traveler#AnonymousTraveler#P

TC @Quantity


nonymou sTraveler#PTC

@Quantity

ServiceListRQ#Travelers#Traveler#AnonymousTraveler#R

esidenc eCode


nonymou sTraveler#ResidenceCode

ServiceListRQ#Travelers#Traveler#RecognizedTraveler Any one of the Travelller

type(AnonymousTraveler or

RecognizedTraveler )is required

ServiceListRQ#Query

ServiceListRQ#Query#OriginDestination#OriginDestinatio

nKey

AirShoppingRS#DataLists#OriginDestinationList#Origi

nDestina tion#OriginDestinationKey

BaggageAllowanceRQ#Query#OriginDestination#Flight

@refs

AirShoppingRS#OffersGroup#AirlineOffers#AirlineOff

er#Price

dOffer#OfferPrice#FareDetail#FareComponent

@refsServiceListRQ#Query#OriginDestination#Flight#Segment

Key

AirShoppingRS#DataLists#FlightSegmentList#FlightSe

gment#S egmentKey

ServiceListRQ#Query#OriginDestination#Flight#Departur

e#Airpor tCode


gment#D eparture#AirportCode


e#Date


gment#D eparture#Date


e#Time


gment#D eparture#Time

ServiceListRQ#Query#OriginDestination#Flight#Arrival#Ai

rportCo de


gment#A rrival#AirportCode

ServiceListRQ#Query#OriginDestination#Flight#Arrival#D

ate


gment#A rrival#Date

ServiceListRQ#Query#OriginDestination#Flight#Arrival#Ti

me


gment#A rrival#Time

ServiceListRQ#Query#OriginDestination#Flight#Marketin

gCarrier #AirlineID


gment# MarketingCarrier#AirlineID

ServiceListRQ#Query#OriginDestination#Flight#Marketin

gCarrier #FlightNumber


gment# MarketingCarrier#FlightNumber

ServiceListRQ#Query#OriginDestination#Flight#Equipme

nt#Aircr aftCode


gment#E quipment#AircraftCode

ServiceListRQ#Query#OriginDestination#Flight#CabinTyp

e#Code


er#Price

dOffer#Associations#ApplicableFlight#FlightSegment

Referenc e#Cabin#CabinDesignatorServiceListRQ#Query#OriginDestination#Flight#CabinTyp

e#Name


er#Price


Referenc e#Cabin#MarketingNameServiceListRQ#Query#OriginDestination#Flight#CabinTyp

e#Origin DestinationReferences


er#Price


Referenc e#refServiceListRQ#Query#OriginDestination#Flight#Details#Fl

ightDur ation#Value


gment#Fl ightDetail#FlightDuration#Value

ServiceListRQ#Query#OriginDestination#Flight#Details#S

tops


gment#Fl ightDetail#Stops

ServiceListRQ#Metadata

ServiceListRQ#Metadata#Shopping#ShopMetadataGroup

#Offer# OfferMetadatas#OfferMetadata#

@MetadataKey

AirShoppingRS#Metadata#Shopping#ShopMetadata

Group#Of fer#OfferMetadatas#OfferMetadata

@MetadataKey

ServiceListRQ#Metadata#Shopping#ShopMetadataGroup

#Offer#

OfferMetadatas#OfferMetadata#AugmentationPoint#Au

gPoint @Key


Group#Of

fer#OfferMetadatas#OfferMetadata#AugmentationP

oint#Aug Point

@KeyServiceListRQ#Metadata#Shopping#ShopMetadataGroup

#Offer#


gPoint#F areDetailAugPoint#FareLevel


Group#Of


oint#Aug Point#FareDetailAugPoint#FareLevelServiceListRQ#Metadata#Shopping#ShopMetadataGroup

#Offer#


gPoint#F areDetailAugPoint#FareBasis


Group#Of


oint#Aug Point#FareDetailAugPoint#FareBasis

ServiceListRQFile AttachmentServiceListRQ.pdf

BaggageAllowanceRQ Mapping Object Remarks

BaggageAllowanceRQ#PointOfSale#Location#CountryCod

e

Example : IT

BaggageAllowanceRQ#PointOfSale#Location#CityCode Example : FCO

BaggageAllowanceRQ#PointOfSale#RequestTimeExample : 2016-05-13T07:38:00

BaggageAllowanceRQ#Document#Name AirShoppingRS#Document#Name

BaggageAllowanceRQ#Document#ReferenceVersion AirShoppingRS#Document#ReferenceVersion

BaggageAllowanceRQ#Party

BaggageAllowanceRQ#Party#Sender#AgentUserSender#

AgentUserID

For all OTAs, connecting as non Agents, this field needs

to be set with the provided Booking Channel.


OtherIDs#OtherID @Description

For B2B login, where the Agent details will be used to

login, this field needs to be set with 'Booking Channel ID'


OtherIDs#OtherID


login, this field needs to be set with the provided

Booking Channel.


AgentUserID @Owner


login, this field needs to be set with the provided Agency

Code


AgentUserID


login, this field needs to be set with the provided Agent

ID

BaggageAllowanceRQ#Party#Recipient#ORA_Recipient This object is mandatory

BaggageAllowanceRQ#Party#Recipient#ORA_Recipient#

AirlineID

ORA (Offer Originating Airline) Recipient. Set the Airline

Iata Code of Offer Originating Airline . (Example: XQ)

BaggageAllowanceRQ#Party#Recipient#ORA_Recipient#

Name Set the Airline Name (Example: Sun Express Airlines)

BaggageAllowanceRQ#Parameters

BaggageAllowanceRQ#Parameters#Languages#Language

Code

Example : en

BaggageAllowanceRQ#Parameters#CurrCodes#CurrCode Example : USD

BaggageAllowanceRQ#Travelers

BaggageAllowanceRQ#Travelers#Traveler#AnonymousTr

aveler#P TC

@Quantity

AirShoppingRS#DataLists#AnonymousTravelerList

#Anonym ousTraveler#PTC

@Quantity


type(AnonymousTraveler or RecognizedTraveler )is

required

BaggageAllowanceRQ#Travelers#Traveler#AnonymousTr

aveler#R esidenceCode

AirShoppingRS#DataLists#AnonymousTravelerList

#Anonym ousTraveler#ResidenceCode

BaggageAllowanceRQ#Travelers#Traveler#RecognizedTra

veler

Any one of the Travelller type(AnonymousTraveler or


BaggageAllowanceRQ#Query

BaggageAllowanceRQ#Query#OriginDestination#OriginD

estinatio nKey

AirShoppingRS#DataLists#OriginDestinationList#O

riginDest ination#OriginDestinationKey

BaggageAllowanceRQ#Query#OriginDestination#Flight

@refs

AirShoppingRS#OffersGroup#AirlineOffers#Airline

Offer#Pri

cedOffer#OfferPrice#FareDetail#FareComponent

@refsBaggageAllowanceRQ#Query#OriginDestination#Flight#S

egment Key

AirShoppingRS#DataLists#FlightSegmentList#Flight

Segmen t#SegmentKey

BaggageAllowanceRQ#Query#OriginDestination#Flight#D

epartur e#AirportCode


Segmen t#Departure#AirportCode


epartur e#Date


Segmen t#Departure#Date


epartur e#Time


Segmen t#Departure#Time

BaggageAllowanceRQ#Query#OriginDestination#Flight#A

rrival#Ai rportCode


Segmen t#Arrival#AirportCode


rrival#D ate


Segmen t#Arrival#Date


rrival#Ti me


Segmen t#Arrival#Time

BaggageAllowanceRQ#Query#OriginDestination#Flight#

Marketin gCarrier#AirlineID


Segmen t#MarketingCarrier#AirlineID

BaggageAllowanceRQ#Query#OriginDestination#Flight#

Marketin gCarrier#FlightNumber


Segmen t#MarketingCarrier#FlightNumber

BaggageAllowanceRQ#Query#OriginDestination#Flight#E

quipme nt#AircraftCode


Segmen t#Equipment#AircraftCode

BaggageAllowanceRQ#Query#OriginDestination#Flight#E

quipme nt#AirlineEquipCode


Segmen t#Equipment#AirlineEquipCode

BaggageAllowanceRQ#Query#OriginDestination#Flight#C

abinTyp e#Code


Offer#Pri

cedOffer#Associations#ApplicableFlight#FlightSeg

mentRef erence#Cabin#CabinDesignatorBaggageAllowanceRQ#Query#OriginDestination#Flight#C

abinTyp e#Name


Offer#Pri


mentRef erence#Cabin#MarketingName

BaggageAllowanceRQ#Query#OriginDestination#Flight#C

abinTyp e#OriginDestinationReferences


Offer#Pri


mentRef erence#refBaggageAllowanceRQ#Query#OriginDestination#Flight#D

etails#Fl ightDuration#Value


Segmen t#FlightDetail#FlightDuration#Value


etails#S tops


Segmen t#FlightDetail#Stops

BaggageAllowanceRQ#Metadata

BaggageAllowanceRQ#Metadata#Shopping#ShopMetada

taGroup #Offer#OfferMetadatas#OfferMetadata

@MetadataKey

AirShoppingRS#Metadata#Shopping#ShopMetada

taGroup #Offer#OfferMetadatas#OfferMetadata

@MetadataKey

BaggageAllowanceRQ#Metadata#Shopping#ShopMetada

taGroup

#Offer#OfferMetadatas#OfferMetadata#AugmentationP

oint#Au gPoint

@Key


taGroup

#Offer#OfferMetadatas#OfferMetadata#Augment

ationPoi nt#AugPoint

@KeyBaggageAllowanceRQ#Metadata#Shopping#ShopMetada

taGroup


oint#Au gPoint#FareDetailAugPoint#FareLevel


taGroup


ationPoi BaggageAllowanceRQ#Metadata#Shopping#ShopMetada

taGroup


oint#Au gPoint#FareDetailAugPoint#FareBasis


taGroup


ationPoi

BaggageAllowanceRQFile AttachmentBaggageAllowanceRQ.pdf

BaggageChargesRQ Mapping Object Remarks

BaggageChargesRQ#PointOfSale#Location#CountryCode Example : IT

BaggageChargesRQ#PointOfSale#Location#CityCode Example : FCO

BaggageChargesRQ#PointOfSale#RequestTimeExample : 2016-05-13T07:38:00

BaggageChargesRQ#Document#Name AirShoppingRS#Document#Name

BaggageChargesRQ#Document#ReferenceVersion AirShoppingRS#Document#ReferenceVersion

BaggageChargesRQ#Party

BaggageChargesRQ#Party#Sender#AgentUserSender#

AgentUserID

For all OTAs, connecting as non Agents, this field needs

to be set with the provided Booking Channel.


OtherIDs#OtherID @Description


login, this field needs to be set with 'Booking Channel

ID'


OtherIDs#OtherID



Booking Channel.


AgentUserID @Owner



Agency Code


AgentUserID



Agent ID

BaggageChargesRQ#Party#Recipient#ORA_Recipient This object is mandatory

BaggageChargesRQ#Party#Recipient#ORA_Recipient#

AirlineID

ORA (Offer Originating Airline) Recipient. Set the

Airline Iata Code of Offer Originating Airline . (Example:

XQ)

BaggageChargesRQ#Party#Recipient#ORA_Recipient#


BaggageChargesRQ#Parameters

BaggageChargesRQ#Parameters#Languages#LanguageCod

e

Example : en

BaggageChargesRQ#Parameters#CurrCodes#CurrCode Example : USD

BaggageChargesRQ#Travelers

BaggageChargesRQ#Travelers#Traveler#AnonymousTrave

ler#PTC @Quantity

AirShoppingRS#DataLists#AnonymousTravelerList#

Anony mousTraveler#PTC

@Quantity

Any one of the Travelller type(AnonymousTraveler or


BaggageChargesRQ#Travelers#Traveler#AnonymousTrave

ler#Res idenceCode

AirShoppingRS#DataLists#AnonymousTravelerList#

Anony mousTraveler#ResidenceCode

BaggageChargesRQ#Travelers#Traveler#RecognizedTravel

er


type(AnonymousTraveler or RecognizedTraveler )is

required

BaggageChargesRQ#Query

BaggageChargesRQ#Query#OriginDestination#OriginDesti

nationK ey

AirShoppingRS#DataLists#OriginDestinationList#Ori

ginDe stination#OriginDestinationKey

BaggageChargesRQ#Query#OriginDestination#Flight

@refs

AirShoppingRS#OffersGroup#AirlineOffers#AirlineO

ffer#P

ricedOffer#OfferPrice#FareDetail#FareComponent

@refsBaggageChargesRQ#Query#OriginDestination#Flight#Seg

mentKe y


Segme nt#SegmentKey

BaggageChargesRQ#Query#OriginDestination#Flight#Dep

arture# AirportCode


Segme nt#Departure#AirportCode


arture# Date


Segme nt#Departure#Date


arture# Time


Segme nt#Departure#Time

BaggageChargesRQ#Query#OriginDestination#Flight#Arriv

al#Airp ortCode


Segme nt#Arrival#AirportCode


al#Dat e


Segme nt#Arrival#Date


al#Tim e


Segme nt#Arrival#Time


al#Cha ngeOfDay


Segme nt#Arrival#ChangeOfDay

BaggageChargesRQ#Query#OriginDestination#Flight#Mar

ketingC arrier#AirlineID


Segme nt#MarketingCarrier#AirlineID

BaggageChargesRQ#Query#OriginDestination#Flight#Mar

ketingC arrier#FlightNumber


Segme nt#MarketingCarrier#FlightNumber

BaggageChargesRQ#Query#OriginDestination#Flight#Equi

pment# AircraftCode


Segme nt#Equipment#AircraftCode

BaggageChargesRQ#Query#OriginDestination#Flight#Equi

pment# AirlineEquipCode


Segme nt#Equipment#AirlineEquipCode

BaggageChargesRQ#Query#OriginDestination#Flight#Cabi

nType# Code


Offer#P

ricedOffer#Associations#ApplicableFlight#FlightSeg

ment Reference#Cabin#CabinDesignatorBaggageChargesRQ#Query#OriginDestination#Flight#Cabi

nType# Name


Offer#P


ment Reference#Cabin#MarketingName

BaggageChargesRQ#Query#OriginDestination#Flight#Cabi

nType# OriginDestinationReferences


Offer#P


ment Reference#refBaggageChargesRQ#Query#OriginDestination#Flight#Deta

ils#Flig htDuration#Value


Segme nt#FlightDetail#FlightDuration#Value

BaggageChargesRQ#Query#OriginDestination#Flight#Deta

ils#Sto ps


Segme nt#FlightDetail#Stops

BaggageChargesRQ#Metadata

BaggageChargesRQ#Metadata#Shopping#ShopMetadataG

roup#

Offer#OfferMetadatas#OfferMetadata @MetadataKey

irShoppingRS#Metadata#Shopping#ShopMetadata

Group #Offer#OfferMetadatas#OfferMetadata

@MetadataKey

BaggageChargesRQ#Metadata#Shopping#ShopMetadataG

roup#

Offer#OfferMetadatas#OfferMetadata#AugmentationPoi

nt#Aug Point

@Key

AirShoppingRS#Metadata#Shopping#ShopMetadat

aGrou

p#Offer#OfferMetadatas#OfferMetadata#Augmen

tation Point#AugPoint

@KeyBaggageChargesRQ#Metadata#Shopping#ShopMetadataG

roup#


nt#Aug Point#FareDetailAugPoint#FareLevel


aGrou


tation BaggageChargesRQ#Metadata#Shopping#ShopMetadataG

roup#


nt#Aug Point#FareDetailAugPoint#FareBasis


aGrou


tation

BaggageChargesRQFile AttachmentBaggageChargesRQ.pdf

ServicePriceRQ Mapping Object Remarks

ServicePriceRQ#PointOfSale

ServicePriceRQ#PointOfSale#Location#CountryCodeSet Point of Sale country code

Example : IT

ServicePriceRQ#PointOfSale#RequestTime

Point of sale timestamp value. Note: This may be used if

the point of sale time zone differs from the message

creation

timestamp.ServicePriceRQ#Document#Name AirShoppingRS#Document#Name

ServicePriceRQ#Document#ReferenceVersion Set version '15.1.2'

ServicePriceRQ#Party

ServicePriceRQ#Party#Sender#AgentUserSender

This object is expected when the agent is a non IATA

agent . This will be used in the case where there is direct

connection between agent system and iFlyRes

ServicePriceRQ#Party#Sender#TravelAgencySender

#OtherIDs#OtherID

This field is mandatory if OTA allows agent login or in

case of traditional agency system. Should set iFlyRes

assigned Booking Channel ID.


#OtherIDs#OtherID @Description Constant text 'Booking Channel ID' should be set here.

ServicePriceRQ#Party#Sender#AgentUserSender#

AgentUserID

If Other ID contains Booking Channel ID, Agent ID

should be set. Else Booking Channel ID itself should be

set here

ServicePriceRQ#Party#Sender#AgentUserSender#Ag

entUserID @Owner

Agency ID should be set If Agent login else this field is

not expected


This object can be expected when the agent is an IATA

agent. In case of OTAs normally public will do the

booking but there are scenario where a travel agent

logins to an OTA system and do the booking for the

passenger. In such cases the details of the agent details

will have mentioned within the Sender.


#OtherIDs#OtherID

This field is mandatory if OTA allows agent login or in

case of traditional agency system. iFlyRes assigned

Booking Channel ID is expected in this.


#OtherIDs#OtherID @Description Constant text 'Booking Channel ID' should be set here.


#AgencyID

If Other ID contains Booking Channel ID, Agent ID

should be set. Else Booking Channel ID itself should be

set here


#AgentUser#AgentUserID

Agent ID should be set if Agent login else this field is not

expected

ServicePriceRQ#Party#Recipient#ORA_Recipient This object is mandatory

ServicePriceRQ#Party#Recipient#ORA_Recipient#

AirlineID

ORA (Offer Originating Airline) Recipient. Set the Airline

Iata Code of Offer Originating Airline . (Example: XQ)

ServicePriceRQ#Party#Recipient#ORA_Recipient#


ServicePriceRQ#Parameters

ServicePriceRQ#Parameters#CurrCodes#CurrCode

AirShoppingRS#Metadata#Other#OtherMetadata

#CurrencyMetadatas#CurrencyMetadata

@MetadataKeySet currency code in which search was done

ServicePriceRQ#Traveler

ServicePriceRQ#Travelers#Traveler#AnonymousTra

v eler

Unlike AirShoppingRS, here we need to create traveler

object for each pax in the booking flow. Eg : If there are

3 ADULT and 2 CHILD , and none of the pax have

passenger details, we need

ServicePriceRQ#Travelers#Traveler#RecognizedTrav

eler

Eg : If there are 3 ADULT and 2 CHILD , and only one

ADULT paxhave passenger details, we need to create 4

AnonymousTraveler, each with count 1 and 1

RecognizedTraveler object with that passenger details in ServicePriceRQ#Query#OriginDestination

@OriginDestinationKey

AirShoppingRS#DataLists#OriginDestinationList#

OriginDestination @OriginDestinationKey

ServicePriceRQ#Query#OriginDestination#FlightAirShoppingRS#DataLists#FlightSegmentList#Fligh

tSegment

ServicePriceRQ#Query#OriginDestination#Flight

@SegmentKey

AirShoppingRS#DataLists#FlightSegmentList#Fligh

tSegment

@SegmentKeyServicePriceRQ#Query#OriginDestination#Flight#Ma

rketingCarrier#AirlineID


tSegment#MarketingCarrier#AirlineID

ServicePriceRQ#Query#OriginDestination#Flight#Ma

rketingCarrier#FlightNumber


tSegment#MarketingCarrier#FlightNumber

ServicePriceRQ#Query#OriginDestination#Flight#Op

eratingCarrier#AirlineID


tSegment#OperatingCarrier#AirlineID

ServicePriceRQ#Query#OriginDestination#Flight#De

parture#Date


tSegment#Departure#Date


parture#Time


tSegment#Departure#Time


parture#AirportCode


tSegment#Departure#AirportCode

ServicePriceRQ#Query#OriginDestination#Flight#Arr

i

val#Date


tSegment#Arrival#Date


i


val#Time tSegment#Arrival#Time


i

val#AirportCode


tSegment#Arrival#AirportCode


t

ails#FlightDuration


tSegment#FlightDetail#FlightDuration


t

ails#Stops


tSegment#FlightDetail#Stops

ServicePriceRQ#Query#OriginDestination#Flight#Ca

b inType#Name

AirShoppingRS#OffersGroup#AirlineOffers#Airlin

eOffer#PricedOffer#Associations#ApplicableFligh

t#FlightSegmentReference#ClassOfService#Mark

etingName

ServicePriceRQ#Query#OriginDestination#Flight#Ca

b inType#Code



t#FlightSegmentReference#ClassOfService#Mark

etingName#CabinDesignator

ServicePriceRQ#Query#OriginDestination#Flight#Eq

u

ipment#AircraftCode


tSegment#Equipment#AircraftCode

ServicePriceRQ#Query#OriginDestination#Flight#Cla

ssOfService#Code



t#FlightSegmentReference#ClassOfService#ServicePriceRQ#Qualifiers#Qualifier

ServicePriceRQ#Qualifiers#Qualifier#ServiceQualifie

r

@ObjectKey

ServiceListRS#Services#Service#ServiceID


r

@refs

Set the object key of FlightAncillaryAugPoint , to map

the field

values of that Service QualifierServicePriceRQ#Qualifiers#Qualifier#ServiceQualifie

r

#Encoding#RFIC#Code

ServiceListRS#Services#Service#Encoding#RFIC#C

ode


r

#Encoding#Code

ServiceListRS#Services#Service#Encoding#Code


r

#Encoding#SubCode

ServiceListRS#Services#Service#Encoding#SubCo

de


r

#Associations#SegmentReferences

ServiceListRS#Services#Service#Associations#Flig

ht#SegmentReferences


r

#Associations#TravelerReferences

Set the passengers for whom the SSR is to be

associated. Eg

:XQ_PAX_1 XQ_PAX_2ServicePriceRQ#Qualifiers#Qualifier#SeatQualifier#

A ssignment

@ObjectKeyUnique ID is set

ServicePriceRQ#Qualifiers#Qualifier#SeatQualifier#

A

ssignment#Location#Column

SeatAvailabilityRS#DataLists#SeatList#Seats#Loca

tion#Column


A

ssignment#Location#Row#Number#

SeatAvailabilityRS#DataLists#SeatList#Seats#Loca

tion#Row#Number


A

ssignment#Location#Row#SeatData#Keywords#Key

Word

Set keywords such as WINDOW/AISLE


A

ssignment#SeatAssociation#SegmentReferences

Set the segments for which the seat is to be associated.

Eg

:XQ_SEG_1 XQ_SEG_2ServicePriceRQ#Qualifiers#Qualifier#SeatQualifier#

A

ssignment#SeatAssociation#TravelerReference

Set the passengers for whom the seat is to be

associated. Eg

:XQ_PAX_1 XQ_PAX_2ServicePriceRQ#DataLists

ServicePriceRQ#DataLists#FareList#FareGroup

@refs

Set passenger reference for each fare group. Fare group

will be different for each pax type. Eg: Consider there

are 3 ADULT PAX , and 2 CHILD PAX. Unique ID of Adult

traveler objects are XQ_PAX_1, XQ_PAX_2, XQ_PAX_3 ;

Child traveler objects are XQ_PAX_4, XQ_PAX_5. Then

there will be 2 fare groups corresponding to each pax

type. Fare Group refs corresponding to adult pax type

:FareGroup refs="XQ_PAX_1 XQ_PAX_2 XQ_PAX_3".

Fare group refs corresponding to childServicePriceRQ#DataLists#FareList#FareGroup#Fare

#FareDetail#FareComponent

@refs

AirShoppingRS#OffersGroup#OffersGroup#Airline

Offer#PricedOffer#OfferPrice#FareDetail#FareCo

mponent

@refsServicePriceRQ#DataLists#FareList#FareGroup#Fare

#FareDetail#FareComponent

@ObjectKey

AirShoppingRS#OffersGroup#OffersGroup#Airline

Offer#PricedOffer#OfferPrice#FareDetail#FareCo

mponent

@ObjectKeyServicePriceRQ#DataLists#FareList#FareGroup#Fare

#FareDetail#FareComponent#PriceBreakdown#Pric

e

booklet ibs vanillaair iflyres -...

Documents