.. _SunExpress:

**********
SunExpress
**********

.. toctree::
   :maxdepth: 1
   :caption: Contents:
   :hidden:
   :titlesonly:

.. raw:: html

 <h3>Operation Restrictions</h3>

IATA_OrderListRQ should not be used by any NDC TO partner of XQ.

.. raw:: html

 <h3>Available Currencies</h3>

+-------+-----------------------+
| 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  |
+-------+-----------------------+

.. raw:: html

 <h3>Available Tariffs</h3>

The following tariffs are open to public use:

- SunLight
- SunEco
- SunClassic
- SunPremium

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

- SunEco

.. raw:: html

 <h3>Supported salutations</h3>

The current implementation allows the following salutations:

- MISS
- MR
- MRS
- MS
- MSTR
- MX

.. raw:: html

 <h3>Supported Forms of Payment</h3>

The current implementation allows the following forms of payment:

- Credit Card
- Cash Payment

.. raw:: html

 <h3>B2B Interface URL</h3>

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

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

.. raw:: html

 <h3>Supported Sender Types</h3>

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:

.. toggle-Header::
    :header: **Corporation**

       .. code-block:: xml

            <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:

.. toggle-Header::
    :header: **TravelAgency**

        .. code-block:: xml

            <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.

.. raw:: html

 <h3>Confirmation shipping logic</h3>

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.

.. toggle-Header::
	:header: **Contact data with parameter**
	
		.. code-block:: xml
		
			<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>
			
|

.. toggle-Header::
	:header: **Contact data without parameter**
		
		.. code-block:: xml

			<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

.. toggle-Header::
	:header: **Request sample including language designator**
	
		.. code-block:: xml
		
			<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>
				
|