p a g e | 0 sunexpress ibs ndc platform developer s...

P a g e | 0

SunExpress – IBS NDC Platform DEVELOPER’S GUIDE

© IBS Software Services 2017 | Page No. 1

SunExpress – IBS NDC Platform P a g e | 1


WELCOME TO SUNEXPRESS [XQ]

An airline flying in Europe and offering seats and services.




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. SunExpress was founded in October 1989 as a subsidiary of the two industry leading airlines Turkish Airlines and Lufthansa. Today, SunExpress carries around seven million passengers per year. With its 25 years of experience and thus the long-term commitment in the traffic between the home markets of Turkey and Germany, the airline has acquired the reputation of the holiday specialist even beyond Turkey. iFly Res, the state-of-the-art software from IBS, enables a strongly enhanced general communication between SunExpress and its important distribution network, the European travel agencies. 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 SunExpress partners within the travel industry and the demand of consumers using the newly redesigned website sunexpress.com. The SunExpress website is now being used more and more intensively for travellers’ direct bookings, for immediate travel modifications, also in responsive design via their mobile devices. iFly Res also enables the integration of 116 online travel agencies, among that important European metasearch engines, as well as over 70 technical providers and organizations, some of whom using the NDC standards. Included are also 9 Departure Control Systems used at all international stations and 9 systems for ticket payments, combined and integrated in the 5 most important GDS systems. The implementation, spread over a year, involved building a first class internet booking engine, B2B and B2C websites as well as training of over 1000 staff and agents. 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. 23 new messages were certified in March 2017, extending to a total of 28 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




SunExpress serves 70+ destinations

In Europe and Middle Ea

P a g e | 0


Sample routes for Hackathon Domestic Flights (Direct)

AYT - ADA

SAW - ADB VAN - AYT

International Flights (Direct)

AYT - FRA ADB - MUC AYT - ZRH

Connection Flights ADA – ADB – ZRH SAW – AYT – FRA ADA – ADB – MUC

Note:- The iFly Res NDC connection Flights are built by combining an Add-on Fare + Route Fare. The Add-on Fare is a two letter Fare Class.

18-May-17


SunExpress – IBS NDC Platform

P a g e | 1


SunExpress Ancillary Services

Service Name

Service Short Description

Long Description Code Sub Code

Seat Extra Leg-room The selected seat will have Extra Leg Room XLEG

Bundle SunClassic Bundle Bundle Includes +5kg Baggage Standard Seat Selection Sandwich Box and 2 Non-alcoholic Beverage

SUNC

Bundle SunPremium Bundle

Bundle Includes +10kg Baggage XLEG Seat Special Meal (SPML)

SUNP SPML selection

Domestic Route SPDA SPDB SPDC SPDD SPDE SPDF

International Route SPIA SPIB SPIC SPID SPIE

18-May-17



P a g e | 2


Note: Here the third letter ‘D’ or ‘I’ in the Code or Sub Code denotes Domestic or International. For example, SPDA is the SPML subcode available in the Domestic routes. Or PMIA is the Meal available in the International route.

Bag Extra Bag Extra Bag +5kg +10kg +15kg +20kg +25kg

XBAG 20KG 25KG 30KG 35KG 40KG

Meal Breakfast Hot Breakfast with Turkish Pastry and 2 Beverages PMDA PMIA

Meal Breakfast Hot Breakfast with Omelette and 2 Beverages PMDB PMIB

Meal Non-Veg Grilled Meat Balls and 2 beverages. PMDC PMIC

Meal Veg Meal Stuffed Aubergine and 2 beverages PMDD PMID

Meal Non-Veg Chicken Shish and 2 beverages. PMDE PMIE

Meal Cheese Snack Cheese Ravioli and 2 beverages. PMDF PMIF

Meal Diabetic Meal Low sugar meal for diabetic passengers DBML

Meal Vegan Snack Vegetarian snack for vegan passengers VGML

Meal Gluten-free Snack Gluten free Snack GFML

Meal Veg Snack Ovo-Lacto-Vegetarian Snack VLML

18-May-17



P a g e | 3


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

SAW ADB

Domestic Economy 17.00 TRY XLEG

ADB SAW

AYT ADA

ADA AYT

VAN AYT

AYT VAN

Seat Extra Leg-room

AYT FRA

International Economy 20.00 EUR XLEG

FRA AYT

ADB MUC

MUC ADB

AYT ZRH

ZRH AYT

Bag Extra Bag

SAW ADB

Domestic Economy

10.00 EUR (+5kg)

20.00 EUR (+10kg)

30.00 EUR (+15kg) 40.00 EUR (+20kg)

50.00 EUR (+25kg)

XBAG

ADB SAW

AYT ADA

ADA AYT

VAN AYT

AYT VAN

Bag Extra Bag

AYT FRA

International Economy

18.00 EUR (+5kg) 35.00 EUR (+10kg)

48.00 EUR (+15kg) 55.00 EUR (+20kg)

65.00 EUR (+25kg)

XBAG

FRA AYT

ADB MUC

MUC ADB

AYT ZRH

ZRH AYT

18-May-17



P a g e | 4


Meal Breakfast

SAW ADB

Domestic Economy 6.00 EUR PMDA

ADB SAW

AYT ADA

ADA AYT

VAN AYT

AYT VAN

Meal Breakfast

AYT FRA

International Economy 15.00 EUR PMIA

FRA AYT

ADB MUC

MUC ADB

AYT ZRH

ZRH AYT

Meal Breakfast

SAW ADB

Domestic Economy 6.16 EUR PMDB

ADB SAW

AYT ADA

ADA AYT

VAN AYT

AYT VAN

Meal Breakfast

AYT FRA

International Economy 14.99 EUR PMIB

FRA AYT

ADB MUC

MUC ADB

AYT ZRH

ZRH AYT

Meal Non-Veg

SAW ADB

Domestic Economy 6.16 EUR PMDC

ADB SAW

AYT ADA

ADA AYT

VAN AYT

AYT VAN

18-May-17



P a g e | 5


Meal Non-Veg

AYT FRA

International Economy 14.99 EUR PMIC

FRA AYT

ADB MUC

MUC ADB

AYT ZRH

ZRH AYT

Meal Veg Meal

SAW ADB

Domestic Economy 6.16 EUR PMDD

ADB SAW

