Change Held Booking




 OrderChange - Change Held Booking Overview


VersionReason for ChangeRelease StatusPre-Live DateLive Date
0.117.2 Servicing - Change Held Booking  

 Introduction

The OrderChange-Servicing Held Booking Webservice provides IATA Accredited Travel Agents etc, new retailers and Service Providers the ability to change a held booking and pay/hold as per IATA NDC schema standards.

The service accepts payment (card or cash aka BSP settlement) and issues eTickets.

 OrderChange - Change Held Booking Webservice

This service is used to confirm the change in date and time of one or more (six at maximum) origin and destination changes to an existing held booking. With this service, agent can pay for the tickets and confirm held booking changes or confirm the changes and hold it for future.
The service accepts the payment and issues eTickets for all passengers in the held booking. Once the eTickets are successfully issued the service returns eTicket details in the response.

Interface Design

This web service is called with the following inputs:

  1. OrderID (Booking reference or PNR reference)
  2. ResponseID/OfferID/OfferItemID returned in the preceding OrderReshopRS(Reprice)
  3. OrderItemID that is going to change.
  4. Payment details (Card or Cash) in case of purchase (To hold the booking further, user don’t need to provide the payment details)
  5. Passenger details
  6. Contact Information

The output data this service returns include:

  1. Booking reference (PNR)
  2. Total Order Price – This is the sum of fare and tax for all passengers in the booking for all passengers in the booking.
  3. Payment Details in case of purchase 
  4. Price details (Total amount, Base amount tax breakdown) for each passenger.
  5. Ticket document information (eTicket details) in case of purcahse 
  6. Passenger details
  7. Contact List
  8. Flight segment details.
  9. Flight list along with associated flight segment references.
  10. Origin and destination list.
  11. Media List
  12. Penalty List

 Mandatory Headers

If you have PRE-LIVE access for 16.1, then you will automatically be able to build to 17.2 using the PRE-LIVE environment.

In order to access our API, you will need to pass the following two headers for each call.

 Web Service URLs


 General Usage Guidelines

The OrderChange - Change Held Booking Service

General

Non-IATA Agents