SunExpress

Available Currencies

Value	Description
AED	UAE Dirham
CHF	Swiss Franc
DKK	Danish Krone
EUR	Euro
GBP	Great Britain Pound
NOK	Norwegian Krone
RUB	Russian Ruble
SEK	Swedish Krone
TRY	Turkish Lira
USD	United States Dollar

Available Tariffs

The following tariffs are open to public use:

• SunLight

• SunEco

• SunValue

• SunClassic

• SunEcoPlus

• SunPremium

• SunComfort

Whenever no tariff is explicitly provided in the request, offers of the following tariffs will be returned by default:

• SunLight

• SunEco

• SunValue

• SunClassic

• SunEcoPlus

• SunPremium

• SunComfort

Supported salutations

The current implementation allows the following salutations:

• MISS

• MR

• MRS

• MS

• MSTR

• MX

Supported Forms of Payment

The current implementation allows the following forms of payment:

• Credit Card

• SEPA

• Cash Payment

B2B Interface URL

Test-Environment: https://xq-uat.aircenter7.com

Production-Environment: https://agency.sunexpress.com

Supported Sender Types

To correctly identify the Sender, there are several possible ways in the NDC Standard, but the following types are supported:

• EnabledSystem

• Corporation

• TravelAgency

The most samples in this documentation are listed with the type “EnabledSystem”, which is used by a single Agent. This agent has all of it’s details stored within his user details as soon as he receives an account for the NDC interface. The type “Corporation” mainly works the same way, but has the possibility to add some minor differentiation using a special CorporateID:

Corporation

<Corporation>
        <CorporateCodeText>{{CODE}}</CorporateCodeText>
        <CorporateID>{{ID}}</CorporateID>
</Corporation>

For some users it is necessary to store even more Agency details, e.g. a single User that is responsible for several agencies. For these users the type “TravelAgency” has been introduced:

TravelAgency

<TravelAgency>
        <AgencyID>{{ID}}</AgencyID>
        <Name>{{NAME}}</Name>
        <TravelAgent>
            <TravelAgentID>{{ID}}</TravelAgentID>
        </TravelAgent>
</TravelAgency>

For further Information on how (and with what) to fill these values, please contact your support at the airline.

National id handling

If national id wants to be added for pax, CitizenshipCountryCode and IdentityDoc information should be present inside the Pax.

Pax data with national id

<Pax>
        <CitizenshipCountryCode>TR</CitizenshipCountryCode>
        <IdentityDoc>
                <Birthdate>2004-01-17</Birthdate>
                <CitizenshipCountryCode>TR</CitizenshipCountryCode>
                <GivenName>AAA</GivenName>
                <IdentityDocID>10000000146</IdentityDocID>
                <IdentityDocTypeCode>709</IdentityDocTypeCode>
                <Surname>LASTNAME</Surname>
        </IdentityDoc>
        <Individual>
                <Birthdate>2004-01-17</Birthdate>
                <GenderCode>M</GenderCode>
                <GivenName>AAA</GivenName>
                <IndividualID>IN1</IndividualID>
                <Surname>LASTNAME</Surname>
                <TitleName>MR</TitleName>
        </Individual>
        <PaxID>PX1</PaxID>
        <PTC>ADT</PTC>
</Pax>

Confirmation shipping logic

If a booking confirmation is to be sent to a specified email address, the parameter “sendItineraryTo” must be specified in the ContactInfoList. If the parameter is not set, no confirmation will be sent from the airline system.

Contact data with parameter

<ContactInfoList>
        <ContactInfo>
           <ContactInfoID>C1</ContactInfoID>
           <ContactPurposeText>Primary</ContactPurposeText>
           <EmailAddress>
                  <ContactTypeText>sendItineraryTo</ContactTypeText>
                  <EmailAddressText>email@domain.com</EmailAddressText>
           </EmailAddress>
           <Individual>
                  <GivenName>JOHN</GivenName>
                  <IndividualID>IN2</IndividualID>
                  <Surname>DOE</Surname>
                  <TitleName>MR</TitleName>
           </Individual>
           <Phone>
                  <PhoneNumber>(+49)12312312</PhoneNumber>
           </Phone>
           <PostalAddress>
                  <CityName>CITY</CityName>
                  <CountryCode>DE</CountryCode>
                  <PostalCode>12345</PostalCode>
                  <StreetText>STREET 1</StreetText>
           </PostalAddress>
        </ContactInfo>
</ContactInfoList>

Contact data without parameter

<ContactInfoList>
        <ContactInfo>
           <ContactInfoID>C1</ContactInfoID>
           <ContactPurposeText>Primary</ContactPurposeText>
           <EmailAddress>
                  <EmailAddressText>email@domain.com</EmailAddressText>
           </EmailAddress>
           <Individual>
                  <GivenName>JOHN</GivenName>
                  <IndividualID>IN2</IndividualID>
                  <Surname>DOE</Surname>
                  <TitleName>MR</TitleName>
           </Individual>
           <Phone>
                  <PhoneNumber>(+49)12312312</PhoneNumber>
           </Phone>
           <PostalAddress>
                  <CityName>CITY</CityName>
                  <CountryCode>DE</CountryCode>
                  <PostalCode>12345</PostalCode>
                  <StreetText>STREET 1</StreetText>
           </PostalAddress>
        </ContactInfo>
</ContactInfoList>

If a booking confirmation is to be send AND the language of the booking confirmation should also be defined (and not be taken from the user management profile), the entity “PayloadAttributes” including the attribute “AltLangID” must be specified as well in the OrderCreate request after the “Party” information. Currently the SunExpress systems supports the following languages: DE, TR, EN, FR, IT

Request sample including language designator

<IATA_OrderCreateRQ xmlns="http://www.iata.org/IATA/2015/00/2019.2/IATA_OrderCreateRQ">
        <Party>
                <Sender>
                        <EnabledSystem>
                                <SystemID>PRIBAS</SystemID>
                        </EnabledSystem>
                </Sender>
        </Party>
        <PayloadAttributes>
                <AltLangID>TR</AltLangID>
                <PrimaryLangID>DE</PrimaryLangID>
        </PayloadAttributes>
        <POS>
                <AgentDutyText>2</AgentDutyText>
        </POS>