OrderChangeNotification 17.2
- Timothy Ling
- Alvaro Chaparro
- Valentina Maio
Functional Description
Iberia is happy to be able to offer the OCN (OrderChangeNotification) functionality.
This allows users of Iberia’s NDC API to receive notifications when a Service in an Order undergoes an involuntary change.
The following are the disruptions we will be notifying:
Order cancellation due to PaymentTimeLimit expiry.
Flight Time Change
Change of Flight
Cancelation of Flight
Change of Seat Assignment
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 2.0” security methods to connect to third parties.
In order to initiate the certification process a support ticket needs to be opened in our Support Portal, and the following information must be included in the request:
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 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:
Sent in the header (recommended by RFC 6749: The OAuth 2.0 Authorization Framework ) or
Sent in the body of the message
An example using CURL of your authentication service, and OCN reception service.
Example 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:
Remark | ActionType | ActionType Context* | Explanation |
|---|---|---|---|
PaymentTimeLimit Expired | Delete | 104 | The Order has been cancelled as the PaymentTimeLimit has expired and the Order has not been paid for. |
Flight number change | Update | 1 | The Flight Number has been changed. This means the passenger has been reallocated onto a different flight, and may also mean that the time of departure has changed. |
Flight retimed | Update | 2 | The departure and/or arrival time of the flight has changed. |
Flight cancelled | Cancel | 3 | The flight they had booked has been cancelled and an alternative could not been provided. |
Seat change | Update | 101 | The pre-assigned seat has been changed. This could be due to a change of flight, change of equipment or a change of cabin configuration. |
*The context code is as per the IATA Padis Code-set REA, except in the case of PaymentTimeLimit expiration.
Acknowledgement
The Seller or Aggregator receiving the OCN message responds with an Acknowledgment message.
<Acknowledgement xmlns="http://www.iata.org/IATA/EDIST/2017.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" Version="5.000" xsi:schemaLocation="http://www.iata.org/IATA/EDIST/2017.2 Acknowledgement.xsd">
<Document/>
<StatusCode>OK</StatusCode>
</Acknowledgement>
