The OrderReshop API provides the capability for sellers to shop for a change of date/time for an existing itinerary for a given ticketed Booking Reference/PNR. It returns a set of reshop offers. The change may result in no addition collection amount to be paid (Even Exchange) or may incur an additional collection amount to be paid (Uneven Exchange).
NDC Schema: IATA OrderReshop RQ & 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:
Multiple Cabin codes can be requested (warning(s) returned for unknown codes). In the response, Brand names will be returned for the Itinerary
ID <-> RefID attribute request/response formats are shown as follows:
Currency is returned based on the currency in which the ticket was issued.
An Offer differs from another Offer(s) with its price or/ and combinations of flights. Uniquely generated OfferID is returned, with a validity of 20 minutes.
One or more OfferItem(s) are included in an Offer and each OfferItem is unique. OfferItem is per PTC (with Variation of Price, taxes)
The fare product for the unchanged segments (O&D) could change depends on the fare being offered for the segments (O&D) being changed. Example: outbound in Economy Classic and inbound in Economy Classic Flex.
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.