...

...

Table of Contents
minLevel 1 maxLevel 7

Introduction

Functional Description

Iberia is happy to be able to offer the OCN (OrderChangeNotification) functionality.

...

To learn more about which elements are sent to us in the OrderCreate, please visit the Involuntary Changes section in our Order Contacts & Communications page.

Registration

To receive the OCN messages you need to open a support ticket through our Support Portal providing us with certain information. To use this service you must also undergo a certification process with a series of tests, which will be advised when registering for the service.

For Iberia to send you the OCN messages, you must publish an endpoint, with the necessary security, to which we can send the messages. Presently Iberia has implemented the “Basic AUTH” and “OAUTH” “OAUTH 2.0” security methods to connect to third parties.

...

• An HTTPS URL for a SOAP or REST endpoint, to which we can send the OCN messages.

  • Please ensure you tell us which protocol the endpoint uses.

• The security method used to connect to your endpoint together with the credentials. We support two security methods: BASIC and OAUTH 2.0.

  • For Basic authentication we need to be able to send the credentials in the “Authorization” header, with the values separated with “:” in Base64 format.

  • For OAUTH 2.0 authentication we require the following:

    • The

    client_id, client_secret and grant_type. (Today we only use the OAUTH implementation where the parameters are sent in the body of the message.)The

    • HTTPS URL from where to obtain the token.

      • Whether you require the “scope” in the call to this URL, and if so then the value you require in the “scope”

    • The client_id, client_secret and grant_type. We support the two ways of sending the credentials in OAUTH 2.0 to obtain the token:

      1. Sent in the header (recommended by https://datatracker.ietf.org/doc/html/rfc6749#section-2.3.1 ) or

      2. Sent in the body of the message

• An example using CURL of your authentication service, and OCN reception service.

Example OAUTH of a BASIC request to send the OCN:

curl --location --request POST 'https://miurl.com/v1/booking/travel-orders/ib-order-change-events' \
--header 'Content-Type: application/xml' \
--header 'Authorization: Bearer xxxxxxxxxxxxxxxxxx' \

Types of Change

The type of change impacting the Order is indicated in the ActionType Context and also reflected in the Remarks. The following are the values returned:

...

*The context code is as per the IATA Padis Code-set REA, except in the case of PaymentTimeLimit expiration.

Example

The following is an example of an OCN message* generated by Iberia:

<OrderChangeNotif Version="5.000" xmlns="http://www.iata.org/IATA/EDIST/2017.2">
	<Document>
		<ReferenceVersion>5.000</ReferenceVersion>
	</Document>
	<Party>
		<Sender>
			<!--Offer Responsible Airline-->
			<ORA_Sender>
				<AirlineID>IB</AirlineID>
				<Name>Iberia</Name>
			</ORA_Sender>
		</Sender>
		<Participants>
			<Participant>
				<AggregatorParticipant SequenceNumber="1">
					<Name>AggregatorName</Name>
					<AggregatorID>00000000</AggregatorID>
				</AggregatorParticipant>
			</Participant>
		</Participants>
		<Recipient>
			<TravelAgencyRecipient>
				<Name>TravelAgencyName</Name>
				<IATA_Number>XXXXXXXX</IATA_Number>
				<AgencyID>77777777</AgencyID>
			</TravelAgencyRecipient>
		</Recipient>
	</Party>
	<Query>
		<Order OrderID="IB6dff0c0b748b48b29fe00d3d4711debdOP" Owner="IB">
			<BookingReferences>
				<BookingReference>
					<ID>A1B2C</ID>
					<AirlineID>IB</AirlineID>
				</BookingReference>
			</BookingReferences>
		</Order>
		<Amendments>
			<Amendment>
				<ActionType Context="1">Update</ActionType>
				<Remarks>
					<Remark>Flight Number Change</Remark>
				</Remarks>
			</Amendment>
		</Amendments>
	</Query>
</OrderChangeNotif>

*The IATA 17.2 schema makes the OrderItems obligatory, however we do not include them.

Acknowledgement

The Seller or Aggregator receiving the OCN message responds with an Acknowledgment message.

...