AYT ADA

ADA AYT

VAN AYT

AYT VAN

Meal Veg Meal

AYT FRA

International Economy 14.99 EUR PMID

FRA AYT

ADB MUC

MUC ADB

AYT ZRH

ZRH AYT

Meal Non-Veg

SAW ADB

Domestic Economy 6.16 EUR PMDE

ADB SAW

AYT ADA

ADA AYT

VAN AYT

AYT VAN

Meal Non-Veg

AYT FRA

International Economy 14.99 EUR PMIE

FRA AYT

ADB MUC

MUC ADB

AYT ZRH

ZRH AYT

18-May-17



P a g e | 6


Meal Cheese Snack

SAW ADB

Domestic Economy 6.16 EUR PMDF

ADB SAW

AYT ADA

ADA AYT

VAN AYT

AYT VAN

Meal Cheese Snack

AYT FRA

International Economy 14.99 EUR PMIF

FRA AYT

ADB MUC

MUC ADB

AYT ZRH

ZRH AYT

Meal Diabetic Meal

SAW ADB

ALL Economy 5.4 EUR DBML

ADB SAW

AYT ADA

ADA AYT

VAN AYT

AYT VAN

AYT FRA

FRA AYT

ADB MUC

MUC ADB

AYT ZRH

ZRH AYT

18-May-17



P a g e | 7


Meal Vegan Snack

SAW ADB

ALL Economy 5.4 EUR VGML

ADB SAW

AYT ADA

ADA AYT

VAN AYT

AYT VAN

AYT FRA

FRA AYT

ADB MUC

MUC ADB

AYT ZRH

ZRH AYT

Meal Gluten-free Snack

SAW ADB

ALL Economy 5.4 EUR GFML

ADB SAW

AYT ADA

ADA AYT

VAN AYT

AYT VAN

AYT FRA

FRA AYT

ADB MUC

MUC ADB

AYT ZRH

ZRH AYT

18-May-17



P a g e | 8


Meal Veg Snack

SAW ADB

ALL Economy 5.4 EUR VLML

ADB SAW

AYT ADA

ADA AYT

VAN AYT

AYT VAN

AYT FRA

FRA AYT

ADB MUC

MUC ADB

AYT ZRH

ZRH AYT

Supported Airplane Types &

Seat Maps

18-May-17


P a g e |

10


Boeing B737-800 Seat Map Key

18-May-17


P a g e |

11


Supported NDC APIs (V 15.2)

18-May-17


P a g e |

12


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

18-May-17


P a g e |

13


NDC PROCESS FLOW

18-May-17


P a g e |

14


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

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:edis="http://www.iata.org/IATA/EDIST">

<soapenv:Header/>

<soapenv:Body> <edis:AirDocDisplayRQ>

<edis:Document> <edis:Name>NDC</edis:Name>

<edis:ReferenceVersion>15.2</edis:ReferenceVersion>

</edis:Document> <edis:Party>

<edis:Sender> <edis:AgentUserSender>

<edis:AgentUserID>*******</edis:AgentUserID>

</edis:AgentUserSender> </edis:Sender>

<edis:Recipient> <edis:ORA_Recipient>

<edis:AirlineID>XQ</edis:AirlineID> </edis:ORA_Recipient>

</edis:Recipient>

</edis:Party> <edis:Query>

<edis:TicketDocument> <edis:TicketDocNbr>5648440344021</edis:TicketDocNbr>

</edis:TicketDocument>

</edis:Query> </edis:AirDocDisplayRQ>

</soapenv:Body> </soapenv:Envelope>

18-May-17


P a g e |

15


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

18-May-17


P a g e |

16


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.

18-May-17


P a g e |

17


Sample Request [1 Adult, One-way search] <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:edis="http://www.iata.org/IATA/EDIST">

<soapenv:Header/> <soapenv:Body>

<AirShoppingRQ

xsi:schemaLocation="https://iflyrestest.ibsgen.com:6012/iRes_NdcRes_WS/services/NdcResServiceSOAPPort?xsd=../../xsd/ndcres/AirShoppingRQ.xsd" Version=""

xmlns="http://www.iata.org/IATA/EDIST" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<PointOfSale>

<Location> <CountryCode>DE</CountryCode>

</Location> </PointOfSale>

<Document> <Name>NDC</Name>

<ReferenceVersion>15.1.2</ReferenceVersion>

</Document> <Party>

<Sender> <AgentUserSender>

<AgentUserID>*******</AgentUserID>

</AgentUserSender> </Sender>

<Recipient> <ORA_Recipient>

<AirlineID>XQ</AirlineID>

</ORA_Recipient> </Recipient>

</Party> <Travelers>

<Traveler> <AnonymousTraveler>

<PTC Quantity="1">ADT</PTC>

</AnonymousTraveler> </Traveler>

</Travelers> <CoreQuery>

<OriginDestinations>

<OriginDestination> <Departure>

<AirportCode>ADA</AirportCode> <Date>2017-05-22</Date>

</Departure> <Arrival>

<AirportCode>AYT</AirportCode>

</Arrival> <CalendarDates DaysAfter="0" DaysBefore="0"/>

</OriginDestination> </OriginDestinations>

</CoreQuery>

<Preferences>

18-May-17


P a g e |

18


<Preference>

<FarePreferences> <Types>

<Type> <Code>SunEco</Code>

</Type>

</Types> </FarePreferences>

</Preference> <Preference>

<TransferPreferences> <Connection>

<MaxNumber>2</MaxNumber>

</Connection> </TransferPreferences>

</Preference> </Preferences>

</AirShoppingRQ>


18-May-17


P a g e |

19


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



<AirShoppingRQ



<PointOfSale>





</Document> <Party>












<PTC Quantity="1">CHD</PTC>



<PTC Quantity="1">INF</PTC> </AnonymousTraveler>

</Traveler>


<OriginDestinations> <OriginDestination>

<Departure>

18-May-17


P a g e |

20


<AirportCode>ADA</AirportCode>

<Date>2017-05-22</Date> </Departure>

<Arrival> <AirportCode>AYT</AirportCode>

</Arrival>

<CalendarDates DaysAfter="0" DaysBefore="0"/> </OriginDestination>

</OriginDestinations> </CoreQuery>

<Preferences> <Preference>

<FarePreferences>

<Types> <Type>

<Code>SunEco</Code> </Type>

</Types>

</FarePreferences> </Preference>

<Preference> <TransferPreferences>

<Connection>

<MaxNumber>2</MaxNumber> </Connection>

</TransferPreferences> </Preference>

</Preferences> </AirShoppingRQ>

</soapenv:Body>

</soapenv:Envelope>

18-May-17


P a g e |

21


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



<AirShoppingRQ



<PointOfSale>





</Document> <Party>












<PTC Quantity="1">CHD</PTC>



<PTC Quantity="1">INF</PTC> </AnonymousTraveler>

</Traveler>


<OriginDestinations> <OriginDestination>

<Departure>

18-May-17


P a g e |

22


<AirportCode>ADA</AirportCode>

<Date>2017-05-22</Date> </Departure>

<Arrival> <AirportCode>AYT</AirportCode>

</Arrival>

<CalendarDates DaysAfter="0" DaysBefore="0"/> </OriginDestination>

<OriginDestination> <Departure>

<AirportCode>AYT</AirportCode> <Date>2017-05-24</Date>

</Departure>

<Arrival> <AirportCode>ADA</AirportCode>

</Arrival> <CalendarDates DaysAfter="0" DaysBefore="0"/>

</OriginDestination>

</OriginDestinations> </CoreQuery>

<Preferences> <Preference>

<FarePreferences>

<Types> <Type>

<Code>SunEco</Code> </Type>

</Types> </FarePreferences>

</Preference>

<Preference> <TransferPreferences>

<Connection> <MaxNumber>2</MaxNumber>

</Connection>

</TransferPreferences> </Preference>

</Preferences> </AirShoppingRQ>


18-May-17


P a g e |

23


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

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"

xmlns:edis="http://www.iata.org/IATA/EDIST" xmlns:ibs="http://www.ibsplc.com/iFlyRes/simpleTypes">>


<edis:BaggageAllowanceRQ EchoToken="23452" TimeStamp="2016-11-21T23:38:00"

Target="Production" Version="15.1" TransactionIdentifier="23" SequenceNmbr="4563453" TransactionStatusCode="Continuation" RetransmissionIndicator="true" CorrelationID="23423"

AsynchronousAllowedInd="true"> <edis:PointOfSale>

<edis:Location> <edis:CountryCode>DE</edis:CountryCode>

<edis:CityCode>FRA</edis:CityCode>

</edis:Location> </edis:PointOfSale>

<edis:Document> <edis:Metadata/>

<edis:Name>NDC</edis:Name>

<edis:ReferenceVersion>15.2</edis:ReferenceVersion> </edis:Document>

<edis:Party> <edis:Sender>

<edis:AgentUserSender> <edis:AgentUserID>*******</edis:AgentUserID>

</edis:AgentUserSender>

</edis:Sender> <edis:Recipient>

<edis:ORA_Recipient> <edis:AirlineID>XQ</edis:AirlineID>

</edis:ORA_Recipient>

</edis:Recipient> </edis:Party>

<edis:Travelers> <edis:Traveler>

<edis:AnonymousTraveler>

<edis:PTC Quantity="1">ADT</edis:PTC> </edis:AnonymousTraveler>

18-May-17


P a g e |

24


</edis:Traveler>

</edis:Travelers> <edis:Query>

<edis:OriginDestination> <edis:OriginDestinationKey>XQ_OD_1492924013610</edis:OriginDestinationKey>

<edis:Flight refs="XQ_FMD_1492924013601">

<edis:SegmentKey>XQ_SEG_1492924013615</edis:SegmentKey> <edis:Departure>

<edis:AirportCode>ADA</edis:AirportCode> <edis:Date>2017-05-22Z</edis:Date>

<edis:Time>09:05</edis:Time> </edis:Departure>

<edis:Arrival>

<edis:AirportCode>AYT</edis:AirportCode> <edis:Date>2017-05-22Z</edis:Date>

<edis:Time>10:15</edis:Time> <edis:ChangeOfDay>0</edis:ChangeOfDay>

</edis:Arrival>

<edis:MarketingCarrier> <edis:AirlineID>XQ</edis:AirlineID>

<edis:FlightNumber>7631</edis:FlightNumber> </edis:MarketingCarrier>

<edis:Equipment>

<edis:AircraftCode>738</edis:AircraftCode> <edis:AirlineEquipCode>800</edis:AirlineEquipCode>

</edis:Equipment> <edis:CabinType>

<edis:Code>Y</edis:Code> <edis:Name>ECONOMY</edis:Name>

</edis:CabinType>

<edis:Details> <edis:FlightDuration>

<edis:Value>PT1H10M0.000S</edis:Value> </edis:FlightDuration>

<edis:Stops>

<edis:StopQuantity>0</edis:StopQuantity> </edis:Stops>

</edis:Details> </edis:Flight>

</edis:OriginDestination> </edis:Query>

<edis:Metadata>

<edis:Shopping> <edis:ShopMetadataGroup>

<edis:Offer> <edis:OfferMetadatas>

<edis:OfferMetadata>

<edis:AugmentationPoint> <edis:AugPoint Key="XQ_FMD_1492924013601">

<ibs:FareDetailAugPoint> <FareLevel>SUNECO</FareLevel>

<FareBasis>ST</FareBasis>

</ibs:FareDetailAugPoint> </edis:AugPoint>

</edis:AugmentationPoint>

18-May-17


P a g e |

25


</edis:OfferMetadata>

</edis:OfferMetadatas> </edis:Offer>

</edis:ShopMetadataGroup> </edis:Shopping>

</edis:Metadata>

</edis:BaggageAllowanceRQ> </soapenv:Body>

</soapenv:Envelope>

18-May-17


P a g e |

26


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


xmlns:edis="http://www.iata.org/IATA/EDIST"

xmlns:ibs="http://www.ibsplc.com/iFlyRes/simpleTypes"> <soapenv:Header/>

<soapenv:Body> <edis:BaggageChargesRQ EchoToken="23452" TimeStamp="2016-11-21T23:38:00"

Target="Production" Version="15.1" TransactionIdentifier="23" SequenceNmbr="4563453" TransactionStatusCode="Continuation" RetransmissionIndicator="true" CorrelationID="23423"

AsynchronousAllowedInd="true">

<edis:PointOfSale> <edis:Location>

