The OrderChange API provides the capability for sellers to confirm the change of date/time of an existing itinerary for a given ticketed Booking Reference/PNR with or without payment. The API will amend the Itinerary and reissue tickets.
OrderChange API provides the capability for sellers to confirm an unticketed order (hold booking) for both Online and Offline sellers. Furthermore, it will provide the capability to add Date of birth and Gender information for the passenger (for hold booking confirmation).
OrderChange API provides the capability to reserve both free and paid seat(s) post order creation.
NDC Schema: OrderChange RQ & OrderChange RS v 21.3
This is a complete replica of production and a test environment where developers can build against our NDC APIs and validate their code for build of new features, ahead of certification and go-live. This environment should also be used for debugging
This environment will have the same capability features as Sandbox but in addition we may deploy breaking changes or new features in advance of release to Sandbox and Production in order to give developers early visibility.
Supported Passenger Type Codes (PTC) are following:
ID <-> RefID attribute request/response formats are shown as follows:
Tickets will be reissued in the same currency in which the original ticket was issued.
The requested OfferID must be from the previous Order Reshop response (in response to OrderQuote) otherwise an error will be returned. The OfferID[s] is valid for 20 minutes, within the time-limit OrderChange request must be triggered otherwise the offer will be deleted from the system and an error will be returned upon requesting this offer.
One or more OfferItem(s) are included in a Priced Offer and each OfferItem is unique with detailed fare and tax breakdown per PTC.
The service checks if the agent calling the service has the rights. If the agent does not have such authority, then the service will not process and will return an error. A booking can only be retrieved and serviced by the same agent that created the booking.
For US & CA countries – Address information is validated (Street, City, Zip-code, State). If given Address is Invalid – Error code: 317 & 708 is returned.
Supported Payment Card Types
Before proceeding for payment authorization, we will be validating received ECI values and authentication status.
Seat assignment will fail if:
Warning returned for: