Order Servicing API Flows

For any use cases for your integration with our APIs, you will need to trigger them in sequence as detailed below. Each API should be called in turn passing details taken from the previous call into the next API call, details can be found on the individual API details pages.

Seat Addition to an existing Order.
Ancillary/Baggage Addition to an existing Order.
Change Flight / Add a Flight to an existing Order.
Cancellation of existing Order.

Note : Currently we are supporting Order servicing only in NDC Long Sell

The below flow represents the Order of API triggers to add a seat to the existing order.

OrderRetrieve SeatAvailability OrderReshop OrderChange

Flow architecture for the Seat Addition to an existing Order (Click on the image to enlarge)

Flow architecture for the Seat Addition to an existing Order (Click on the image to enlarge)

The below flow represents the Order of API triggers to add ancillaries to the existing order.

OrderRetrieve ServiceList OrderReshop OrderChange

Flow architecture for the Ancillaries Addition to an existing Order (Click on the image to enlarge)

Flow architecture for the Ancillaries Addition to an existing Order (Click on the image to enlarge)

The below flow represents the Order of API triggers to add / change flight in existing order.

OrderRetrieve OrderReshop OrderReshop OrderChange

Flow architecture for the Change / Add a Flight to an existing Order (Click on the image to enlarge)

Flow architecture for the Change / Add a Flight to an existing Order (Click on the image to enlarge)

The below flow represents the Order of API triggers to Cancellation of existing order.

OrderRetrieve OrderReshop OrderCancel

Flow architecture for the Cancellation of an existing Order (Click on the image to enlarge)

Flow architecture for the Cancellation of an existing Order (Click on the image to enlarge)