<edis:CountryCode>DE</edis:CountryCode> <edis:CityCode>FRA</edis:CityCode>

</edis:Location>

</edis:PointOfSale> <edis:Document>

<edis:Metadata/> <edis:Name>NDC</edis:Name>


<edis:Party>


<edis:AgentUserID>*******</edis:AgentUserID> </edis:AgentUserSender>

</edis:Sender>



</edis:Recipient>

</edis:Party>

18-May-17


P a g e |

27


<edis:Travelers>

<edis:Traveler> <edis:AnonymousTraveler>


</edis:Traveler>

</edis:Travelers> <edis:Query>


<edis:Flight refs="XQ_FMD_1492924013601"> <edis:SegmentKey>XQ_SEG_1492924013615</edis:SegmentKey>

<edis:Departure>



<edis:Arrival>



</edis:Arrival>



<edis:Equipment> <edis:AircraftCode>738</edis:AircraftCode>

<edis:AirlineEquipCode>800</edis:AirlineEquipCode>



</edis:CabinType>



<edis:Stops> <edis:StopQuantity>0</edis:StopQuantity>

</edis:Stops>

</edis:Details> </edis:Flight>


<edis:Metadata>



<edis:OfferMetadata>

<edis:AugmentationPoint> <edis:AugPoint Key="XQ_FMD_1492924013601">

<ibs:FareDetailAugPoint>

18-May-17


P a g e |

28


<FareLevel>SUNECO</FareLevel>

<FareBasis>ST</FareBasis> </ibs:FareDetailAugPoint>

</edis:AugPoint> </edis:AugmentationPoint>

</edis:OfferMetadata>


</edis:ShopMetadataGroup> </edis:Shopping>

</edis:Metadata> </edis:BaggageChargesRQ>

</soapenv:Body>

</soapenv:Envelope>

18-May-17


P a g e |

29


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


xmlns:edis="http://www.iata.org/IATA/EDIST"


<soapenv:Body> <edis:FlightPriceRQ Version="15.2">

<edis:PointOfSale>



<edis:Document>

<edis:Name>NDC</edis:Name> <edis:ReferenceVersion>15.1.2</edis:ReferenceVersion>



<edis:AgentUserID>*******</edis:AgentUserID>



<edis:AirlineID>XQ</edis:AirlineID>

</edis:ORA_Recipient> </edis:Recipient>

</edis:Party>

18-May-17


P a g e |

30


<edis:Parameters>

<edis:CurrCodes> <edis:CurrCode>EUR</edis:CurrCode>

</edis:CurrCodes> </edis:Parameters>

<edis:Travelers>

<edis:Traveler> <edis:AnonymousTraveler ObjectKey="XQ_PAX_1">


</edis:Traveler> </edis:Travelers>

<edis:Query>


<edis:Flight> <edis:SegmentKey>XQ_SEG_1494289508280</edis:SegmentKey>

<edis:Departure>



<edis:Arrival>



</edis:Arrival> <edis:MarketingCarrier>







</edis:CabinType> <edis:ClassOfService>

<edis:Code>D</edis:Code>

</edis:ClassOfService> <edis:Details>

<edis:FlightDuration> <edis:Value>PT1H10M0.000S</edis:Value>

</edis:FlightDuration>


</edis:Stops> </edis:Details>

</edis:Flight>


<edis:DataLists>

18-May-17


P a g e |

31


<edis:FareList>

<edis:FareGroup refs="XQ_PAX_1" ListKey="XQ_FG_ADT"> <edis:Fare>

<edis:FareCode> <edis:Code>SUNECO</edis:Code>

</edis:FareCode>

<edis:FareDetail> <edis:FareComponent refs="XQ_SEGREFS_1494289508284

XQ_FMD_1494289508282 XQ_FARECOMPREFS_1494289508286" ObjectKey="XQ_FC_1494289508287-1247">

<edis:SegmentReference>XQ_SEG_1494289508280</edis:SegmentReference>

<edis:PriceBreakdown>

<edis:Price> <edis:BaseAmount Code="TRY">15.75</edis:BaseAmount>

</edis:Price> </edis:PriceBreakdown>

<edis:FareBasis>

<edis:FareBasisCode> <edis:Code>DXDOM</edis:Code>

</edis:FareBasisCode> </edis:FareBasis>

</edis:FareComponent>

</edis:FareDetail> </edis:Fare>

</edis:FareGroup> </edis:FareList>

</edis:DataLists> <edis:Metadata>

<edis:Shopping>

<edis:ShopMetadataGroup> <edis:Flight>

<edis:FlightMetadatas> <edis:FlightMetadata>

<edis:AugmentationPoint>

<edis:AugPoint Key="XQ_SEGREFS_1494289508284">

<edis:SegmentReferences>XQ_SEG_1494289508280</edis:SegmentReferences> </edis:AugPoint>

</edis:AugmentationPoint> </edis:FlightMetadata>

</edis:FlightMetadatas>

</edis:Flight> <edis:Offer>

<edis:OfferMetadatas> <edis:OfferMetadata>


<AugPoint Key="XQ_FMD_1494289508282"> <ibs:FareDetailAugPoint>

<FareType>SUNECO</FareType> <FareLevel>ST</FareLevel>

</ibs:FareDetailAugPoint>

</AugPoint> <AugPoint Key="XQ_FARECOMPREFS_1494289508286">

<ibs:FareComponentAugPoint>

18-May-17


P a g e |

32


<BaseFare Code="TRY">35.584744</BaseFare>

<DisplayFare Code="EUR">6.27</DisplayFare> <Discount Code="EUR">7.64</Discount>

</ibs:FareComponentAugPoint> </AugPoint>

</edis:AugmentationPoint>

</edis:OfferMetadata> </edis:OfferMetadatas>

</edis:Offer> </edis:ShopMetadataGroup>

</edis:Shopping> <edis:Traveler>

<edis:TravelerMetadata MetadataKey="XQ_TM_1">

<edis:AugmentationPoint> <edis:AugPoint Key="XQ_TM1_TA_1">

<ibs:TravellerAugPoint> <PnrType>NORMAL</PnrType>

</ibs:TravellerAugPoint>


</edis:TravelerMetadata> </edis:Traveler>

</edis:Metadata>

</edis:FlightPriceRQ> </soapenv:Body>

