OrderChangeNotif

Order Change Notifications provide IBS with the ability to send messages to inform Travel Agents/Service Providers in an unsolicited manner of involuntary changes to Orders, for instance, schedule changes. IBS will send the OrderChangeNotif message to Travel Agents/Service Providers who have subscribed to receive these messages. The OrderChangeNotif message will be sent for disruption events (both planned and operation events).

Currently, IBS will send the OrderChangeNotif message for the following disruption events:

2) Flight Change

3) Cancel and Rebook

4) Add/Delete Flight

Depending on the type of disruption IBS may or may not have rebooked the disrupted flight on to an alternative flight.

Action types are also used in the OrderChangeNotif message to identify which Order Items have been removed from the Order (Action Type “Cancel”) and which have been added to the Order (Action Type “Create”).

The messages published contain the following details:

· Booking reference (PNR)

· Passenger details

· Disrupted flight segment details

· New (rebooked) flight segment details

· E-ticket details with passenger association

· IBS will send OrderChangeNotif message to Travel Agents/Service Providers who have subscribed to receive messages for disruption events, and they will only receive messages about bookings they created, and only for those bookings that were created through their channels.

· The OrderChangeNotif message will be sent to the endpoints exposed by the Travel Agent/Service Provider.

In order to register your interest in receiving OrderChangeNotif messages, please contact IBS and provide the following information about your endpoint:

· Which endpoint you wish to receive the OrderChangeNotif messages on. Currently, only SOAP URLs are supported. The URL has to start with “https://” so that the communication channel is secure.

· Confirmation that the SOAP endpoint accepts messages with Content-Type application/soap+xml.

· Confirmation that the endpoint supports TLS 1.2.

· Basic Auth credentials (username and password) that IBS should use to authenticate with the endpoint.

· Confirmation that the endpoint is protected by a form of authentication. Currently, only Basic Auth is supported.

· SOAPAction that IBS should use when calling the endpoint.

· Which IATA NDC version you wish to receive OrderChangeNotif messages in. Currently, only 17.2 is supported.

· Which type of Order Change events you wish to receive OrderChangeNotif messages for. Currently, only time change within threshold notifications are supported.

· Confirmation of the expected average and maximum response time of the endpoint. The endpoint should respond in a timely manner. Anything longer than 30 seconds will be considered to have timed out.

· All of the above for both Test and Live environments.