Release 2023.21

Examples of messages with complete flows can be downloaded from here.

The response is the OrderViewRS

Error rendering macro 'excerpt-include' : User 'null' does not have permission to view the page 'NDCDOCStage:Copy of API Messages with Examples'.

Common Sections

HTTP Header

Error rendering macro 'excerpt-include' : User 'null' does not have permission to view the page 'NDCDOCStage:Copy of HTTP Header'.

Language, Version and Name Space

Error rendering macro 'excerpt-include' : User 'null' does not have permission to view the page 'NDCDOCStage:Copy of Language, Version and Name Space'.

Point of Sale

Error rendering macro 'excerpt-include' : User 'null' does not have permission to view the page 'NDCDOCStage:Copy of Point of Sale and Document'.

Document

Error rendering macro 'excerpt-include' : User 'null' does not have permission to view the page 'NDCDOCStage:Copy of Point of Sale and Document'.

Party

Error rendering macro 'excerpt-include' : User 'null' does not have permission to view the page 'NDCDOCStage:Copy of Party Elements'.

In addition to the Common Sections, this service is called with the following data:

Query

Query - Common

NAME	DESCRIPTION	FORMAT	ALLOWED/POSSIBLE VALUES
<Query> (Common)
OrderID	Order ID previously generated	Alphanumeric	Any

Query - AcceptRepricedOrder

NAME	DESCRIPTION	FORMAT	ALLOWED/POSSIBLE VALUES
<Query / AcceptRepricedOrder>
ResponseID	The ID of the response from which the new offer is being accepted and applied to the Order on hold	Alphanumeric	Any

Query - PassengerServicing

NAME	DESCRIPTION	FORMAT	ALLOWED/POSSIBLE VALUES
<Query / PassengerServicing> (Update contact info flows, name, e-mail, phone, frequent flyer info…)
New Attribute PassengerID	The unique identifier of the Passenger whose information is being updated.	Alphanumeric	The PassengerID obtained from the previous OrderViewRS having previously retrieved the Order.
New / ContactInfoRef	Contact info reference, which contact info (email & phone) filled in below will update original contact info.	Alphanumeric	Any
New / Individual / Given	Name of the passenger to change	Alphanumeric	Any
New / Individual / Surname	Surname of the passenger to change (Agency can specify separated by a special character "@" first and second surname → Ex: De la Morena@López)	Alphanumeric	Any
New / LoyaltyProgramAccount / Airline / AirlineDesignator	Airline ID associated to frequent flyer number	Alphanumeric	Any
New / LoyaltyProgramAccount / AccountNumber	Frequent Flyer or On Business number account	Alphanumeric	Any
New / ActionType	Action type Name correction flow Contact info (email & phone) correction flow Add/Update Frequent Flyer Number Add/Update On Business Number	Alphabetical	Add Remove
Previous Attribute PassengerID	Passenger ID, which info will be updated PassengerID attribute value can be indicated in PassengerID attribute from AirShopping request.	Alphanumeric Alphanumeric	Type of Passengers Value indicated in PassengerID attribute from AirShopping request
Previous / Individual / GivenName	Old passenger given name, not mandatory, but if informed and does not match, an error will be shown	Alphanumeric	Any
Previous / Individual / Surname	Old passenger surname, not mandatory, but if informed and does not match, an error will be shown	Alphanumeric	Any
Previous / ContactInfoRef	Old contact info reference	Alphanumeric	Any
Previous / ActionType	Action type	Alphabetical	Add Remove

Query - OrderServicing

NAME	DESCRIPTION	FORMAT	ALLOWED/POSSIBLE VALUES
<Query / OrderServicing> (Add ancillaries, delete paxes, partial refund and voluntary flight change flows…)
AcceptOffer / Offer Attribute OfferID	Identification of the service Offer SeatAvailability ResponseID / ServiceList ResponseID / New Offer Identification (Voluntary Change Flow) Add ancillaries flow Voluntary Change flow Delete Passengers flow Partial Refund flow	Alphanumeric	Any
AcceptOffer / Offer Attribute Owner	Airline identification Add ancillaries flow Voluntary Change flow Delete Passengers flow Partial Refund flow	Alphabetical	IB
AcceptOffer / Offer Attribute ResponseID	Response Identification Add ancillaries flow Voluntary Change flow Delete Passengers flow Partial Refund flow	Alphanumeric	Any
AcceptOffer / Offer / OfferItem Attribute OfferItemID	Offer item identification of the new service to add Add ancillaries flow Voluntary Change flow Delete Passengers flow Partial Refund flow	Alphanumeric	Any
AcceptOffer / Offer / OfferItem / PassengerRefs	Reference for the passengers Add ancillaries flow Voluntary Change flow Delete Passengers flow Partial Refund flow	Alphanumeric	Type of Passengers
AcceptOffer / Offer / OfferItem / SeatSelection / Row	Row for the seat Add ancillaries flow	Numeric	Any
AcceptOffer / Offer / OfferItem / SeatSelection / Column	Column for the seat Add ancillaries flow	Alphabetical	Any
Delete / OrderItemID	OrderItem identification to be deleted. When cancelling flights with Ancillaries or other associated services it is only necessary to include the OrderItemIDs of the flights, as all associated services will automatically be cancelled with the flights.	Alphanumeric	Any

Query - Payments

NAME	DESCRIPTION	FORMAT	ALLOWED/POSSIBLE VALUES
<Query / Payments / Payment> (Add ancillaries and voluntary flight change flows…)
Type	Payment Methods can vary depending on market and type of seller. Please check here.	Alphabetical	CA (Cash) CC (Credit Card) MS (Voucher) SF (Service Fee)
-- This refers to Cash payment method --
Method / Cash Attribute CashInd	Cash payment method.	Alphabetical	true
Amount Attribute Code	Total amount of the offer. Code refers to currency code for payment.	Numeric	Any
Payer / ContactInfoRefs	Reference for the payer info, that must be associated correctly in the XML below. In Cash Payment Method is OPTIONAL	Alphanumeric	Any valid reference associated in the XML below.
-- This refers to Credit Card method – If Secure Payment applies additional info needed is defined below in 3DS INFO --
Method / PaymentCard Attribute refs	NDC Mandatory for 3DS and/or installments payment. This is used to reference the associated 3DS info in PaymentCardSecureInfo ObjectKey, and/or the installment payment info in PaymentFormMetadata MetadataKey. If both 3DS and installment payments are being used for the same Order, then the two references are included here together separated by a space. Example: <PaymentCard refs="KEY_3DS KEY_QUOTAS">	Alphanumeric	Any
Method / PaymentCard / CardType	Type of credit card	Alphanumeric	1-6 characters
Method / PaymentCard / SeriesCode	Series Code of credit card	Numeric	1-8 characters
Method / PaymentCard / CardHolderName	Card Holder Name	Alphanumeric	0-50 characters
Method / PaymentCard / CardHolderBillingAddress / Street	Street of the billing address of the cardholder. NDC Mandatory that at least one field has to be filled in inside "CardHolderBillingAddress" tag.	Alphanumeric	If tag is indicated once, only first 40 characters will be considered If tag is indicated twice, only first 80 characters will be considered
Method / PaymentCard / CardHolderBillingAddress / CityName	City of the Billing Address of cardholder NDC Mandatory that at least one field has to be filled in inside "CardHolderBillingAddress" tag.	Alphanumeric	Only first 50 characters will be considered
Method / PaymentCard / CardHolderBillingAddress / StateProv	State Prov. of the Billing Address of cardholder NDC Mandatory that at least one field has to be filled in inside "CardHolderBillingAddress" tag.	Alphanumeric	1-40 characters
Method / PaymentCard / CardHolderBillingAddress / PostalCode	Postal Code of the Billing Address of cardholder NDC Mandatory that at least one field has to be filled in inside "CardHolderBillingAddress" tag.	Alphanumeric	2-10 characters
Method / PaymentCard / CardHolderBillingAddress / CountryCode	Country Code of the Billing Address of cardholder NDC Mandatory that at least one field has to be filled in inside "CardHolderBillingAddress" tag.	Alphabetical	2 characters
Method / PaymentCard / CardNumber	Number of credit card	Numeric	1-9 characters
Method / PaymentCard / EffectiveExpireDate / Expiration	Effective expiration date of the credit card	Numeric	4 characters
Amount Attribute Code	Total amount of the offer. Code refers to currency code for payment.	Numeric	Any
Payer / ContactInfoRefs	Reference for the payer info, that must be associated correctly in the XML below.	Alphanumeric	Any valid reference associated in the XML below.
-- This refers to Voucher payment method --
Method / Voucher	Voucher payment method.	Alphabetical	true
Method / Voucher / Number	Number of the voucher	Alphanumeric	any
Amount Attribute Code	Total amount of the offer. Code refers to currency code for payment.	Numeric	Any
Payer / ContactInfoRefs	Reference for the payer info, that must be associated correctly in the XML below.	Alphanumeric	Any valid reference associated in the XML below.
-- This refers to Service Fee method --
Method / Other / Remarks Attribute refs	References for all passengers of the order	Alphanumeric	any
Method / Other / Remarks / Remark	Service Fee payment method Mandatory for schema if "Remarks" tag is indicated	Alphabetical	ServiceFee
Amount Attribute Code	Total amount of the Service Fee Code refers to currency code for payment.	Numeric	Any

OrderChangeMetadata

NAME
DESCRIPTION
FORMAT
ALLOWED/POSSIBLE VALUES
<OrderChangeMetadata / Other / OtherMetadata / PaymentFormMetadatas> ↔ 3DS INFO (Add ancillaries and voluntary flight change flows…)
PaymentFormMetadata

Attribute
MetadataKey

For 3DS info, this key is mandatory and can be filled in with any value.
For installments payment info, this key have to match with installments reference in PaymentCard Refs.
Alphanumeric
Any
PaymentFormMetadta / Text
Installments payment info
Alphanumeric
installments/n
where n=number of installments.
Valid example: installments/3
PaymentFormMetadata / AugmentationPoint / AugPoint

Attribute
Owner
Airline code associated to 3DS Payment, in this case IB.
Alphabetical
IB
PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment

Attribute
xsi:schemaLocation
Reference to IATA 3DS new schema info xsd for Secure Payment.
Alphanumeric
3-D Secure Payment
PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment

Attribute
xmlns
Reference to IATA 3DS new schema info for Secure Payment.
Alphanumeric
3-D Secure Payment
PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment

Attribute
xmlns:xsi
Reference to IATA 3DS new schema info for Secure Payment.
Alphanumeric
3-D Secure Payment
PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo

Attribute
ObjectKey
This Attribute is used to reference the applicable PaymentCard in the Payments section of this message.
Alphanumeric
Any
PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentMethodCriteria / PaymentCardCriteria / SecurePayerAuthenticationVersion / CardEnrollmentVersionText
The version of 3D-Secure for which the card is enrolled.

Alphanumeric
This field must contain the specific 3DS version used for authentication:
1.0.2
2.1.0
2.2.0
PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentMethodCriteria / PaymentCardCriteria / SecurePayerAuthenticationVersion / SupportedVersionText
The version of 3D-Secure supported.