</soapenv:Envelope>

18-May-17


P a g e |

33


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


<soapenv:Header/>

<soapenv:Body> <edis:FareRulesRQ Target="Production" Version="15.2">

<edis:PointOfSale> <edis:Location>

<edis:CountryCode>DE</edis:CountryCode> <edis:CityCode>FRA</edis:CityCode>

</edis:Location>


<edis:Name>NDC</edis:Name> <edis:ReferenceVersion>15.2</edis:ReferenceVersion>

</edis:Document>




<edis:Recipient>


<edis:Name>SunExpress</edis:Name> </edis:ORA_Recipient>

</edis:Recipient>

</edis:Party> <edis:Parameters>

<edis:Languages> <edis:LanguageCode>en</edis:LanguageCode>

</edis:Languages>

</edis:Parameters> <edis:Query>

<edis:Departure> <edis:AirportCode>ADA</edis:AirportCode>

<edis:Date>2017-05-22</edis:Date>

18-May-17


P a g e |

34


<edis:Time>09:05</edis:Time>

</edis:Departure> <edis:Arrival>

<edis:AirportCode>AYT</edis:AirportCode> <edis:Date>2017-05-22</edis:Date>


<edis:ChangeOfDay>0</edis:ChangeOfDay> </edis:Arrival>

<edis:FareBasisCode> <edis:Code>LXDOM</edis:Code>

</edis:FareBasisCode> <edis:AirlineID>XQ</edis:AirlineID>

</edis:Query>

</edis:FareRulesRQ> </soapenv:Body>

</soapenv:Envelope>

18-May-17


P a g e |

35


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



<edis:InvGuaranteeRQ>

<edis:Document> <edis:ReferenceVersion>15.2</edis:ReferenceVersion>

<edis:Name>NDC</edis:Name> </edis:Document>


<edis:AgentUserSender>



<edis:ORA_Recipient>

<edis:AirlineID>XQ</edis:AirlineID> <edis:Name>Sun Express Airlines</edis:Name>


</edis:Party>

18-May-17


P a g e |

36


<edis:Query>

<edis:OfferItemID Owner="XQ" ObjectKey="XQ_OFFERITEM_1492924013600">XQ_OFFERITEM_1492924013600</edis:OfferIte

mID> <edis:OfferItemID Owner="XQ"

ObjectKey="XQ_OFFERITEM_1492924013656">XQ_OFFERITEM_1492924013656</edis:OfferIte

mID> </edis:Query>

<edis:DataLists> <edis:AnonymousTravelerList>

<edis:AnonymousTraveler ObjectKey="XQ_PAX_1478857845750"> <edis:PTC Quantity="1">ADT</edis:PTC>

</edis:AnonymousTraveler>

</edis:AnonymousTravelerList> <edis:FlightSegmentList>

<edis:FlightSegment SegmentKey="XQ_SEG_1492924013615" ElectronicTicketInd="true" refs="XQ_OFFERITEM_1492924013600">

<edis:Departure>



<edis:Arrival>



</edis:Arrival> <edis:MarketingCarrier>





</edis:Equipment> <edis:FlightDetail>


</edis:FlightDuration> <edis:Stops>

<edis:StopQuantity>0</edis:StopQuantity>

<edis:StopLocations/> </edis:Stops>

</edis:FlightDetail> <edis:ClassOfService>

<edis:Code>A</edis:Code>

<edis:MarketingName CabinDesignator="Y">ECONOMY</edis:MarketingName> </edis:ClassOfService>

</edis:FlightSegment> <edis:FlightSegment SegmentKey="XQ_SEG_1492924013606"

ElectronicTicketInd="true" refs="XQ_OFFERITEM_1492924013656">


<edis:Date>2017-05-22Z</edis:Date>

18-May-17


P a g e |

37









<edis:Equipment>


</edis:Equipment> <edis:FlightDetail>

<edis:FlightDuration>



<edis:StopLocations/>

</edis:Stops> </edis:FlightDetail>

<edis:ClassOfService> <edis:Code>E</edis:Code>

<edis:MarketingName CabinDesignator="I">ECONOMY</edis:MarketingName> </edis:ClassOfService>

</edis:FlightSegment>

</edis:FlightSegmentList> <edis:FlightList>

<edis:Flight FlightKey="XQ_FL_1492924013612"> <edis:Journey>

<edis:Time>P0Y0M0DT1H10M0.000S</edis:Time>

</edis:Journey> <edis:SegmentReferences>XQ_SEG_1492924013615</edis:SegmentReferences>

</edis:Flight> <edis:Flight FlightKey="XQ_FL_1492924013607">

<edis:Journey> <edis:Time>P0Y0M0DT1H10M0.000S</edis:Time>

</edis:Journey>

<edis:SegmentReferences>XQ_SEG_1492924013606</edis:SegmentReferences> </edis:Flight>

</edis:FlightList> <edis:ServiceList/>

</edis:DataLists>

</edis:InvGuaranteeRQ> </soapenv:Body>

</soapenv:Envelope>

18-May-17


P a g e |

38


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


<soapenv:Header/>

<soapenv:Body> <edis:InvReleaseNotif Version="15.2">



<edis:Party>



</edis:Sender>


<edis:AirlineID>XQ</edis:AirlineID> <edis:Name>SunExpress</edis:Name>


</edis:Party>

<edis:Query> <edis:Guarantee>

<edis:InvGuaranteeID>22</edis:InvGuaranteeID> </edis:Guarantee>

</edis:Query>

</edis:InvReleaseNotif> </soapenv:Body>

</soapenv:Envelope>

18-May-17


P a g e |

39


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

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:edis="http://www.iata.org/IATA/EDIST"


<soapenv:Body>

<edis:OrderCreateRQ> <edis:PointOfSale>



<edis:Document>



<edis:Sender>



<edis:Recipient>

18-May-17


P a g e |

40





<edis:Query>

<edis:Passengers> <edis:Passenger ObjectKey="XQ_PAX_1">

<edis:PTC Quantity="1">ADT</edis:PTC> <edis:Age>

<edis:BirthDate>1972-02-01</edis:BirthDate> </edis:Age>

<edis:Name>

<edis:Title>MR</edis:Title> <edis:Surname>Adams</edis:Surname>

<edis:Given>Anton</edis:Given> <edis:Middle/>

</edis:Name>

<edis:Contacts> <edis:Contact Type="HOME">

<edis:AddressContact> <edis:Street>Nieuwe Plaatsen 201a</edis:Street>

<edis:CityName>NACHGERAAD</edis:CityName>

<edis:PostalCode>7501KO</edis:PostalCode> <edis:CountryCode>MO</edis:CountryCode>

</edis:AddressContact> <edis:EmailContact>

<edis:Application>Personal</edis:Application> <edis:Address>[email protected]</edis:Address>

</edis:EmailContact>

<edis:PhoneContact> <edis:Application>HOME</edis:Application>

<edis:Number>313712387</edis:Number> </edis:PhoneContact>

</edis:Contact>

</edis:Contacts> <edis:AdditionalRoles PrimaryContactInd="true"/>

<edis:Gender>Male</edis:Gender> </edis:Passenger>

</edis:Passengers> <edis:OrderItems>

<edis:OfferItem refs="XQ_PAX_1">

<edis:OfferItemType> <edis:DetailedFlightItem ConnectionInd="false">


</edis:Price>

<edis:OriginDestination> <edis:Flight>


<edis:AirportCode>ADA</edis:AirportCode>

<edis:Date>2017-05-22Z</edis:Date> <edis:Time>09:05</edis:Time>

</edis:Departure>

18-May-17


P a g e |

41


<edis:Arrival>



</edis:Arrival>







</edis:CabinType>

<edis:ClassOfService> <edis:Code>D</edis:Code>

</edis:ClassOfService> <edis:Details>

<edis:FlightDuration>



</edis:Stops> </edis:Details>

</edis:Flight>

</edis:OriginDestination> <edis:FareDetail>

<edis:FareComponent refs="XQ_SEGREFS_1494289508284 XQ_FMD_1494289508282" ObjectKey="XQ_FC_1492924013602-646">

<edis:FareBasis>

<edis:FareBasisCode> <edis:Code>DXDOM</edis:Code>

</edis:FareBasisCode> </edis:FareBasis>

</edis:FareComponent> </edis:FareDetail>

</edis:DetailedFlightItem>

</edis:OfferItemType> </edis:OfferItem>

</edis:OrderItems> <edis:Payments>

<edis:Payment>

<edis:Method> <edis:PaymentCard>

<edis:CardCode><<Card Type Code Here>></edis:CardCode> <edis:CardNumber><<PCI Compliant Encryption>> </edis:CardNumber>

<edis:SeriesCode><<CVV Code here>> </edis:SeriesCode>

<edis:CardHolderName><<Card Holder Name here>></edis:CardHolderName>

<edis:CardHolderBillingAddress>

18-May-17


P a g e |

42


<edis:Street>ST PT ROAD</edis:Street>

<edis:Street>VIA DELLE ARTI</edis:Street> <edis:CityName>ROM</edis:CityName>

<edis:PostalCode>23535</edis:PostalCode> <edis:County>ITALY</edis:County>

</edis:CardHolderBillingAddress>

<edis:Amount Code="EUR">6.27</edis:Amount> <edis:EffectiveExpireDate>

<edis:Expiration><<Card Expiry Date>></edis:Expiration> </edis:EffectiveExpireDate>

</edis:PaymentCard> </edis:Method>

<edis:Amount Code="EUR">6.27</edis:Amount>

</edis:Payment> </edis:Payments>

<edis:Metadata> <edis:Other>

<edis:OtherMetadata>

<edis:CurrencyMetadatas> <edis:CurrencyMetadata MetadataKey="EUR">

<edis:Decimals>2</edis:Decimals> </edis:CurrencyMetadata>

</edis:CurrencyMetadatas>

<edis:PriceMetadatas> <edis:PriceMetadata>

<edis:AugmentationPoint> <AugPoint Key="XQ_FMD_1494289508282">

<ibs:FareDetailAugPoint> <FareType>SUNECO</FareType>

<FareLevel>ST</FareLevel>

</ibs:FareDetailAugPoint> </AugPoint>

</edis:AugmentationPoint> </edis:PriceMetadata>

</edis:PriceMetadatas>

</edis:OtherMetadata> </edis:Other>

<edis:PassengerMetadata refs="?" MetadataKey="?"> <edis:AugmentationPoint>

<edis:AugPoint Key="XQ_SEGREFS_1494289508284">

<edis:SegmentReferences>XQ_SEG_1494289508280</edis:SegmentReferences>


</edis:PassengerMetadata> </edis:Metadata>

</edis:Query>

</edis:OrderCreateRQ> </soapenv:Body>

</soapenv:Envelope>

18-May-17


P a g e |

43


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



<edis:OrderRetrieveRQ>



<edis:Party>







</edis:Party>

<edis:Query> <edis:Filters>

<edis:OrderID Owner="XQ">B28L24</edis:OrderID> </edis:Filters>

</edis:Query>

</edis:OrderRetrieveRQ> </soapenv:Body>

</soapenv:Envelope>

18-May-17


P a g e |

44


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


xmlns:edis="http://www.iata.org/IATA/EDIST"> <soapenv:Header/>

<soapenv:Body>

<edis:OrderListRQ> <edis:Document>


</edis:Document>



</edis:AgentUserSender>




</edis:Party>

<edis:Query> <edis:Filters>

18-May-17


P a g e |

45


<edis:CreateDateRange>

<edis:Effective>2017-05-01Z</edis:Effective> <edis:Expiration>2017-05-10Z</edis:Expiration>

</edis:CreateDateRange> </edis:Filters>

</edis:Query>

</edis:OrderListRQ> </soapenv:Body>

</soapenv:Envelope>

18-May-17


P a g e |

46


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



<soapenv:Body>

<edis:ServiceListRQ EchoToken="6546" TimeStamp="2017-05-09T23:38:00" Target="Production" Version="33" TransactionIdentifier="3" SequenceNmbr="33"

TransactionStatusCode="Start" RetransmissionIndicator="true" CorrelationID="3" AsynchronousAllowedInd="true">

<edis:PointOfSale>


<edis:CityCode>FRA</edis:CityCode> </edis:Location>


<edis:Metadata/>



<edis:Sender>



<edis:Recipient>



</edis:Party> <edis:Travelers>

18-May-17


P a g e |

47


<edis:Traveler>

<edis:AnonymousTraveler ObjectKey="XQ_PAX_1"> <edis:PTC Quantity="1">ADT</edis:PTC>

</edis:AnonymousTraveler> </edis:Traveler>

</edis:Travelers>

<edis:Query> <edis:OriginDestination>

<edis:OriginDestinationKey>XQ_OD_1492924013610</edis:OriginDestinationKey> <edis:Flight refs="XQ_FMD_1492924013601">


<edis:AirportCode>ADA</edis:AirportCode>



<edis:AirportCode>AYT</edis:AirportCode>



<edis:MarketingCarrier>

<edis:AirlineID>XQ</edis:AirlineID> <edis:FlightNumber>7631</edis:FlightNumber>

</edis:MarketingCarrier> <edis:Equipment>


</edis:Equipment>

<edis:CabinType> <edis:Code>Y</edis:Code>

<edis:Name>ECONOMY</edis:Name> </edis:CabinType>

<edis:Details>


</edis:FlightDuration> <edis:Stops>

<edis:StopQuantity>0</edis:StopQuantity> </edis:Stops>

</edis:Details>

</edis:Flight> </edis:OriginDestination>

</edis:Query> <edis:Metadata>

<edis:Shopping>

<edis:ShopMetadataGroup> <edis:Offer>

<edis:OfferMetadatas> <edis:OfferMetadata>


<edis:AugPoint Key="XQ_FMD_1492924013601"> <ibs:FareDetailAugPoint>

<FareLevel>SUNECO</FareLevel>

18-May-17


P a g e |

48


<FareBasis>ST</FareBasis>

</ibs:FareDetailAugPoint> </edis:AugPoint>

</edis:AugmentationPoint> </edis:OfferMetadata>

</edis:OfferMetadatas>

</edis:Offer> </edis:ShopMetadataGroup>

</edis:Shopping> </edis:Metadata>

</edis:ServiceListRQ> </soapenv:Body>

</soapenv:Envelope>

18-May-17


P a g e |

49


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



<soapenv:Body>

<edis:ServicePriceRQ Version="15.2"> <edis:PointOfSale>


<edis:CityCode>FRA</edis:CityCode>



<edis:ReferenceVersion>15.2</edis:ReferenceVersion>




</edis:Sender>



</edis:ORA_Recipient>


<edis:Parameters> <edis:CurrCodes>

<edis:CurrCode>EUR</edis:CurrCode> </edis:CurrCodes>

</edis:Parameters>

<edis:Travelers> <edis:Traveler>

<edis:RecognizedTraveler ObjectKey="XQ_PAX_1"> <edis:PTC Quantity="1">ADT</edis:PTC>

<edis:ResidenceCode>IT</edis:ResidenceCode>

<edis:CitizenshipCountryCode>IT</edis:CitizenshipCountryCode>

18-May-17


P a g e |

50


<edis:Name>

<edis:Surname>P</edis:Surname> <edis:Given>RAHUL</edis:Given>

</edis:Name> </edis:RecognizedTraveler>

</edis:Traveler>

</edis:Travelers> <edis:Qualifiers>

<edis:Qualifier> <edis:ServiceQualifier ObjectKey="XQ_SSR_1494289512731">

<edis:Encoding> <edis:RFIC>

<edis:Code>XLEG</edis:Code>

</edis:RFIC> <edis:Code>XLEG</edis:Code>

</edis:Encoding> <edis:Associations>

<edis:SegmentReferences>XQ_SEGREFS_1492924013603</edis:SegmentReferences> <edis:TravelerReferences>XQ_PAX_1</edis:TravelerReferences>

</edis:Associations> <edis:Include>true</edis:Include>

</edis:ServiceQualifier>

</edis:Qualifier> </edis:Qualifiers>


<edis:OriginDestinationKey>XQ_OD_1492924013610</edis:OriginDestinationKey> <edis:Flight>

<edis:SegmentKey>XQ_SEG_1492924013615</edis:SegmentKey>



</edis:Departure>

<edis:Arrival> <edis:AirportCode>AYT</edis:AirportCode>



<edis:MarketingCarrier>

<edis:AirlineID>XQ</edis:AirlineID> <edis:FlightNumber>7631</edis:FlightNumber>

</edis:MarketingCarrier> <edis:Equipment>

<edis:AircraftCode>738</edis:AircraftCode>

<edis:AirlineEquipCode>800</edis:AirlineEquipCode> </edis:Equipment>

<edis:CabinType> <edis:Code>I</edis:Code>

<edis:Name>ECONOMY</edis:Name>

</edis:CabinType> <edis:ClassOfService>

<edis:Code>I</edis:Code>

18-May-17


P a g e |

51


</edis:ClassOfService>



</edis:Details>

</edis:Flight> </edis:OriginDestination>

</edis:Query> <edis:DataList>

<edis:FareList> <edis:FareGroup refs="XQ_PAX_1">

<edis:Fare>

<edis:FareCode> <edis:Code>SUNECO</edis:Code>

</edis:FareCode> 

<edis:FareDetail>

 <edis:FareComponent refs="XQ_SEGREFS_1492924013603

XQ_FMD_1492924013601 XQ_FARECOMPREFS_1492924013605" ObjectKey="XQ_FC_1492924013602-646">

<edis:SegmentReference>XQ_SEG_1492924013615</edis:SegmentReference> <edis:PriceBreakdown>


</edis:Price> </edis:PriceBreakdown>



<edis:FareBasis> 

<edis:FareBasisCode> <edis:Code>AXDOM</edis:Code>

</edis:FareBasisCode>

</edis:FareBasis> </edis:FareComponent>

</edis:FareDetail> </edis:Fare>

<edis:FareBasisCode> <edis:Code>AXDOM</edis:Code>

</edis:FareBasisCode>

</edis:FareGroup> </edis:FareList>

</edis:DataList> <edis:Metadata>




<edis:Flight> 

<edis:FlightMetadatas>

 <edis:FlightMetadata MetadataKey="V1_MDK_12">

18-May-17


P a g e |

52



 <edis:AugPoint Key="XQ_SEGREFS_1492924013603">

<ibs:SegmentReferences>XQ_SEG_1492924013615</ibs:SegmentReferences>

</edis:AugPoint>

</edis:AugmentationPoint> </edis:FlightMetadata>