Alphanumeric
This field must contain the specific 3DS version used for authentication:
1.0.2
2.1.0
2.2.0
PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentProcessingDetails / PaymentMethod / PaymentCard / SecurePaymentVersion1 / PayerAuthenticationResponseText
Contains the information that conveys the result of the 3D Secure authentication transaction. Applicable for 3D Secure Version 1.x.x. This tag is NDC mandatory for version 1.x.x and if is not included, an error will be returned.
This field is the authentication response for the 3-D Secure transaction. It is used to determine whether or not the customer has been authenticated by the card issuer. It must be included in the final authorization request. Example: eJzVWFmzosgSfudXdPQ8Gt1sbkzYRhQ7KCjI/sYOsimgoL/+lp7Tp5c5t2d67tMw8yv/WqiluJXS8WyyVFEQT28qz
Alphanumeric
Any
PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentProcessingDetails / PaymentMethod / PaymentCard / SecurePaymentVersion2 / AuthenticationMerchantName
Contains all information for the result of 3D-Secure authentication process. Applicable for 3D Secure Version 2.x.x
This field is related to name of the merchant assigned by the Acquirer or Payment System.
Alphanumeric
Maximum → 40 characters
Any
PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentProcessingDetails / PaymentMethod / PaymentCard / SecurePaymentVersion2 / AuthenticationValue
Contains all information for the result of 3D-Secure authentication process. Applicable for 3D Secure Version 2.x.x
This field is related to 3DS authentication value returned. It is a cryptographic value generated by the ACS to provide a way, during authorisation processing, for the authorisation system to validate the integrity of the authentication result. The AV algorithm is defined by each Payment System.
Alphanumeric
Maximum → 28 characters
Any
PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentProcessingDetails / PaymentMethod / PaymentCard / SecurePaymentVersion2 / DirectoryServerTrxID
Contains all information for the result of 3D-Secure authentication process. Applicable for 3D Secure Version 2.x.x
This field is related to DS (Directory Server) transaction ID returned. Universally unique transaction identifier assigned by the Directory Server (DS) to identify a single transaction.
Alphanumeric
Maximum → 36 characters
Any
PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentProcessingDetails / PaymentMethod / PaymentCard / SecurePaymentVersion2 / ElectronicCommerceInd
Contains all information for the result of 3D-Secure authentication process. Applicable for 3D Secure Version 2.x.x
This field is related to 3DS ECI (electronic commerce indicator). Payment System-specific value provided by the ACS or DS to indicate the results of the attempt to authenticate the Cardholder.
This tag is NDC mandatory for version 2.x.x and if is not included, an error will be returned.
Some ECI values and the meaning of this is the following:
01 → Authentication could not be completed but a proof of authentication attempt was provided SLI = 1 → MasterCard
02 → Cardholder was successfully authenticated (SLI = 2) → MasterCard
05 → This value means that the cardholder was authenticated by the issuer by verifying the cardholder’s password or identity information. The value is returned by the ACS in the Payer Authentication Response message when the cardholder successfully passed 3-D Secure payment authentication → Visa
06 → This value means that the merchant attempted to authenticate the cardholder, but either the cardholder or issuer was not participating. The value should be returned by the ACS in the Authentication Response message for an Attempt Response. Additionally, merchants may use an ECI 6 in the authorization request when a Verify Enrollment of N is received from the Visa Directory Server → Visa
07 → This value is set by the merchant when the payment transaction was conducted over a secure channel (for example, SSL/TLS), but payment authentication was not performed, or when the issuer responded that authentication could not be performed. An ECI 7 applies when either the Verify Enrollment or the Payer Authentication Response contains a U for Unable to Authenticate → Visa
Numeric
Two characters
Any
PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentProcessingDetails / PaymentMethod / PaymentCard / SecurePaymentVersion2 / ProgramProtocolText
Contains all information for the result of 3D-Secure authentication process. Applicable for 3D Secure Version 2.x.x
This field is related to Program Protocol.
Alphanumeric
Any
PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentProcessingDetails / PaymentMethod / PaymentCard / SecurePaymentVersion2 / TrxStatusReasonText
Contains all information for the result of 3D-Secure authentication process. Applicable for 3D Secure Version 2.x.x
This field provides information on why the Transaction Status field has the specified value
Alphanumeric
Two characters
Any
PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentProcessingDetails / PaymentMethod / PaymentCard / SecurePaymentVersion2 / TrxStatusText
Contains all information for the result of 3D-Secure authentication process. Applicable for 3D Secure Version 2.x.x
This field indicates whether a transaction qualifies as an authenticated transaction or account verification.
Alphabetic
One character
Any
PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentProcessingDetails / PaymentMethod / PaymentCard / SecureProgram / EnrollmentStatusText
Contains all information for the result of 3D-Secure authentication process. Applicable for 3DS.
3D Secure Program Enrollment Status. Examples → CardNotEnrolled, CardEnrolled, CardMayBeEnrolled, Unknown
Alphabetical
Any
PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentProcessingDetails / PaymentMethod / PaymentCard / SecureProgram / SecurePaymentProgramName
Contains all information for the result of 3D-Secure authentication process. Applicable for 3DS.
Name of the secure payment program. Example → Verified by Visa.
Alphanumeric
Any
PaymentFormMetadata / AugmentationPoint / AugPoint / Backport_IberiaSecurePayment / PaymentCardSecureInfo / PaymentFunctions / PaymentProcessingDetails / PaymentMethod / PaymentCard / SellerOwnCardInd
Contains all information for the result of 3D-Secure authentication process. Applicable for 3DS.
When TRUE, indicates the seller is using their own card. If FALSE, customer card is being used.
Boolean

true/false

DataLists - PassengerList

Error rendering macro 'excerpt-include' : User 'null' does not have permission to view the page 'NDCDOCStage:Copy of PassengerList'.

DataLists - ContactList

Error rendering macro 'excerpt-include' : User 'null' does not have permission to view the page 'NDCDOCStage:Copy of ContactList'.

DataLists - FlightSegmentList

Error rendering macro 'excerpt-include' : User 'null' does not have permission to view the page 'NDCDOCStage:Copy of FlightSegmentList'.

DataLists - InstructionsList

Error rendering macro 'excerpt-include' : User 'null' does not have permission to view the page 'NDCDOCStage:Copy of InstructionsList'.

Example OrderChangeRQ:

XML Sample

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.iata.org/IATA/EDIST/2017.2">
	<soapenv:Header/>
	<soapenv:Body>
		<OrderChangeRQ Version="5.000" PrimaryLangID="es" xmlns="http://www.iata.org/IATA/EDIST/2017.2">
			<PointOfSale>
				<Location>
					<CountryCode>ES</CountryCode>
				</Location>
			</PointOfSale>
			<Document>
				<ReferenceVersion>5.000</ReferenceVersion>
			</Document>
			<Party>
				<Sender>
					<TravelAgencySender>
						<IATA_Number>78288254</IATA_Number>
						<AgencyID>firstAgency</AgencyID>
					</TravelAgencySender>
				</Sender>
				<Participants>
					<Participant>
						<AggregatorParticipant SequenceNumber="1">
							<AggregatorID>00000022</AggregatorID>
						</AggregatorParticipant>
					</Participant>
				</Participants>
			</Party>
			<Query>
				<OrderID>IB5908506ad86443e48f241f318a18bb26OC</OrderID>
				<PassengerServicing>
					<New PassengerID="ADULT_02">
						<ActionType>Add</ActionType>
					</New>
				</PassengerServicing>
			</Query>
			<DataLists>
				<PassengerList>
					<Passenger PassengerID="ADULT_01">
						<PTC>ADT</PTC>
						<Birthdate>1965-12-20</Birthdate>
						<Individual IndividualID="IND_ADULT_01">
							<Gender>Male</Gender>
							<NameTitle>MR</NameTitle>
							<GivenName>JANE</GivenName>
							<Surname>SMITH</Surname>
						</Individual>
						<FOID>
							<FOID_Number>30000529L</FOID_Number>
							<FOID_Type>NI</FOID_Type>
						</FOID>
						<ContactInfoRef>ADULT_01_CONTACT</ContactInfoRef>
					</Passenger>
					<Passenger PassengerID="ADULT_02">
						<PTC>ADT</PTC>
						<Birthdate>1955-04-01</Birthdate>
						<Individual IndividualID="IND_ADULT_02">
							<Gender>Female</Gender>
							<NameTitle>MRS</NameTitle>
							<GivenName>BAMBI</GivenName>
							<Surname>DISNEY RESERVAS</Surname>
						</Individual>
						<FOID>
							<FOID_Number>47226285V</FOID_Number>
							<FOID_Type>NI</FOID_Type>
						</FOID>
						<ContactInfoRef>ADULT_01_CONTACT</ContactInfoRef>
					</Passenger>
				</PassengerList>
				<ContactList>
					<ContactInformation ContactID="ADULT_01_CONTACT">
						<ContactType/>
						<ContactProvided>
							<EmailAddress>
								<EmailAddressValue>iteggo.cavalos@iberia.es</EmailAddressValue>
							</EmailAddress>
						</ContactProvided>
						<ContactProvided>
							<Phone>
								<Label>Passenger</Label>
								<PhoneNumber>+34666554433</PhoneNumber>
							</Phone>
							<Phone>
								<Label>Emergency</Label>
								<PhoneNumber>34666554433</PhoneNumber>
							</Phone>
						</ContactProvided>
						<Individual>
							<GivenName>CONTACTO</GivenName>
							<Surname>EMERGENCIA</Surname>
						</Individual>
					</ContactInformation>
					<ContactInformation ContactID="Payer">
						<ContactType>Payer</ContactType>
						<ContactProvided>
							<EmailAddress>
								<EmailAddressValue>accept@accept.com</EmailAddressValue>
							</EmailAddress>
						</ContactProvided>
						<ContactProvided>
							<Phone>
								<PhoneNumber>1273211111</PhoneNumber>
							</Phone>
						</ContactProvided>
						<IndividualRef>IND_ADULT_01</IndividualRef>
					</ContactInformation>
				</ContactList>
				<FlightSegmentList>
					<FlightSegment SegmentKey="IB042320240527">
						<Departure>
							<AirportCode>BIO</AirportCode>
							<Date>2024-05-27</Date>
							<Time>09:15</Time>
							<AirportName>Bilbao</AirportName>
						</Departure>
						<Arrival>
							<AirportCode>MAD</AirportCode>
							<Date>2024-05-27</Date>
							<Time>10:25</Time>
							<ChangeOfDay>0</ChangeOfDay>
							<AirportName>Madrid Adolfo Suarez-Barajas</AirportName>
							<Terminal>
								<Name>4</Name>
							</Terminal>
						</Arrival>
						<MarketingCarrier>
							<AirlineID>IB</AirlineID>
							<Name>Iberia</Name>
							<FlightNumber>0423</FlightNumber>
						</MarketingCarrier>
						<OperatingCarrier>
							<AirlineID>IB</AirlineID>
							<Name>Iberia</Name>
							<FlightNumber>0423</FlightNumber>
							<Disclosures>
								<Description>
									<Text>IB</Text>
								</Description>
							</Disclosures>
						</OperatingCarrier>
						<Equipment>
							<AircraftCode>32A</AircraftCode>
							<Name>Airbus A320 (Sharklets)</Name>
						</Equipment>
						<FlightDetail>
							<FlightDuration>
								<Value>PT1H10M</Value>
							</FlightDuration>
						</FlightDetail>
					</FlightSegment>
					<FlightSegment SegmentKey="IB380420240527">
						<Departure>
							<AirportCode>MAD</AirportCode>
							<Date>2024-05-27</Date>
							<Time>15:40</Time>
							<AirportName>Madrid Adolfo Suarez-Barajas</AirportName>
							<Terminal>
								<Name>4</Name>
							</Terminal>
						</Departure>
						<Arrival>
							<AirportCode>IBZ</AirportCode>
							<Date>2024-05-27</Date>
							<Time>16:55</Time>
							<ChangeOfDay>0</ChangeOfDay>
							<AirportName>Ibiza</AirportName>
						</Arrival>
						<MarketingCarrier>
							<AirlineID>IB</AirlineID>
							<Name>Iberia</Name>
							<FlightNumber>3804</FlightNumber>
						</MarketingCarrier>
						<OperatingCarrier>
							<AirlineID>I2</AirlineID>
							<Name>Iberia Express</Name>
							<Disclosures>
								<Description>
									<Text>I2</Text>
								</Description>
							</Disclosures>
						</OperatingCarrier>
						<Equipment>
							<AircraftCode>32Q</AircraftCode>
							<Name>Airbus A321neo</Name>
						</Equipment>
						<FlightDetail>
							<FlightDuration>
								<Value>PT1H15M</Value>
							</FlightDuration>
						</FlightDetail>
					</FlightSegment>
				</FlightSegmentList>
				<InstructionsList>
					<Instruction ListKey="Instruction_1">
						<FreeFormTextInstruction refs="ADULT_02 IB042320240527 IB380420240527">
							<Remark>BAGGAGE/SP/0DD</Remark>
						</FreeFormTextInstruction>
					</Instruction>
				</InstructionsList>
			</DataLists>
		</OrderChangeRQ>
	</soapenv:Body>
</soapenv:Envelope>

Response Body

Order View RS v17 v2 (Branded Fares)

Error messages

For further information about all kind of error messages, please go to the following link:

Error Codes