</edis:FlightMetadatas> </edis:Flight>




<edis:OfferMetadata MetadataKey="V1_MDK_13"> 

<edis:AugmentationPoint> 

<edis:AugPoint Key="XQ_FMD_1492924013601">

<ibs:FareDetailAugPoint> <FareType>ECONOMY</FareType>

<FareLevel>ST</FareLevel> </ibs:FareDetailAugPoint>

</edis:AugPoint>

<edis:AugPoint Key="XQ_FARECOMPREFS_1492924013605"> <ibs:FareComponentAugPoint>

<BaseFare Code="TRY">57.618643</BaseFare> <DisplayFare Code="EUR">18.92</DisplayFare>

<Discount Code="EUR">0.0</Discount> </ibs:FareComponentAugPoint>

</edis:AugPoint>

</edis:AugmentationPoint> </edis:OfferMetadata>


</edis:ShopMetadataGroup>

</edis:Shopping> <edis:Traveler>

<edis:TravelerMetadata MetadataKey="V1_MDK_13"> <edis:AugmentationPoint>

<edis:AugPoint Key="V1_TA_1"> <ibs:TravellerAugPoint>

<PnrType>NORMAL</PnrType>

</ibs:TravellerAugPoint> </edis:AugPoint>

</edis:AugmentationPoint> </edis:TravelerMetadata>

</edis:Traveler>

</edis:Metadata> </edis:ServicePriceRQ>

18-May-17


P a g e |

53


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


xmlns:edis="http://www.iata.org/IATA/EDIST">


<edis:SeatAvailabilityRQ EchoToken="6546" TimeStamp="2016-11-21T23:38:00" Target="Production" Version="33" TransactionIdentifier="3" SequenceNmbr="33"

TransactionStatusCode="Start" RetransmissionIndicator="true" CorrelationID="3"

AsynchronousAllowedInd="true"> <edis:PointOfSale>


<edis:CityCode>FRA</edis:CityCode> </edis:Location>

</edis:PointOfSale>

<edis:Document> <edis:Metadata/>


</edis:Document>




<edis:Recipient>


<edis:Name>SunExpress</edis:Name> </edis:ORA_Recipient>

</edis:Recipient>

</edis:Party> <edis:ShoppingResponseIDs>

<edis:Owner>XQ</edis:Owner> <edis:ResponseID>1F126AF1-7FCF-414F-8A3D-E4FFA408F747</edis:ResponseID>

</edis:ShoppingResponseIDs>


18-May-17


P a g e |

54


<edis:OriginDestinationReferences>XQ_OD_1492924013610</edis:OriginDestinationReferences>


<edis:DataList>

<edis:FlightSegmentList> <edis:FlightSegment SegmentKey="XQ_SEG_1492924013615">



</edis:Departure>

<edis:Arrival> <edis:AirportCode>AYT</edis:AirportCode>


</edis:Arrival>



<edis:Equipment>

<edis:AircraftCode>320</edis:AircraftCode> </edis:Equipment>

</edis:FlightSegment> </edis:FlightSegmentList>

<edis:OriginDestinationList> <edis:OriginDestination refs="XQ_SEG_1492924013615"

OriginDestinationKey="XQ_OD_1492924013610">

<edis:DepartureCode>ADA</edis:DepartureCode> <edis:ArrivalCode>AYT</edis:ArrivalCode>

<edis:FlightReferences>XQ_SEG_1492924013615</edis:FlightReferences> </edis:OriginDestination>

</edis:OriginDestinationList>

</edis:DataList> <edis:Metadata/>

</edis:SeatAvailabilityRQ> </soapenv:Body>

</soapenv:Envelope>

18-May-17


P a g e |

55


NDC Developer Portal &

Documentation

18-May-17


P a g e |

56


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:

http://xq.airgtwy.com:8181/sunexpress/ 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.

18-May-17


P a g e |

57


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

http://xq.airgtwy.com:8181/sunexpress/

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.

HKTHONUSR

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

userName iflyxmluser0

password v1KlFYrcfecw

Card Info Applicable for Payment:

Card Type VI

Card Number 4355084355084358

CVV Code 513

Hold Name ABDUL

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/O6ktEdxRnvLmPfpRtVzPhLXa9h71Bhkz5jmhXQVgp/cwGHN4s6+3dpn6Iur0zCC88Nin4gii4Etwg73Iao/HRlY6HYmKtRMf34jb49pvqA== SeriesCode: Myx8YAI5iQRv/k5BCGbW6w==%~~`%~~~~~~~%^**(%$#%R+juo+cfqt/VgPXxfTBmwzrzn6oIpQBE+Ybk0vPLEobF9TzA1MLY8f6xsuJFRB6UASy+QGfpnR4pbWNUtTK2/BSC5lmhKLGkrgjYHnu49MnTSMxsZAIh85n0N4ZuLw80McJ2eG/d124s4TESKm+TzolDIQrvsI5TrtcYT9/mu95hG9CBwlYthksDz9gi6sK23iHPHbLpH0g/foHLOG6iZInOBhKL865Ah5ehCm0jhE2WaLrh8MUcD6IlFqxTOeqLoUvCG4CbBiCMzCP9jLy6x2SeYOggau6iGkYuhMcdFfArM6nUfc71VRCHFerlUFJqgExS1a1IG7s5UHUvGa6Hhg==

18-May-17


P a g e |

58


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

18-May-17


P a g e |

59


Checklist before Order Creation The HTTP request is send to the right URL. The correct WSDL end-point is used.

http://xq.airgtwy.com:8181/sunexpress/

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.

18-May-17


P a g e |

60


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. http://xq.airgtwy.com:8181/sunexpress/

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.

18-May-17


P a g e |

61


18-May-17


P a g e |

62


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

BaggageAllowanceRQ AirShoppingRS

BaggageChargesRQ AirShoppingRS

ServicePriceRQ AirShoppingRS

ServiceListRS

SeatAvailabilityRS

SeatAvailabilityRQ AirShoppingRS

FlightPriceRQ AirShoppingRS

BaggageAllowanceRS SeatAvailabilityRS

ServiceListRS OrderCreateRQ AirShoppingRS

BaggageChargesRS

FlightPriceRS SeatAvailabilityRS

ServiceListRS

End of Document

p a g e | 0 sunexpress ibs ndc platform developer s...

Documents